Last month I tracked something I had been avoiding. Every time a client asked for a "quick extra," I logged the actual time it took to handle. Not the work. The handling.
The result was depressing. A 20-minute design tweak cost me 90 minutes once I added the email back-and-forth, the internal Slack discussion about whether to charge, the awkward "by the way this is technically out of scope" message, the half-built invoice line item, and the silent decision to just absorb it because charging 35 euros felt petty.
This is the scope change tax, and most agencies pay it daily.
The math nobody wants to do
If you handle four small "quick extras" a week and each one burns an hour of administrative overhead on top of the actual work, that is four hours a week of pure friction. Two hundred hours a year. A full month of working days, gone to deciding whether something is worth charging for.
Most owners I talk to have the same instinct. They eat the extras because "it is good for the relationship." That instinct is not wrong. What is wrong is the assumption that the only alternatives are (a) eat it or (b) start a fight.
There is a third option. Most agencies just never set it up.
The real problem is upstream
I used to think scope creep was a billing problem. I would read articles about how to write a firmer change-order email, or how to push back without sounding like a lawyer. None of it worked, because by the time the client is already asking, you have already lost.
The agencies I know who handle this cleanly do not have better scripts. They have a different first week.
When a project kicks off, they sit down with the client and produce one signed page. Not a forty-page SOW. One page. It lists what is in scope, what is explicitly out of scope, and what counts as a change. The client signs it. That is the entire trick.
Everything downstream gets easier because of that page. The client is not surprised when something falls outside it. You are not awkward about pointing to it. Nobody has to argue about whether a "small tweak" is a small tweak, because you defined the answer in advance, together, before anyone was annoyed.
The three-step setup
If you want to stop bleeding hours on scope friction, here is the system I run now.
Step one: the in/out page. During the kickoff call, write two columns on a shared doc. Left column: what we are doing. Right column: what we are not doing. Be specific. "Two rounds of revisions on the homepage" beats "revisions included." "Up to five product pages" beats "the website." Read it back to the client. Add anything they expected that you did not list. Then both sign it digitally. This takes twenty minutes.
Step two: define the trigger. On the same page, write the sentence that defines a change request. Mine is: "Any request that adds a new page, replaces approved work, or extends the timeline by more than three days is a change request." Notice what that does. It removes the judgment call. The client does not have to wonder if asking for a new section "counts." The answer is mechanical.
Step three: make the path easy. This is the one most agencies skip. If the only way for a client to request a change is to email you and wait for a quote, they will instead just ask casually in Slack and hope you absorb it. Give them a real path. A short form, a Notion page, a dedicated email address. Whatever it is, the client should know exactly where to send a change request and what to expect back (usually a quote and a revised timeline within 48 hours).
That is it. One page, one trigger sentence, one intake path.
What changes after you do this
A few things happen, and they happen fast.
First, the awkwardness disappears. You are not negotiating in the moment. You are pointing at a thing the client already agreed to. The conversation becomes "let me write that up as a change request" instead of "uhh, technically that is not included."
Second, the admin time collapses. The 90-minute tax on a 20-minute job drops back to roughly 20 minutes, because there is no internal debate and no diplomatic email. You just file it through the path you already built.
Third, and this surprised me, clients ask for fewer freebies. Not because they are being cheap, but because the act of submitting a change request makes them stop and ask themselves if they actually need it. Half the time the answer is no.
Where to start
You do not need to rewrite your contracts or buy software. You need one page, signed in week one, that says what is in, what is out, and how to ask for more.
If you want a template version of that page plus the kickoff checklist I use to actually get it signed without making the client feel cornered, I put a free version at agencyonboardingos.com/checklist. Steal it, change it, make it yours.
The scope change you are not charging for is not really about the work. It is about the conversation you skipped at the start.
Top comments (0)