Looking back: April 2026
The first time I formally ended a customer relationship was harder than I expected and more important than I realized. It’s one of those small professional moments that shaped everything that came after, though I couldn’t have said so at the time.
The Setup
The customer in question was well-known. They paid. They weren’t particularly difficult in obvious ways. But over the course of the engagement, a pattern had emerged: they consumed disproportionate resources, they negotiated every small item as though it were existential, and their team treated my team as adversarial rather than collaborative.
The math on the account had slowly shifted from profitable to marginal to negative. Support hours escalated. The delivery team dreaded every call. Morale around the customer had soured.
I’d been told by every mentor and business book I’d ever consumed that firing a customer was legitimate. That some customers cost more than they produced. That walking away was sometimes the right call. Intellectually, I agreed.
In practice, actually doing it was something else entirely.
Why It Was Hard
Three reasons, in order of intensity:
1. The revenue was real.
Losing the account meant losing revenue. Revenue is always tangible. The cost of keeping the account was distributed across the team and the quarter — less tangible, harder to sum. The instinctive math always favored keeping them.
2. The story I’d tell myself about losing a customer felt worse than the reality of keeping them.
I’d spent years building a book of business. Every customer was a win. Losing one felt like a loss, regardless of the circumstances. I realized, in thinking about it, that I had an irrational attachment to the customer count as a measure of my professional standing — and that the attachment was making it hard to make the economically rational decision.
3. The conversation itself required specific skills I hadn’t developed.
“We’re choosing not to continue our relationship” is a sentence I’d never had to say before. Saying it well, without drama, without burned bridges, required a poise I didn’t naturally have. I rehearsed the conversation more than any meeting I can remember preparing for.
How It Went
The conversation itself went better than I’d feared. The customer was surprised, then defensive, then — once they realized I wasn’t going to be negotiated out of the decision — gracious. They appreciated the directness. They wished us well. The meeting ended in about 40 minutes.
A week later, the lead stakeholder sent me a note thanking me for the professionalism. He said — and I remember this exactly — that he’d had vendors walk away from his business before, and none of them had done it with the clarity I had. It was the first time I’d heard that feedback, and it changed how I thought about what “firing a customer” even meant.
It wasn’t a failure. It wasn’t even a loss. It was a specific professional action, done well, that left both sides better off than if I’d tried to limp through another six months of a dying relationship.
What Shifted
Several things changed for me permanently after that experience:
The customer count stopped being my benchmark.
I started paying attention to customer quality in ways I hadn’t before. The question became not “how many customers do we have?” but “how many of our customers are ones we’re proud to work with?” The first question has a ceiling. The second one has a floor.
I got better at the pre-signing conversation.
Having actually walked away from a customer, I became more willing to surface fit concerns before a contract was signed. The customers I’m most reluctant to bring on now are the ones I know would be hard to walk away from later. Better to have the hard conversation up front than to manage through months of difficulty.
My team changed.
The delivery team, specifically, noticed that I’d chosen their morale over the revenue. That one decision did more for team trust than any of my leadership intentions had. They knew, after that, that I wasn’t going to trade their well-being for my numbers. Every retention and recruiting conversation we had afterward built on that foundation.
The remaining customer base got better.
It wasn’t immediate, but over the following year, the quality of our customer base noticeably rose. Partly because we’d freed up resources to serve the good customers better. Partly because word travels in any industry, and the customers we wanted more of could tell we were the kind of vendor who wouldn’t tolerate bad-fit relationships — which is exactly the kind of vendor the best customers want to work with.
The Principle That Generalized
The first time I fired a customer, I was operating on the assumption that every customer is valuable and that ending a relationship is a failure mode. What I learned is the opposite: the willingness to end a customer relationship is a marker of operational maturity, and companies that can’t do it have a ceiling they can’t see.
This generalizes beyond the specific action of customer termination. The same underlying skill — ending what isn’t working with clarity and grace — applies to underperforming hires, failed partnerships, unprofitable products, strategic dead ends. The founders and operators I’ve watched scale successfully all share this skill. The ones who struggle often can’t bring themselves to exercise it.
If you’ve never fired a customer, it might be a skill worth developing before you need it. Not because you should fire any specific customer today — just because the capacity to do it changes how you think about every other decision downstream.
The first time is hard. Every time after is easier. By the third or fourth time, it’s just one tool among others in the operator’s kit, used sparingly, but present.
That’s where you want to be. It took me one specific customer to get there. I’m grateful for the lesson.