Notes

The four sentences that end scope creep without a fight

Scope creep almost never arrives as a demand. It arrives as a favour.

“While you're in there, could you just…” The thing being asked for genuinely is small, which is what makes it hard. Saying no to a twenty-minute task makes you look difficult over twenty minutes. So you do it. Then the next one arrives, and the one after, and eleven small favours later you are working a second project for free and quietly resenting a client who has no idea anything is wrong.

That last part matters. In the overwhelming majority of cases the client is not exploiting you. They cannot see the edge of the work, because you never drew it.

Name it as work, not as a problem

The instinct is to push back. Do the opposite. Treat the request as a completely normal thing to want, because it is.

Happy to do that.

Say it first and mean it. Everything difficult that follows lands softer after those three words, and you have avoided the confrontation entirely.

Place it outside the current scope

No grievance, no “as we agreed”, no reminding them of the contract like a parent. Just a fact about where the boundary sits.

That sits outside the build we scoped, so it'd be a change order.

“Change order” is doing real work there. It is procedural language rather than personal language, so it does not read as you being annoyed. It reads as how the job works.

Price it, immediately, with a number

This is where people fail. They say “that would be extra” and leave the amount vague, hoping the client backs down. Vagueness always resolves in favour of the person with less to lose.

That's another $400, and it moves delivery to the 14th.

Both costs, money and time, in one sentence. The time cost is often the more persuasive of the two.

Hand them the choice

Say the word and I'll add it, or we ship as planned and pick it up after.

Two real options, both fine with you. The client does not have to decline anything to keep their dignity, and they very often take the second one, which is the point.

The whole thing, in one message

Happy to do that. It sits outside the build we scoped, so it'd be a change order: another $400, and it moves delivery to the 14th. Say the word and I'll add it, or we ship as planned and pick it up after.

Four sentences, roughly forty words, and no version of that message starts an argument.

The real fix is earlier

Every one of these conversations is easier when the boundary existed before the work started. Not a contract, which nobody reads, but one short note at the beginning: what is in, what is out, and what a change costs. Two minutes of writing that saves the entire conversation above.

The finished version is the change order, $12. Also the scope note that prevents it, $12.