How to stop scope creep
Scope creep rarely arrives as one big request. It's a series of small ones, each too small to argue about. Here's how to catch it early.
1. Write the scope as deliverables
"A website" is not a scope. "Up to 5 pages, a contact form, basic SEO setup and 2 rounds of design revisions" is. List what the client receives, how many, and in what form.
2. Say what is not included
This is the most useful line on a proposal. Copywriting, photography, hosting, extra pages, new features after launch: whatever clients often assume, write that it's not included.
3. Break big projects into phases
Discovery, design, build, testing and launch, each with its own timeline and, ideally, its own payment. Changes requested in a later phase are easy to see and to price, and you're never owed for the whole project at once.
4. Agree a change process up front
5. Respond to small requests the same way as big ones
Offering "a later phase" keeps the relationship positive and often turns scope creep into the next project.
6. Count revision rounds
Unlimited revisions are scope creep in disguise. Include a set number per deliverable and price the extras (see how to charge for extra revisions).
7. Keep everything in writing, in one place
Approvals in calls and chat threads are hard to point back to. Keep the scope, the changes and the approvals together.
The checklist
- Deliverables listed with quantities
- What's not included
- Revision rounds per deliverable, and the price of extras
- Phases with timelines and payments
- A change process
- A valid-until date on the quote
Kanvo proposals hold all of this on one link: requirements, what's included and not, phases on a timeline, and a fixed price or a price per phase. When the client accepts, the project starts with its timeline.
Free tool: Write a quote with a deposit and payment schedule, as a PDF.
Open the free tool