AI search and working with a developer
What is Scope creep?
Scope creep is a project growing beyond what was agreed, one small request at a time, without the price or timeline changing. It is rarely anyone acting in bad faith — it happens because each individual request genuinely is small.
Also called: requirement drift
How it actually happens
The client sees working software and thinks of something reasonable. The supplier, wanting to be helpful, absorbs it. Ten reasonable additions later the project is a third larger, the date has slipped, and neither party can point at the moment it went wrong.
The fix that works for both sides
- A written scope, agreed before payment
- Anything outside it quoted before it is built — briefly, without ceremony
- Genuinely small adjustments absorbed without counting, because pedantry is its own failure mode
- A named approver, so requests arrive from one place rather than four
What it protects the client from
Not being charged — being surprised. A supplier who absorbs everything eventually rushes the end of the project, and the part that suffers is whatever was scheduled last. That is usually testing.
Where this is covered in depth
A definition can only go so far. Writing a website brief that gets you comparable quotes covers this properly — 3 minutes, free, no email required.
Who wrote this
Anas Bin Masud builds e-commerce sites and does technical SEO for businesses in the UK, Canada and Pakistan. These definitions come from client work rather than from a content brief — where an entry describes a mistake, it is usually one found on a real site. More about how I work.