FinOps is a culture, not a spreadsheet
Mature FinOps is not a quarterly cost review. It is a continuous practice where engineering, finance, and product teams share accountability for cloud value.
The maturity model
- Crawl — visibility. Tag, report, and assign cost to teams.
- Walk — optimisation. Rightsizing, savings plans, scheduled scaling.
- Run — forecasting and unit economics. Cost per transaction, per tenant, per feature.
The accountability gap
The biggest blocker to FinOps maturity is the gap between the people who spend (engineering) and the people who pay (finance). Close it with shared dashboards and showback reports tied to business metrics.
From cost to value
Mature teams stop asking 'how much did we spend?' and start asking 'what did that spend buy us?' — measured in unit economics like cost per active user or cost per pipeline run.

