Current state
Review the existing repositories, configuration sources, manual changes and deployment responsibilities.
Cloud platforms · 01 · The problem and the decision
IaC and GitOps quick startHow do you know production matches the repository?
Console changes create drift and rollback depends on whoever made the last change. Establish a controlled path for an agreed platform slice and hand it over to the team that owns it.
For Heads of Engineering and platform teams at SaaS companies and mid-size enterprises.
3–4 weeks elapsedAn agreed repository, delivery path and platform sliceA named architect accountable
02 · What we check
Agree the scope. Inspect the evidence.
Begin with the current change process and ownership. Choose the smallest useful implementation that makes infrastructure changes reviewable and repeatable.
Change path
Define the agreed infrastructure code, checks, approval boundary and delivery workflow for the selected platform slice.
Verification and handover
Demonstrate the agreed change and rollback path in an authorised environment. Document ownership and how exceptions are handled.
What we need from you
- The agreed repositories and target environment, plus owners able to approve changes.
- Current configuration, access boundaries and the team's chosen or approved toolchain.
- A representative change and an authorised window for implementation and verification.
Scope and boundaries
- A whole-estate migration, broad application rewrite and ongoing platform operation are excluded.
- Additional repositories, environments, migration work, remediation outside the agreed platform slice and detailed engineering of further implementation tickets require separate agreement.
03 · What you get
A decision you can act on.
- A working delivery path for the agreed platform slice.
- Versioned configuration and review/check steps in the agreed toolchain.
- Evidence of the selected deployment and rollback checks.
- An operating guide and handover to the team that will extend the pattern.
04 · Relevant work and a sample
See the thinking behind the review.
Make the change traceable
The sample shows an acceptance record for a controlled change path. It is not evidence of a client deployment-frequency result.
05 · Duration and price
A defined engagement. An agreed scope.
From €12,500Starting price, excluding VAT
From €12,500, excluding VAT. We quote a fixed fee after agreeing the repository and environment inventory, platform slice, access and implementation depth. The proposal confirms the elapsed delivery window and authorised change path. Further migration, remediation outside that slice and detailed ticket engineering for follow-on work are separate.
We agree the included scope, deliverables and fixed fee in the proposal before work starts.
- Duration
- 3–4 weeks elapsed
- Base scope
- An agreed repository, delivery path and platform slice
- Your data
- Access is limited to the agreed repositories and environments. Implementation permissions, approval steps and data handling are defined in the proposal before changes are made.
Our own AI-assisted tooling collects evidence and drafts findings; a named architect checks and signs them. How we work and handle data →
06 · Request a working session
Start with the question you need to resolve.
In 45 minutes, walk through one current infrastructure change and what makes it difficult. Agree a useful first implementation boundary.
This requests a 45-minute conversation. We confirm a suitable time with you.
Does the platform need an independent review before choosing what to change? Explore the landing-zone assessment.