// Definition
FinOps maturity describes how advanced an organization's cloud financial management capability is, measured against the FinOps Foundation's Crawl, Walk, Run framework. At the Crawl stage, cloud costs are opaque and optimization is reactive. At Walk, costs are allocated and teams are accountable. At Run, optimization is automated, unit economics are tracked, and FinOps is embedded across engineering.
// Why It Matters
The maturity model is useful because it sets realistic expectations for what's achievable at each stage and provides a structured path for improvement. Organizations often overestimate their maturity: having Cost Explorer enabled and doing occasional rightsizing is Crawl, not Walk. Walk requires consistent showback reporting, a centrally managed committed purchase portfolio, and a dedicated FinOps function with engineering credibility.
Critically, maturity is domain-specific. An organization can be at Walk maturity for EC2 cost optimization while still at Crawl for Kubernetes cost visibility. The FinOps Foundation's capability framework allows maturity to be assessed per domain, which is more actionable than a single overall rating.
The most important thing about maturity levels: they're descriptive, not prescriptive. Reaching Run stage isn't the goal — reaching the maturity level that matches your organization's cloud spend, growth rate, and internal FinOps capacity is. For most organizations under $2M/year cloud spend, a mature Walk-stage practice delivers 70–80% of the financial benefit with significantly less organizational investment than Run. See the complete framework in our FinOps maturity model guide.
// In Practice
Self-assessment indicators — Crawl: No team-level cost visibility, tagging below 40%, no dedicated FinOps resource, cost reviewed only by finance. Walk: Monthly showback reports, tagging 70–90%, dedicated FinOps team, RI/SP portfolio managed centrally. Run: Full chargeback operational, tagging 95%+, unit economics in product reviews, automated rightsizing in CI/CD pipelines.