How To Say No To A Project

The projects that damage a business are rarely the ones that went wrong. They are the ones that should never have been taken.

The signs, before you start

They are shopping on price alone. Not negotiating, shopping. If the only question is the number, the relationship will be about the number forever.

The scope keeps moving in the conversation. Three calls in and the brief has changed twice. That does not stop after the contract.

They have had three suppliers before you. Sometimes bad luck. Usually a pattern, and worth asking about directly.

Too many decision makers, or the real one is not in the room. A project approved by committee and briefed by one person goes badly for reasons nobody controls.

They want something you do not do. The temptation to stretch is strongest when work is slow, and it is exactly when a stretch is most expensive.

The timeline is impossible and they know it. Agreeing to it makes the failure yours.

Something feels off and you cannot name it. Worth more attention than it usually gets. Experienced operators are usually right about this and talk themselves out of it.

The cost of the wrong yes

It is not just the project.

It occupies the capacity you needed for good work. It absorbs disproportionate attention, because difficult clients always do. It damages morale if you have a team. And it produces work you cannot show, which means it does not even buy you a case study.

Then there is the opportunity cost, which is the one nobody calculates: the better project you could not take because you were busy.

How to decline properly

Do it quickly. A slow no is worse than a fast one. They have a decision to make and you are holding it up.

Be honest about the reason, without criticising them. "This is not the kind of work we do best" is true and complete. "Your budget is unrealistic" is true and unnecessary.

Do not invent a reason. Claiming you are booked out when you are not creates a problem when they come back in three months.

Refer them on if you can. Genuinely useful, costs nothing, and it is the thing people remember. A referral given without an angle builds more goodwill than most marketing does.

Leave the door open where you mean it. If it is a scope problem rather than a client problem, say what would make it work. Some of those come back correctly framed.

The versions that are not quite no

A smaller first piece. Where you are unsure about a client rather than the work, a small paid engagement first tells both sides a lot. It is the most useful de-risking tool available and it is underused.

A different scope. Sometimes the project is wrong and the client is right. Propose what you would do instead.

A different price. A project you would take at a higher price is not a no, it is a quote. Say the number and let them decide.

When you have already said yes

Occasionally you are in it before you see it.

Two options that work. Reset the scope explicitly, in writing, with a conversation about what changed and what the revised arrangement is. Or finish it properly, on time, and do not take the next one.

The option that does not work is resenting it quietly while delivering at half attention. That produces the bad outcome and the bad reputation together.

The test worth using

Before agreeing, ask whether you would want this client's name on your website and their number in your phone in two years.

If the answer is no, the money is not the reason to do it.