How to say no to a client (without losing them)
A short note about the only negotiation that matters: the one you have with yourself before you accept.
For years I thought saying yes to everything was how you were professional. The client asks for X, you deliver. Asks for more, you deliver. Asks for something you know is wrong, you deliver anyway.
Three years of that taught me otherwise.
The question I forgot to ask
Before accepting any project, the only question that matters is: can I do this work well with the time and resources I’m being given?
Not “can I do it?”. Not “do I know how?”. But: can I do it WELL, with what’s there, in the time that’s there?
If the answer is no, saying yes is stealing time and money from the client, and stealing hours from myself that I won’t get back.
How to say it
The trick isn’t what to say, but when. There are three windows:
- Before signing: the easiest. “With this budget and this timeline, I can’t hit the standard I want. I can do X or do it slower, or we can adjust the expectation.”
- Halfway through the project: the most uncomfortable. But if the scope changed, saying so is the difference between a professional project and a guilty improvisation.
- At the end: the worst moment, but not too late. Better to renegotiate at the end than to break trust with mediocre work.
In all three cases, the format is the same: concrete fact, consequence, alternative.
What changed when I started saying no
Three things:
- Clients who say yes to a smaller, better-executed project come back for the next one.
- Free time for the projects where I could give 100%. Better work = better references.
- Fewer Friday 11pm debugging sessions on something I knew would break.
Saying no isn’t losing a client. It’s choosing the clients I can give something both of us can be proud of.