Three stages. Three exits. No surprises.
Each stage has a fixed scope, a fixed price and a concrete deliverable. At the end of each one you own what we built, and you decide whether to scale up, carry on or stop. There are no lock-ins and no sunk-cost pressure.
- Step 1Weeks 1–2
Requirement Analysis & Audit
We find out what you actually have, what it costs and where it's exposed.
- Structured interviews with the people who run, pay for and depend on the environment. These take hours, not weeks.
- Read-only inventory of every account, subscription and project: compute, data, network, identity and spend.
- Baseline measurements of monthly cost, deploy frequency, provisioning time, open security findings and recovery capability.
- Business requirements captured as testable acceptance criteria, not wish lists.
You receive: a prioritized findings register, the baseline report and a readout session.
Decision point: Fix the quick wins yourself, or move to architecture with a fixed quote.
- Step 2Weeks 2–4
Solutions Architecture & Build Plan
We design the target state and turn it into work that can be started on Monday.
- Target-state architecture for your cloud (AWS, Azure, Google Cloud or a combination): account structure, identity, network, data, pipelines and guardrails.
- Architecture decision records (ADRs) explaining every significant choice, the alternatives and why we rejected them.
- A sequenced build backlog: each item scoped, estimated and tied to an acceptance criterion and to the baseline number it moves.
- A migration wave plan and cutover strategy, where migration is in scope.
- Fixed pricing per milestone.
You receive: diagrams, ADRs and a build backlog your own team could execute. No slide deck.
Decision point: Build it with us, build it in-house from our plan, or build part of it and hand the rest to your team.
- Step 3Week 4 onward
Buildout, Deployment & Handover
We ship production infrastructure into your account in small, reviewable increments.
- Work lands as pull requests in your repositories every week. Each one is tested, policy-checked and ready for your engineers to review.
- A weekly written update covering what shipped, what's next, any blockers, and movement against the baseline.
- Environments promoted from development to staging to production through your pipelines, not by hand.
- Rehearsed migrations and cutovers, with rollback plans tested before go-live.
Handover includes- The Terraform repository, pipelines and module library
- Runbooks for every routine operation and failure scenario
- Final ADRs and architecture diagrams
- A recorded walkthrough session for your team
- The before-and-after report: your day-one baseline next to the handover numbers
Decision point: Run it yourself, or keep it healthy with Proactive Cloud Administration.
The same five rules on every engagement
Your accounts, your repositories.
We work inside your environment, and you hold the keys from day one.
Nothing merges without review.
We don't make changes outside code and we don't apply in production on a Friday afternoon.
No scope change without written approval.
You'll never see a surprise line item.
One accountable lead.
One person owns your outcome, so you never have to work out who to call.
Everything is documented.
If we disappeared tomorrow, your team could run what we built.
Book the audit and
start the clock.
Step 1 is fixed-scope and fixed-fee. In 10 business days you'll have the findings register, the baseline report and a readout — and a real decision to make, not a sales call.
- Read-only access. We make no changes during the audit.
- Prioritized findings register in 10 business days.
- Fixed fee, and no obligation to build with us afterwards.