Onboarding: What to Expect
The 30–90 day journey from discovery to full operational ownership.
Overview
Onboarding isn't a checkbox exercise. It's a phased, controlled transfer of operational ownership, designed so nothing falls through the cracks and your team has full visibility at every stage.
Standard timeline: 30–90 days depending on environment complexity, compliance requirements, and the number of workloads in scope.
The Four Phases
Discovery & Risk Mapping Weeks 1–2
We map your entire estate: workloads, dependencies, integration points, and risk posture. Every service gets a criticality score. Every dependency gets documented. This becomes the foundation for the operating model.
Architecture Workshop Week 3
A collaborative working session where we define ownership boundaries, escalation paths, monitoring baselines, and change governance rules. You leave with a documented operating model tailored to your environment.
Controlled Rollout Weeks 4–10
Phased handover. We start with monitoring and alerting, add incident triage, then patch management, then full change governance. Each phase has acceptance criteria before we move to the next.
Steady-State Operations Week 10+
Full 24/7 operational ownership. Continuous optimization, executive reporting, and quarterly business reviews. The relationship deepens over time as we learn your environment's patterns.
What You Need to Prepare
Access & Credentials
Read-only access to your current environment for discovery. We'll define the specific access roles needed during the architecture workshop.
Stakeholder Availability
A technical lead and a business stakeholder available for the architecture workshop and weekly check-ins during rollout.
Existing Documentation
Any existing runbooks, architecture diagrams, or incident history. Don't worry if it's incomplete. That's what discovery is for.
Communication Channels
Slack, Teams, or PagerDuty integration for real-time incident communication. We adapt to your existing tools.