TL
The short answer

The cloud spend KPIs a CFO should track are unit cost, commitment coverage, commitment utilization, forecast accuracy, allocation coverage, and the cost of identified waste. Together they answer the only questions finance actually cares about: is cloud getting more efficient per unit of business, are we capturing the discounts available without wasting them, can we predict the bill, and does every dollar have an owner. Absolute spend is context, not a headline, because a growing company should expect cloud to grow; what matters is whether it grows efficiently. These six work the same across AWS, Azure, GCP, and OCI, because they sit above provider specifics and measure financial control, not engineering detail.

A good FinOps program already produces a median reduction of 31 percent in the first 90 days; the KPIs below are how a CFO confirms that gain is real and keeps it from eroding. Here is what each one measures and why it belongs on the finance dashboard.

Unit cost: is cloud getting more efficient?

Unit cost is cloud spend divided by a unit of business value: per customer, per transaction, per order, or per unit of revenue. It is the single most important cloud metric for finance because it ties spend directly to margin. Absolute spend rising is not a problem if cost per unit falls, and spend staying flat while the business doubles is a genuine win that an absolute number would hide. Pick the unit that maps to how the company makes money, track it monthly, and a CFO can finally say whether cloud is helping or hurting gross margin.

Commitment coverage and utilization: are discounts working?

These two are read as a pair. Coverage is the share of eligible usage sitting under a discount instrument such as Savings Plans, Reserved Instances, Azure Reservations, the Azure Savings Plan, Committed Use Discounts, or Universal Credits. Utilization is the share of the commitment you bought that is actually being used. High coverage with low utilization means you over committed and are paying for discounts you waste. High utilization with low coverage means you are leaving savings on the table by running too much on demand. The healthy zone is high on both, reached by committing to a defensible forecast floor rather than to a current run rate. Treat any provider discount range as indicative until verified against the current pricing terms.

Forecast accuracy: can finance trust the number?

Forecast accuracy measures how close last period's projection landed to actual spend. A program that cannot forecast within a reasonable band cannot plan, cannot commit confidently, and cannot give the board a number it will stand behind. Tracking the variance turns forecasting into a discipline that improves, and it exposes the drivers, a launch, a model change, a runaway environment, that caused the miss. For finance, a tightening forecast band is as valuable as a lower bill, because predictability is what lets the rest of the plan hold.

KPIWhat it answersHealthy direction
Unit costIs cloud efficient per unit of business?Falling per unit
Commitment coverageAre we capturing available discounts?High, matched to a floor forecast
Commitment utilizationAre bought discounts being used?High, near full
Forecast accuracyCan we predict the bill?Tightening variance
Allocation coverageDoes every dollar have an owner?Rising toward complete
Cost of identified wasteHow much known waste remains?Falling, then held low

Table: the six cloud spend KPIs for finance and the direction each should move.

Allocation coverage and the cost of waste

Allocation coverage is the share of spend mapped to an owning team, product, or cost centre. Until allocation approaches complete, showback and chargeback are guesswork and no team feels accountable, so this metric underpins every other. The cost of identified waste is the running total of known, actionable inefficiency, idle resources, oversized instances, orphaned storage and load balancers, that has been found but not yet removed. Tracking it turns optimization into a backlog finance can hold engineering to, and watching it fall and then stay low is the proof that governance is operating, not just promising.

A worked example

Worked example

A Fortune 500 retailer reported cloud to the board as a single growing number, and every review became an argument about whether it was too high. Introducing the six KPIs changed the conversation. Unit cost per order, tracked monthly, showed cloud falling per order even as total spend rose with the business. Coverage and utilization read together exposed a block of underused reservations, which were corrected. Allocation coverage climbed as teams were mapped, and the cost of identified waste gave finance a backlog to drive down. The same disciplined program delivered a reduction in line with the 31 percent median in the first 90 days, and the board stopped debating the absolute number. Figures are verified against billing data and anonymised.

Where this fits the wider program

These KPIs are the reporting layer of a FinOps operating model. The accountability behind them comes from aligning procurement and engineering, the maturity to sustain them is assessed in the governance maturity checklist, and the data they rest on must be trustworthy, which is the subject of audit trails for cloud financial data. The full governance picture lives in the FinOps operating model guide, which links up to the cross cloud cost optimization guide.

Frequently asked questions

What is the single most important cloud KPI for a CFO?
Unit cost: cloud spend per unit of business value, such as per customer, per transaction, or per unit of revenue. Absolute spend rising is not a problem if it falls per unit, and spend flat while the business grows is real progress. Unit cost connects cloud directly to margin.
How should a CFO measure commitment health?
Two paired metrics: coverage, the share of eligible usage under a discount, and utilization, the share of purchased commitment actually used. High coverage with low utilization means wasted discounts; high utilization with low coverage means discount left on the table. They only make sense read together.
Should the CFO track absolute cloud spend?
As context, not as the headline. Absolute spend shows the size of the line but not its efficiency. A growing company should expect cloud spend to rise, so the governing metrics are unit cost, forecast accuracy, and commitment health, read against the business volume behind them.

Build your CFO cloud dashboard with us

We stand up these KPIs across your AWS, Azure, GCP, and OCI estate and connect them to the operating model that keeps them honest, with zero provider commissions. Our guarantee: we reduce your cloud spend or we reimburse our service fee. Pricing is either a Fixed Fee scoped up front or Gainshare, a share of verified savings with no retainer and no risk.

Independent · buyer-side

Put a defensible number on your cloud spend.

No provider in the room, no published price list. Tell us your footprint and we will scope the savings against your billing data — we reduce your cloud spend or we reimburse our service fee.

Buyer-side intelligence, monthly.

The Cloud Spend Navigator: what changed in cloud pricing, commitments, and FinOps — no vendor spin.