The project is scoped, the price is agreed, the work is moving. Then a message lands: "Hey, quick thing. Can you also add a careers page? It's just a small change."
Every freelancer knows the next ten seconds. Say yes and you just agreed to work for free. Say no and you are suddenly the difficult one on an otherwise healthy project. This article is about what to say instead, word for word, and why it works.
Why "small" is a trap
Here is the uncomfortable part: the client is not lying. From where they sit, the request really is small. They typed one sentence. They cannot see the responsive breakpoints, the CMS fields, the QA pass, or the deploy that sentence drags in. Effort is invisible from the outside, so people price it at the effort of asking.
That is why arguing about size never works. You cannot win a debate about how big something is when the other side cannot see the work. You explain the hidden complexity, they hear excuses, and the relationship gets a little worse whoever wins.
Say yes to one small freebie and you have not lost two hours. You have set a price: zero. The next request arrives pre-priced, and by month three you are running an unpaid change subscription you never meant to sell.
The move: agree on the size, switch to process
The reply that works does the opposite of what instinct says. You do not push back on "small". You agree with it, and then you change the subject from size to process.
Works in Slack, email, WhatsApp, and out loud on a call.
Yes, I can do that. It is outside the current scope, so I will send a quick approval with the price and timeline impact before I start. Once you approve it, I will schedule it in.
Look at what this does. It says yes immediately, so there is nothing to push back against. It names the boundary without drama: "outside the current scope" is a fact, not an accusation. And it hands the decision back to the client. They approve the cost, or they drop the request. Either way you never work unpaid, and you never said no.
Three situations that need their own line
Agree with the size. Point at the process. Keep it light.
On its own it is small, agreed. I run every change through a quick approval anyway, so the budget and timeline never surprise either of us. Sending it over now, it takes one click.
Stop pricing favors one by one. Batch them into a single decision.
Quick one, so the budget never surprises you. The smaller requests from this week add up to about [4 hours / $540]. Two options: I send one approval for the batch, or we park them for after launch. Which do you prefer?
Free favors are fine when they are rare and visible. Say it out loud, or free becomes the default.
Done, no charge for this one, it took two minutes. Anything bigger than this will go through the usual quick approval first.
What "small" adds up to
Take an honest example. Your rate is $90 an hour. A "small" request costs two hours, and a polite freelancer absorbs three of them a month. That is $540 a month and $6,480 a year, donated to whichever client asks most nicely. If you want the number for your own projects, the scope creep calculator does the math in a minute, and seeing your own figure changes how fast you reply.
Make it a system, not a comeback
Scripts work, but they depend on you being sharp at the exact moment the message lands. A system works every time, and this one fits in a sentence: no out-of-scope work starts before a written yes.
- Tag it. Name the request as outside the agreed scope, in one neutral sentence.
- Price it. Cost and timeline impact, in numbers, not adjectives. The change order template gives you the structure.
- Get the yes in writing. An email reply that says "approved" is enough. The extra work email handles the wording.
- Then start. Not before.
Clients learn the system fast. By the third approval, most stop asking "can you also just" and start asking "what would it cost to". That question is the whole game: changes still happen, but they enter the project priced.
Where ProofNod fits
Everything above works with plain email, and the free scripts will get you through this week. We are building ProofNod because doing it by hand has friction at exactly the wrong moment: you are mid-sprint, the client is waiting, and writing a formal-enough email feels heavier than just doing the favor. ProofNod turns the same move into a two-minute approval link: price, timeline impact, one click for the client, and a timestamped record for you.