When to refuse work, and how to say it
In short
|
Everybody knows the project they should not have taken. It is usually obvious in hindsight and was usually visible at the time.
Here is what the signals look like before you sign, and what to say.
What should you actually refuse?
Six situations. Not moral judgements, patterns that reliably lose money and time.
The client who has fired everyone before you. Three agencies in two years is not bad luck. Ask what happened with each. If every answer blames the supplier, you are the fourth.
The work you cannot do well. Taking a project outside your competence to keep the lights on is understandable and usually a mistake. The work goes badly, the relationship ends badly, and the reference is worse than the revenue.
The brief with no measure and no budget, from someone who will not discuss either. Covered in the nine questions. A project with neither is a project where success is whatever they decide it is afterwards.
The one where the timeline is impossible and everyone is pretending. If it cannot be done properly in the time, agreeing to it does not get it done ,it gets it done badly, on time, and blamed on you.
The client who is rude before you have started. How someone treats you during the sale is the best version you will get. It does not improve after the contract.
Anything you would not want your name on. Claims you cannot support, an audience you would not want to sell to, tactics you would have to defend to someone you respect. This one is a judgement call and worth taking seriously, the work you produce becomes what you are known for.
What about the money?
The honest answer is that refusing work is easier when you have some, and harder when you do not.
If cash is tight, a bad project may genuinely be better than no project. That is a real constraint and pretending otherwise is unhelpful advice from people who have not been in that position.
Two things that help even when it is tight:
Do the arithmetic properly. A difficult project does not cost what it earns, it costs what it earns minus the extra hours, minus the work you could not take because you were busy, minus the damage to whoever has to deliver it. Projects that look profitable on the invoice are frequently losses once that is counted.
Take it with limits rather than taking it whole. A smaller first piece, a shorter term, a tighter scope. You get the revenue and cap the exposure, and you find out what they are like before you are committed for six months.
How do you say no?
Early, short, without a list of justifications.
The instinct is to explain thoroughly, because a long explanation feels more respectful. It has the opposite effect, it reads as either an apology or an invitation to negotiate, and it gives the other person points to argue with.
Three sentences is the right length:
"Thanks for thinking of us. I don't think we're the right people for this one — [one honest reason]. If it's useful, [name or thing] would be a better fit."
One reason, not four. Four reasons sound like you are building a case. One sounds like a decision.
Make the reason about fit, not about them. "This isn't the kind of work we do well" is true, unarguable, and does not require them to be at fault. Even when they are.
Offer something. A name, a suggestion, an honest comment about what they actually need. This is the part that gets remembered, and it is why a good refusal is not a lost relationship.
What if you have to refuse mid-project?
Different problem, and the standard is higher.
You have taken money and made a commitment, so walking away is a serious step. It is sometimes correct, if the work has become something you would not have agreed to, or the relationship has become one you cannot work in.
Three rules:
Give real notice. Enough to hand over properly. Leaving a client stuck is the version that damages your name.
Hand over everything. Files, access, drafts, notes, whatever exists. Withholding work to make a point is a short-term satisfaction and a long-term cost.
Say it in one conversation, not by degrees. Slowly becoming unresponsive is worse for everyone than a direct conversation.
And settle the money cleanly. Most disputes at this point are not about the amount; they are about the manner.
Doesn't refusing work make you look arrogant?
It makes you look busy, which is a different thing, and it is usually read well.
There is a version that is arrogant, refusing loudly, implying the client is beneath you, making the refusal about your standards. That is unpleasant and it travels.
The version that works is quiet and warm. You are not refusing because you are too good for it. You are declining because it is not a good match, which is a normal thing that happens between professionals.
What clients actually take from a clean refusal: this person turns down work, so when they say yes they mean it. That is a stronger signal than any credential, and it is why the honest no is worth more than the reluctant yes.
What to do this week
Look at your current projects and ask which one you would not take again. Then work out what you could have seen at the start.
Write your three-sentence refusal now, before you need it. Under pressure you will write four paragraphs.
Say no to one small thing. The skill is entirely a matter of practice, and the low-stakes reps are how you get comfortable for the high-stakes ones.
The thing to remember
The projects that hurt you are rarely the ones you lost. They are the ones you took.
Read the Method page — refusing work that cannot be done properly is part of what we teach, not an afterthought. See the 90-day program if you want to practise judging work before you accept it. |
Written by Harry Aloysius. He runs Kreative Clan and teaches at School of Kreate.
FAQ
How do I know if a client is going to be difficult to work with?
Look at how they behave before you agree to the project. If they have repeatedly changed agencies, blame every previous supplier, refuse to discuss budget or success measures, or are already rude during the sales process, those can be warning signs. The way a client treats you before the contract is often a useful indication of what working with them will be like.
Should I take a bad project if I really need the money?
Sometimes financial pressure makes turning down work difficult. If you do accept it, try to limit the risk by starting with a smaller project, shorter commitment or tighter scope. Also calculate the real cost of the work, including extra hours, lost opportunities and the pressure it puts on the people delivering it.
How do you politely say no to a client?
Keep the refusal short, honest and focused on fit. Thank them, explain one genuine reason why you are not the right fit, and where possible recommend someone or something that may help them. You don't need to give a long list of reasons because that can make the conversation feel like a negotiation.
What should I do if I realise a project is not right after I have already started?
If the project has become something you would not have agreed to originally, or the working relationship has become unmanageable, address it directly rather than slowly becoming unresponsive. Give the client reasonable notice, hand over the files and information properly, and settle the financial side cleanly.
Is it okay to refuse a client even when they are offering good money?
Yes. A high fee does not automatically make a project worthwhile. If the work is outside your ability, the timeline is unrealistic, the client relationship is already unhealthy, or you would not be comfortable putting your name on the work, the long-term cost can outweigh the immediate revenue.
Can refusing a client hurt my reputation?
A professional refusal does not necessarily damage the relationship. In fact, a clear and respectful “no” can show that you understand your limits and only accept work you can genuinely deliver. The problem is not refusing work; it is refusing rudely, disappearing or leaving the client without a useful next step.
Comments