FinOps maturity is described with a Crawl, Walk, Run model: a simple way to gauge how deeply cloud financial management is embedded across your organization. Crawl is basic visibility and reactive, ad hoc action. Walk is consistent process, automation, and broad adoption. Run is cost as a continuous, near-real-time input to how every team builds and decides. The point of the model is not a badge; it is to tell you what to do next, because each stage has a characteristic bottleneck.
This article is part of our FinOps cluster. For the foundation, start with what is FinOps, a practical introduction for 2026, the pillar this guide links up to. Maturity advances across all three phases of the operating model, so it pairs closely with the sibling guide on the FinOps operating model, Inform, Optimize, Operate.
Crawl: visibility and first wins
At the Crawl stage, an organization has started to look at cloud cost but acts on it reactively. There is some reporting, tagging is partial, and optimization happens in occasional fire drills, usually after a bill shock. Coverage of commitments and rightsizing is low, and there is often one person or a small team carrying the whole effort informally. Crawl is a normal and necessary starting point; the risk is staying there, treating each cost spike as a one-off rather than building the habit.
Most organizations that think they have a FinOps practice are actually stuck in Crawl: they react well to bill shocks but have no continuous process. A strong one-off cleanup feels like progress, but if spend creeps back, you have not left Crawl. The exit is process, not effort.
Walk: consistent process and adoption
At the Walk stage, FinOps is a defined practice rather than a reaction. Tagging coverage is high and enforced, there is a regular cost review, budgets and anomaly alerts are in place, and commitment and rightsizing decisions follow a repeatable process. Importantly, more teams are involved: engineering takes some ownership of cost, finance has reliable forecasts, and a central FinOps function enables rather than polices. Most organizations that take cloud cost seriously can reach and sustain Walk, and for many that is the right ceiling.
Run: cost as a continuous input
At the Run stage, cost is a normal, near-real-time consideration in everyday decisions. Engineers see the cost impact of changes as they make them, unit economics like cost per customer or per transaction are tracked and improving, commitment portfolios are actively managed, and automation handles routine optimization. Run is hard to reach and harder to sustain, and not every workload needs it. The mark of Run is not perfection but that cost-aware behavior is the default rather than something a central team has to drive.
Maturity is per capability, not one global score
A common mistake is assigning the whole organization a single maturity level. In reality you are at different stages for different capabilities: perhaps Run on visibility, Walk on rightsizing, and Crawl on unit economics. That is normal and useful, because it points precisely at where to invest. Assess maturity capability by capability, and your roadmap writes itself: pick the capability holding back the most value and move it up one level.
Want an honest read on your FinOps maturity?
We assess your practice capability by capability, show where you really sit against Crawl, Walk, Run, and lay out the specific moves to advance the ones that matter most. On the performance model, you pay only from realized savings. No savings, no fee.
Talk about FinOps implementation →How to move up a level
Advancing is rarely about working harder at what you already do; it is about adding the missing structure. Crawl to Walk is about process and enforcement: a regular review, enforced tagging, a repeatable optimization cadence, and a named function. Walk to Run is about embedding and automation: putting cost data in front of engineers in their own tools, tracking unit economics, and automating routine actions so the central team is freed for strategy. The sibling guide on how to build a FinOps team and operating structure covers the staffing that underpins each jump.
| Stage | Hallmark | Bottleneck to clear |
|---|---|---|
| Crawl | Partial visibility, reactive fixes | No repeatable process |
| Walk | Defined process, broad adoption | Cost not yet in daily decisions |
| Run | Cost is a continuous default | Sustaining it without central push |
Crawl, Walk, Run is the FinOps Foundation's published maturity model. Its definitions are periodically revised, so confirm the current wording on the FinOps Foundation site before using it in a formal assessment.
The FinOps Operating Model Blueprint includes a capability-by-capability maturity assessment template and the specific moves that advance each one, so you can build a real roadmap rather than a vanity score.
The short version
FinOps maturity runs Crawl to Walk to Run: from partial visibility and reactive fixes, to defined process and broad adoption, to cost as a continuous default in every decision. Assess it per capability rather than as one global score, and advance by adding the missing structure, not by working harder. When you want an honest maturity read and a roadmap to advance, that is part of what our FinOps implementation service delivers.