How to handle scope creep: draw a line and hold it
Here is how to handle scope creep on client projects: draw a clear line between what was agreed and what is new, then treat everything on the new side of that line as a change to be logged, priced, and approved in writing before you build it. Scope creep is not the client being difficult. It is the natural, gravitational pull of every project toward more, and your job is to meet it with a process rather than a sigh.
I have spent fifteen years shipping inside teams at Apple, PlayStation and Schwab, and I have never seen a project where the scope did not try to grow. The agencies that stay profitable are not the ones with tougher clients. They are the ones who handle the growth calmly, out loud, and on the record.
The Change Line: four steps to hold the boundary
The Change Line is our CCC method for handling scope creep without friction. It is one clear boundary between the agreed work and the new work, and a four-step routine you run every time something crosses it. The point is not to say no. The point is to say yes on terms.
- Log the request. The moment a new ask appears, write it down and name it as a new item, out loud, to the client. Naming it is half the battle, because it moves the request from an assumption to a decision.
- Price it as a change. Size the new work the way you sized the original scope. It gets its own small fee or its own line, separate from the agreed price.
- Get a yes in writing. A short message confirming the change and its cost is enough. No written yes, no build. This protects both sides and removes the awkward conversation at invoice time.
- Then build it. Only after the written yes does the work start. In that order, every time, without exception.
Why silent absorption is the real trap
The instinct that quietly kills agencies is absorption. The request is small, the client is nice, and it feels easier to just do it than to have the conversation. So you absorb it. Then the next one. Each absorption is tiny. The sum is your margin.
Worse, silent absorption teaches the client that extra work is free. The precedent you set on the third small ask determines what happens on the fifteenth. Holding the Change Line from the first request is kinder to the relationship than caving early and resenting it later.
This is doubly true for Claude Code builds, where a small-sounding request, add one more integration, handle one more input type, can hide real work behind a friendly sentence. The Change Line forces that hidden work into the open where it can be priced.
Saying yes on terms, without friction
Handled well, the Change Line makes you look more professional, not less. Clients trust a supplier who tells them the cost before doing the work far more than one who surprises them on the invoice. The change conversation, done calmly, is a trust-building moment.
Frame every change as a yes. Not, that is out of scope, but, I can absolutely do that, here is what it adds. You are on the client's side, helping them get what they want, and being straight about what it costs. That framing keeps the relationship warm while your margin stays intact.
Hold the line, then compare notes
The Change Line is not a document. It is a discipline. It works because you run it consistently from the very first new request, before any precedent of free work has set. Hold it early and the rest of the project runs on rails.
Every agency owner has a project where they absorbed too much and learned the hard way. If you are wrestling with a client who keeps nudging the line, bring the situation to the CCC community and compare notes on how others have held it without losing the relationship.
Frequently asked questions
What is the Change Line?
The Change Line is a CCC method for handling scope creep. It is a clear boundary between the agreed work and new requests, plus a four-step routine: log the request, price it as a change, get a yes in writing, then build. It keeps extra work paid for.
How do I say no to scope creep without upsetting the client?
You do not say no. You say yes on terms. Frame the new request as something you can absolutely do, then state what it adds in cost. Being straight about the price before you build is what clients trust, and it keeps the relationship warm.
Should I ever absorb a small request for free?
Be very careful. The occasional tiny goodwill gesture is fine, but silent absorption teaches the client that extra work is free and sets a precedent that compounds. If you do absorb something, name it out loud as a one-time gesture so the boundary stays visible.
Do I need a formal change order for every request?
No. Keep it light. A two-line message confirming the change and its small fee is usually enough. Heavy formal change orders for tiny asks feel bureaucratic and push clients to route around your process.
How do I prevent scope creep before it starts?
Set the expectation in your proposal. A single line saying new requests are handled as small priced changes makes every later change feel expected rather than confrontational. Clear original scope and a named sign-off person also reduce creep.
Why is scope creep worse on AI and Claude Code projects?
Because a friendly-sounding request can hide real work. Add one more integration or handle one more input type can each be significant effort behind a short sentence. The Change Line forces that hidden work into the open where it can be sized and priced.
Last reviewed by Duncan Rogoff on June 29, 2026
