Key takeaway
- FinOps has three phases (Inform, Optimize, Operate) and three maturity levels (Crawl, Walk, Run). See how they differ and how to assess and raise yours.
FinOps has two separate ideas that are often confused. The three phases, Inform, Optimize and Operate, describe the repeating cycle a team runs. The three maturity levels, Crawl, Walk and Run, describe how well each capability is performed. The FinOps Foundation defines both, and this guide explains each, how to assess where you stand and how to move up. For the cost-side basics, see our guide to FinOps for AWS.
For CIOs, CTOs and platform leads the practical point is that maturity is judged per capability, not once for the whole organisation. The Foundation says the goal should never be simply to reach Run in every capability, so the useful question is which capabilities justify the effort.
What is FinOps today?
The FinOps Foundation describes FinOps as "an operational framework and cultural practice which maximizes the business value of technology", with shared financial accountability across engineering, finance and business teams. Its current definition also covers spend on SaaS, licensing, data centre and data cloud platforms, not only public cloud (FinOps Foundation: What is FinOps).
What are the three FinOps phases?
According to the FinOps Framework, the FinOps journey consists of Inform, Optimize and Operate. The phases page describes them as a repeating cycle that teams move through quickly, with different members working on different phases at different cadences.
| Phase | What the team does | Who is mostly involved |
|---|---|---|
| Inform | Examines cost, usage and efficiency data: ingestion, allocation, reporting, forecasting and unit economics. | Finance, engineering, FinOps practitioners |
| Optimize | Identifies and documents ways to improve efficiency and value. Usage optimisation uses fewer resources; rate optimisation pays an appropriate price. | Engineering (usage); procurement and leadership (rates) |
| Operate | Implements the chosen changes in small, incremental steps and can also mature capabilities or FinOps operations themselves. Loops back to Inform and Optimize. | Engineering, finance and business teams |
What are the Crawl, Walk and Run maturity levels?
The Foundation's maturity model lets organisations start small and expand scale, scope and complexity as business value justifies it. Each capability can sit at a different level. The goals in the table are the Foundation's own sample goals, not targets for every organisation.
| Level | How the Foundation describes it | Sample goals (Foundation) | Typical fit |
|---|---|---|---|
| Crawl | Little reporting and tooling. Basic KPIs, processes and policies exist but not every major team follows them. Plans address low-hanging fruit. | At least 70% of cost allocated to a known owner; commitment discount coverage of about 60%; forecast variance below 20% | New cloud estates, first FinOps hire or small team |
| Walk | The capability is understood and followed across the organisation. Difficult edge cases are identified and some are deliberately left alone. Automation or process covers most needs. | At least 85% allocated; commitment coverage above 75%; forecast variance below 10% | Growing estates with several business units |
| Run | Followed by all teams. Difficult edge cases are being addressed. Very high KPIs and automation is the preferred approach. | Over 90% allocated; commitment coverage above 80; forecast variance below 5% | Large, multi-cloud or multi-scope estates where the value justifies the effort |
What does Crawl look like in practice?
Cloud costs are hard to attribute, bills are reviewed after the fact and reports are built by hand. Early goals are to understand which services are used, allocate spend to teams, set up basic reporting and draft initial budgets. Common blockers are missing usage policies, billing surprises and thin FinOps resources.
What does Walk look like in practice?
Allocation maps cloud resources to business needs, policies are in place and spend is monitored proactively. Goals include better visibility, rightsizing, policy enforcement and first forecasts from historical data. Common blockers are maturing early processes, engaging every department and sustaining a cost-aware culture.
What does Run look like in practice?
Tagging, reporting and optimisation are largely automated and FinOps is part of daily operations. Goals include advanced automation, continuous optimisation from current data, strategic tagging and refined goal setting. The main risks are over-complexity and automation that stops matching how cloud use evolves.
How can Stratusphere FinOps support the Crawl level?
XenonStack's Stratusphere FinOps is aimed at AWS cost visibility. The cards below summarise the Crawl-level benefits it lists: financial alignment, actionable insights, visibility tracking and contextual guidance.
Actionable Insights
The outlined platform gives straightforward actionable advice on cost savings on AWS with their ranking depending on the effort demanded.
Smart Contextual Guidance
Out of the box solutions are much easier than the paradigm of having to build large data projects to develop insights.
Visibility Tracking
A complete look at AWS usage and possible cost savings assists businesses comprehend costs.
Financial Alignment
That Stratusphere™ FinOps resembles financial reports which can help finance teams to synchronize cloud costs with financial forecasts.
How do you check your FinOps maturity?
The Foundation notes that organisations can use the FinOps Assessment with its Crawl, Walk and Run rubric to see where they operate and which capabilities to move next. A simple self-check works alongside it:
- Tools and processes: are cost reports automated and repeatable, or built by hand?
- Stakeholder engagement: do IT, finance and business units take part in FinOps decisions?
- Optimisation practice: is saving work planned and tracked, or opportunistic?
- Reporting and forecasting: how accurate is forecast variance against the sample goals above?
- External view: would a consultant or assessment tool score you differently?
How do you move from Crawl to Walk, and from Walk to Run?
| Move | Focus | Watch for |
|---|---|---|
| Crawl to Walk | Formal usage and cost policies, better visibility, stakeholder engagement, a shift from reactive to proactive savings, and FinOps training. | Policies that teams do not follow; allocation gaps |
| Walk to Run | Automation of complex areas, integrating FinOps into wider business processes, stronger forecasting, tighter allocation and community learning. | Automation that drifts as cloud use changes; complexity that outweighs savings |
What has changed in FinOps recently?
The Framework now organises work into four domains (Understand Usage and Cost, Quantify Business Value, Optimize Usage and Cost, Manage the FinOps Practice) and defines scopes that cover technology categories such as public cloud, SaaS, data platform, private cloud, licences and data centre. The Foundation lists a March 2026 framework update covering Executive Strategy Alignment and refined scopes, and its framework poster is labelled March 2026 (FinOps Framework). Data-heavy estates have their own cost patterns, covered in FinOps for data mesh and data fabric.
How do governance, security and cost fit together?
Cost accountability depends on reliable usage data, so observability and allocation come first; our guide to monitoring as a service in the cloud covers the monitoring side. As AI agents start to trigger cloud spend, teams also need policy and an audit trail around those actions. ElixirData Context OS keeps governed context, versioned policy and decision traces in one decision layer above AI agents, and AgentGRC keeps autonomous agent actions inside policy, with the audit trail risk teams need.
When should you not push to Run?
Run is not the target for every capability. A small estate may gain little from automating a capability that Walk already covers, and automation has its own maintenance cost. Prioritise capabilities by business value, accept informed ignoring of low-value edge cases at Walk, and revisit the assessment as spend and scope grow.
To map one cost decision your agents should make, and the context and policy it depends on, book a Context Workshop. See what happens in the workshop.
FAQ: FinOps phases and maturity levels
What is the difference between FinOps phases and maturity levels?
The phases (Inform, Optimize, Operate) are a repeating cycle of activity. The maturity levels (Crawl, Walk, Run) rate how well each capability is performed.
What are the FinOps maturity levels?
Crawl, Walk and Run. Crawl has basic KPIs and policies not followed by every major team, Walk is understood and followed across the organisation, and Run is followed by all teams with automation preferred.
Do we need to reach Run in every capability?
No. The FinOps Foundation says the goal should never be simply to reach Run in every capability. Prioritise the capabilities that deliver the highest business value.
How do we assess our FinOps maturity?
Use the FinOps Assessment with the Foundation's Crawl, Walk and Run rubric, rating each capability separately and comparing KPIs such as allocation percentage and forecast variance with the sample goals.
Does FinOps only cover public cloud?
No. The Foundation describes modern FinOps as covering spend across technology categories such as SaaS, licensing, data centre and data cloud platforms.
Follow XenonStack on LinkedIn: XenonStack on LinkedIn for new guides on agentic AI, data and platform engineering.
Ready to put AI agents to work? Explore ElixirClaw, the agentic OS platform to build, orchestrate and govern AI agents.
Explore the XenonStack platform family: ElixirData · ElixirClaw · ElixirHub · NexaStack · MetaSecure · Neural AI · AgentGRC · AgentSRE · AgentAnalyst · AgentInstruct · AgentRAI · AgentScrum · AgentSearch · AgentForce · AI Aviator · SAIF Aviator · CohortIQ · XenonStack AI · XenonStack UAE