Scope Creep
"Can you also…?" The project grows. You're doing more for the same price. Scope creep is when client projects expand beyond the original agreement without additional payment. It kills profitability and scalability. You're working more for the same fee; boundaries blur. Must be managed ruthlessly—with a clear scope document, contract terms, and the discipline to say "that's a change order" or "that's a separate project."
Same client, with and without boundaries. Without: "We'll do the engagement." Three months later you've done the program, two extra workshops, and 10 "quick" calls. With a scope document and enforcement: "Deliverables: 6 sessions, one follow-up report, two check-ins. Anything beyond is a change order." Scope creep stops when you define what's in, what's out, and hold the line. Productization and service standardization make this easier—you're selling a defined outcome, not open-ended support.
What's in. What's out. When they ask for more, it's a new agreement or a new price.
How to prevent and handle scope creep
Define scope before you start. Scope document and contract terms in writing: deliverables, timeline, what's not included. "One round of revisions" not "revisions." "Two 60-minute strategy calls" not "ongoing support." The more specific, the easier to hold the line when they ask for more.
Respond with a boundary, not a yes. When they say "can you also do X?", the answer isn't "sure"—it's "that's outside this scope. We can add it as a change order for $Y or as a separate project." You're not saying no to the client; you're saying "that's a new agreement." Scope document gives you the reference: "Here's what we agreed. This isn't in it."
Productize so scope is built in. When you sell a productized service—"Leadership intensive: 6 sessions, $4.5k, these outcomes"—the scope is the product. There's no "also" unless you've defined add-ons (e.g. "Extra session: $500"). Service standardization turns "we'll figure it out" into "this is what's included."
What breaks
Saying yes once "because it's small." One "sure, I can do that" teaches them that boundaries are flexible. The next ask gets bigger. Hold the line from the first request. "Small" adds up.
No written scope. If it's only in your head or in a conversation, "we didn't agree to that" is hard to prove. Put it in the scope document and contract terms. When they ask for more, you have something to point to.