Cloud Centre of Excellence.
Strategy plus the operating model that runs it. RACI, governance, FinOps, AI enablement principles. Pairs cleanly with the Cloud Kickstarter or Managed Services.
See the solution→ [01] / SERVICE — CLOUD STRATEGY & ARCHITECTURE
Decisions you can run on Monday.
Cloud strategy that ends in ADRs, not slides. Architecture reviews that name what changes and what stays. We hand back artefacts your engineering team will actually use, not a deck to file away.
[01] / CAPABILITIES _
What you get out of a strategy engagement.
- [01] / VISION
Cloud vision & roadmap
12 to 24 months ahead, mapped to the business outcomes the platform exists to enable. Reviewed quarterly.
- [02] / TARGET
Target architecture
AWS or Azure. Identity, network, accounts, data, AI. A diagram you can defend and an ADR for every important call.
- [03] / DECISIONS
ADRs and RFCs
Every significant decision recorded as a markdown ADR in your repo, with context, options, decision, consequences.
- [04] / COSTS
Cost model
Unit economics per service. Cost-aware design from the first sprint, not a finance review after.
- [05] / VENDORS
Vendor selection
We compare on the trade-offs that matter to you: data residency, support model, total cost over three years, exit cost.
- [06] / RISKS
Risk register
Named risks, named owners, mitigations. Reviewed with security and finance, not left in a planning doc.
[02] HOW WE RUN IT _
How a strategy engagement runs.
From audit to handoff2–6 weeks
Every architectural decision we make together ends in a record like this — one page, the decision captured, consequences written, auditable forever.
[FIG.01 / STRATEGY · SAMPLE ADR] ONE DECISION · ONE PAGE
[01] / AUDIT
45 minutes.
Three questions. We send a written summary either way.
⏱ 45 min [02] / DISCOVERY
Two weeks of listening.
Architecture review, cost review, interviews with platform, security, finance.
⏱ 2 wks [03] / DRAFT
Reference architecture and ADRs.
Documented, costed. Reviewed with your team, not at them.
⏱ 1–2 wks [04] / HANDOFF
You own the artefacts.
Repo, diagrams, decisions, roadmap. Quarterly review optional, not bundled.
⏱ 1 wkQuestions we get asked about strategy.
[01] We already have a strategy deck. What's different? +
We don't ship decks. We ship ADRs, a target architecture, a cost model, and a written roadmap. Things your engineering team can act on without re-interpreting.
[02] Do you push a specific cloud? +
No. We go deep on AWS and Azure, and we'll tell you honestly when GCP fits better. We compare on data residency, support model, total cost over three years, exit cost.
[03] How is AI baked into the strategy? +
Data residency, identity for service-to-service AI, observability that includes AI usage and cost. We name the trade-offs (latency, vendor risk, hallucination class) and write them into the ADRs.
[04] Can you start before we know what we want? +
Yes. The 45-minute audit is the entry point. We send a written summary either way. If we're not the right team, we say so.
[NEXT STEP]