Sounds strange for a business to say. But it’s one of the most important decisions I’ve learned to make.
Early in my career, I took every client. More clients, more money — seemed logical. In practice it turned out differently.
Turns out some clients cost you more than they bring in. Not in money — in time, energy, and your team’s focus. A difficult client doesn’t just occupy their own project slot; they leak into everything else. The team spends evenings on rework nobody agreed to, and I spend mornings on calls that go in circles. Meanwhile the good clients quietly get less attention than they deserve.
So here are my four red flags. When I see them, the answer is no.
Unrealistic expectations
“Do in a week what normally takes a month, and cheaper if you can.” In practice, a project that starts like this almost always ends in conflict.
The problem isn’t ambition — I like ambitious deadlines. The problem is a client who won’t hear “here’s what’s actually possible” before signing, because they won’t hear it after signing either. The gap between expectations and reality doesn’t disappear when the contract starts. It just moves to the end of the project and gets a new name: “you failed.”
What I do instead: give an honest estimate with the reasoning behind it, and offer to cut scope rather than quality. If a smaller first version within that week works — great, we start. If the answer is “no, everything, in a week” — then that’s my answer too.
No respect for process
When a client ignores agreements, keeps changing terms, and doesn’t value the team’s time — that’s a signal, not a one-off.
This is exactly why I fix the terms on shore, before the work starts: scope, payment stages, what happens when something slips. Not out of love for paperwork — because it shows me how the client treats agreements while honoring them is still cheap. Someone who argues about a written milestone before the project will argue about everything after it. Late payments follow the same rule: one delay is life, a pattern is a decision the client has made.
Values don’t line up
If the client wants the result at any cost, with no transparency and no honesty about it.
This one is the hardest to spot on a first call, but it shows in small things: how they talk about their previous contractors, whether “we’ll sort it out later” replaces every uncomfortable topic. Trust is built from small consistent actions — and destroyed the same way. If the honesty isn’t there at the start, when everyone is on their best behavior, it won’t appear under pressure.
The task isn’t in our wheelhouse
It’s better to say honestly “we’re not the best fit for this” than to take it on and do it badly.
Of the four, this “no” costs me the least and returns the most. A client remembers who saved them from a bad engagement — that kind of honesty tends to come back as trust, sometimes as a recommendation. A bad delivery, on the other hand, follows you around for years.
Once I turned a project down honestly and handed it to a colleague — another CEO who specialized in exactly the stack and the kind of tasks the client needed. The client thanked me with a small cash bonus. The colleague delivered the project successfully and sent me a small reward for the referral. And the key part: for both the client and the colleague, everything was transparent from the very start.
How I actually say it
Without drama. “Based on what you’ve described, we’re not the right team for this — here’s why, and here’s the kind of partner I’d look for instead.” Short, honest, and with a direction to point at. A no with a reason and a recommendation attached keeps the relationship; a vague maybe kills it slowly.
Saying no to the wrong client is saying yes to your own reputation and your team. The team gets to work on projects where it can win. And the clients I do say yes to get a team that isn’t burned out by the one I should have refused.