What is scope creep?
Every agency has been asked what is scope creep by somebody who has just experienced it and does not yet have the word. It is the gradual expansion of what a project includes, after the price was agreed and without the price changing — and the reason it is dangerous is that no single instance of it looks unreasonable.
Definition
scope creep — Scope creep is the gradual expansion of a project’s deliverables beyond what was originally agreed, without a corresponding change to the budget, the timeline or the contract. It usually accumulates through small, individually reasonable requests rather than through one large change, which is why it is typically noticed only after the project is already unprofitable.
Also called: requirement creep, feature creep.
See also: statement of work, agency retainer.
Written in English, and written to be useful on its own — the definition above names no product on purpose.
What this changes
Three specifics, rather than a feature list
It arrives in small pieces
A second language. One more template. A revision that is really a redesign. Each takes an afternoon and none of them justifies an invoice on its own.
It is agreed in conversation
Almost always in a reply, a call or a message — somewhere the original agreement is not, which is why nobody notices the drift until the margin has gone.
The fix is a record, not a spine
Saying no is hard. Pointing at what was agreed, in writing, on the day, is much easier and does not damage the relationship.
Why "just one more thing" compounds
A single unbilled hour on a five-thousand project is a rounding error. Eleven of them, spread over six weeks and never counted together, is a fifth of the fee and the difference between a good month and a bad one. The arithmetic is invisible because it is never performed: nobody adds up a series of favours.
The second cost is worse and less discussed. Every accepted addition resets the client’s expectation of what is included, so the tenth request is not ten times bolder than the first — it is simply the current normal.
Three places it can still be caught
- At the proposal: a scope that says what is not included is worth more than one that lists what is.
- At the request: naming it as a change, in the moment, in writing, costs one sentence and saves the argument.
- At the invoice: a change recorded at the time is a line item; a change remembered at the end is a difficult conversation.
Scope creep is not a failure of firmness. It is a failure of record-keeping that eventually requires firmness.
How this shows up in software
Most tools cannot see it, because the request arrives in an email and the agreement lives in a document, and nothing joins the two. A project board shows more tasks; it does not know they were not in the deal.
What helps is that the accepted proposal — its body, its number, the date the client agreed — is on the same record as the message that just arrived. Then "is this in scope" is a comparison rather than a memory, and the answer is available at the moment somebody could still charge for it.
Questions people ask about this
Is scope creep always the client’s fault?
Rarely. Most of it originates on the agency side as a vague scope, an eager yes, or a proposal that describes the outcome without bounding the work. A client asking for more is behaving normally; the agreement is what is supposed to answer them.
How is it different from a change request?
A change request is scope creep that was named. Same work, same conversation, but recorded and priced — which turns an unpaid favour into either revenue or a decision the client makes with the cost in front of them.
Does a retainer prevent it?
It moves it. A retainer bounds the money rather than the work, so creep shows up as a month that quietly contains twice the agreed hours. What prevents it is defining what the retainer covers, which most retainers do not.
What is the earliest warning sign?
A deliverable somebody cannot point at in the original agreement. If two people on the team disagree about whether something is included, it is already outside the scope as written, whatever anybody intended.
Last reviewed on . Something out of date or wrong? Tell us and it gets fixed.
Continua a leggere
Point it at one client and see what it prepares.
Connect a mailbox, designate the contacts for a single client, and read what the operator has drafted by tomorrow morning. Free to start, and nothing leaves without you.