Before Next Sprint
MoSCoW-prioritised build list — triggered on booking day.
Before Next Sprint
When a client books, this is the build list. Not before.
The retrospective and methodology capture what went wrong and how the process adapts. This file captures what to build to support the next engagement. Each item links to a detail file with full context — designed to be picked up by an AI agent and executed with the specific client's context on booking day.
Must Have
1. Team Onboarding Flow
All workshop attendees complete onboarding before Day 1 — understanding what the sprint delivers, what it doesn't, and where the boundaries are. The specific problem: uninformed team members cause scope creep mid-workshop.
Should Have
2. Assumptions Video Walkthrough
Project-specific video explaining methodology and assumptions. Client confirms they watched it before accepting terms. Deep Work's most effective expectation-setting tool — never shipped without it.
Could Have
3. Dynamic Proposal System
Make sprint.zebradesign.io generate proposals for any client. Currently hardcoded for Research Tech — every new client requires code changes.
4. Terms & Boundary Enhancements
Explicit checkboxes for workshop dates, scope change costs (€1,000+), participant minimums (3+), date change fees, and late payment penalties. Currently in T&Cs but not surfaced as individual acknowledgments.
Won't Have (This Sprint)
5. Payment Upgrades
Stripe integration for instant payment confirmation. Required billing address field. Currently bank transfer only — works fine at current volume and avoids ~3% transaction fees.
Trigger: The afternoon the next client books. Build with their specific context. Source: retrospective.md, next-client.md, deep-work-upfront-admin-reference.md 9 February 2026