Fixed-scope engagements

Bounded work, stated duration, a deliverable you keep

Each of these has a stated duration, a price agreed before we start, and a deliverable your team keeps. Most client relationships begin with one of them, because it gives both sides a clear view of the estate before any longer commitment.

4–6 weeks

Azure Landing Zone Accelerator

A deployed, policy-governed landing zone aligned to the Azure landing zone design areas, with the source handed to your team.

2–3 weeks

Well-Architected Review

A structured WAF assessment of a named workload across all five pillars, with findings ranked by risk and effort.

3–4 weeks

Microsoft CAF Readiness Assessment

Where you are against the Microsoft Cloud Adoption Framework, and what it takes to close the gap.

4–8 weeks

Security Baseline Hardening

A worked remediation programme across Defender for Cloud and Entra ID, closing findings in order of risk so Secure Score moves for a reason.

4–6 weeks

Terraform Governance Framework

Module standards, state design and policy-as-code, so infrastructure as code reduces drift as more teams adopt it.

2–3 weeks

Cloud Cost Assessment

A costed reduction plan with the savings attributed line by line: commitment coverage, waste, and licensing position.

2–3 weeks

Agentic AI Security Assessment

Every agent in your tenant, what each one can read and do, and whether your assurance panel should sign off the deployment.

Choosing an engagement

If it isn't clear yet where the gaps are, the CAF Readiness Assessment is often the right place to begin. If you already know the problem, the engagement built around it is usually the one to pick.

Book 30 minutes