Scope creep calculator

Where the hours actually go

Nobody loses a project to one large unreasonable demand. It goes in twenty-minute pieces, each of which would be petty to argue about, from five reliable sources:

• Revisions past whatever was agreed — usually because nothing was agreed, so every round is round one.
• "While you're in there" requests: a small addition attached to feedback on something else, which is how a new deliverable enters a project without a conversation.
• Direction changes after approval, where the work is redone and the redo is invisible on the invoice.
• Calls that were sold as check-ins and are really unpaid consulting or new briefs.
• Client-side delays that make you re-familiarise yourself with a project you had finished in your head three weeks ago.

The conversation that stops it

There is one sentence to learn, and the whole trick is that it comes before the work rather than after: "Happy to do that — it is outside what we scoped, so it would be an extra $X and add about three days. Want me to go ahead?"

Said in advance it is a change order and a normal commercial exchange. Said after the work is done it is a bill for a surprise, and now you are the difficult one. The words are almost identical; the timing is everything.

Two things make it easy to say. First, a written scope you can point at, so the boundary is a document rather than your mood that day. Second, saying it every time, including for small things — inconsistent boundaries teach clients that the boundary depends on how busy you sound.

Revision rounds that hold

"Two rounds of revisions" means nothing until you define a round. Write it down: a round is one consolidated set of feedback from the client, delivered at once. Without that, five emails on five days become five rounds, delivered for the price of one.

Say what happens after the included rounds, in the scope, in advance: further rounds are billed at your hourly rate, or at a fixed price per round. A client who knows round three costs $150 sends better feedback in rounds one and two. That is not a punishment — it is the mechanism that makes their feedback worth reading.

Then log the rounds as they happen. When you tell a client they are on round three, the useful version of that sentence has dates attached.

What to change in your next proposal

You do not need a new contract to stop most of this. Four lines in the next scope you send will do it:

• A deliverables list specific enough that you could argue about it — formats, quantities, page counts, and what is explicitly not included.
• A number of revision rounds, plus a definition of a round, plus the price of another one.
• A timeline with client responsibilities in it: feedback within five working days, assets supplied by a date, and what happens to the schedule if they slip.
• A line saying anything outside the above is quoted separately before it starts.

Why the number above is probably low

The calculation only counts hours you worked and did not bill. It does not count the paid project you turned down because you were busy absorbing someone else's extra round, the reputational cost of finishing late because of it, or the compounding effect of a client who learns over two years that your scope is negotiable.

It also does not count the part most freelancers feel first: not the money, but ending a good week annoyed.