FinOps Maturity Model: Moving from Crawl to Walk to Run

Why Maturity Models Matter for FinOps

The FinOps Foundation's Crawl–Walk–Run framework is one of the most practical constructs in enterprise cloud financial management. Unlike prescriptive maturity frameworks that treat all organisations as identical, this model acknowledges that the right level of maturity for any given capability depends entirely on the organisation's environment, scale, and business objectives. You do not need to achieve Run-stage maturity across every FinOps capability to generate significant value — and chasing Run prematurely is one of the most common ways enterprise FinOps programmes fail.

What the model does exceptionally well is give teams a shared language. When a CTO says "we need to get serious about cloud costs" and a FinOps practitioner says "we are mid-Walk on allocation and early-Crawl on forecasting," both parties have enough shared vocabulary to have a productive conversation about investment and prioritisation. That shared language is often the first and most important thing a new FinOps programme should establish.

This guide is part of our broader FinOps enterprise framework implementation guide, which covers the full programme lifecycle from initial business case through to governance at scale.

Stage One: Crawl — Building the Foundation

The Crawl stage is characterised by limited visibility, manual processes, and a basic acknowledgement that cloud costs need governance. Organisations in this stage typically have cloud bills arriving as a surprise each month, tagging compliance below 40 percent, and no consistent mechanism for attributing costs to the business units generating them.

What Good Looks Like at Crawl

A well-executed Crawl stage should produce four core outputs: a cost visibility dashboard covering at least 80 percent of cloud spend, a basic tagging taxonomy applied to new resources, an initial mapping of spend to business units or teams, and a documented understanding of the top ten cost drivers. None of these require automation or specialised tooling — they can be built with native cloud cost management tools and a spreadsheet.

The most important cultural outcome of the Crawl stage is establishing that cloud cost is a shared responsibility, not a finance problem. Engineering teams need to see cost data alongside performance and reliability metrics. That shift in mindset is harder than the technical work and takes longer to embed.

Common Crawl-Stage Failures

Organisations that struggle in Crawl typically fall into one of three traps. The first is over-investing in tooling before establishing data quality — buying a sophisticated FinOps platform when the underlying tagging and allocation structure is too inconsistent for any tool to produce reliable outputs. The second is treating Crawl as a finance exercise rather than an engineering enablement exercise, which produces dashboards nobody in engineering uses. The third is failing to secure executive sponsorship, which means the FinOps team has visibility without the authority to act on what they see.

Stage Two: Walk — Building Accountability

The Walk stage is where most enterprise FinOps programmes spend the majority of their operational life. It is also where the most value is generated and — paradoxically — where organisations most frequently stall. Walk is characterised by structured cost allocation, automated reporting, initial chargeback or showback models, and the beginning of proactive optimisation rather than reactive cost firefighting.

What Good Looks Like at Walk

At a well-executed Walk stage, tagging compliance should be above 80 percent, cost reports should be generated automatically on at least a weekly cadence, and engineering teams should be receiving cost anomaly alerts before the bill arrives rather than after. Showback models — where costs are allocated to business units without financial consequences — are typically implemented before chargeback models, as they build the engagement and data trust required for cost ownership to stick.

Walk-stage organisations should also be actively managing Reserved Instance and Committed Use Discount coverage, targeting 70–80 percent coverage of steady-state workloads. This alone typically delivers 20–30 percent savings on covered compute. Our guidance on FinOps and AWS negotiation integration covers how committed use strategies interact with broader commercial negotiation to compound savings.

The Walk stage also requires establishing the FinOps operating cadence — monthly cost reviews, quarterly planning sessions, and a defined escalation path for anomalies. Without cadence, even well-designed Walk programmes drift back toward reactive management.

The Walk-to-Run Transition Blocker

The most common reason organisations stall at Walk is the absence of engineering ownership. FinOps practitioners can build perfect dashboards and send accurate cost reports to every team in the business, but if engineering managers do not treat cost as a first-class metric alongside latency and uptime, the programme generates information without generating action. Transitioning to Run requires embedding cost accountability in engineering sprint planning, deployment pipelines, and architecture review processes — not just in monthly finance reviews.

Stage Three: Run — Embedding FinOps in Engineering Culture

The Run stage is achieved when FinOps is no longer a separate function reviewing engineering decisions after the fact, but is embedded in how engineering teams design, build, and operate cloud services. At Run, cost optimisation happens continuously and automatically, forecasting accuracy is high enough to inform commercial commitments, and unit economics are tracked as standard business metrics alongside revenue and margin.

What Good Looks Like at Run

Run-stage organisations operate with near-real-time cost visibility, automated anomaly detection and response, and forecasting models accurate to within five to ten percent across a twelve-month horizon. Commitment coverage (Reserved Instances, Savings Plans, CUDs) is managed dynamically rather than reviewed annually. Engineers use internal cost benchmarks to evaluate architectural decisions before deployment, and cost per customer or cost per transaction is reported alongside standard business KPIs to leadership.

The FinOps team at Run stage spends the majority of its time on strategic value work — unit economics modelling, commercial negotiation support, multi-cloud optimisation, and AI and SaaS cost governance — rather than operational reporting and allocation. Our work on FinOps enterprise software governance describes how Run-stage organisations extend this discipline beyond cloud infrastructure into software licensing and SaaS.

Run Stage Does Not Mean Finished

A critical misconception about the Run stage is that it represents a destination. In practice, the FinOps Foundation's own framework is explicit that maturity should be calibrated to the capability and the context, not pursued uniformly. A Run-stage programme in public cloud infrastructure management may still be at Crawl for SaaS cost management, AI spend governance, or data centre FinOps — all of which are increasingly included in the FinOps Cloud+ scope. The target is always appropriate maturity for each capability domain, not Run everywhere.

Transition Criteria: How to Know You Are Ready to Advance

Organisations often advance maturity stages prematurely because they conflate tool deployment with capability maturity. The following criteria provide a more rigorous assessment for each transition:

Crawl-to-Walk Readiness Checklist

• At least 80 percent of cloud spend is tagged and attributable to a business owner
• Cost reports are generated automatically and reviewed by at least one engineering team monthly
• At least one executive sponsor has active involvement in FinOps governance
• The top five cost anomalies from the previous quarter have been investigated and documented
• A tagging policy exists, is enforced for new resources, and is remediating existing untagged resources on a defined schedule

Walk-to-Run Readiness Checklist

• Chargeback or showback models are active and accepted by business unit owners
• Reserved Instance or Committed Use Discount coverage exceeds 70 percent of eligible steady-state workloads
• At least one engineering team includes cost metrics in sprint reviews as standard practice
• Forecasting accuracy for the previous six months is within 15 percent of actuals
• A defined FinOps operating cadence exists and is followed consistently by all stakeholder groups
• Cost anomaly detection is automated and generates actionable alerts, not reports requiring manual review

Extending FinOps Maturity Beyond Cloud

The FinOps Foundation's 2025 and 2026 framework updates formalised what practitioners had been implementing for several years: FinOps maturity applies not just to public cloud infrastructure but to the full technology spend portfolio. The Cloud+ scope now includes SaaS, software licensing, AI compute, and on-premises infrastructure — all managed through the same Crawl–Walk–Run progression.

For most enterprises, cloud infrastructure FinOps is the most mature capability, followed by SaaS management, with software licensing and AI spend management at earlier stages. The Crawl-stage work for software licensing involves establishing a complete licence inventory and basic allocation. Our analysis of FinOps for enterprise software licensing covers how procurement data intersects with FinOps practice across the licence estate.

Oracle customers operating OCI alongside commercial licence estates have specific maturity considerations. The intersection of cloud consumption management and licence compliance in Oracle environments is covered in our guide to the Oracle OCI FinOps framework, which addresses OCI CUDs, licence bring-your-own rights, and support cost governance in a single integrated model.

The Role of Commercial Negotiation in Maturity Progression

One dimension of FinOps maturity that practitioners frequently underestimate is its relationship to commercial negotiation. Walk-stage organisations use cost data to understand their consumption patterns. Run-stage organisations use cost data as negotiation leverage — presenting cloud provider account teams with detailed utilisation, coverage, and forecast data to extract better commercial terms at renewal.

The progression from internal cost visibility tool to commercial negotiation asset is one of the most high-value transitions in the entire FinOps maturity journey. A FinOps programme that reaches Run stage for cloud infrastructure but never connects its data to the procurement and renewal cycle is leaving significant value on the table. The benchmark for FinOps-enabled commercial negotiation typically shows 15–35 percent improvement in committed discount rates compared to organisations negotiating without structured cost intelligence.

Next Steps for Your FinOps Programme

Advancing FinOps maturity is not a project with a defined end date — it is an organisational capability development programme that evolves alongside your technology environment and commercial relationships. The most important next step is an honest assessment of where your programme genuinely sits today across the core FinOps capability domains, not where you aspire to be.

For organisations at Crawl, the priority is establishing reliable cost allocation before investing in optimisation tooling. For organisations at Walk, the priority is engineering ownership and commitment programme optimisation. For organisations approaching Run, the priority is connecting FinOps data to commercial strategy and extending the practice to SaaS and licensing.

If you are building or advancing a FinOps programme and want independent guidance on sequencing your capability investments, our enterprise FinOps advisory specialists work with organisations at every maturity stage. Contact us via the Redress Compliance contact page to arrange an initial maturity assessment.