Launch - Scoping & Estimation (Internal)

Never client-facing. The unit each step is sized in, its S/M/L/XL bands, and the role mix - one section per step, in step order. Hours per step per tier are in the effort model; the tier model and prices in productisation.md. Bands and tiers are defined in depth.md.

6.1 Launch Readiness

Near-fixed: 8 hrs. Historical practice ran validation and launch together at ~3–13 hrs total; the formalised split provisions deliberately - see the effort model.

Role mix: lead engineer runs the checks; PM confirms the window and dependencies with the client.

6.2 Deployment & Monitoring

Near-fixed: deployment 2 hrs + early-life monitoring 4 hrs across the two weeks. See the effort model.

Role mix: lead engineer owns the cutover and rollback; mid runs the early-life checks; PM keeps the client informed through launch week.

6.3 Handover & Enablement

Near-fixed: 2 hrs (setup audit + kickoff meeting or email). The codebase handover, when taken, is a conditional +~8 hrs (cleanup pass, repo and space transfer) priced at £1,000. See the effort model.

Role mix: PM owns the handover; lead engineer runs the cleanup and transfers on the standalone path.