Scope creep isn't a failure of willpower. It's a failure of the contract.
The one-page rule
If you can't describe a project on one page, what's in, what's out, what we ship on what date, you don't have a project. You have a wish. I send a one-page contract with every engagement:
- Three bullets of in-scope
- Three bullets of explicitly out-of-scope
- A price and a date
- One paragraph on what happens if the scope changes mid-build
That last paragraph does 80% of the work.
The out-of-scope list
People obsess over the in-scope list. The out-of-scope list is where the margin lives.
"We're building a billing dashboard."
"Out of scope: webhook retry UI, refund automation, custom invoice templates, SSO."
Writing it down doesn't stop clients from asking, but it makes the conversation honest. "That's out-of-scope" becomes a reference to a shared document, not a judgment call in the middle of week 3.
When scope does change
It will. The contract has a change clause: scope changes get a short written addendum, a new line item, and a new delivery window. Both sides sign. Five minutes of friction, zero scope creep, zero surprise invoices.
Written 2026-01-22.