Launch
Deploy, document, train, hand over — with us on the line during cutover.
Launch is the cutover. We deploy to production, configure infrastructure, run smoke tests, and stay on the line during the rollout window so any problem gets solved live instead of escalating.
You get production documentation, runbooks, training for your team, and an on-call window covering the first days of live traffic. After Launch we either move into Support or hand the codebase off cleanly.
Launch usually takes 3 to 5 days of focused work, plus a 7-day hypercare window.
Activities in this phase
- Production deployment
- Infrastructure provisioning and DNS cutover
- Smoke and canary testing
- Documentation hand-off
- Team training session
- Hypercare on-call coverage
Inputs
- UAT sign-off
- Production infrastructure access
- Domain and DNS access
- Stakeholders for go-live call
Deliverables
- Production deployment
- Deployment documentation
- Runbook for operations
- User training materials
- Launch support window
Who is involved
- Engineering and ops from our side
- Operations or IT lead from your side
- End-user team for training
Decisions locked in
- Go-live date confirmed
- Cutover plan approved
- Rollback plan approved
Acceptance criteria
- Production live and stable
- Smoke tests passing
- Hypercare window staffed
Frequently asked
Do you handle the production deployment?
Yes. We deploy, configure DNS, set up monitoring, and run the cutover. Your team is in the loop the whole time.
What is hypercare?
The first 7 days after launch we are on standby with same-day response for any production issue. After hypercare we transition to either Support or hand-off.
Can we roll back if something goes wrong?
Yes. Every launch has a rollback plan agreed in advance. Most modern deploys roll back in minutes.
Ready to start a discovery call?
A 30-minute call to understand the work. A signed Statement of Work before any code is written.