FinOps Maturity Model Framework Explained

Understanding where your organization stands in cloud cost management maturity is the first step toward improving it. Without an honest assessment of your current capabilities, optimization efforts lack direction -- you invest in advanced automation when basic visibility is still missing, or you stay stuck in manual processes when your organization is ready for the next level.

The FinOps Maturity Model provides a simplified, practical framework for this assessment. It defines three stages -- Crawl, Walk, and Run -- each with clear benchmarks for cost allocation, forecast accuracy, and organizational behavior. The framework is not a certification or a scorecard. It is a diagnostic tool that helps teams understand their current state and identify the highest-leverage improvements for their specific situation.

Crawl

The Crawl stage is where most organizations begin their FinOps journey. At this stage, cloud cost management is reactive and manual. A small number of key members understand FinOps principles, but the broader organization has limited awareness of cloud cost dynamics.

Characteristics of the Crawl stage:

• Limited tooling: Cost visibility comes primarily from the cloud provider's native billing console and basic cost explorer tools. There is no centralized platform for cross-account or cross-service analysis.
• Low-hanging fruit: Optimization efforts focus on the most obvious waste -- unused resources, unattached storage volumes, idle load balancers. These are valuable wins, but they represent only a fraction of the total optimization opportunity.
• Inconsistent tagging: Resource tags are incomplete, inconsistent, or entirely absent. Cost allocation relies on account-level grouping rather than granular attribution to teams, products, or business functions.
• Siloed ownership: Cloud cost management is owned by one person or a small team within finance or platform engineering. Engineering teams have limited visibility into the cost impact of their decisions.

Benchmarks:

• Cost Allocation: Approximately 50% of spend is allocated to teams or projects.
• Forecast Accuracy: Approximately 20% variance from actual spend.

Walk

At the Walk stage, organizations have moved beyond basic visibility and are actively optimizing with defined processes. Automation is expanding, new savings opportunities beyond the low-hanging fruit are becoming visible, and decision-making increasingly relies on data rather than intuition.

Characteristics of the Walk stage:

• Expanding automation: Manual processes are being replaced or augmented with automated tools. Scheduled reports, automated anomaly detection, and programmatic commitment purchases are in place.
• Broader savings visibility: Optimization goes beyond obvious waste to include rightsizing, commitment strategy, architecture optimization, and rate negotiation. The team understands not just where waste exists but why it exists and how to prevent it.
• Data-driven decisions: Cost data is integrated into engineering and business decision-making. Teams review cost impact before deploying new infrastructure. Budget forecasts are based on usage trends rather than historical averages.
• Defined tagging standards: Tagging policies are established and mostly followed. Enforcement mechanisms are in place, though compliance is not yet universal.
• Multi-team engagement: Multiple teams across the organization are engaged in cost management, not just a centralized FinOps team. Engineering teams accept some responsibility for the cost of the infrastructure they deploy.

Benchmarks:

• Cost Allocation: Approximately 80% of spend is allocated.
• Forecast Accuracy: Approximately 15% variance.

Run

The Run stage is the target state for mature FinOps organizations. Cloud cost management is automated, continuous, and embedded in engineering culture. The entire organization follows FinOps principles, edge cases are addressed systematically, and automation is the default rather than the exception.

Characteristics of the Run stage:

• Organization-wide FinOps culture: Cost awareness is part of every engineering decision, from initial architecture design through deployment and ongoing operations. It is not an afterthought or a quarterly review item -- it is embedded in how teams build and operate software.
• Edge cases addressed: Optimization goes beyond the standard categories to address edge cases -- unusual instance types, legacy workloads, multi-cloud complexity, and organizational exceptions. The team has the maturity and tooling to handle non-standard situations.
• Automation preferred: Manual optimization is the exception, not the rule. Rightsizing, commitment purchases, waste elimination, and governance enforcement are automated and integrated into CI/CD pipelines. Human judgment is reserved for strategic decisions, not routine operations.
• Proactive governance: Policies prevent waste before it happens. Shift-Left guardrails catch misconfigured or oversized infrastructure at the code level, before deployment. Budget controls and approval workflows enforce cost discipline automatically.

Benchmarks:

• Cost Allocation: 90% or more of spend is allocated.
• Forecast Accuracy: Approximately 12% variance.

5-Step Self-Assessment

To determine your current maturity level and identify the most impactful areas for improvement, work through these five assessment areas:

1. Evaluate Current Processes

How much of your cloud cost management is automated versus manual? If your primary optimization tool is a spreadsheet and your primary communication channel is email threads, you are likely in the Crawl stage. If you have automated detection and programmatic remediation workflows, you are moving toward Run. The degree of automation is one of the most reliable indicators of maturity -- more automated processes correlate directly with higher maturity.

2. Understand Skills and Governance

What FinOps expertise exists in the organization, and how is it structured? A single practitioner managing costs in isolation indicates Crawl. A dedicated FinOps team with defined policies and governance frameworks indicates Walk. Distributed cost ownership with FinOps principles embedded in engineering standards indicates Run.

3. Review Consumer Team Maturity

How do the teams that consume cloud resources engage with cost management? If engineering teams have no visibility into the cost of their infrastructure, maturity is low. If they receive cost reports but do not act on them, you are in early Walk. If they actively optimize their own resources and consider cost impact in architectural decisions, you are approaching Run.

4. Examine Current Tools

What tools are you using, and how effectively? Native cloud provider tools (Cost Explorer, Budgets) without additional platforms suggest Crawl. Third-party visibility tools with manual remediation suggest Walk. Integrated platforms that automate the full lifecycle from detection through remediation suggest Run.

5. Document Action Points

Based on the previous four assessments, identify the specific actions that would move your organization from its current stage to the next. Focus on the highest-leverage improvements -- the changes that would have the most impact relative to the effort required. A Crawl organization might prioritize tagging standards and basic automation. A Walk organization might prioritize automated remediation and Shift-Left governance. Document these as concrete action items with owners and timelines.

Glassity automates AWS cost optimization — delivering up to 50% savings on EC2 and 69% on RDS. You only pay 10% of what we actually save you. Book a free savings assessment.