Scope creep almost never arrives as one unreasonable demand. It arrives as seven reasonable ones, each too small to be worth a fight — which is precisely why it works. The fix is not resisting harder. It is making the running total visible while each request is still small.
You quoted $6,000 for 60 hours. That is $100/hour. Over the project the client asks for seven small things: a second logo variant, a shorter version of the copy, one more pass on the homepage, a quick export for their board deck.
Each one feels like twenty minutes. Each one actually costs about two hours, because the real cost is reopening the file, doing the thing, exporting it, sending it, and handling the revision it triggers. Twenty minutes of work, two hours of project.
That is 14 unbilled hours. You delivered 74 hours for $6,000 — $81.08 an hour. You took a 19% pay cut, and at no point did you or the client decide to.
One question decides it: would I have quoted differently if this had been in the original brief?
That last clause is the part everyone skips and it is the whole game. Quoting at zero is not a formality — it is what converts a favour into visible credit instead of invisible precedent.
The default. Note that the persuasive line is not the money, it is the date. Clients treat fees as negotiable and calendars as physics.
Why it works: the explicit “no costs you nothing” removes the pressure, which is exactly why it gets a yes. A quote that feels like an ultimatum gets argued with; one that feels like a menu gets ordered from.
For the client who genuinely has no more budget. Do not refuse; hand them the trade and let them choose.
Why it works: attaching hours to existing deliverables is the move. It reframes the project as a fixed container rather than an open tap, and the client — not you — becomes the person who said no to something.
The one almost nobody sends, and the highest-leverage of the three.
Why it works: free work only buys goodwill if the client knows it was free. Done silently it buys precedent instead — and then your first invoiced change request reads as a sudden hardening of attitude rather than the continuation of a policy you have been applying all along.
Every scope-creep argument happens in the gap between what you listed and what the client assumed. You cannot close that gap by describing your deliverables more lovingly. You close it by naming, in writing, the adjacent things that are not included — because those are the only ones anyone ever fights about.
Two more clauses do most of the remaining work:
The load-bearing words are “consolidated” and “reverses or replaces”. Without the first, eleven separate feedback emails count as one round in the client’s head and eleven in yours. Without the second, “actually, can we go back to the blue one?” is free forever — and re-doing approved work is where the hours really go.
Two rounds is the conventional number, but the number is not what protects you. The definition is.
Being handed a contract rather than writing one? Check it in about thirty seconds with the free contract red-flag checker — it runs in your browser and nothing is uploaded.
Most people find this page mid-project, not before signing. In that case: do not try to bill retroactively. Work you already handed over for free is gone, and invoicing for it now reads as a bait and switch — you will damage the relationship and still not get paid.
Draw the line forward instead. Summarise what has been added, state its value, mark it explicitly as absorbed at no charge, and state that further additions will be quoted before they start. You lose the past hours and you keep every remaining one. If an invoice is also now overdue, that is a separate escalation — the follow-up sequence is here.
Any work that would have changed your quote had it been in the original brief. Requests that merely clarify something your own scope left ambiguous are not creep — absorb those.
You mostly do not have to. Say yes with a price and a revised date attached, and make declining explicitly free. If there is no budget, offer the swap and let the client pick.
Yes — but never silently. Do it, name the hours you waived, and keep a running total. Unannounced free work sets precedent instead of earning credit.
Two per deliverable is standard. Define a round as one consolidated set of written feedback within a stated window, and define reversing approved direction as a change, not a revision. Those definitions matter more than the number.
Do not retro-bill. Summarise what was added, mark it absorbed at $0, and state that future additions get quoted first. Concede the past, protect the remainder.
The scope-of-work skill writes the deliverables list, the exclusions section and the change-order clause from a plain description of the job — then, as the project runs, drafts the change quote with the hours and the revised date already filled in from your project file. It ships with the 14-skill Freelance OS pack.
Two of the fourteen skills — the rate calculator and the follow-up writer — are free and MIT licensed, if you would rather try the pattern before paying for anything.
All 14 skills — $39 Get 2 free on GitHub