How Do You Assess Your Current FinOps Maturity Level?
A proper maturity assessment covers all six FinOps domains defined by the FinOps Foundation: Understand Cloud Usage and Cost, Quantify Business Value, Optimize Cloud Usage and Cost, Manage the FinOps Practice, Manage Commitment-Based Discounts, and Manage Anomalies. According to the FinOps Foundation capability model, each domain contains multiple capabilities that should be individually assessed.
[UNIQUE INSIGHT] Many assessment efforts fail because they focus only on tooling and cost visibility. A thorough assessment also examines organizational culture, process maturity, and decision-making patterns. We've found that the gap between "having a FinOps tool" and "having a FinOps practice" is where most organizations stall.
Step-by-Step Assessment Process
Step 1: Inventory your capabilities. List every FinOps capability from the Foundation's framework. For each one, document what you're currently doing, who's responsible, and what tools you're using. Be honest about gaps.
Step 2: Score each capability. Rate each capability as Crawl, Walk, or Run based on the Foundation's criteria. Involve stakeholders from engineering, finance, and operations to get accurate perspectives. A single team's view will be incomplete.
Step 3: Identify patterns. Look for clusters. Are all your "Crawl" ratings in the optimization domain? That tells you where to focus. Are your "Run" ratings concentrated in visibility? That suggests you're collecting data but not acting on it effectively.
Step 4: Benchmark externally. Compare your results against industry data from the FinOps Foundation's annual survey. This context helps distinguish between areas where you're behind peers and areas where the entire industry struggles.
[INTERNAL-LINK: FinOps KPIs to track -> /blogs/finops-kpis-metrics-cloud-cost/]
What Does the Crawl Stage Look Like in Practice?
The Crawl stage is where approximately 45% of organizations sit for most FinOps capabilities, according to the FinOps Foundation's 2024 data. At this stage, cloud cost management is typically reactive and centralized in a small group rather than distributed across engineering teams.
[CITATION CAPSULE: Approximately 45% of organizations remain at the Crawl stage for most FinOps capabilities, per the FinOps Foundation's 2024 State of FinOps report. Crawl-stage organizations typically rely on reactive, manual cost management with limited automation.]
Common Crawl-Stage Characteristics
Tagging is inconsistent or incomplete. You might have a tagging policy on paper, but enforcement is spotty. Cost allocation relies on account-level groupings rather than granular tag-based attribution. Shared costs get dumped into a catch-all bucket.
Reporting is manual and periodic. Someone pulls a Cost Explorer report before monthly reviews. There's no automated anomaly detection, so spending spikes get discovered days or weeks after they start. Forecast accuracy is low because historical data isn't structured for prediction.
Optimization happens in bursts. After a big bill, someone runs a rightsizing analysis. Reserved instances or savings plans may be purchased ad hoc, without a systematic coverage strategy. There's no continuous optimization loop.
Does any of this sound familiar? You're not alone, and recognizing these patterns is the first step toward improvement.
How Do You Move from Crawl to Walk?
The transition from Crawl to Walk is where organizations see the highest return on effort. McKinsey research suggests that basic FinOps hygiene, including tagging enforcement, regular rightsizing, and commitment-based discounts, can reduce cloud costs by 15-25% within the first year.
Priority Actions for the Walk Stage
Enforce tagging standards. Implement automated tagging policies that prevent untagged resources from being deployed. Use tag inheritance and remediation tools to backfill existing resources. Aim for 80%+ tag compliance as a minimum threshold.
Establish regular cost review cadences. Weekly reviews for engineering teams, monthly reviews for business stakeholders, and quarterly reviews for executive leadership. Each cadence serves a different purpose and audience.
Automate basic reporting. Replace manual report pulling with scheduled dashboards and automated alerts. Set anomaly detection thresholds so spending spikes trigger immediate notifications rather than showing up in next month's review.
Build a commitment strategy. Analyze your steady-state usage patterns and purchase reserved instances or savings plans to cover predictable workloads. A coverage rate of 60-70% is a reasonable Walk-stage target.
[PERSONAL EXPERIENCE] In our work with mid-market companies, we've found the Crawl-to-Walk transition typically takes 3-6 months when there's executive sponsorship. Without it, the same transition can stall for over a year. Leadership buy-in isn't just helpful; it's the primary predictor of success.
[INTERNAL-LINK: showback and chargeback models -> /blogs/finops-showback-vs-chargeback-guide/]
What Does Reaching the Run Stage Require?
The Run stage represents operational excellence in cloud financial management. According to the FinOps Foundation, fewer than 15% of organizations achieve Run-level maturity across multiple capabilities simultaneously. Getting there requires sustained investment in automation, culture, and cross-functional processes.
[CITATION CAPSULE: Fewer than 15% of organizations achieve Run-level FinOps maturity across multiple capabilities, according to the FinOps Foundation. Run-stage organizations embed cost awareness into engineering culture and automate routine optimization decisions.]
Run-Stage Capabilities
Automated optimization. Rightsizing recommendations are automatically implemented with guardrails. Commitment purchases follow algorithmic models. Idle resources are automatically flagged and scheduled for termination after defined grace periods.
Unit economics integration. Cloud costs are measured per customer, per transaction, or per business unit rather than just in aggregate. Engineering teams have real-time visibility into the cost impact of their code changes and architecture decisions.
Accurate forecasting. Forecasts are within 5-10% of actual spend. Variance analysis happens automatically, and forecast models incorporate business growth projections, not just historical trends.
Cultural embedding. Engineers consider cost as a non-functional requirement alongside performance and reliability. Cost reviews are part of sprint ceremonies. Architecture review boards include cost analysis as a standard evaluation criterion.
[INTERNAL-LINK: FinOps roles and responsibilities -> /blogs/finops-roles-responsibilities-guide/]
What Are the Most Common Maturity Model Pitfalls?
Advancing through the FinOps maturity model isn't always linear. Organizations frequently get stuck or regress, often for predictable reasons. The FinOps Foundation's 2024 report identified organizational adoption and getting engineers to take action as the top two challenges cited by FinOps practitioners, ahead of tooling or technical issues.
Pitfall 1: Tool-First Thinking
Buying a FinOps platform doesn't equal FinOps maturity. Tools provide data, but maturity requires processes and people to act on that data. We've seen organizations with best-in-class tooling stuck at Crawl because nobody reviews the dashboards or acts on recommendations.
Pitfall 2: Skipping Walk
Some organizations try to jump from Crawl to Run by implementing advanced automation before establishing basic hygiene. This creates brittle systems. Automated rightsizing without accurate tagging, for example, risks optimizing resources that belong to the wrong team or project.
Pitfall 3: Centralizing Too Long
A centralized FinOps team is essential at Crawl stage. But staying centralized too long creates a bottleneck. Walk and Run stages require distributed accountability where engineering teams own their costs. The central team should shift from doing the work to enabling others.
[ORIGINAL DATA] Based on our client engagements, the average time to progress from Crawl to Walk is 4-8 months, while Walk to Run typically takes 12-18 months. The most common stall point is the transition from centralized to distributed cost ownership.
Frequently Asked Questions
How long does it take to move through all three maturity stages?
Most organizations take 18-36 months to progress from Crawl to Run across core capabilities. The Crawl-to-Walk transition is fastest, typically 3-6 months with executive support. Walk-to-Run takes longer because it requires cultural change, not just process improvements. The FinOps Foundation notes that maturity is not uniform; organizations typically reach Run in some capabilities while others remain at Walk.
Do I need a dedicated FinOps team to advance maturity?
At minimum, you need a designated FinOps practitioner, even if it's a part-time role. The FinOps Foundation recommends a centralized team of 2-5 people for mid-size organizations, scaling with cloud spend. At Walk stage and above, this team coordinates efforts rather than doing all cost management themselves.
Can small organizations benefit from the maturity model?
Yes. The maturity model scales to any organization size. Small teams with $50,000-$100,000 monthly cloud spend can apply the same framework with lighter processes. The key capabilities, such as tagging, commitment management, and regular reviews, deliver value regardless of scale.
Which FinOps capabilities should I mature first?
Start with cost allocation and tagging, then move to commitment-based discounts and anomaly management. These three capabilities deliver the fastest financial returns. According to the FinOps Foundation, cost allocation is the foundational capability that enables all others.
Building Your FinOps Maturity Roadmap
The FinOps maturity model isn't a destination. It's a continuous improvement framework that helps organizations get progressively better at managing cloud costs. Start by honestly assessing where you stand across all capabilities. Prioritize the transitions that deliver the highest financial and organizational impact.
Focus on people and processes before tools. The organizations that advance fastest are the ones that build cross-functional alignment between finance, engineering, and leadership. They treat cost as an engineering metric, not just a finance concern.
If you're looking to accelerate your maturity journey, explore how cloud cost optimization services can provide the expertise and frameworks to move from reactive cost management to proactive cloud financial governance.
[INTERNAL-LINK: FinOps certification guide -> /blogs/finops-certification-practitioner-guide/]
