What are the FinOps maturity model levels Crawl, Walk, Run?

The FinOps maturity model is a progression framework defined by the FinOps Foundation that describes how organizations evolve their cloud financial management capabilities across three stages: Crawl, Walk, and Run. Each stage reflects increasing sophistication across cost visibility, accountability, optimization, and automation giving FinOps programs a structured benchmark for continuous improvement.

Why the maturity model matters

Most organizations fail at FinOps not because they lack tools, but because they attempt Run-stage complexity on Crawl stage foundations. The model helps teams identify where they actually are, what capability gaps are costing the most money, and what to prioritize next.

Stage 1: Crawl

At Crawl, organizations are establishing basic cost visibility for the first time. Cost data is pulled manually, reviewed infrequently, and allocated inconsistently. Key characteristics include:

• Tagging coverage sits below 50%, making reliable cost attribution to teams, products, or environments practically impossible at any meaningful scale.
• Reserved Instances and Savings Plans are purchased reactively  triggered by large bills rather than forward-looking analysis leaving significant discount opportunities unrealized every month.
• No designated FinOps owner exists, so cost accountability is diffuse and anomalies are discovered on the monthly invoice rather than in real time.

The primary goal at Crawl is not optimization, it is getting accurate cost data in front of the right people on a consistent schedule.

Stage 2: Walk

At Walk, organizations have established consistent cost allocation, regular reporting cadences, and begun executing optimization actions. Key characteristics include:

• Tagging coverage reaches 50–80%, enabling reliable showback or chargeback reporting to business units and product teams across most of the cloud environment.
• A designated FinOps practitioner coordinates between engineering and finance, conducts quarterly commitment reviews, and drives rightsizing recommendations through to execution.
• Commitment purchasing is now data-driven rather than intuition-based, but the review and purchase cycle remains manual, typically quarterly meaning waste accumulates between review cycles.

The primary bottleneck at Walk is execution capacity: teams know what to optimize but rely entirely on human effort to act, limiting both speed and coverage of cost improvements. The cloud cost optimization best practices that Walk-stage teams implement help close this gap.

Stage 3: Run

At Run, FinOps is embedded in engineering culture and financial planning, with optimization happening continuously and automatically. Key characteristics include:

• Commitment portfolios are continuously rebalanced by automation based on real-time usage signals, eliminating the quarterly review gap where most commitment waste originates.
• Unit economics metrics cost per customer, cost per API call, infrastructure gross margin are tracked in live dashboards and directly inform product and architecture decisions.
• AI-driven anomaly detection escalates cost deviations within hours, enabling teams to respond before issues compound across billing cycles.

Maturity comparison by dimension

What most organizations get wrong

Organizations at Crawl underestimate how quickly untagged resources accumulate, creating attribution debt that becomes exponentially harder to resolve at Walk stage. Teams at Walk over-invest in dashboards and reporting without building the feedback loop that turns insights into actions visibility without execution produces reports nobody acts on. Understanding why cloud cost management keeps failing and what teams are missing is critical before advancing between stages. At Run, the most common failure is treating automation as static, allowing commitment portfolios to drift out of alignment as workloads grow or architecture changes.

How Usage.ai accelerates FinOps maturity

The Walk-to-Run transition is the hardest stage because it requires replacing manual review cycles with automated execution, a volume of decisions that exceeds what any team can reliably handle by hand. Before committing to build this infrastructure internally, it is worth understanding the FinOps build vs buy decision and where autonomous platforms deliver faster results. Usage.ai eliminates this bottleneck by automating commitment management entirely across AWS, Azure, and GCP:

• Its fully autonomous Autopilot continuously purchases and rebalances commitments using AI/ML-powered analysis of real-time usage data, removing the quarterly review cycle that defines Walk-stage operations.
• Its cashback and credits guarantee on any underutilization means organizations reach Run-stage commitment efficiency without needing to build the internal risk management infrastructure that normally takes years to develop.
• Setup requires billing-layer access only no infrastructure changes, no engineering involvement removing the implementation friction that typically delays maturity advancement by six to twelve months. See how Usage AI works. 

Bottom line

The FinOps maturity model is most useful as a diagnostic tool, not a sequential checklist. Most organizations are Run in some areas and Crawl in others simultaneously. The highest-leverage move is to identify the single capability where immaturity is generating the most financial waste, typically commitment management and advance that area first.