Sort every request into one of three buckets before you reply: a defect in what you promised, a clarification of what’s already in scope, or new work. Fix the first free, explain the second, and price the third calmly, in writing, with the timeline effect attached. Never answer on the spot.
Most advice on client change requests is about paperwork. Paperwork matters, and we cover the form and the process in our change request process for website projects. But the form doesn’t save you in the moment. What saves you is what you say in the first ninety seconds after a client writes “can we also just…” on a fixed-fee build.
After 15+ years of WordPress work and 1,500+ clients, I can tell you the money is rarely lost on a big dramatic request. It leaks out of the small ones, answered fast and answered nicely.
What should you say when a client change request lands?
Say less than you want to, and say it later. The instinct to reply within five minutes with “sure, no problem” is the single most expensive habit in agency work, because it sets the price at zero before anyone has looked at the request.
Your first reply should do exactly three things: confirm you heard it, say you’re checking how it fits the plan, and give a time you’ll come back. Something like: “Got it, thanks for flagging. I’m going to check how that sits against what we scoped and the schedule, and I’ll reply by end of day tomorrow.” That’s it. No yes, no no, no price, no sigh.
Clients rarely mind a day’s wait. They mind being surprised later. Use the gap to find the sentence in the signed scope that the request touches, or to confirm there isn’t one.
How do you decide between a goodwill fix and a priced change?
Ask what the request is correcting. If it corrects something you got wrong, it’s yours to fix. If it adds or changes something the client asked for and approved, it’s theirs to pay for. Most arguments about change requests are disagreements over which of those two it is, so decide honestly yourself before you talk to the client.
| Type of request | How to respond | What it costs you |
|---|---|---|
| Defect (you built it differently from what was agreed) | Own it, fix it, say nothing defensive | Your time, and it’s the right cost to carry |
| Clarification (the scope covers it, the client read it differently) | Show the line in the scope, explain, and do it if it’s genuinely small | A short conversation, or a little goodwill spend |
| Real tweak (a few minutes, one revision, no knock-on effects) | Do it as a named goodwill gesture, and count it | Minutes, but only if you track the running total |
| New work (a feature, page, integration or round not in scope) | Price it in writing, with the timeline effect, before starting | Free work plus a slipped schedule if you skip this step |
| Late-stakeholder reversal (someone new overturns an approved decision) | Treat it as a scope change and route it through your single client contact | Rework on approved pages, usually the most expensive type |
| Pattern of small asks (the fifth “quick one” this month) | Bundle them, price the bundle, and ask what changed | Margin erosion that no single request ever shows |
Basis: planning guidance explained in this post, drawn from the judgement calls above, not a published benchmark. Adjust the thresholds to your own margins and contracts.
The “real tweak” row is where good agencies get hurt. A goodwill gesture only works if the client knows it was one. Say so: “Happy to do that one on us.” Otherwise it quietly becomes the baseline.
How do you say no without damaging the relationship?
You rarely need to say no. Say “yes, and here’s what that involves” instead. A flat refusal makes the client feel judged. A priced yes puts the decision back in their hands.
When you do have to hold a line, keep it impersonal:
- Point at the document, not at the person. “The scope we both signed lists five templates, and this would be a sixth” is a fact. “You’re asking for more than we agreed” is an accusation.
- Name the tradeoff, not the rule. “We can add it, and the launch moves a week” lands better than “that’s out of scope.”
- Never apologize for the contract. It signals the boundary is negotiable.
A client who leaves over a clearly explained, fairly priced change was going to leave over the next one too.
How do you phrase the price conversation?
Treat price as information, not an apology. State what the change is, what it costs, and what it does to the schedule, in one message. Then stop writing. Every “unfortunately” and “I hate to ask” tells the client you expect them to be angry.
A version that works: “That’s a new feature, so it sits outside the original scope. Adding it comes to this amount and moves launch from the 14th to the 21st. If you’d rather keep the date, we can swap it for the gallery page instead. Tell me which you prefer and I’ll start.”
Two habits help. Quote the change as a fixed amount when you can, so the client isn’t watching a meter run, the same logic behind fixed price versus hourly web design. And never start on a verbal “okay, fine.” Wait for one line in writing. “I thought that was included” is much harder to say about an email than about a phone call.
- Never answer a change request in the moment. Acknowledge it, name a reply time, and use the gap to check it against the signed scope.
- If the request corrects your mistake, fix it free. If it changes something the client approved, price it. Decide which before you reply.
- Say “yes, and here’s what it involves” instead of no, and always state the timeline effect next to the price.
- Label every goodwill fix as a gift and keep a running count, or small favors become the new baseline.
- A steady stream of changes usually points at a scope that was written wrong, not a difficult client.
How do you handle “it’s just a small tweak”?
Stop judging each tweak on its own. “It’s just a small tweak” is a pattern, not an event. Five tweaks a week across a six-week build is a month of unbilled work that no single email made visible.
Keep a visible tally of goodwill changes and share it when it’s reasonable: “That’s the fourth small adjustment this month, so I’m going to batch the next few into one quoted round.” Said once, kindly, it resets expectations without a fight.
Also check what “small” actually touches. A new button label that appears in the header, footer and mobile menu is a templated change with testing attached. Clients judge size by one screen, and you judge it by what’s underneath: “It looks tiny, but it sits in four places, so I want to check it properly.”
What do you do when a new stakeholder appears late?
Treat it as a scope change, because it is one. A director or board member who joins at week five and wants approved pages different is not giving feedback. They are reopening decisions your contact already signed off.
Don’t argue with the new person. Route it through your single client contact: “Since these pages were approved on the 3rd, any changes now count as a revision round. Can you confirm with the wider team what’s final before we go further?” That puts the job of aligning their own people back on the client.
Prevention is cheaper. At kickoff, ask in writing who else has to approve things, and get their names.
When does a run of changes mean the scope itself was wrong?
When the changes cluster. Scope creep is common enough that PMI’s 2018 Pulse of the Profession found 52% of projects experienced it, up from 43%, so a few changes aren’t a sign of failure. A cluster is different: five requests that all circle the same area tell you the original description of that area was vague, wrong or missing.
The usual suspects: content nobody was assigned to supply, a “simple” integration with its own rules, a page described by name rather than by what’s on it. If you’re pricing request after request in the same area, rewrite that part of the plan with the client, once, instead of defending it line by line. Then look at how you wrote it in the first place, and our guide on how to scope a website project covers the questions that close those gaps before kickoff.
For a number rather than a feeling, run your totals through the scope creep calculator to see what the unbilled changes cost on that project.
If you’d rather not absorb this volatility yourself, send us the scope and we’ll come back with a fixed quote within 2 business hours. You mark it up, we build under your brand, and John is your single point of contact, so changes get priced and routed once instead of landing on your team’s evenings.
Frequently asked questions
Should I charge for every client change request?
No. Charge for new work and for changes to approved things. Fix your own defects free, and treat genuinely tiny tweaks as labeled goodwill.
How do I tell a client a request is out of scope?
Point to the signed scope, not to the client, and pair it with an option: the cost, the effect on launch, and their choice.
What if the client says the change should have been included?
Check the scope honestly first. If the wording was vague, absorb it once and tighten it next time. If it’s clearly outside, show the line and offer to quote it.
How many revision rounds should a website project include?
There’s no universal number, but every build needs a stated one per stage, written into the agreement, and counted down visibly.
Is it okay to start a change before the client approves the price?
Don’t. Wait for a one-line written approval, even by email. Starting on a verbal okay is how a quoted change becomes a dispute.
When should I walk away from a client who keeps adding changes?
Rarely mid-project. Reset scope and pricing in one frank conversation first. If the pattern continues, finish the build and decline follow-on work.
Get a free consultation and a fixed quote, usually within one business day, delivered under your agency's brand.