The CFO's Cloud Stack

What a CFO actually owns in the cloud estate — cost visibility, forecasting discipline, FinOps cadence, and the continuous optimisation muscle that keeps cloud spend governable rather than mysterious.

BusinessCapabilityTechnology
Compass
  • Businesspersona, use case, outcome
  • Capabilitywhat the org needs to do
  • Technologythe technology choices
Guided journey · Step 1 of 4

Cost Visibility & Allocation

Stand up tagged cost visibility before anything else. You can't optimise what you can't allocate.

~ 6 weeks

Search any SKU, capability, risk, or source on this map.

Filter by type

Narrative intro

Cloud cost is the line item every CFO has had a surprise about. This map names the discipline that prevents the surprise: tagged visibility, governed forecasting, FinOps cadence, and continuous optimisation. None of it requires more SKUs than the CIO already owns — it requires the rhythm to use them.

Key takeaways

  • Visibility before optimisation — you can't allocate what isn't tagged
  • Forecasting belongs in the regular planning cycle, not on a separate calendar
  • FinOps cadence is quarterly, with platform and product owners present
  • Continuous optimisation — reservations, right-sizing, idle cleanup — is a platform discipline

Programme shape

Estimated duration
12–26 weeks
Estimated FTE
0.5 FTE FinOps practitioner + part-time platform and finance partners
Spend tier
moderate
Risk level
low

FinOps maturity is a rhythm story — visibility, forecasting, optimisation, then governance. Skipping a step leaves cost discipline performative rather than load-bearing.

Back to all maps