FinOps Pilote by AB Conseil
Guide · Steering

FinOps KPIs: the indicators to track, with their targets

A good FinOps dashboard fits in about ten indicators. Here are the ones we track at the SteerCo, how to compute them, and the targets we aim for.

By Aymeric Boucher · 20 October 2026 · 3 min read

Visibility

KPIFormulaIndicative target
TaggingCost tied to a CMDB application / total cost≥ 95%
Metric coverageVMs reporting usage metrics / total VMs100%
Scopes under budget alertScopes with an active alert / total scopes100%

Efficiency

KPIFormulaIndicative target
Commitment coverageEligible compute covered by an RI or savings plan / eligible compute≥ 80%
Commitment utilizationCommitment consumed / commitment purchased≥ 95%
Effective Savings Rate1 − actual compute cost / on-demand costIncreasing
RightsizingCorrectly sized VMs / total VMs≥ 90%
Non-prod and VDI Stop/StartNon-prod VMs running less than half the time / non-prod VMs≥ 80%
Realized / identified savingsSavings measured on the bill / savings recommendedIncreasing

Steering

KPIFormulaIndicative target
Forecast accuracyGap between forecast and actual, in %Under 5 to 10%
Unit cost (unit economics)Cloud cost / business unit (customer, order, transaction)Stable or decreasing
Average cost per VMFull monthly VM cost, disks included / number of VMsDecreasing
Anomaly detection timeTime between the start of a drift and the alertUnder a day
FinOps scoringMaturity score out of 100, per application or business unitIncreasing
Carbon intensitykg CO₂e per VM or per business unitDecreasing

How to keep them alive

  • A dashboard refreshed daily, with each KPI overall and by business unit: see our FinOps dashboard.
  • A monthly SteerCo that looks at the gaps to targets and decides on actions.
  • Few indicators: ten tracked KPIs beat forty ignored ones.

The targets above are orders of magnitude observed in our engagements. They adjust to your maturity: the aim isn't “Run” everywhere.

FAQ

What are the most important FinOps KPIs?

Tagging, commitment coverage and utilization, rightsizing, forecast accuracy and unit cost. They tell whether costs are visible, efficient and steered.

What is the Effective Savings Rate?

The saving actually achieved on compute through commitments, relative to what the same consumption would have cost on demand.

What reservation coverage should you target?

At least 80% of steady compute, with commitment utilization of at least 95%. Beyond that, the risk of paying for nothing increases.

Aymeric Boucher has been a FinOps consultant for 8 years and is the founder of FinOps Pilote. He works with large international enterprises and SMEs on Azure and AWS, and has delivered more than €20M in cloud savings. Learn more →

First conversation

How much are you losing every month on a poorly optimized cloud?

SMEs: we are paid 20% of the annual savings achieved. Large enterprises: day-rate engagement. A first 30-minute conversation, no commitment.