How we build · Stage 06
Launch
Go live deliberately, with a way back.
- Typical duration
- 1–3 weeks plus a 2–4 week hypercare window
- Portal phase
- launch
- Stage
- 06 of 08
- CRM stages
- 1
What this stage is for
Launch is a rehearsed procedure with a named owner, a cutover plan, a rollback path and a period of heightened support afterwards.
Your part
Approve the go/no-go, prepare your users, and staff the hypercare window with us.
Activities
What happens
- Production readiness review against a written checklist
- Data migration and reconciliation
- Cutover rehearsal, then cutover
- Monitoring, alerting and on-call activation
- Team training and handover documentation
- Hypercare: elevated support and daily review immediately after launch
Outputs
What you get
- Release record with what shipped, who approved it and how to reverse it
- Production runbooks, alert routes and escalation paths
- Training materials and recorded handover sessions
- Hypercare log and exit report
Exit criteria
We do not move on until
Written down so neither side has to rely on a feeling that things seem fine.
- The service is live, monitored and meeting its agreed targets
- The hypercare period closes with no unresolved critical issues
- Support entitlement and escalation routes are active and understood
Behind the scenes
How this shows up in our systems
This is not a diagram made for a website. The stage you are reading maps onto literal values in our CRM and the phase label in your client portal.
- CRM pipeline stages
- Deployment / hypercareLive, with elevated support.
- What you see in the portal
- Your project shows the phase "launch", with this stage's purpose and your part written on the project page.
Where it applies
Services that run this stage
Next step
Talk to us about launch
The Project Architect asks the questions this stage depends on, and tells you which stage your project should actually start at.