What does the mission need?
Clarify the services, outcomes, constraints and decisions driving the work.
PREPARE YOUR TEAMYour leads hold the decisions.
Your leads hold the decisions.
We structure the evidence.
Name the people who own the mission, platform, security and operations. In weeks 1–2, your evidence owners gather approved material and record what is missing. In weeks 3–8, we work through the architecture and recommendations together.
The engagement delivers assessment and plans. Implementation, deeper discovery and formal security assessment are separately scoped; designated officials retain authorization decisions.
YOUR TEAM
The right people at the right decisions.
Agree participation and review checkpoints at scoping. The roles below describe contributions, not fixed staffing levels or weekly hour commitments.
| Role | When involved | Bring to the discussion |
|---|---|---|
| Mission sponsor / program lead | Scope, recommendation reviews and final handover | Mission outcomes, constraints, priorities and decisions. |
| Evidence coordinator | Data-call preparation and evidence questions | Existing inventories and approved source material; a record of what is missing. |
| Architecture / platform owners | Architecture and shared-service discussions | Current estate, boundaries, dependencies and platform responsibilities. |
| Security / authorization representatives | Readiness and preparation discussions | Applicable requirements, review paths and evidence gaps. |
| Operations / service owners | Operating design and handover | Service ownership, change, recovery and cross-team handoffs. |
| Record owner | Handover and subsequent reviews | Custody of the evidence record, next actions and the next review date. |
How evidence becomes a recommendation
Prepared source material and synthesis help organize the record and surface questions. The consultant checks interpretations and recommendations with the people who own the work. Evidence, assumptions and unresolved questions remain distinguishable.
THE WORK
Five questions that shape the foundation.
What do we have today?
Establish the current estate and operating picture from available evidence and focused discussions.
What can we share or inherit?
Examine existing enterprise and cloud services, their boundaries and the responsibilities they actually provide.
What must change?
Develop architecture recommendations, surface unresolved dependencies and identify readiness gaps.
Who takes it forward?
Assign proposed next actions, sequence the transition and define operating handoffs for client review.
SCOPE
A foundation for the next work.
Foundations delivers assessment, architecture recommendations, transition planning and operating preparation. Implementation, formal security assessment, authorization decisions and deeper discovery are separately scoped.
When Foundations Plus ADM fits
Where workload relationships need observed evidence, Application Dependency Mapping can deepen the starting picture and refine sequencing and operational handoffs. The longer engagement has its own scope and calendar; it is not automatically included in the eight-week offer.
Discuss dependency-mapping scope →