The FinOps cost maturity model is the FinOps Foundation's Crawl, Walk, Run scale for grading how advanced each FinOps capability is in your organization. Crawl is mostly manual and reactive, Walk adds defined processes and partial automation, Run is continuous, automated, and measured against targets. You grade every capability separately, because a practice is rarely uniform: allocation might be at Walk while commitment management is still at Crawl. Use it as a diagnostic to find the weakest capabilities that gate your savings, set a realistic target stage for each, pick the moves that close the gap, and re-score on a quarterly cadence. Not every capability needs to reach Run; aim for the maturity your spend profile justifies. This is the same assessment lens we apply across 500+ environments to sequence a 31% average bill reduction.
The FinOps cost maturity model is the framework that tells you how advanced your cloud cost practice actually is, capability by capability, rather than by gut feel. It uses three stages, Crawl, Walk, and Run, and the value is in the diagnosis: it shows where your practice is weak, what is gating better cost outcomes, and what to invest in next. This guide defines the model and gives you a step-by-step way to use it. It is part of our practical introduction to FinOps, the cluster this article links up to.
What is the FinOps maturity model?
The FinOps maturity model is a three-stage scale, Crawl, Walk, and Run, that the FinOps Foundation defines for assessing how developed each capability in a FinOps practice is. It is deliberately not a single overall grade. The Foundation's framework breaks FinOps into domains and capabilities, such as allocation, anomaly management, forecasting, rate optimization, and workload optimization, and the model asks how mature each one is on its own. A practice can be at Run on visibility and still at Crawl on commitment management, and that unevenness is exactly what the model is built to expose.
What do Crawl, Walk, and Run mean?
Crawl, Walk, and Run describe how automated, continuous, and measured a capability is. Crawl is the starting point: visibility is basic and mostly manual, action is reactive, and processes are ad hoc. Walk is the working middle: most of the capability is addressed, processes are defined, automation covers the common cases, and the organization acts on the data with some consistency. Run is the mature end: the capability is highly automated, runs continuously, is measured against explicit targets, and is owned across engineering, finance, and product. The model assumes you climb in order, because Run-level automation only pays off once the Walk-level process underneath it exists.
The three maturity stages at a glance
| Stage | Visibility | Automation | Action | Measurement |
|---|---|---|---|---|
| Crawl | Basic, manual reports | Little to none | Reactive, ad hoc | Few or no metrics |
| Walk | Most spend allocated | Common cases automated | Defined processes, acted on regularly | Key metrics tracked |
| Run | Near-complete, real time | Continuous and automated | Proactive, embedded in delivery | Targets set and measured against |
Verdict: grade each capability against these rows separately. The pattern of stages across your capabilities is the real output, not a single number, and it tells you where the next dollar of effort returns the most.
How do you use the FinOps maturity model? A step-by-step method
Use the model as a repeatable assessment, not a one-time audit. The following five steps turn the Crawl, Walk, Run scale into a prioritized plan, and they pair directly with the scorecard in our companion guide on how to build a FinOps capability assessment scorecard.
- Score each capability. Rate every FinOps capability your team performs against the Crawl, Walk, Run descriptions and record the current stage per capability, not a single overall grade. The result is a row per capability.
- Find the constraint. Identify the lowest-scoring capabilities that block the others, such as allocation or anomaly management. Maturity is gated by the weakest links that other work depends on, not by the average.
- Set a target stage per capability. Decide the realistic next stage for each capability over the next quarter. Not everything needs to reach Run, only what drives value for your spend profile.
- Pick the moves that close the gap. For each capability, choose the concrete actions that lift it one stage, for example moving allocation from manual spreadsheets to automated tag-based showback, or anomaly management from monthly review to real-time alerts.
- Re-assess on a cadence. Repeat the scoring each quarter and track the share of capabilities at Walk or Run over time, so maturity becomes a measured trend rather than a one-off opinion.
Want an honest read on your FinOps maturity?
Our cloud cost audit scores your practice capability by capability against the Crawl, Walk, Run model, then sequences the moves that lift the capabilities actually gating your savings. On the performance model, you pay only from realized savings. No savings, no fee.
Book a cloud cost audit →How does maturity connect to value and reporting?
Higher maturity shifts a practice from cleaning up existing waste to preventing it, which changes the mix of value it produces. Early-stage practices report mostly realized savings from idle cleanup and rightsizing, because that is what manual review surfaces. As capabilities reach Run, more of the value comes from prevention and good defaults, which shows up as cost avoidance rather than a falling invoice. That is why maturity and value reporting move together, and why we treat cost avoidance versus cost savings as the sibling topic to this one. The progression itself maps onto the Lock and Run stages of our See, Cut, Lock, Run method, and a FinOps implementation is how most teams move several capabilities up a stage in a single engagement.
The FinOps Operating Model Blueprint pairs the maturity model with an operating cadence, so advancing a capability becomes a planned quarter of work rather than a vague aspiration.
Common questions about the FinOps maturity model
What are the stages of the FinOps maturity model?
The FinOps Foundation maturity model uses three stages: Crawl, Walk, and Run. Crawl means basic, mostly manual visibility and reactive action. Walk means most capabilities are addressed with some automation and defined processes. Run means capabilities are highly automated, continuous, and measured against targets. You score each capability separately rather than assigning one overall grade.
Does every capability need to reach Run?
No. The goal is the right maturity for your spend profile, not Run everywhere. A capability only needs to advance where the cost or risk justifies the effort. A team with simple, steady workloads may rationally leave some capabilities at Walk while pushing allocation and anomaly management to Run.
How is the maturity model different from a capability assessment?
The maturity model is the Crawl, Walk, Run scale you grade against; a capability assessment is the exercise of applying that scale across every capability to produce a scorecard. The model is the ruler; the assessment is the measurement. You use the model inside the assessment to decide where each capability sits and where to invest next.
Written by Fredrik Filipsson and reviewed by Morten Andersen, applying our See, Cut, Lock, Run method. Independent and vendor neutral.
Cloud pricing and service behavior change frequently. Verify the specifics in this guide against the providers’ own current documentation and the FinOps Foundation: FinOps Foundation Framework ↗ and FinOps Rate Optimization capability ↗. This article also reflects Cloud Cost Room’s hands-on, vendor-neutral engagement experience.