Scope Creep
scope expansion · requirements creep
Work that expands past what was agreed without the price expanding with it. It is the most common way profitable projects become unprofitable, and it usually arrives one small favor at a time.
In practice
A $10,000 project with $4,000 of delivery cost. Four unbilled 'quick additions' at $500 each and the margin has gone from sixty percent to forty, with the invoice unchanged.
The common mistake
Absorbing small requests to protect the relationship. The client cannot see the cost, so nothing signals that a boundary exists, and the requests continue at the same rate.
Scope creep is the steady expansion of what is included in a piece of work after the price has been agreed. Nobody decides to do it; it accumulates one reasonable request at a time.
How it happens
A project is agreed. A client asks for a small addition — genuinely small, and refusing it would feel petty. Then another. Each request is defensible on its own, and the total is a project that costs half again as much for the same fee.
The mechanism is that every individual request is cheaper to accept than to discuss. Saying yes takes an hour; saying no takes a conversation, some discomfort, and a risk to the relationship. The incentive runs toward yes on every single occasion, which is why the outcome is reliable across every service business.
What it costs
Gross margin falls while the invoice stays flat. On a $10,000 project costing $4,000 to deliver, four unbilled additions at $500 each take the margin from sixty percent to forty.
It also resets expectations. Work given away once becomes part of the standard offer, so the next project is quoted against a scope that now silently includes it. On a retainer, this is why a profitable arrangement becomes a loss-making one over eighteen months with nothing visibly changing. See recurring revenue and the hidden cost.
Controlling it
The fix is structural rather than a matter of firmness.
- Write what is excluded, not only what is included. Silence is read as inclusion by both sides honestly.
- Define the number of revisions, meetings and stakeholders. These are where scope actually expands, rather than in the deliverable itself.
- Price additions rather than refusing them. "Yes, that's a change — here is what it costs and what it moves" is easier to say than no and produces better outcomes than either.
- Say it the first time. The first unbilled extra sets the precedent, and every later objection has to explain why this one is different.
Concept web
Open the full webQuestions
What is scope creep?
The gradual expansion of work included in a project after the price is fixed, accumulated through individually small requests that are each easier to accept than to discuss.
How do you prevent scope creep?
Write down what is excluded as well as included, define limits on revisions, meetings and stakeholders, and price additions as changes rather than absorbing or refusing them.
Why is the first unbilled extra the most expensive?
Because it sets the precedent. Once work has been given away without comment, every later objection has to explain why that request is different from the one already accepted.