We Fired a Client. Here's What They Did to Deserve It.

But it's real, it's happened more than once, and it's worth being honest about, because most agencies won't tell you what actually makes them walk away from money.

It's never really about difficulty

People assume the clients we've parted ways with were "difficult" — demanding, particular, hard to please. That's not it. Some of our best long-term relationships are with founders who push back hard, ask tough questions, and expect a lot. That's not a red flag. That's someone who cares about what they're paying for.

What actually ends a project is something closer to bad faith. A client who agrees to a scope, then treats every subsequent request as if it was always included, and gets hostile when told otherwise. Someone who skips two rounds of feedback, then blames the team for building "the wrong thing" when what shipped matched exactly what was signed off. A founder who talks to developers like they're disposable — sharp with juniors in a way they'd never be on a call with us directly.

That last one is close to a hard line for us. We've built this team on the idea that everyone on it deserves to be spoken to like a professional, not an inconvenience. A client who can't manage that, no matter how much they're paying, is telling us something true about what the rest of the relationship will look like.

The moment it usually happens

It's rarely the first missed expectation. It's the second or third time the same pattern repeats after we've already named it directly — because we do try to name it directly, first. "Here's what's outside the original scope. Here's what it'll cost to add it. Here's why we can't keep absorbing changes that were never part of the agreement." Most clients hear that and adjust, because most people are reasonable once the boundary is actually stated instead of just felt.

The ones who don't adjust are the ones we eventually part ways with. Not out of pride. Out of the very practical fact that a project built on a relationship that's already broken doesn't tend to produce good work anyway — for either side.

What this actually costs us, and why we do it anyway

Turning down or walking away from paying work is not free. We're a seven-person team; every project matters to the business in a way it might not at a bigger shop that can absorb a bad client as a rounding error. So this isn't a costless stance we're striking for the blog post. It's an actual trade-off we've made more than once.

We make it because the alternative is worse for everyone who isn't that client. A team that's being run ragged by one bad relationship builds worse work for every other client on their plate at the same time. Keeping a toxic project alive to protect one invoice quietly taxes every other project we're responsible for.

What we're actually telling you with this

If you're reading this as a prospective client, the point isn't "don't disagree with us" — disagree all you want, that's normal and usually makes the work better. The point is closer to: we will name a problem directly before it becomes one we can't work through, and if it keeps happening after that, we'll walk, even though that costs us. That's not a threat. It's information about how we operate, which is exactly the kind of thing you'd want to know about any team before you hand them a project.

We'd rather you know that going in than find out the hard way that we don't.

Want to know if we're actually the right fit for how you work? Book a free 30-minute strategy call — we'll tell you honestly, in both directions.
Image by Tyli Jura