Most first AI projects don't fail on the technology. They fail because nobody wrote down what "done" means, so every "can it also..." request gets absorbed until the project is weeks late and outreach has stopped. A one-page scope document and a fixed 14-day sprint fix that.
The one-page scope lock
Signed on day 0, before any work starts. Four sections:
- The one outcome. Example: "Inbound emails to quotes@ are routed to the right rep with a draft reply attached within 15 minutes."
- The exact deliverables. What you hand over on day 14.
- Out of scope. Longer than you think. Example: outbound email, CRM updates, phone channels, other languages, the accounting system.
- The success criterion. A measurable test both sides accept. Example: "95% of a 20-email test batch routes correctly with a draft inside 15 minutes."
The 14-day sprint
| Day | What happens |
|---|---|
| 0 | 60-minute kickoff; scope lock signed |
| 1 to 7 | Build. One short async progress video on day 4. No meetings. |
| 8 | 30-minute review: the client uses the working build against the success criterion |
| 9 to 13 | Refine, strictly inside the scope lock |
| 14 | 45-minute handoff, sign-off, and the case study ask |
As a solo founder, run no more than two sprints at once, and block each on your calendar end to end before it starts.
Free worksheet
Is this project safe to scope?
The scorecard checks inputs, review owner, risk and whether the pilot can be bounded before you sign anything.
Get the free scorecardThe reply for "can it also..."
"Great idea. That sits outside this sprint's scope lock. I've added it to the phase 2 plan with an estimated [price, timeline]. Want me to lock it in for the next sprint once we close this one out?"
Send it in writing within 24 hours of the request. Clients who value clear delivery appreciate it; the few who push back hard are usually the ones who would have disputed the final invoice.
After handoff: the 7-day loop
- Days 1 to 3: a one-page case study: the buyer, the problem in their words, the build, the result in numbers and a short client quote.
- Day 5: a written retainer proposal: maintenance scope, monthly price and the next build you recommend.
- Day 7: one specific introduction ask, naming a person or situation they mentioned during the project.
Copy this template
Project: [name]
Outcome: [one sentence]
Deliverables: [list]
Out of scope: [list]
Success criterion: [measurable test]
Timeline: Day 0 [date] to Day 14 [date]
Changes: New requests become priced phase 2 items.
Signed: [client] / [you]
Go deeper
Delivery, case studies and retainers
The Launch Kit's field guide covers the full 14-day sprint and the post-delivery loop with worked examples, and the prompt pack writes your scope lock, case study and retainer pitch. 30-day money-back guarantee.
See the Launch Kit - $59
Cold Email Templates for AI Agencies (That Don't Sound Like Spam)