Scope creep almost never arrives as a demand. It arrives as a question. “While you’re in there, could you also…” “Quick one, would it be hard to…” “I assumed this came with…” Each request is small, reasonable, and impossible to refuse without feeling petty. Six of them later you’ve done a second project for free, and the client believes it was all part of the first.
The problem isn’t the client. It’s that the boundary was never written down, so every request has to be argued case by case, on the spot, with money and goodwill on the line. A “not included” line moves that argument to before the contract is signed, when nobody is upset yet.
Why it works
Most proposals describe what you’ll do in generous detail and say nothing about what you won’t. That leaves the edges of the job to the client’s imagination, and clients imagine generously. Naming three or four things that are explicitly outside the project draws the edge for them. It also changes what a later request feels like. Instead of you saying no, the document is saying no, and you’re just the person reading it aloud.
It also does quiet sales work. A client reading “Does not include: ongoing monthly updates” often replies with “What would monthly updates cost?” You just got asked to quote more work before the first project started.
How to run it
Write the list from your last three projects. Think about what got added, what got argued over, what you ended up doing for free. Those are your first entries. A designer’s list might read: does not include copywriting, stock photo licensing, printing, or changes after final approval. A bookkeeper’s: does not include tax filing, payroll, or catching up prior years.
Keep it to four or five items, in plain words. This isn’t legal language, it’s a courtesy. Long lists read as defensive. Short ones read as clear.
Put it near the top, not buried under the terms. Right after the summary of what the project is. The client should see the edge of the job at the same moment they see the job.
Add one sentence that opens a door. “Any of these can be added as a separate quote.” Now the list isn’t a wall, it’s a menu.
Use it the first time, gently. When the first extra request comes in, don’t argue. Reply: “Happy to. That’s outside the original scope, so I’ll send a quick quote for it this afternoon.” Warm, fast, and priced. After you’ve done this once, the client does it for you: “I know this is probably extra, but…”
The mistake most people make
Writing the list and then not using it. The first small ask comes in and you do it anyway because it really was only twenty minutes. That’s the moment the list stops meaning anything. Twenty minutes is fine, but say it: “This one’s small, I’ll fold it in, but the next one I’ll need to quote.” You just gave a gift and set a boundary in the same sentence.
The other mistake is treating “not included” as a place to be clever or cold. It’s not a warning label. It’s you being clear so the client doesn’t have to guess.
Do this today
Open your most recent proposal. Write four things that project didn’t include, based on what actually happened. Save those four lines as a block you can paste into every proposal from now on. If you have a project in flight with a request you’ve been avoiding, send the “happy to, here’s a quote” reply this afternoon.
Article contributed by
The AFE Editorial Team