Skip to main content

Decide what belongs in cloud, on owned infrastructure, and what should be retired.

You get a verified current-state map, a keep, move or retire decision for each in-scope workload, the target architecture, the implementation sequence and the inputs needed for a defensible budget. Where private AI is in scope, the design includes capacity, power, network, storage and vendor-neutral hardware requirements.

Plan the Infrastructure Review

What changes

  1. 01Cloud, server, storage, network and recovery components are mapped to the workloads that depend on them.
  2. 02Requirements for availability, recovery, security, data location, capacity and support are agreed.
  3. 03Each workload receives a keep, move or retire decision across public cloud, private infrastructure or a hybrid route.
  4. 04The target design, implementation sequence, decision risks and budget inputs are documented for approval.

How completion is verified

The engagement is complete when the agreed results can be demonstrated.

  • The current environment and its critical dependencies are verified
  • Every in-scope workload has a keep, move or retire decision
  • The target architecture includes availability, recovery, ownership and operating requirements
  • The implementation sequence, decision risks and budget inputs are accepted by the decision owner

Full scope

Responsibilities, exclusions and handover details remain available before a conversation.

What is included and excluded
  • No production settings, workloads or data are changed during the review
  • No hardware purchase, rack installation or vendor contract negotiation
  • No migration, platform upgrade or restore remediation
  • Implementation is scoped and approved separately from the architecture decision
What the client provides
  • Provide read-only access and existing diagrams, bills and support records
  • Nominate owners who can confirm workload and recovery requirements
  • Make the final platform and budget decisions
Change and rollback method
  • Discovery uses read-only platform evidence, configuration exports and owner interviews.
  • Assumptions are separated from verified facts and assigned before they can drive the target design.
  • No platform is selected until the business, technical and operating requirements are agreed.
What is handed over
  • Verified current-state architecture and dependency map
  • Workload decision register: keep, move or retire
  • Target architecture with availability, recovery and ownership requirements
  • Implementation sequence, decision risks and budget inputs
  • Private-AI capacity and hardware requirements where included

Have a project in mind?

Tell us what needs to be delivered, the environment involved and any deadline.

Get a Fixed Price in Writing