When Your Startup Has Outgrown a Customer
We’ve talked about those "OK" customers before and you've decided on the ones that have to go.
Good.
You're not wrong.
Now you've got to actually do it.
And that's where it gets uncomfortable.
Because the customers you're thinking about letting go aren't always bad customers.
Some of them backed you early.
Some have been with you for years.
Some of your team genuinely like working with them.
You may have had dinner together. You may know their family. They may have taken a chance on your company when there wasn't much to take a chance on.
So how do you decide when a customer relationship has run its course?
And once you've decided, how do you actually end it?
Pre-PMF, this is normal
Before product-market fit, you're experimenting.
You try things.
You build things for customers.
You take on opportunities that might teach you something.
Some of those things work.
Some don't.
And some sit somewhere in the middle.
Maybe you have a proof of concept that never quite died.
Maybe you built a custom integration for one account.
Maybe you've kept a feature alive because one customer still uses it.
That isn't necessarily a problem before you've found product-market fit.
You're learning what the market wants.
The problem is what happens when you keep carrying those decisions forward after the company has changed.
At some point, you have to stop asking, "Did this customer help us get here?"
And start asking, "Does this customer fit where we're going?"
Not every customer is equally valuable
One of the simplest ways to look at your customer base is to map two things.
How much effort does this customer require?
And how much reward do they create for the company?
The customers that are high reward and relatively easy to serve are usually obvious.
The difficult part is looking honestly at the other end.
The customers that consume significant amounts of time, require custom work, create exceptions, and aren't giving much back.
Those are the accounts worth discussing.
And importantly, make sure nobody's bonus is dependent on keeping them.
Otherwise you've created a situation where someone inside the company has a financial reason to argue against the decision.
Before doing anything, check the contracts.
Understand the notice periods.
Know what you're actually committed to.
They deserve six months' notice where that's required.
Three months at a minimum.
This isn't about punishing the customer.
It's about making a deliberate business decision and handling the consequences properly.
Don't quietly starve the relationship
This is where founders can make things much worse.
You know the relationship isn't working anymore.
So you stop investing in it.
You take longer to respond.
You stop giving it attention.
You don't prioritise their requests.
You hope that eventually they notice and leave.
It's the startup equivalent of refusing to break up with someone and behaving badly until they do it for you.
Don't use that strategy.
Your team is watching.
If employees see that the way the company deals with unwanted relationships is to quietly starve them until they disappear, you've taught them something about the culture.
And it's not a particularly good lesson.
If you're going to make the decision, make it properly.
Your board should know too.
Put it in writing, then have the conversation.
They don't need to discover later that a significant customer relationship disappeared because nobody wanted to say it out loud.
Choose trusted over liked
This is probably the hardest part.
You can like someone and still decide not to keep serving them.
Those two things aren't mutually exclusive.
The conversation doesn't need to become complicated.
You can tell them the truth.
You've narrowed what you're building.
They need things you're not going to build.
Keeping them on a product that's moving further away from what they need isn't going to make the relationship better.
In fact, it's likely to make it worse.
The goal isn't to convince them that leaving is good for them.
The goal is to help them leave properly.
Export their data.
Give them engineering support for a week if that's what they need.
Introduce them to a company that might be a better fit.
Do what you reasonably can to make the transition easier.
But don't offer a discount just to keep them.
Now you're solving the same problem at a lower margin.
Some customers are going to be hurt
And you need to let them be.
You don't get to decide how someone should feel because you made a reasonable business decision.
Some customers will be angry.
Some will be disappointed.
Some will feel like you abandoned them.
If the relationship matters, don't hide behind an email or send your customer success lead to deliver the news.
Have the conversation yourself.
You can say:
"You backed us early. We wouldn't be here without it. I am grateful, and I'm still ending this."
Both things can be true.
You can be grateful for what someone did for your company and still decide that the relationship needs to end.
That's part of being a founder.
Don't let the gap become the story
Once you've decided, don't spend weeks sitting on it.
Tell your company.
Tell your board.
Tell the customers.
The space between those conversations should be measured in days, not weeks.
Because information leaks.
If the customer hears from someone else that you're ending the relationship, you've created an entirely different conversation.
And if something does leak, deal with it quickly.
Call the customer that afternoon.
A leaked decision handled quickly is one thing.
A leaked decision that you deny for two weeks is something else entirely.
Trust gets damaged when people realise they were the last person to know.
What this teaches your team
There's another reason these decisions matter.
Your team is learning from how you handle them.
Your board is learning too.
When you make a difficult customer decision deliberately, you're showing the board that you're willing to protect the direction of the company even when the decision is uncomfortable.
Your team sees something else.
They see what the company does when something that once worked stops working.
That matters.
You can outgrow someone without pretending they didn't matter
This is the part founders sometimes miss.
Ending a customer relationship doesn't erase the history.
They may have helped you survive your earliest years.
They may have given you feedback that shaped the product.
They may have introduced you to someone who changed the company.
That still matters.
But the company today has different needs.
Companies, like people, drift apart.
That doesn't mean they can't be friends after.
Some relationships will end completely.
Others might survive.
And some customers may even come back later when what you're building fits what they need again.
The goal isn't to make every customer happy.
The goal is to build the company you actually decided to build, while treating the people who helped you get there with respect.
That is a very different thing from quietly hoping they'll leave.
What’s Next?
Join My Weekly Newsletter! Get founder insights, funding strategies, and exclusive resources straight to your inbox.
Want more insights on building a thriving startup without burnout?
