The FinOps maturity model describes three progressive stages of cloud financial management capability: Crawl, Walk, and Run. Organizations move through these stages as they improve their ability to allocate cloud costs, build accountability across teams, and make increasingly informed decisions that balance cost, performance, and business value. This article walks through each level, how to progress between them, and what tools and frameworks support the journey.
What are the three levels of the FinOps maturity model?
The three levels of the FinOps maturity model are Crawl, Walk, and Run. Each level represents a measurable step forward in how well an organization governs, allocates, and optimizes cloud spending. At Crawl, basic visibility exists. At Walk, accountability and processes take hold. At Run, cloud financial management becomes a continuous, cross-functional discipline tied directly to business outcomes.
The FinOps Foundation, which maintains the official FinOps framework, describes these maturity levels not as a one-time progression but as a repeating cycle. An organization can be at different maturity levels for different FinOps capabilities simultaneously. For example, you might be at the Run stage for cost allocation but still at Crawl for anomaly detection or unit economics.
- Crawl: Basic cloud cost visibility is in place. Teams can see what they are spending, but there is little tagging discipline, minimal allocation, and no formal ownership of cloud costs.
- Walk: Cost allocation is more complete, tagging policies are enforced, and teams begin to take ownership of their cloud budgets. Optimization activities such as rightsizing and reserved instance purchasing happen on a regular cadence.
- Run: Cloud financial management is embedded into engineering and business workflows. Real-time data drives decisions, unit economics are tracked, and cloud spend is actively tied to business value and strategic priorities.
Understanding where your organization sits across these levels is the starting point for meaningful improvement. A FinOps maturity assessment gives you a factual baseline across people, processes, governance, and tooling before you invest in the next stage.
How does an organization move from crawl to walk in FinOps?
Moving from Crawl to Walk in FinOps requires shifting from passive visibility to active accountability. The transition happens when teams stop asking “what are we spending?” and start asking “who owns this spend and what are we doing about it?” This shift involves enforcing tagging standards, assigning cost ownership to application or product teams, and establishing a regular cadence for reviewing and acting on cloud cost data.
In practice, the Crawl-to-Walk transition typically involves several concrete steps:
- Tagging and allocation: Implement a consistent tagging policy across cloud environments so costs can be attributed to teams, products, or business units. Without reliable allocation, accountability is impossible to establish.
- Defining ownership: Assign clear responsibility for cloud budgets. Application teams and engineers need to understand that they influence cloud spend and are accountable for it, not just IT finance.
- Creating a review rhythm: Establish a recurring decision-making cadence, such as weekly or monthly FinOps reviews, where cost data is reviewed and optimization actions are prioritized and tracked.
- Starting rightsizing: Begin identifying and acting on obvious inefficiencies, such as oversized instances, idle resources, and missed savings plan opportunities across AWS, Azure, and GCP.
- Aligning finance and engineering: Break down the silo between finance, IT, and engineering so that cost conversations happen early in the delivery cycle rather than after the invoice arrives.
One of the most common reasons organizations stay stuck at Crawl is that tooling and reporting improve visibility but do not create a decision-making rhythm. Optimization remains ad hoc. Moving to Walk requires governance structures, not just better dashboards.
What does FinOps maturity look like at the run stage?
At the Run stage of FinOps maturity, cloud financial management is no longer a periodic activity but a continuous capability embedded in how teams build and operate. Organizations at this level use real-time data to make cost, performance, and risk trade-offs proactively. Cloud spending is directly connected to business value, and decisions about scaling, architecture, and investment happen with full financial awareness.
Several characteristics distinguish Run-stage organizations from those at earlier levels:
- Unit economics are tracked: Cost per transaction, cost per customer, or cost per product feature are measured and used to evaluate whether cloud investment is generating proportional business value.
- Forecasting is accurate and automated: Spend forecasts are generated from usage patterns and business plans, not manual spreadsheet exercises. Finance and engineering align on forward-looking budgets.
- Optimization is continuous: Rightsizing, commitment management, and architectural decisions are reviewed on a regular cadence, not triggered by a budget overrun.
- Governance enables rather than blocks: Policies, decision rights, and accountability structures are in place, but they are designed to accelerate value delivery, not create bureaucratic friction.
- Cloud and on-premises costs are integrated: Total technology cost, including on-premises infrastructure, is visible alongside cloud spend, enabling informed hybrid and cloud-vs-on-premises trade-off decisions.
Reaching the Run stage does not mean the work is finished. New cloud services, organizational changes, and shifting business priorities mean that FinOps maturity requires ongoing investment to maintain.
How long does it take to reach FinOps maturity?
There is no fixed timeline for reaching FinOps maturity. Most organizations take between one and three years to move from Crawl to a consistent Walk or Run capability, depending on the size of their cloud environment, the complexity of their organizational structure, and the level of executive support behind the program. Smaller, more agile organizations can progress faster; large enterprises with multiple cloud accounts and business units typically take longer.
Several factors have the most influence on how quickly an organization progresses:
- Data quality: Poor tagging and incomplete cost allocation slow every subsequent step. Organizations that invest early in a reliable data foundation progress faster overall.
- Cross-functional alignment: FinOps maturity requires finance, IT, engineering, and procurement to work together. Organizations where these functions operate in silos consistently stall at the Walk stage.
- Executive sponsorship: Without visible support from leadership, FinOps initiatives tend to remain isolated within IT finance and never achieve the cross-organizational accountability that the Run stage requires.
- Tooling investment: The right tooling accelerates progress by automating allocation, anomaly detection, and optimization recommendations. Manual processes cap scalability as cloud environments grow.
Progress is also non-linear. Many organizations reach Walk-level maturity in their core capabilities within six to twelve months, then spend additional time building toward Run in more advanced areas such as unit economics or integrated governance.
What tools support each FinOps maturity stage?
The tools that support FinOps maturity vary by stage because the problems being solved at each level are fundamentally different. At Crawl, the priority is visibility. At Walk, the focus shifts to allocation and optimization workflows. At Run, tooling needs to support automation, forecasting, and integration with broader business and IT financial management systems.
Crawl stage tools
At the Crawl stage, native cloud provider tools such as AWS Cost Explorer, Azure Cost Management, and Google Cloud Billing are often sufficient to get started. These tools provide basic spend visibility, budget alerts, and high-level breakdowns by service or account. They are useful for establishing a baseline but limited in their ability to support cross-account allocation or multi-cloud visibility.
Walk and Run stage tools
As organizations move into Walk and Run, they typically need dedicated FinOps platforms that go beyond what native tools offer. Apptio Cloudability, for example, provides multi-cloud cost allocation, container cost visibility, commitment management, and rightsizing recommendations across AWS, Azure, and GCP. At the Run stage, integration between FinOps tooling and broader IT financial management platforms becomes important, connecting cloud cost data with on-premises infrastructure costs and business value frameworks. This is where the combination of FinOps and Technology Business Management becomes particularly relevant, enabling organizations to see total technology cost in a single view and make trade-off decisions with full financial context.
How does the FinOps maturity model relate to the broader FinOps framework?
The FinOps maturity model is one component of the broader FinOps framework maintained by the FinOps Foundation. The framework defines the principles, personas, capabilities, and lifecycle phases that together describe how organizations should practice cloud financial management. The maturity model applies to each individual capability within the framework, meaning an organization can assess and improve maturity at a granular level rather than treating the entire practice as a single block.
The FinOps framework organizes cloud financial management into three lifecycle phases: Inform, Optimize, and Operate. These phases describe what needs to happen, while the Crawl, Walk, Run maturity levels describe how well an organization executes each phase. An organization at the Crawl level in the Inform phase, for example, has basic cost visibility but lacks reliable allocation. At the Run level in the same phase, it has fully automated, trusted cost data that feeds real-time decisions across teams.
The maturity model also connects directly to organizational design. The FinOps framework defines specific personas, including the FinOps Practitioner, Finance, Engineering, and Product roles, and describes how each persona’s involvement deepens as maturity increases. At Crawl, FinOps is often owned by a small team in IT finance. At Run, it is a shared responsibility embedded across the organization.
For organizations managing both cloud and on-premises infrastructure, the FinOps framework integrates naturally with strategic portfolio management and Technology Business Management, extending cloud financial discipline into a broader model for total IT cost transparency and value-driven investment decisions.
How we help you advance through the FinOps maturity model
We support organizations at every stage of the FinOps maturity journey, from establishing the foundations to embedding cloud financial management as a continuous organizational capability. Our approach is practical and grounded in where you actually are today, not where a framework says you should be.
Here is what we bring to each stage of your maturity progression:
- FinOps Maturity Assessment: We assess your current maturity across people, processes, governance, and tooling, and deliver a prioritized roadmap focused on value realization, not just cost reduction.
- Full cost allocation: We implement reliable tagging and allocation models across AWS, Azure, and GCP, including containers and support charges, so you have a trusted data foundation before building further.
- Rightsizing and optimization: We identify and act on savings opportunities across your cloud environments on a structured cadence, moving optimization from ad hoc to systematic.
- Governance and operating model design: We define decision rights, accountability structures, and review rhythms that connect finance, IT, engineering, and procurement around shared cloud cost goals.
- TBM and FinOps integration: We connect cloud cost management with on-premises IT financial management, giving you a complete view of technology spend and enabling informed hybrid and cloud-vs-on-premises trade-offs.
- Flexible delivery models: Whether you need a full managed FinOps service, advisory support for an existing practice, or temporary role coverage, we adapt to your situation without replacing your existing teams.
If you want to understand where your organization stands today and what the clearest path forward looks like, get in touch with us to start with a FinOps maturity assessment.