Public cloud spending reached $723.4 billion globally, up 21.5% year over year. At that rate of growth, the gap between infrastructure scaling decisions and cost visibility can widen faster than existing reporting processes are designed to handle.
In many organizations, engineering teams make provisioning decisions based on performance and delivery requirements, while finance teams receive billing data that lags those decisions by weeks and lacks the granularity to explain specific changes.
A FinOps maturity model gives enterprise leaders a structured way to close that gap one capability at a time, rather than treating cost governance as a single, organization-wide transformation.
FinOps maturity is a per-capability assessment and the most effective programmes improve one capability at a time, letting each step deliver value before the next begins.
What Is A FinOps Maturity Model
FinOps maturity is assessed through a three-stage framework of crawl, walk and run. The FinOps Foundation maturity model defines this progression as a structured way for organizations to move from basic cost visibility to full-scale, automated cloud financial governance, with increasing scale and complexity at each stage.
The framework’s core principle sets it apart from other maturity models. Maturity is measured per capability, not as a single organization-wide score. A team may run advanced automation in anomaly detection while staying at a foundational stage in forecasting, and that unevenness is expected. The goal is not reaching run across every capability, but performing each one at the maturity level appropriate for the environment.
The numbers reflect why this matters. Cloud infrastructure runs at an average waste rate of 35%, and that figure holds even among top-quartile operators. The underlying cause is consistent: deployment tends to scale faster than the governance practices needed to manage its cost.
The Three Stages Of FinOps Maturity Explained
Each stage of the FinOps maturity model reflects a distinct posture toward visibility, forecasting and governance. Progression between stages depends on tooling maturity, tagging discipline and the degree of coordination between finance and engineering teams, factors that vary significantly across organizations. Together, these stages form the backbone of a practical cloud cost governance framework that organizations can apply consistently across business units.
Crawl: Cost visibility exists but stays basic. Teams can see billing data at the account or service level, though tagging coverage is often incomplete. Forecasting is manual, usually built from historical spend rather than workload behaviour. Governance is limited to periodic reviews rather than continuous oversight.
Walk: Allocation improves. Showback or chargeback models start assigning costs to specific business units, and automation begins replacing manual reporting. Forecasting incorporates usage trends. Governance shifts from reactive to structured, with defined ownership over cost anomalies.
Run: Cloud spend is treated as a managed, value-driven variable rather than a fixed cost. Unit economics, such as cost per customer, per feature and per transaction, become standard reporting metrics. Forecasting is continuous and tied to real-time usage signals. Governance is embedded into engineering workflows.
| Stage | Visibility | Forecasting | Governance |
| Crawl | Account or service-level billing and partial tagging | Manual, based on historical spend | Periodic, reactive reviews |
| Walk | Showback or chargeback by business unit | Usage-trend based | Structured ownership of anomalies |
| Run | Unit economics (cost per customer or feature) | Continuous, real-time signals | Embedded in engineering workflow |
Where Does Your Organization Stand On The FinOps Maturity Curve?
Most organizations assume they are further along than they actually are. Four capabilities tell you where you genuinely sit: tagging coverage, whether costs reach the teams that drive them, unit economics visibility, and whether a dedicated FinOps function exists. Run through these and the answer becomes clear.
1. Tagging Coverage: The share of cloud resources carrying complete, accurate tags is a reliable indicator of maturity stage. Crawl-stage organizations typically have partial coverage with gaps in ownership or cost-centre fields. Walk and run stages require near-complete tagging, since allocation and unit economics both depend on it.
2. Showback or Chargeback Status: Showback and chargeback are two points on the same spectrum. Showback means cost data is reported to business units for awareness. Chargeback means those units are actually held accountable against a budget. Whether an organization has moved from one to the other, or has not implemented either, is one of the clearest signals of where it sits in the crawl-to-walk transition.
3. Unit Economics Visibility: The ability to trace cost to a customer, feature or transaction is the capability that separates run-stage organizations from walk-stage ones. It connects cloud spend directly to business outcomes rather than to infrastructure categories.
4. FinOps Team Presence: A dedicated FinOps function is a sign that cost governance has moved from being a shared, ad hoc concern to a structured discipline with clear ownership. When cost management is distributed informally across engineering and finance, accountability tends to be thin and progress stalls.
Did you know, roughly 70% of large enterprises now maintain a dedicated FinOps or cloud economics team, a significant shift from just a few years ago!
Running through these four checkpoints of tagging, allocation, unit economics and team structure places most organizations somewhere between crawl and walk, with run-stage capabilities still concentrated in a smaller group of enterprises with mature governance in place. Taken together, these checkpoints offer a practical way to benchmark cloud financial operations maturity against peers.
Common Blockers To Progressing Stages
Tagging discipline is the most common blocker at the crawl-to-walk transition. Standard billing tools typically allocate spend to accounts and services rather than to the pods, containers or functions consuming resources. Enforcing consistent tagging across engineering teams with different deployment patterns is a known challenge, and gaps in coverage limit what allocation models can reliably produce.
At the walk-to-run transition, the blocker tends to shift from availability of data to its granularity and timeliness. Dashboards at this stage often report spend retrospectively rather than surfacing inefficiency as it occurs.
The engineering-finance disconnect compounds both issues. Fewer than half of developers report having real-time access to data on idle resources (43%), unused or orphaned resources (39%) and over- or under-provisioned workloads (33%). When the people making provisioning and scaling decisions are working without current data, those decisions default to guesswork.
These blockers are both technical and structural. Closing them requires better data pipelines, cleaner ownership definitions and tooling that makes cost signals visible to the people making the decisions that drive them.
Business Impact Of Higher FinOps Maturity
Organizations using FinOps frameworks are 2.5 times more likely to meet or exceed cloud ROI expectations compared to those without structured practices in place.
Waste reduction is a documented outcome of FinOps maturity progression. Organizations with advanced practices have reduced cloud waste by as much as 40%, compared to the 35% industry average.
Forecast accuracy is the third gain, and arguably the one executives feel most directly during budget cycles. Crawl-stage forecasting relies on historical spend, which lags behind actual usage patterns. Run-stage forecasting draws on continuous, real-time signals, giving finance teams numbers that hold up through the quarter rather than requiring mid-cycle correction. Cost efficiency is a stated priority for 87% of organizations, a figure that reflects how central cloud financial governance has become to broader technology investment decisions.
Across these dimensions, the relationship between maturity and outcome is consistent in the research. ROI improves, waste decreases and forecasting accuracy increases as organizations move from crawl toward run, with each capability reinforcing the next.
Path Forward
FinOps maturity progresses one capability at a time rather than through a single organization-wide transformation. Most organizations start with tagging, move to allocation and then to unit economics, with each step delivering value independently before the next begins.
The per-capability structure of the framework means that meaningful progress is possible without a complete governance redesign. Identifying which capabilities are at crawl, which are at walk and which are approaching run gives a clear view of where incremental investment would have the most immediate impact.
For organizations that want to move faster, the starting point is usually the same: better data infrastructure and clearer accountability. Those two things unlock progress across every other capability.
If your organization is looking to assess where it stands or accelerate progress through the maturity stages, Cloud Kinetics works with enterprises to build and mature FinOps practices through structured cloud cost governance.
