Practice 01

Cloud architecture, cost and governance

A cloud that is well built, governed and paid for on purpose. We review your environment against best practice, show you where spend goes and who owns it, and tell you what to change first.

We work on Azure and AWS, using the Azure Well-Architected Framework, the AWS Well-Architected Framework and the Cloud Adoption Framework for landing zones and governance.

Who it is for

  • Organizations running production workloads on Azure, AWS or both
  • Finance and technology leaders who need to explain cloud spend to the business
  • Teams in regulated sectors that must show control over their cloud environment
  • Organizations planning a migration or rapid growth that want governance in place first

Signs you need it

  • The cloud bill grows faster than the business does
  • Nobody can say which team or product a cost belongs to
  • Your environment has never been checked against the Well-Architected Framework
  • Tags are missing or inconsistent, so reports cannot be trusted
  • Virtual machines and databases were sized once and never revisited
  • Subscriptions or accounts have grown without clear boundaries or owners
  • Policies exist on paper but are not enforced in the platform
The entry step

Cloud Well-Architected Review

Every engagement in this practice starts with a fixed-scope review. We agree the exact scope, access and timeline with you in writing before any work begins, and you decide afterwards whether to go further.

Scope: what we look at

  • Well-Architected review across the pillars the Azure and AWS frameworks share: security, reliability, cost optimization, performance efficiency and operational excellence
  • Cost governance (FinOps): tagging and cost allocation, budgets, rightsizing from usage telemetry, and commitments such as reservations and savings plans
  • Governance: policy and policy-as-code, landing-zone design, identity and access, and subscription and account structure

What you receive

  • A written findings report, organized by Well-Architected pillar
  • A prioritized plan: what to change first, and why
  • A walk-through of the findings with your team
How it runs

How the review runs

  1. Step 1

    Scoping call

    We agree the questions to answer, the subscriptions or accounts in scope, the access needed and the timeline.

  2. Step 2

    Access and data

    You grant the agreed access. We review architecture, cost data, usage telemetry, tagging, identity and policy settings.

  3. Step 3

    Analysis

    We assess each pillar, find where spend comes from and where governance is missing, and decide which changes matter most.

  4. Step 4

    Findings and plan

    We walk your team through the report and the prioritized plan, and answer questions.

After the review

Follow-on options

None of these is required. You can act on the plan with your own team.

Remediation support

Hands-on help to put the plan in place: architecture fixes, tagging, rightsizing, account and subscription boundaries, and policy.

Governance design

Landing-zone and policy-as-code design so new workloads arrive governed from day one.

Ongoing cost reviews

Regular check-ins to keep spend visible and catch drift early.

Experience

Architecture and cost governance our Principal has led

Our Principal has applied the Cloud Adoption and Well-Architected frameworks at enterprise scale, architected infrastructure to a 99.99% availability SLA (a design target) with validated failover, and built cloud cost governance (tagging strategy, cost boundaries and rightsizing from telemetry). Delivered:20% spend reduction in one estate and $600K in recurring savings in another.

See the work

FAQ

Common questions

Which clouds do you cover?

Azure and AWS. We review against the Azure Well-Architected Framework or the AWS Well-Architected Framework, depending on where you run. If you run on both, we agree in scoping how to cover both.

What access do you need to our cloud environment?

We agree access with you during scoping and ask for the least access the work needs. The review can normally be done with read-only roles; we do not need to change anything in your environment to run it.

Do we have to buy more work after the review?

No. The review stands on its own. You receive the findings and the plan, and you decide whether to act on them yourselves or ask us for help.

Why is there no price on this page?

Every cloud estate is different, so we agree the scope on a first call and then send a fixed quote for that scope before any work begins.

Who does the work?

Our Principal, Anup Gandhi, leads the review personally. He has more than 20 years in cloud and infrastructure leadership, including cloud architecture and cost governance work.

Is this only about saving money?

No. Cost is one of several areas we review. The same tagging, account and subscription boundaries and policies that make spend visible also make your environment easier to secure, audit and run.