A bounded strategy engagement
Thirty business days, four named points of contact, three sponsor reviews, and an agreed next decision with an owner attached to it.
What this is
A Phase Zero cloud-readiness engagement — not another platform.
cMAP is six weeks of consulting work with an instrument behind it. The instrument makes the reasoning legible and repeatable; it does not make the decisions, and it is not something you buy, install or operate.
Not execution, and not an authorization
cMAP does not perform migration, detailed design or authorization determinations. It scopes and sequences that work for the phase and the teams that follow.
Why day two comes first
Migration is an event. Operating is a posture.
The cloud is a different operating model in kind, not degree — interdisciplinary foundation teams, and awareness beyond any one tower’s swim lane. Before any workload moves, one question needs a name attached to it: who owns the incident at 0300, when the workload is in the cloud and the process is still on premise?
Shared services
Yours, acquired, or inherited from a larger program you join — and each of those puts the accountability in a different place.
Mission services
They sit on top of the shared layer, inside an authorization boundary somebody has to own.
The boundary
Naming it early is what keeps the second year from surprising you. It is the question that outlives the migration.
How we talk about it
Department strategy first. Service language second.
The engagement speaks in the department’s terms, and translates into a service’s vocabulary where that helps a sponsor act.
Joint warfighting ITThe mission systems and the networks that carry them.
Networks & computeTransport, hosting, and the foundation the rest inherits.
IT governanceDecision rights, risk tolerance, and the forum where both are exercised.
Digital workforceThe people who will run it on day two, and the skills that has to imply.
The line we hold
Named individuals with authority decide.
Evidence informs; it does not decide. Target posture, pace, funding, architecture, risk acceptance and every authorization decision stay with the people who hold that authority. Where our reading is overridden, the computed value is kept beside the written rationale — so the record shows both what the instrument found and what a person concluded.
A bounded next step
Start with the mission question.
A focused scoping conversation, then a fixed-scope estimate after it. No commitment beyond the conversation, and nothing priced before we agree what we are pricing.