Scope creep
also known as feature creep · requirements creep
The gradual expansion of a project beyond its agreed scope without matching changes to time or fee - the most common margin killer for agencies. Controlled with explicit out-of-scope clauses and change orders.
For example, a 'quick logo refresh' slowly grows into new business cards, a social media kit and a brand guidelines document - none of it ever quoted. The team keeps saying yes to small favours, and three weeks later the project has doubled in effort for the same fee.
Why it matters to agencies: unchecked scope creep silently destroys profitability and burns out your team. Catching it early - with a clear scope, out-of-scope clauses and a habit of raising change orders - is one of the highest-leverage things an agency can do to protect margin.
everything past the agreed line is unpaid work - unless it becomes a change order
- Starting work before the scope is written down and agreed.
- Saying yes to 'small' extras instead of logging them as change orders.
- Treating change orders as confrontational rather than a routine, expected step.
What is scope creep?
The gradual expansion of a project beyond its agreed scope without matching changes to time or fee - the most common margin killer for agencies. Controlled with explicit out-of-scope clauses and change orders.
What causes scope creep?
Vague initial scope, eager-to-please teams saying yes to 'small' extras, and no routine for change orders - so unpriced additions quietly accumulate.
How do you prevent scope creep?
Define scope and exclusions up front, log every new request, and make change orders a normal, low-friction step rather than a confrontation.
How do you tell a client something is out of scope?
Point to the agreed scope, frame the ask as a welcome addition, and offer a quick change order with the time and cost - keeping it factual, not personal.