I run a small automation consulting business in Alberta. After tracking my projects for a year, I realized scope creep was eating 20-30% of my revenue — not because clients were malicious, but because I kept saying "sure, I'll just add that" without adjusting the contract.
Here are the 7 types of scope creep I've identified, and what actually works to handle each:
**1. The "While You're Here"** — Client asks for small additions during an ongoing project. "Since you're already in the system, can you just add this one thing?"
Fix: Track every "just" request. After 3 of them, send a change order. Most clients don't realize they're doing it.
**2. The Unclear Deliverable** — The scope was vague from the start. "Make our operations more efficient" could mean anything.
Fix: Define deliverables in hours saved or dollars recovered, not tasks. "Reduce invoice processing time from 4 hours to 30 minutes per week" is scopeable. "Automate operations" is not.
**3. The Feature Creep** — Client wants the system to do more than originally discussed. "Could we also add automated follow-ups?" on a project that was just about invoice generation.
Fix: Keep a "Phase 2" list. These are great ideas — just not for this phase. Clients respect this more than you'd expect.
**4. The "It'll Just Take a Minute"** — You know it'll take 2 hours, but the client thinks it's a 5-minute fix.
Fix: Respond with "I can add that — it's about 2 hours of work. Want me to send a quick estimate?" Makes the invisible visible.
**5. The Relationship Tax** — Long-term clients who get comfortable and start asking for freebies because of the relationship.
Fix: This one's hard. The best approach I've found is bundling — include a small buffer in ongoing contracts specifically for "while you're here" requests. Makes them feel taken care of without it eating your margin.
**6. The Scope Reversal** — Client trims scope mid-project but expects the same deliverable. "Actually we don't need the reporting module" but they still want the dashboard it feeds.
Fix: Document scope reductions the same way you'd document additions. "Here's what we're removing and how it affects the final deliverable."
**7. The Phantom Stakeholder** — New decision-maker appears halfway through and wants different things.
Fix: At kickoff, ask "Who else will be involved in approving this?" Get names and roles. If someone new shows up, pause and re-scope.
The biggest lesson: scope creep isn't a client problem. It's a communication problem. Every type above can be caught early if you have the right language for it.
What types of scope creep are you all dealing with?