FinOps for CFOs

A CFO's view of running cloud spend as a discipline rather than a line item — visibility, optimisation, forecasting, and the operating cadence that converts cost data into business decisions. The FinOps Foundation framework applied to a Microsoft cloud estate.

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

Cost Visibility & Allocation

Start here. Cost visibility is the load-bearing precondition for everything else. Tag enforcement, allocation hierarchy, showback by business unit — without these, forecasting is fiction and optimisation is theatre.

~ 6 weeks

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

Filter by type

Narrative intro

Cloud spend is the third-largest line item for most enterprise CFOs after compensation and real estate — and the only one that can grow 30% year-on-year while the headcount holds steady. The CFO question isn't whether cloud is expensive; it's whether the spend is predictable, attributable, and continuously optimised. This map covers the four FinOps pillars that produce credible answers to all three. The FinOps Foundation framework structures the work as Inform → Optimise → Operate, and that order matters. Visibility first — you can't optimise what you can't see, and you can't forecast what you can't attribute. Optimisation next — weekly triage, not annual sweeps. Forecasting third — budgets per business unit with named owners, not central spreadsheets. Operating cadence underneath all of it, running forever.

Key takeaways

  • Cloud spend is the line item that can grow without headcount. FinOps is the discipline that keeps growth on purpose.
  • Inform → Optimise → Operate. Visibility before optimisation; optimisation before chargeback; chargeback before unit economics. Skipping a step produces unsustainable noise.
  • The tooling is mostly free or already paid for. The investment is in operating shape and people — a FinOps lead, BU champions, monthly cadence.
  • Board reporting on total cloud bill is the wrong metric — it grows with the business. Unit economics (cost per transaction, per customer, per BU revenue) is the metric the board can act on.

Programme shape

Estimated duration
16–40 weeks
Estimated FTE
FinOps lead, finance analyst, platform-engineering partner, business-unit FinOps champions. Mid-market 2–3 FTE; enterprise 4–6 plus part-time BU champions.
Spend tier
minimal
Risk level
moderate

Mostly free or already-paid tooling — Cost Management is free for Azure, Power BI typically already in the estate. The investment is in operating shape and people, not procurement. Risk shifts to elevated if showback is launched before tag hygiene is established — the reports will be wrong, finance loses trust, the programme stalls.

Back to all maps