How to say no to a client request without losing the client
How to say no to an out-of-scope client request when you run a one-person AI agency: a four-part reply, example wording and the yes you can offer instead.
A café owner texts on a Wednesday evening. The website you built in November is going well, and could you "just quickly" add online ordering before the weekend? It's a lovely message. It's also a new feature with a payment provider, a menu system and a lot of testing, and it wasn't in anything she paid for.
You have three choices. Do it for free and lose the week. Ignore the text until Friday and hope. Or reply tonight with a clear, friendly no that still gives her something.
The third one keeps the client. Saying no to a client request well means answering quickly, saying plainly what isn't included, and offering a way forward: a quote, a date, or a smaller version you can do now. Most clients take that well. What damages the relationship is a slow reply, a vague "maybe", or doing the work and resenting it.
How do I tell a client something is out of scope?
Use the same four parts every time:
- Thank them and repeat the request. One line, so you both agree on what was asked.
- Say where it stands. Plainly: it's not part of the website project, or not covered by the care plan.
- Offer a way forward. A quote, a later date, or a smaller version that is included.
- Say what happens next. When they'll hear from you, or what you need from them.
For the café:
Thanks for this, and great to hear the site's going well. Online ordering would mean adding a menu with prices, a way to take payment, and testing it with your team, so it's a new project rather than a change to the current site. I can send you a price and a date by Friday. If you'd like something for this weekend, I can add a "Call to order" button to the menu page today, which is covered by your plan.
That reply says no to the request and yes to the client. She gets an answer the same evening, a clear reason, a date for the price, and something useful before the weekend.
Why does scope creep happen in web design?
Mostly because nobody wrote down where the line was. "Small changes included" means one thing to you and another to a café with a seasonal menu. When the line isn't written, every request becomes a negotiation, and the easiest way to end a negotiation is to say yes. Australia's business.gov.au makes the same point about agreements in general: a verbal agreement can leave both sides unsure of their rights and obligations, and a dispute may arise when nothing in writing explains what you both agreed to do.
It also happens because each request looks small on its own. Adding a page is small. So is a new form. So is "just move the booking button". Together they're a second project, done for free.
The fix starts before the work does. A proposal with a "not included" list gives you something to point to later. If you're writing one, a website proposal template walks through the sections, including the list of what's not included and what happens if the client wants it later. For ongoing work, a care plan does the same job month to month.
What should I say for common requests?
Here's wording you can adapt for the requests that come up most:
| The request | Where it stands | A reply that keeps the client |
|---|---|---|
| "Can you add a new page?" | Usually extra | "A new page for catering would be a small project. I'll send a price by Thursday." |
| "Can you change the colours?" | Extra, if the design was approved | "The colours were signed off in the design stage, so changing them now is a new piece of work. Happy to quote it." |
| "Can you add online booking?" | Extra | "Booking needs a booking tool and some setup. I can send two options with prices." |
| "Can you write the text for us?" | Extra, unless agreed | "The plan covers adding your text. I can write it too, quoted separately, or edit what you send." |
| "Can you fix this typo?" | Usually included | "Done, it's live now." |
| "Can you do our social media?" | Not what you do | "That's not something I offer, but I can suggest someone who does." |
Two rules for the wording. First, never make the client feel told off. "As per our agreement" reads like a lawyer's letter; "that's a new piece of work" reads like a person. Second, keep the reason short. One clause is enough. A paragraph of justification sounds defensive.
What if the client pushes back?
Sometimes the client says it was included. Go back to what you both agreed in writing, the proposal, the care plan or the email where they said yes, and quote the line. Calmly:
I've checked the proposal from October, and the pages we agreed were home, menu, about and contact, with new pages quoted separately. I'm happy to quote the catering page now.
If the wording really was unclear, don't win the argument. Do this one, say so, and fix the wording:
Looking back, the proposal wasn't as clear as it should have been on this, so I'll include this one. I'll update the care plan so we're both clear on new pages from here.
That turns an awkward moment into a better agreement, and you've shown you're fair.
How do I say yes to part of it?
Look for the version you can do now. It's often the thing that makes a no feel like help:
- A smaller version. Not online ordering, but a "call to order" button and the menu as a clear page.
- A later date. Not this week, but next month, as a small project.
- A different route. Not a custom booking system, but a link to a booking tool they sign up for themselves.
- Someone else. Not your service, but a name you trust.
Clients mostly want their problem solved. If you solve part of it today and quote the rest, they get something and you get paid for the rest.
When the extra is a paid project, treat it like any other: a short quote, the price, and the payment terms. If the terms say work starts once a payment arrives, the same applies here. When to ask for a web design deposit covers that part, and it applies to a small add-on just as much as a whole site.
Should I ever do extras for free?
Sometimes, on purpose. If a good client asks for something small and you'd like to do it, do it and say so:
I've added the Christmas hours to the home page as a thank you for a good year. Normally new sections are quoted separately, but this one's on me.
That's a gift, and the client knows it. What causes trouble is the free extra nobody names. Done quietly once, it becomes the expectation. Done quietly three times, it becomes part of the plan in the client's mind, and the first time you quote for the same thing, it feels like a price rise.
If you choose to give something, name it. If you don't, quote it.
How do I keep track of what's included for each client?
Most scope arguments are memory problems. The client remembers a call; you remember a line in the proposal; neither of you can find the email. The answer is writing down what each client bought and checking every request against it.
Keep the agreement next to the client's messages, so "is this covered?" takes a glance. When you reply, keep a copy of what you said and the date. The page for freelancers running client work alone covers more of the everyday side.
Volant keeps each client's messages next to what they paid for, so your agent can draft the reply with the plan in view. Anything Volant sends or publishes waits for your approval, so a no, a quote or a gift goes out in your words, when you've read it. Keeping track of clients and promises shows how, and quotes, deposits and payments in one place covers the quote that follows.
However you run your AI agency, the reply is the same: thank them, say where it stands, offer a way forward, and send it the same day.