Playbook summary
A fixed-scope, fixed-fee modernization of one named legacy workload — usually a batch process, an internal application, or a data pipeline — onto your current cloud-native target. The deliverable is the new workload running in production with a written cutover plan and the old one retired on the calendar.
What you get
Fixed deliverables.
Listed in the SOW. Every line is shipped before the engagement closes — no add-on quote, no surprise scope.
- One named legacy workload modernized to the target platform
- Architecture-of-record diagram and decision log for every cross-cutting choice
- Data migration plan with cutover, rollback, and reconciliation steps
- Written cutover plan with named owners and a rollback procedure for every step
- Operational instrumentation wired into your existing observability stack
- Runbook and operational handover to your on-call team
- Retirement plan for the legacy workload with the calendar date
Timeline
Week-by-week.
Weeks 1–2
Workload deep dive, dependency mapping, target architecture decision log started.
Weeks 3–6
Modernized workload build on the target platform, with the existing one still running.
Weeks 7–9
Data migration plan, dual-run validation, cutover plan drafted with named owners.
Weeks 10–11
Cutover rehearsal, runbook completion, operational instrumentation review.
Week 12
Production cutover, written post-cutover review, legacy retirement scheduled.
Who this is for
Who this is for
A good fit when…
- You have one named legacy workload that is blocking a bigger modernization plan.
- You have a current cloud-native target chosen (Azure, AWS, GCP, or Kubernetes-native).
- You have an executive sponsor and an operations team ready to take the new workload on call.
- You want a measurable outcome (latency, cost, reliability, or audit posture) in writing.
Who this is not for
Pass on this when…
- You want to modernize twelve workloads in one engagement. (Start with one.)
- You have not chosen a target platform yet. We will help, but that is a separate engagement.
- You want a like-for-like rewrite with no operational outcome on the contract. That is rarely worth the cost.
What happens next
The first thirty days, written down.
- 01Briefing call within five business days of engagement signature.
- 02Week-one kickoff with the workload deep dive and decision log started.
- 03Weekly written status against milestone calendar.
- 04Day-90 cutover with the legacy retirement date on the calendar.