You shipped the fixed-price site. Then the client emails: "Can you just add a blog section? Should be quick." If you freelance or run a small dev shop, you know exactly what happens next.
Here is the reply I send now:
Happy to help with this. It falls outside the original scope, so I can either swap it for [existing deliverable] or quote it as an additional item. Which works better for you?
That is Script 1 of 9. The rest of this post is why it works, the other two scripts I use most, and the math that made me stop giving this work away.
A client of mine once ended a call with the blog-section line. I said "sure, no problem" because that is what you say when you like the client and want the next invoice paid on time. The blog section was two weeks of work. I did the two weeks. I did not invoice for them. That was an expensive way to learn that scope creep is not a communication problem. It is a billing problem, and it has a script.
The framework: acknowledge, clarify, price
Every scope-creep request gets the same three-part reply:
- Acknowledge the request positively. You are not refusing. You are being a professional who tracks what things cost.
- Clarify: swap or add? Every new item either replaces an existing deliverable or is new work. Make the client pick. This one question kills most scope creep, because it forces the trade-off into the open.
- State the cost in writing. Not on a call. In writing, with a number, before the work starts.
The order matters. If you skip to step 3, you sound adversarial. If you skip step 2, you end up doing the original scope and the additions.
Script 2: the big ask
When the request is clearly a new phase of work:
This is a great idea and I want to do it properly. It is outside what we scoped, so I will put together a short change brief: what it includes, what it costs, and how it moves the timeline. You will have it tomorrow, and nothing starts until you approve it in writing.
Note what this does: you said yes to the relationship, yes to the work, and no to doing it for free. All in three sentences. "Nothing starts until you approve it in writing" is the load-bearing sentence. Say it every time.
Script 3: the retroactive ask
The worst kind: they mention, after the fact, that they assumed something was included.
I understand you read it that way, and I should have caught the ambiguity earlier. Looking at our agreement from [date], the scope covers [X, Y, Z]. This item is new, so here are the two ways we can handle it: swap it for something in the current scope, or I quote it separately. I do not want billing surprises for either of us.
"I should have caught the ambiguity earlier" is deliberate. You give them a face-saving exit, and in exchange the swap-or-pay frame stands. You are not conceding the work is free. You are conceding that contracts are read optimistically by people who want things.
The math that makes this non-negotiable
Freelancers treat each "small thing" as too petty to bill. Run the annual number instead. If you give away 30 minutes a day on a $100/hour rate, that is $12,500 a year. That is not a rounding error. That is a used car, or two months of runway, every single year.
The five-minute reply that prevents it costs nothing but the discomfort of sending it. The discomfort fades after the third time. The $12,500 does not fade.
Approvals live in writing, or they do not exist
Every scope decision, every approval, every "yes go ahead" gets an email or a message you can point to later. Not because clients are dishonest. Because in six weeks, both of you will remember the conversation differently, and the written record is the only version that invoices.
My rule: after any call where scope comes up, I send a two-line recap. "Confirming: we are swapping the testimonial section for the FAQ block, no price change." One reply of "confirmed" and I am covered. It takes ninety seconds.
The client with the blog section? I still work with them. The next time they called with "one small thing," I sent Script 1. They chose the swap, we both knew exactly what the project was, and the invoice after that was paid in four days.
Scope creep is a billing problem. Treat it like one.
What is the worst "one small thing" you have ever gotten?
Disclosure: this article was drafted with AI assistance and reviewed and edited by the Change Brief team before publication.
Top comments (6)
The swap-or-add question is the part I will actually use. I have said yes to too many small additions and then felt awkward bringing up the cost later, so forcing the trade-off into the open feels much fairer to both sides. I also like the two-line recap after a call. Do you send that recap even when the client said no change on the call, just to lock in what was agreed?
Yes - especially then. The recap costs ninety seconds and it is the only version of "we agreed to nothing new" that exists six weeks later. When nothing changed on the call I keep it to one line: "Good call - scope stays as agreed, next delivery Friday." If the client later remembers a different conversation, that message ends the discussion before it starts.
On the awkwardness of raising cost later: it fades once the swap-or-add question does the work up front. You are not raising the price, you are asking which trade they want. The client does the math themselves.
The acknowledge, clarify, price order is the part people skip under pressure. One thing that helps me is deciding the price floor before the client ever asks, so "quote it as an additional item" doesn't turn into a stalled guess mid-conversation. For the retroactive case, I'd also put the date next to the agreed scope line in the reply, since it keeps the exchange about the document rather than anyone's memory. And on the small stuff, a running tally of what you absorbed makes the later conversation about a pattern instead of a single favor.
The price floor is the part I wish I had learned first - the awkward bit of 'quote it as an additional item' is never the sentence, it is doing the math while the client waits. Deciding the number before the call turns it back into a sentence. The date next to the scope line keeps the exchange about the document, which is the only ground you can win on. And the tally turns six favors into a pattern - and patterns are billable.
Swap it or quote it is a good line because it gives the client a real choice instead of a refusal. Most scope creep is not bad faith. The client simply cannot see that the small thing touches three screens and a data model.
The rule that nothing starts until it is approved in writing is the part that protects both sides. In our fixed price work, the original scope is written as one defined problem with a clear finish line, so any request can be checked against that sentence. If it does not serve the sentence, it is a new item with its own price.
Jack Li's two line recap after every call is a simple habit worth copying, since most disputes start from different memories of the same meeting. ScopePaid's point about deciding the price floor before the conversation also helps, because pricing on the spot usually means pricing too low.
Does the retroactive script still work when the extra work is already delivered?
Honest answer: mostly, but with the leverage reversed. Once the work is delivered, billing for it now converts a scope conversation into a trust dispute, and you usually lose both. The version that still works: name it without billing it. 'I included X - that sits outside our agreement from [date], so this one is on me. If you want more like it, here is what it costs.' You give away the instance, you keep the rule. The swap-or-quote frame moves to the next item. Where it fails completely is silence: absorbed quietly, the extra becomes the new baseline, and your next quote reads as a price increase instead of a boundary.