How to tell a client no and keep them.
Say no to the request and yes to the problem behind it. A client keeps an agency that refuses a piece of work and still arrives with a way to get the outcome they wanted.
The no that loses accounts is the bare one. The no that keeps them comes with an alternative, a reason the client can repeat inside their own company, and a date.
The three kinds of no
- No to work that belongs to someone else. A task that has rolled downhill to the agency because a department is stretched or a decision has no owner. Hand it back, and name who on their side should hold it. Returning a task with its owner attached is help twice over: the client is spared the work and spared the question of where it goes.
- No to a direction you think is wrong. Say it once, clearly, with the reason and what you would do instead. Then, if the client still wants their version, make it as well as it can be made. A recommendation stated once is judgement. The same recommendation stated three times is an argument the client has to win.
- No to a date or a price that will not hold. This is the no that agencies delay the longest, and the delay is what costs the account. Raise it early enough that a choice still exists, and bring a plan for what to protect in the same conversation.
How to say it
The problem first, in one sentence. The alternative in the next. Then the date by which the alternative can be delivered.
Never a list of reasons. A list reads as a defence, and the client starts answering the reasons instead of hearing the answer. One reason they can repeat to their own manager is worth more than five they cannot.
Say it in a call or in the room, not in an email. A no in writing arrives without a face, and the client reads it in whatever mood they are in.
The second time is the moment
The first time a request drifts past the scope, it is a favour and it is usually right to do it. The second time is when to say something, with a price or an owner attached. By the third time it is no longer a favour. It is how the account works, and nobody remembers agreeing to it.
So the discipline is timing, not refusal. An agency that says no on the second appearance keeps its scope and its client. An agency that says no on the tenth has already lost the margin and is about to lose the relationship over it.
When the no is not heard
Early in my career, on an FMCG account in Beirut, we recommended a route the client's marketing team backed as strongly as we did. Their management chose a different idea. I made my case one time, and then we built their version properly.
The campaign underperformed, and the results meeting was with the same marketing team who had agreed with us. Saying so would have taken one sentence. What I said instead was where we were and what I would do about it now, and then we did that.
That is the second half of telling a client no. Once the no has been said and overruled, the agency's job is to make the client's choice work, and never to be proved right in front of the people carrying the decision.
If the same warning keeps being overruled, that deserves one conversation of its own. Frame it as a question about how the client makes decisions, never as a count of who was right.
What it looked like across the years
In the eight years I owned an agency in Dubai, the accounts that stayed were not the ones where I said yes most often. Eighty per cent of more than 50 clients renewed year after year, and the ones that trusted us most were the ones who had watched us say no with a plan attached, then deliver the plan.
A no with an alternative is the advisor's answer. A no on its own is the vendor protecting its scope, and a yes to everything is the vendor protecting its fee. Neither one keeps a client for long.
The longer version
- Have the call before they ask for it →
- Drop the credit and keep the client →
- Own the bit that was never in scope →