"How mature is our FinOps practice?" is a question every cloud leader eventually asks, usually right after a budget review goes badly. The FinOps maturity model gives you a structured way to answer it and to decide what to improve next.
What is the FinOps maturity model?
The FinOps maturity model is a framework from the FinOps Foundation that rates each FinOps capability at one of three levels: Crawl, Walk or Run. Capabilities include cost allocation, anomaly management, forecasting, commitment management, budgeting and workload optimisation, among others.
Two principles matter most:
- Maturity is per capability. You might be at Run for commitments and Crawl for forecasting.
- Run is not always the goal. Invest where the business value justifies it.
What do Crawl, Walk and Run look like?
| Dimension | Crawl | Walk | Run |
|---|---|---|---|
| Visibility | Monthly invoice review | Daily dashboards by team | Real-time, self-service, unit costs |
| Allocation | Under 50% allocated | 80%+ allocated | 90%+ allocated, shared costs distributed |
| Anomalies | Found at month-end | Alerts to a central team | Routed to owners, resolved within a day |
| Commitments | Ad hoc purchases | Planned, reviewed quarterly | Automated, layered, continuously tuned |
| Forecasting | Spreadsheet estimates | Driver-based by team | Integrated with business planning |
| Culture | FinOps is finance's job | Engineering participates | Cost is a design requirement |
How do you assess your FinOps maturity?
Run a simple self-assessment:
- List the capabilities that matter most to you today. Start with five or six.
- Score each one Crawl, Walk or Run using evidence, not opinion. "Do we have 80% of spend allocated?" is better than "Do we understand our costs?"
- Interview each persona. Finance, engineering, product and leadership often rate the same capability differently. That gap is itself useful data.
- Choose two or three priorities for the next quarter based on business impact.
- Reassess every quarter.
How do you move from Crawl to Walk?
Crawl-to-Walk is where most organisations get the fastest return. Focus on:
- Enforcing a small tag schema and reaching 80% allocation (how to do it)
- Enabling anomaly detection with owner routing
- A weekly cost review per team
- Basic training so finance understands cloud pricing and engineers understand cost drivers
How do you move from Walk to Run?
Walk-to-Run is about automation and business alignment:
- Unit economics, such as cost per order or cost per customer
- Automated commitment management and rightsizing
- Policy-as-code guardrails that prevent waste at creation
- Forecasts built from business drivers and fed into financial planning
- Cost considered in architecture reviews before anything is built
Which KPIs show FinOps maturity?
Track a small set over time:
- Percentage of spend allocated
- Commitment coverage and utilisation
- Mean time to detect and resolve cost anomalies
- Forecast variance
- Unit cost trend
- Percentage of engineers trained in FinOps fundamentals
Why does training matter so much?
Most FinOps programmes stall at Walk because knowledge stays with one or two people. Moving up requires that finance, engineering and leadership all share a common language. That is why enablement is a core part of a durable practice, not an optional extra.
Most FinOps programmes stall at Walk because knowledge stays with one or two people.
How Crozaint approaches FinOps maturity
Crozaint's FinOps Starter Package is designed to move organisations from Crawl to a solid Walk in 60–90 days. The final phase, Enablement (weeks 9–12), focuses on exactly what usually stalls programmes: team training, a governance framework and a prioritised maturity roadmap.
Every engagement includes an AI FinOps LMS, a training platform aligned to the FinOps Foundation framework with role-based learning paths for finance, engineering and leadership. Clients who continue to Managed FinOps Services (85% of Starter Package clients do) get quarterly maturity advancement as part of the retainer.
Common mistakes to avoid
- Scoring the whole organisation with a single maturity level
- Trying to reach Run on every capability at once
- Assessing maturity by opinion rather than evidence
- Skipping training and relying on one FinOps expert
- Never reassessing after the first scorecard
Conclusion
The FinOps maturity model is a compass, not a scorecard. Assess honestly, pick a few priorities, train your people and reassess every quarter.
Want an outside view of your FinOps maturity? Book a 30-minute discovery call with Crozaint.
