Programme / FinOps maturity
FinOps Framework 2026: Crawl, Walk, Run maturity model
The FinOps Foundation maturity model in three stages, with concrete capabilities at each level, the six FinOps domains, typical timeframes, and the metrics that signal progress. Pair with the savings playbook to translate framework into action.
Crawl
Gaining visibility
Months 1-3
The Crawl stage is about establishing basic cloud cost visibility and creating a shared understanding across teams. Many organisations discover they are in the Crawl stage when they first audit their cloud spending seriously.
Walk
Building accountability
Months 3-9
The Walk stage establishes systematic cost accountability across engineering teams. Costs are allocated to teams or products, and there is a clear forecast versus actual review cadence. Commitment discounts are purchased deliberately rather than reactively.
Run
Continuous optimisation
Months 9+
The Run stage runs cost optimisation as a continuous engineering practice. Cost is a first-class metric in development, alongside performance and reliability. Engineers self-serve cost data and the FinOps team focuses on strategic decisions rather than firefighting.
Crawl stage / detail
Crawl: Gaining visibility
Characteristics
- Basic cost reporting from cloud provider consoles only
- Limited or no resource tagging for cost allocation
- Cloud costs managed reactively when bills surprise stakeholders
- No regular review cadence or cost ownership by teams
- Savings primarily from one-off rightsizing and terminating obvious waste
Goals to advance
- Implement a tagging strategy covering team, environment, and product
- Establish a monthly cost review meeting with engineering and finance
- Enable budget alerts for anomaly detection on top spending services
- Identify and terminate obvious idle resources
- Document who owns each major cost line
Metrics that signal progress
- Tagging coverage (target 80%+)
- Number of unallocated resources (target trending toward zero)
- Monthly review meeting attendance
- Time from anomaly to investigation (target under 7 days)
Walk stage / detail
Walk: Building accountability
Characteristics
- Costs allocated by team, product, or environment via tags
- Monthly chargeback or showback to engineering teams
- Forecast versus actual reviews with finance
- Reserved Instance and Savings Plan portfolio actively managed
- Anomaly detection automated with team-specific alerts
Goals to advance
- Achieve 60-75% commitment coverage on stable workloads
- Implement automated rightsizing recommendations
- Reduce hidden cost line items by 50%
- Establish FOCUS-aligned reporting if multi-cloud
- Run quarterly cost optimisation sprints
Metrics that signal progress
- Commitment coverage percentage
- Forecast accuracy (target within 10%)
- Engineer-led savings actions per quarter
- Cost per business unit (chargeback transparency)
Run stage / detail
Run: Continuous optimisation
Characteristics
- Cost dashboards integrated into engineering tooling
- Pre-deployment cost review for significant infrastructure changes
- Continuous Spot, Savings Plan, and CUD portfolio rebalancing
- Sustainability and cost both measured per team
- Architecture decisions consider total cost of ownership
Goals to advance
- Embed cost reviews in design documents and architecture reviews
- Achieve target unit economics (cost per request, cost per customer)
- Run automated commitment management for stable workloads
- Cross-cloud cost reporting via FOCUS where applicable
- Establish FinOps Foundation membership and benchmarking
Metrics that signal progress
- Unit cost trend (cost per business metric)
- Engineer self-serve adoption rate
- Days to detect and respond to anomaly (target under 24 hours)
- Commitment portfolio realised utilisation (target 90%+)
The six FinOps domains
Capability areas across all stages
Understanding cloud usage and cost
Foundation: tagging, allocation, and the analytical capabilities that turn raw billing data into management information.
Performance tracking and benchmarking
KPIs, unit economics, forecast versus actual, and benchmarks against industry peers.
Real-time decision making
Anomaly detection, automated alerts, and the ability for engineers to make cost-aware decisions in development.
Cloud rate optimisation
Commitment portfolio management: Savings Plans, Reserved Instances, Committed Use Discounts.
Cloud usage optimisation
Rightsizing, Spot adoption, idle resource elimination, architecture-level efficiency.
Organisational alignment
FinOps culture, team responsibilities, training, and cross-functional collaboration with finance and engineering leadership.
Common questions
FAQ
How long does it take to reach the Run stage?+
Most organisations take 12-18 months to reach mature Run stage capabilities. Crawl stage is achievable in 3 months. Walk stage requires 6-12 months of consistent practice and tooling investment. Run stage requires both technical maturity (automated reporting, integrated tooling) and cultural change (engineers caring about cost as a first-class metric).
Do I need a dedicated FinOps team?+
It depends on cloud spend. Below $50K/mo, FinOps responsibilities can be shared across engineering and finance leadership. Between $50K and $500K/mo, a dedicated FinOps practitioner usually pays for themselves within months through commitment optimisation alone. Above $500K/mo, a small FinOps team (2-4 people) becomes appropriate, with engineering teams self-serving day-to-day cost decisions.
How is the FinOps framework different from cost management?+
Cost management is a tool category. FinOps is a cultural practice that brings financial accountability to cloud spending. The framework defines six domains spanning visibility, optimisation, and organisational alignment. Tools are necessary but not sufficient. The practice is what makes the difference.
What is the FinOps Foundation?+
An open community under the Linux Foundation that publishes the FinOps Framework, certifications (FinOps Certified Practitioner, FinOps Certified Engineer, FinOps Certified FOCUS Practitioner), and the FOCUS billing specification. Membership and resources are useful for benchmarking, hiring, and accessing peer practitioners.
Continue reading