The night before we fired our first client, I didn't sleep. I lay there running the numbers, and the numbers said we couldn't afford it. This was a real chunk of our monthly revenue walking out the door by our own choice, and every instinct I had screamed that you don't turn away money when you're small, that a paying client is a paying client, that maybe it would get better, that maybe the problem was us. I had a dozen stories ready to explain why we should keep them, and every one of those stories was a way of avoiding the thing I already knew, which was that this client was quietly draining the whole studio and had been for months.
We fired them the next morning. Politely, professionally, but we ended it. And the thing I remember most clearly is what happened in the hours afterward: relief. Not the anxious relief of having done something scary, but a deep, physical lightening, as if a low-grade weight I'd stopped noticing had suddenly been lifted. The team felt it too. Within days the work we were doing for our other clients got noticeably better, because we suddenly had the energy and attention that this one client had been silently consuming. The catastrophe I'd lost sleep over didn't happen. What happened instead was that the business got better almost immediately.
I've since fired several more clients, and it's followed the same pattern every single time. The fear beforehand is enormous. The aftermath is relief and improvement. I have never once regretted letting a bad client go, and I have frequently regretted how long I waited to do it. Which taught me something that took me an embarrassingly long time to understand: I'd been treating firing a client as a loss, a failure, a thing that happens to businesses that can't hold onto their clients. It's almost the opposite. It's one of the healthiest, most clarifying things a business can do, and the discomfort around it is mostly a story we tell ourselves.
This is what those clients — the ones we fired, and the ones we kept too long before firing — actually taught me. I'm writing it partly because nobody talks about this honestly, and partly because I wish someone had told me earlier, on one of those sleepless nights, that the thing I was so afraid of was the thing that was going to help most.
Key Takeaways
- Firing a bad client almost always makes the business better. The energy a draining client silently consumes gets redirected to your good clients, and the quality of everything you do goes up.
- The fear beforehand is worse than the aftermath, every time. The catastrophe you lose sleep over rarely arrives. What arrives is relief and clarity.
- A bad client costs far more than their revenue. They cost morale, focus, and the good clients you can't properly serve while they have you — costs that never show up on the invoice.
- Keeping a bad client is a decision, not a default. Inertia isn't loyalty. Every month you don't act is a month you've chosen to keep paying the hidden cost.
- Firing a client is information about your own judgment. Ask why you took them and why you kept them, and you'll learn more about your business than the client relationship ever gave you.
Why Firing a Client Feels Like Failure
It's worth sitting with why this is so hard, because the difficulty is emotional, not rational, and naming it helps.
The first reason is the revenue fear, which is real and shouldn't be dismissed. When you're small, losing a client feels existential, and choosing to lose one feels reckless. The math in the moment is simple and frightening: this money is leaving. What the math in the moment leaves out is everything the client is costing you beyond what they pay — but in the middle of the night, all you can see is the revenue line, and the revenue line says stay.
The second is the story that a lost client equals a personal failure. We absorb the idea that good businesses keep their clients and struggling ones lose them, so ending a relationship, even a terrible one, feels like an admission that we couldn't make it work. That framing is completely backwards — choosing your clients is a sign of a healthy business, not a failing one — but it runs deep, and it keeps people tethered to relationships they'd be far better off without.
And the third is the endless supply of rationalizations, because a bad client always gives you material to justify staying. Maybe it'll get better. Maybe the last project was just a rough patch. Maybe it's partly our fault and we should try harder. Maybe they'll turn into a great client if we just fix this one thing. Each of these can be true in isolation, which is what makes them dangerous — they're plausible enough to keep you from acting, month after month. I got very good at generating these stories, and every one of them was a way of not doing the thing I knew needed doing.
The Clients We Kept Too Long
Looking back, the clients we eventually fired all shared something: the warning signs were visible early, and we kept them anyway, telling ourselves the stories above. There was the client who was never, ever satisfied — every deliverable met with a new round of complaints, every fix generating two new problems, a person for whom "good" did not appear to be an achievable state. There was the one who paid late every single time, turning our cash flow into a source of constant low-grade stress. And there was the one who was pleasant enough but treated the team badly in small, corrosive ways that slowly made everyone dread the work.
What they had in common wasn't that they were evil. It was that each one extracted more than they paid for — in energy, in stress, in the attention they pulled away from everything else — and we let them, because ending it felt harder than enduring it. Most of these were clients whose red flags I could see now, clearly, from the very first conversations, if only I'd been willing to read them. [BACKLINK PLACEHOLDER → suggestion: internal link to article #35, the five clients you should never accept] We didn't fail to notice the signs. We noticed them and overrode them, because we wanted the work, and then we compounded the mistake by staying long after the evidence was overwhelming.
The pattern I want to name is the compounding. A bad client rarely gets fired on the first bad month, because the first bad month looks like a fluke. By the time the pattern is undeniable, you've already invested months, and the sunk cost makes leaving feel even more wasteful, which keeps you in longer, which increases the sunk cost. The relationships that drain you most are precisely the ones the sunk-cost trap makes hardest to leave. Recognizing that loop is most of the battle.
What Actually Happened When We Let Them Go
Here is the part that still surprises me, even now, having lived it several times: the aftermath was consistently better than I could have imagined during the sleepless nights.
The most immediate thing was the redirected energy. A draining client doesn't just take the hours you bill them — they take a background share of your attention that you don't even notice until it's gone. After each firing, the studio had more to give everyone else, and the work for our good clients visibly improved. We weren't working more hours; we'd just stopped leaking energy into a relationship that consumed it. This is the hidden cost made visible in reverse — you only see how much a bad client was costing you once you stop paying it.
The second thing was morale. It's hard to overstate what one genuinely difficult client does to a small team's spirit, and how much lifts when they're gone. The team stopped bracing for the next round of complaints or the next late payment or the next round of being treated poorly. People were lighter, more creative, more willing. And the third thing was space — literal capacity that had been occupied by a bad client, now open for a good one. More than once, the client we replaced a fired one with was better in every way, and we'd never have had room for them if we'd kept clinging to the bad one out of fear. The empty slot I'd been so afraid of turned out to be the thing that let something better in. A bad client, it turns out, is not just a bad client — it's an occupied space where a good client can't go. [BACKLINK PLACEHOLDER → suggestion: internal link to article #12, the margin trap / the month we had six clients and made less than the month we had two]
The Lessons That Stuck
A few things crystallized across these experiences, and they've changed how I run the business.
The first is that a bad client costs enormously more than their revenue, and the invoice hides all of it. The revenue is visible and the costs are not, which is exactly why the math in the moment always argues for staying — it's measuring only the part you can see. Once you learn to weigh the invisible costs (the morale, the opportunity cost, the drain), the decision to fire a bad client stops looking reckless and starts looking obvious. Businesses over-retain unprofitable clients for the same reason people hold losing investments too long — the loss feels more real than the freedom would. [BACKLINK PLACEHOLDER → suggestion: external link to a credible source on unprofitable customers / customer profitability, e.g. Harvard Business Review on firing customers or the concept of customer profitability]
The second is that keeping a bad client is an active decision, even when it feels like a default. Every month you don't act, you are choosing to keep paying the hidden cost. Inertia disguises itself as loyalty or patience, but it's just a decision you're making by not deciding. Naming it as a choice — "I am choosing to keep this client and everything that comes with them" — makes the cost impossible to ignore.
The third, and maybe the most useful, is that firing a client is a mirror. The most valuable thing each firing gave me wasn't the relief; it was the question afterward: why did we take them, and why did we keep them so long? The answers pointed at my own patterns — the red flags I was willing to ignore when I wanted the work, the stories I reached for to avoid hard conversations, the way our lack of a strong pipeline made every client feel too precious to lose. Learning to say no earlier and to let go faster is one of the clearest markers of a business maturing, and it's the same muscle as learning what to stop doing generally. [BACKLINK PLACEHOLDER → suggestion: internal link to article #13, six things I stopped doing in year two]
🎬 Embed a short reflection on the decision framework for when a client should be let go versus managed — the questions to ask before firing.
How to Actually Let a Client Go
Since this is a real thing you may need to do, here's how I approach it now, having done it badly and then better.
First, be sure it's a firing and not a fixable problem. Some difficult situations are the result of a fixable misunderstanding — unclear scope, a bad brief, a miscommunication — and those deserve a real attempt to fix before you end things. The clients worth firing are the ones where the pattern is stable and the cost is structural, not the ones having a fixable rough patch. If you've genuinely tried to address it and the pattern holds, it's a firing.
Second, do it cleanly and kindly. You rarely need to explain that they're a bad client. You can cite capacity, a change in focus, or simply that you don't think you're the right fit going forward, and help with a graceful transition — finishing current work, giving reasonable notice, pointing them elsewhere if appropriate. The goal is to end the relationship without burning it down; professionalism on the way out protects your reputation and leaves the door closed but not slammed.
And third, resist the urge to backfill the fear with a new bad client. The trap after firing is to rush to replace the revenue with whoever's available, which is how you end up with another bad client. Trust the space. The relief and the improved work are the point, and the right replacement is worth waiting for.
