Dear SaaStr: What Types of Customers Should be Avoided and How Do I Recognize Them?
You will get lots of advice on “bad customers”, “firing customers”, and the like. For the most part, in SaaS, I don’t agree.
The “Bad Customer” Myth: Why Your Most Demanding B2B Customers Are Actually Your Best Teachers
The B2B echo chamber loves to preach about “firing bad customers.” You’ll hear it at every conference, in every Slack community, on every podcast. The conventional wisdom goes something like this: cut the tire-kickers, dump the demanding accounts, focus only on your “ideal customer profile.”
Here’s the thing: for the most part, this advice is dead wrong.
Your Most Demanding Customers Are Building Your Future
The customers who push your product to its limits, who flood your support queue with requests, who make your engineering team groan when their name pops up in Slack—these aren’t problems to be solved. They’re prophets showing you the promised land.
Every time a paying, engaged customer using your core product complains, they’re giving you free product strategy consulting. They’re stress-testing your assumptions. They’re revealing gaps you didn’t even know existed. Most importantly, they’re showing you where the market is heading before your competitors figure it out.
That customer who’s burning through your support resources? They’re not a cost center—they’re R&D. That account that keeps pushing for features you don’t have yet? They’re not being unreasonable—they’re being visionary.
Here’s what most SaaS founders miss: a feature-poor product with great customers will absolutely tax your product and support teams. The internal complaints will be loud. Your team will push back. But this tension is a feature, not a bug. It’s the market pulling you forward faster than you planned to go.
The Real Customer Red Flags (There Are Only Two)
Now, let’s be clear—not every “customer” deserves your attention. There are exactly two types you should avoid:
1. Free “Customers” That Will Never Convert to Paid (They’re Not Customers)
Free users aren’t customers. Full stop. They’re prospects at best, distractions at worst. And in the middle, they may still be champions even if they never pay. They’ll give you terrible advice because they have no skin in the game. They’ll consume disproportionate support resources because they have nothing to lose by being needy. Most dangerously, they’ll mislead you about what actual paying customers want because their use cases and pain tolerance are completely different.
The harsh truth: if they won’t pay for your solution, their opinion about your solution is worthless.
2. Customers You Fundamentally Cannot Support
This is different from feature gaps. This is different from building something for one customer today that you hope ten or a hundred others will use tomorrow. This is about customers who will never be satisfied regardless of what you build.
These are the accounts where the fundamental mismatch runs so deep that no amount of product development will bridge the gap. The customer who churns is a customer you never actually had in a recurring revenue model. They’re not teaching you about the future—they’re teaching you about markets you shouldn’t be in.
But here’s the critical distinction: the line between “a customer dragging you into the future” and “a customer you can’t support” is razor-thin. Most of the time, what looks like an impossible customer is actually a customer three steps ahead of where your product needs to go.
The B2B Imperative: Extensibility Over Simplicity
This is where B2C thinking will kill your B2B SaaS. In consumer products, you need everyone using the same handful of features. Simplicity scales. Uniformity drives growth.
B2B is the opposite game entirely. You’re building extensible workflows. You’re creating platforms that bend to unique business processes. Your job isn’t to force customers into your box—it’s to make your box infinitely expandable.
Every demanding customer request is a stress test of your platform’s extensibility. Every complex use case is a preview of where enterprise software is heading. Every “impossible” integration request is market research you couldn’t buy at any price.
The Real Work: Building Systems, Not Excuses
When a customer becomes a drain on your core team, you have two choices: build systems or build excuses.
Building excuses looks like: “This customer is too demanding.” “They don’t fit our ICP.” “We should focus on simpler use cases.”
Building systems looks like: hiring dedicated customer success managers, creating scalable support processes, building your product to handle complexity gracefully.
The companies that win in B2B SaaS don’t avoid complexity—they systematize it. They don’t fire demanding customers—they build the infrastructure to serve them profitably.
The Bottom Line: Embrace the Pull
Your most demanding customers aren’t anchors dragging you down—they’re rockets pulling you toward the future. The tension they create isn’t a problem to be solved but a force to be harnessed.
In B2C, you can afford to say no to edge cases. In B2B, edge cases today become mainstream tomorrow. The customer who’s impossible to satisfy this quarter might be describing your core product two years from now.
So the next time your team complains about that high-maintenance customer, ask a different question: What if they’re not the problem? What if they’re the solution to problems you don’t even know you have yet?
Close them all. At least to learn. Build the systems to support them. Let them drag you kicking and screaming into the future.
