# Scale-up readiness checklist · [Bet name] · [Date] **Gate:** Pilot to scale (gate 4) **Receiving owner:** [Name] **Transfer path:** Absorb into core unit / Grow standalone / Sell or spin out Every item needs an evidence link. An item with a claim and no evidence is a fail. | # | Item | Pass / Fail | Evidence link | Owner | Fix by | |---|---|---|---|---|---| | 1 | Results hold outside the pilot: customers representative of the target segments, not only the friendliest | | | | | | 2 | Results hold without pilot-level attention from the team | | | | | | 3 | Unit economics at scale volumes, including inference cost as a dated curve | | | | | | 4 | For AI: autonomy matches the job; a simpler workflow was considered and rejected on evidence | | | | | | 5 | Evals cover the actions and outputs customers will rely on, and will keep running after transfer | | | | | | 6 | Operational readiness: support runbooks, escalation path, on-call, documentation | | | | | | 7 | Go-to-market readiness: price, SKU, billing, sales compensation, partner enablement | | | | | | 8 | Compliance and risk: security review, audit logs, data residency, AI risk documentation | | | | | | 9 | Receiving owner has the bet in their plan, budget and roadmap | | | | | | 10 | Integration and technical debt listed, each with an owner | | | | | | 11 | Pilot exceptions listed, with what replaces each at scale | | | | | | 12 | Metrics and dashboards continue in the receiving unit's business review for two or three quarters | | | | | | 13 | Sunset or migration plan for anything the bet replaces | | | | | | 14 | Exit report written: what was learned, open assumptions, what the receiving unit must keep doing | | | | | ## Decision [Scale / Scale with conditions / Not yet], decided by [forum] on [date]. Conditions: [list].