How to say no to a client politely, with real examples

Say no quickly, give one honest reason, and offer something useful if you can: a later date, a smaller scope or someone better suited. Keep it short. A clear no in two days is kinder than a vague maybe that lasts two weeks.

Saying no is part of the job. Every project you take fills time you could have given to a better one, and every unclear answer keeps a client waiting on a decision you have already made. The examples below cover the situations that come up most, written so you can adapt them in a minute.

Why a clear no is kinder than a slow maybe

When you leave a message unanswered, the client keeps a slot open for you in their plan. They delay asking someone else. When the no finally comes, it costs them more than it would have on day one.

A fast, warm no does the opposite. It frees them to move on, and it leaves a good impression. Clients you turn down well often come back, with a bigger budget or a better timeline, or they send someone else your way.

The shape of a good no

Most good refusals have the same five parts. You won’t always need all of them, but this is the order that reads best.

Thank them. They chose to write to you. That deserves a line.
Decline clearly. “I won’t be able to take this on” leaves no room for doubt. “I’m not sure I can” invites a follow up.
Give one reason. One honest sentence. Not a list, not an essay.
Offer something, if you can. A later date, a smaller scope, a referral, a resource.
Close warmly. Wish them well with the project, and mean it.

Examples you can adapt

Each reply below is an example. Swap in your own names, dates and reasons.

When the budget is too low

Be honest that it is about the budget, and don’t apologize for your price. If a smaller scope would work, offer it; if not, say no.

Example reply

Thanks for sending the brief. At this budget I can’t do the project the way it deserves, so I’ll pass this time.

If it helps, I could do the logo and a short style sheet within your budget, and the rest later. If not, I hope it goes really well, and I’d be glad to hear from you if the scope changes.

There is a longer guide to this situation, including how to counter without cutting your rate, in how to answer a lowball client offer.

When you are fully booked

Give a real date if you have one. “Not now” with a date is a plan; without one it is a no.

Example reply

Thank you for thinking of me. I’m fully booked until the end of January, so I can’t start in time for your launch.

If your date can move, I could begin on 2 February. If it can’t, I’d suggest asking [name], who does excellent work in this area.

When the work is not a fit

You don’t owe a detailed reason. A short one is enough, and it helps them find the right person.

Example reply

Thanks for reaching out. This project leans more on illustration than identity work, and I don’t think I’m the best person for it.

I’d look for an illustrator with editorial experience. Good luck with it, it sounds like a great project.

When they want free work first

A test project, a sample or a pitch with full designs is spec work. You can decline it and still offer a paid first step.

Example reply

Thanks for considering me. I don’t do unpaid tests or pitches, but I’m happy to share case studies that are close to your brief.

If you’d like to see how I work before committing, I can do a paid discovery session first. It would give you a written direction you can keep, whoever you hire.

When the scope keeps growing

This is a no to the extra work, not to the client. Name the change and give two options.

Example reply

Happy to look at the new pages. They weren’t part of the original scope, so I’ll send a separate quote for them.

Or, if the budget is fixed, we could swap them for two of the pages we planned. Let me know which you prefer.

Saying this early is the simplest way to stop scope creep before it eats the project.

When you need to step away from a project

This one is harder, and rarer. Give notice, finish what you can, and hand over cleanly.

Example reply

I wanted to tell you early: I won’t be able to continue past the current phase. I’ll finish everything in it by the 15th and send all the files and notes, so whoever continues can pick up without a gap. I’m sorry to leave midway through, and I’ll make the handover as easy as I can.

What to leave out

A few things make a polite no worse, even when they are meant kindly.

Long apologies. One “sorry” is enough, and often none is needed.
Excuses that aren’t true. “I’m too busy” when you are not invites a follow up next month.
Comments on their budget. “That’s very low for this kind of work” helps nobody. “I can’t do it at this budget” says the same thing without the judgment.
A maybe you don’t mean. If the answer is no, don’t say “let me think about it”.
Silence. No reply is still an answer, just the least kind one.

Saying no when the requests never stop

All of this is easy for one message. It is harder when twenty arrive in a week, half of them overnight, and each one deserves a thoughtful reply.

Yume takes the first conversation for you. Your agent answers anyone who opens your link, any hour, and talks to other people’s agents on Yume when your goals match. When one of those conversations doesn’t fit, because the budget is below your range, it hits one of your deal breakers or it simply isn’t a fit this time, your agent ends it politely and notes the reason for you. The ones worth your time wait for you in your 08:00 report, and anything binding waits for your yes.

It always says it is an AI agent, it never pretends to be you, and you can pause it any time. You can claim your link here.

The words matter less than the timing. A short, honest no, sent quickly, is almost always the right one.

For more on clients, pricing and boundaries, see Yume for freelancers.