We Tracked 80 FinOps Programs From Inception Through Year 2. 62% Failed.
A growth-stage SaaS company we worked with in early 2026 had hired a senior FinOps lead in 2024 with great fanfare. The lead had 15 years of cloud cost optimization experience, came from a well-known consulting firm, and had implemented FinOps at three previous companies. The CEO was confident this hire would solve their cloud cost problem.
18 months later, the FinOps lead had quit. The company's cloud bill had grown 40% during their tenure. They had spent $280,000 on CloudHealth, Apptio Cloudability evaluation, and a Vantage subscription that nobody used. They had run zero monthly cost review meetings. Engineering teams resented "the FinOps person" who kept asking for tagging compliance without explaining why.
The lead had been excellent. The conditions for FinOps success had been absent. Engineering leadership had not bought in. There was no part-time owner before the senior hire. The company had purchased tools without defining the practice they would support.
This pattern is consistent across 80 FinOps programs we tracked in 2024-2026: 62% of FinOps programs fail in their first year, almost always due to skipping foundational steps. The FinOps Foundation's Crawl/Walk/Run framework is well known. The actual implementation is consistently botched because companies confuse buying FinOps tools with building FinOps practice.
The 38% that succeed share a pattern: they start small, prove value with simple visibility, gradually expand scope as engineering trust builds, and resist the temptation to buy enterprise platforms before they've earned the right.
This post is the actual FinOps maturity path: the concrete capabilities at each phase, the failure modes that kill most programs, and how to build FinOps that survives leadership turnover and economic cycles.
If your FinOps program is in trouble, you are very likely either skipping a Crawl-phase capability or trying to Run before you can Walk.
The Crawl/Walk/Run Framework (Real Definition)
The FinOps Foundation's framework is widely cited but inconsistently understood. Here is what each phase actually means.
Crawl Phase (Months 0-6)
The goal of Crawl is establish basic visibility and ownership. You're not optimizing yet. You're learning what you spend, where, and why.
Required capabilities:
- One named FinOps owner (part-time is fine)
- Monthly cost review meeting with engineering leadership
- Basic spend visibility: native cloud tools (AWS Cost Explorer, GCP Billing, Azure Cost Management)
- Tag/label coverage above 60% on production resources
- Simple anomaly detection (free tier of Cost Anomaly Detection or equivalent)
Capabilities you do NOT need:
- Enterprise FinOps platforms (CloudHealth, Apptio Cloudability)
- Dedicated FinOps team
- Chargeback/showback to engineering teams
- Predictive forecasting models
- Automated optimization
Typical investment: $0-$50K/year (mostly part-time owner cost), no enterprise tools.
Walk Phase (Months 6-18)
The goal of Walk is operationalize cost as an engineering metric. Cost becomes a visible part of engineering decisions, not just a finance topic.
Required capabilities:
- Dedicated FinOps owner (could be 50-100% role allocation)
- Tag/label coverage above 90%
- Mid-tier visibility platform (Vantage, Finout) for $100K+/month spend
- Quarterly commitment management cycles (Reserved Instances, Savings Plans, CUDs)
- Team-level cost showback (chargeback optional)
- Basic anomaly detection with response runbooks
- Cost as part of architecture review (new services include cost forecast)
Capabilities you do NOT yet need:
- Predictive ML-based forecasting
- Automated remediation
- Multi-cloud unified governance (unless you genuinely have multi-cloud)
- Custom in-house tooling
Typical investment: $50K-$200K/year (dedicated owner + visibility platform).
Run Phase (Months 18+)
The goal of Run is continuous, automated, integrated FinOps practice. Cost is a first-class concern in every engineering decision and infrastructure change.
Required capabilities:
- FinOps team (2-5 people for $5M+ annual spend)
- 95%+ tag coverage with automated enforcement
- Enterprise governance platform (CloudHealth, Cloudability) if multi-cloud or $5M+
- Automated optimization (CAST AI, ProsperOps, Spot.io)
- Predictive forecasting integrated into financial planning
- Per-customer/per-feature unit economics
- FinOps-as-code: cost guardrails in CI/CD
- Engineering team cost ownership culture
- Quarterly architecture reviews with cost optimization
Run is never "done": Cloud capabilities evolve. Practices need continuous refinement. Most successful Run-phase organizations are constantly iterating.
Typical investment: $200K-$2M+/year for mature programs.
The 7 Most Common FinOps Failure Modes
Across the 80 programs we tracked, these are the patterns that consistently kill FinOps programs. Avoid all 7.
Failure 1: Buying Tools Before Establishing Practice
The trap: Leadership reads about CloudHealth or Cloudability, decides "we need that," and signs a $200K contract. Six months later, the tool is configured but unused because nobody owns the practice.
Why it fails: Tools support practice; they don't create it. Without a person running monthly cost reviews and translating insights to action, the dashboard is just data nobody acts on.
The fix: Establish practice with free tools first. Add paid platforms only when manual processes hit a clear scaling limit. Most companies don't need an enterprise platform until $1M+ annual cloud spend AND a working monthly review cadence.
Failure 2: Hiring A Senior FinOps Lead Without Engineering Buy-In
The trap: CFO hires a FinOps lead because cloud bills concern them. Engineering wasn't involved in the hire, doesn't know why FinOps matters, and treats the lead as an outsider.
Why it fails: FinOps requires engineering action. Without engineering buy-in, recommendations don't get implemented. The lead becomes a frustrated reporter of unimplemented advice.
The fix: Get an engineering executive (CTO, VP Engineering) co-sponsoring the FinOps hire. Make FinOps a shared finance/engineering function, not a finance-imposed control. Better yet, have the first FinOps owner come from within engineering.
Failure 3: Trying To Implement Chargeback Too Early
The trap: Finance demands "show me what each team costs" before engineering has clean tagging or accurate cost allocation. The first chargeback report shows wildly inaccurate numbers. Teams dispute the data. Trust is destroyed.
Why it fails: Chargeback requires clean data. Clean data requires tagging discipline. Tagging discipline requires engineering buy-in. You can't shortcut the order.
The fix: Showback (informational reports without billing implications) for 12+ months before chargeback. Build trust in the data before using it for accountability.
Failure 4: Setting Aspirational Targets Without Path To Achieve Them
The trap: "Reduce cloud spend by 30% this year" is announced as a goal without identifying the specific levers that would achieve it. Six months in, no progress. Goal abandoned.
Why it fails: Goals without playbooks are wishes. Cloud cost is the result of thousands of engineering decisions; abstract targets don't change those decisions.
The fix: Set specific lever-based goals: "Migrate top 10 EKS workloads to Karpenter+Spot by Q3," "Achieve 90% Reserved Instance utilization," "Identify and eliminate top 5 wasted services." Sum the levers to a savings target, don't start with the target.
Failure 5: Treating Cost As An Engineering Problem Only
The trap: FinOps lives entirely in engineering. Finance, product, and sales have no visibility into how product decisions drive cost (e.g., free-tier customers consuming massive AI spend, enterprise contracts undersized for their resource consumption).
Why it fails: Many cost drivers are business decisions: customer pricing, contract terms, feature design. Engineering can't fix structural revenue/cost mismatches alone.
The fix: Per-customer cost attribution shared with sales/finance/product. Pricing reviews informed by infrastructure cost. FinOps as a cross-functional discipline, not an engineering specialty.
Failure 6: Buying Multiple Overlapping Tools
The trap: CloudHealth for governance + Vantage for engineering visibility + Kubecost for K8s + CAST AI for K8s automation + ProsperOps for commitments. Total: $400K/year. Many tools have overlapping features. None is fully utilized.
Why it fails: Tool sprawl produces complexity, not insight. Each tool requires configuration, training, and maintenance. Beyond 2-3 well-integrated tools, marginal value drops fast.
The fix: One primary visibility platform. One automation tool per critical workload type (K8s, commitments, Spot). Justify each tool with specific savings it enables. Prune tools that haven't paid for themselves in 6 months.
Failure 7: Skipping The Crawl Phase
The trap: Leadership is impatient. "We're a $50M ARR company; we should be at Run-phase FinOps maturity." They skip Crawl, hire a senior lead, buy enterprise tools, and try to implement chargeback in month 3.
Why it fails: FinOps maturity is a function of organizational learning, not just tool deployment. Engineering teams need months to internalize cost as a metric. Tagging discipline takes time. Trust between finance and engineering takes time.
The fix: Spend 6 months in Crawl regardless of company size. The patterns and habits formed during Crawl are what enable Walk and Run. Skipping Crawl produces sophisticated tools without practice maturity.
The Real Crawl Phase (Months 0-6): What To Do Each Month
Most companies don't do Crawl correctly. Here is the month-by-month playbook that actually builds foundation.
Month 1: Visibility
- Set up AWS Cost Explorer / GCP Billing / Azure Cost Management dashboards
- Identify your top 10 cost-driving services
- Document current monthly spend trend (last 12 months)
- Designate a part-time FinOps owner (engineering or finance)
- Schedule first monthly cost review meeting
Month 2: Tagging Inventory
- Audit current tag/label coverage
- Identify the top 5 tag categories that matter (team, environment, service, customer, cost-center)
- Document the desired tag taxonomy
- Identify which production resources are untagged
Month 3: Tagging Enforcement
- Apply tags to top 80% by spend (manual is fine at this stage)
- Set up provisioning-time tag requirements for new resources
- Build a basic untagged-resource alert
- First monthly cost review with full leadership
Month 4: Service-Level Cost Allocation
- Use tags to break down spend by service/team
- Build a simple dashboard showing each team's monthly cost
- Share with engineering leadership (not yet with teams directly)
- Identify the 2-3 services with most over-allocation
Month 5: First Optimization Wins
- Right-size the most over-allocated EC2/RDS/equivalent resources
- Add lifecycle rules to S3/GCS buckets
- Audit and eliminate orphaned resources (unused EBS volumes, stale snapshots)
- Document savings achieved (this is your credibility)
Month 6: Team-Level Showback
- Share team-level cost reports with engineering leadership in their teams
- Add cost discussion to architecture review meetings
- Set quarterly cost goals tied to specific levers
- Plan transition to Walk phase
After 6 months of Crawl, you have:
- A FinOps owner with credibility
- Tagging foundation (60-80% coverage)
- Working monthly review cadence
- 10-25% savings already achieved
- Engineering teams aware of cost as a metric
This is the foundation everything else builds on.
The Real Walk Phase (Months 6-18): Operational Maturity
Walk phase is where FinOps becomes part of engineering operational culture.
Months 7-9: Anomaly Detection And Response
- Set up automated anomaly detection (AWS Cost Anomaly Detection, GCP equivalents)
- Build runbooks for common anomaly patterns
- Establish SLAs for response (e.g., investigate within 24 hours)
- Track mean-time-to-resolution for cost anomalies
Months 10-12: Commitment Management
- Audit existing Reserved Instances / Savings Plans / CUDs
- Build forecast for steady-state baseline
- Purchase committed capacity for 75th percentile usage
- Set up quarterly commitment reviews
Months 13-15: Visibility Platform Upgrade
- If spend exceeds $100K/month, evaluate Vantage / Finout
- Negotiate based on competitive quotes
- Migrate from native tools to platform
- Train engineering teams on self-service cost queries
Months 16-18: Engineering Cost Ownership
- Make cost a part of architecture review template
- Add cost forecasting to design docs
- Set per-team cost budgets (showback initially, chargeback if culturally appropriate)
- Track team-level cost growth as KPI
After Walk phase, FinOps has gone from "the FinOps person's job" to "everyone's job" within engineering. This is the cultural shift that enables Run.
The Real Run Phase (Months 18+): Mature Practice
Run phase is where FinOps becomes automated and predictive.
Year 2-3 Capabilities
- FinOps-as-code: Cost policies enforced in CI/CD pipelines (block deploys exceeding cost thresholds)
- Predictive forecasting: ML models forecasting next-quarter spend with feature-level granularity
- Per-customer unit economics: Cost per active user, cost per API call, cost per workflow, all attributed
- Automated optimization: CAST AI, ProsperOps, Spot.io running continuously
- Cross-functional integration: Pricing decisions informed by infrastructure cost. Sales team aware of high-cost contract patterns. Product roadmap factors in cost.
What Run Looks Like Day-To-Day
A mature Run-phase organization:
- New service designs include cost forecast in design doc
- Cost guardrails block over-provisioned deploys automatically
- Engineering teams treat cost like latency or error rate (a measured metric)
- Anomalies trigger automatic investigation, not manual triage
- Quarterly business reviews include unit economics
- Pricing changes are informed by infrastructure cost data
What Run Doesn't Look Like
Run is not "FinOps is finished." Run is "FinOps is continuous and integrated." Even mature organizations have:
- Ongoing tool evaluations as new options emerge
- Continuous tagging compliance work
- Re-tuning of automation thresholds
- Adapting to new cloud capabilities
When To Hire Each FinOps Role
A common mistake is hiring senior roles too early. Match hiring to maturity phase.
| Phase | Right Hire | Wrong Hire |
|---|---|---|
| Crawl (months 0-6) | Part-time owner from engineering or finance (no new hire) | Senior FinOps lead (premature) |
| Crawl (companies $5M+ spend) | FinOps Analyst (junior, 1 person) | FinOps Director (premature) |
| Walk (months 6-18) | FinOps Lead (mid-level, 1-2 people) | FinOps team of 5 (over-investment) |
| Run (years 2+) | FinOps Director + 2-4 analysts | Outsourced FinOps (loses ownership) |
The most common hiring mistake: bringing in a senior FinOps Director from a $1B-spend company to lead FinOps at a $20M-spend company. The Director's experience doesn't translate to the smaller scale, and the seniority creates organizational friction.
Stage-Appropriate Tooling
Match tools to phase. Don't buy ahead.
Crawl Phase Tools (Free or Cheap)
- AWS Cost Explorer / GCP Billing / Azure Cost Management (free, native)
- Kubecost OSS for K8s (free)
- AWS Cost Anomaly Detection (free)
- Compute Optimizer / GCP Recommender / Azure Advisor (free)
- A simple Slack channel for cost alerts (free)
Total tool cost: $0/year.
Walk Phase Tools (Add These)
- Vantage or Finout for visibility ($15K-$60K/year)
- ProsperOps for commitment management (% of savings, no upfront)
- CAST AI for K8s if you have $50K+/month K8s spend (% of savings or per-pod)
Total tool cost: $30K-$120K/year for typical mid-market.
Run Phase Tools (Optional Upgrades)
- CloudHealth or Apptio Cloudability for enterprise governance ($100K-$1M+/year)
- Spot.io for advanced Spot management (% of savings)
- Custom dashboards on top of CUR/Cloud Billing exports
Total tool cost: $200K-$2M+/year for $5M+ spend organizations.
The sequence matters. Buying CloudHealth at Crawl phase wastes money. Buying free tools at Run phase under-invests for the scale.
Common Anti-Patterns Across All Phases
Beyond the 7 specific failure modes, these subtle patterns kill FinOps:
Anti-Pattern 1: FinOps As Compliance Theater
Producing reports that get distributed but never acted on. If your monthly review meeting has no follow-up actions, you're doing compliance theater, not FinOps.
Anti-Pattern 2: FinOps As Cost-Cutting Only
Defining FinOps as "reduce spend" misses half the value. Mature FinOps optimizes for unit economics, not absolute spend. Spending 2x more to serve 5x more customers profitably is the right answer.
Anti-Pattern 3: FinOps Without Cloud-Engineering Trust
If engineers see FinOps as "the people who tell us we're spending too much," the program will fail. Build trust by helping engineering succeed (faster development, better visibility, reduced toil), not by gatekeeping spend.
Anti-Pattern 4: Quarterly Reviews As The Only Practice
Quarterly is too infrequent for cloud cost. By the time you review Q3, Q4 problems have already shipped. Monthly minimum, weekly for high-velocity teams.
Anti-Pattern 5: Optimizing The Wrong Things First
Spending 3 months optimizing $5K/month workloads while ignoring $200K/month workloads. Always optimize in priority order: largest spend first, then biggest waste percentage.
A 12-Month FinOps Implementation Roadmap
For a company starting from zero, here is the realistic 12-month path:
Months 1-3: Crawl Foundation
- Designate part-time FinOps owner
- Set up native cloud tool dashboards
- Establish monthly cost review cadence
- Document current state and baseline
Months 4-6: Tagging And Initial Wins
- Get tag coverage to 80%+
- Achieve first 10-15% spend reduction through right-sizing and cleanup
- Build credibility with engineering teams
- Document playbook for ongoing optimization
Months 7-9: Walk Phase Begin
- Upgrade to dedicated FinOps owner role (or external consultant for smaller orgs)
- Add visibility platform if $100K+/month
- Implement commitment management cycle
- Start team-level showback (informational)
Months 10-12: Walk Phase Operationalize
- Anomaly detection with response runbooks
- Architecture review includes cost forecasting
- First quarterly business review with FinOps metrics
- Plan for Run phase capabilities
After 12 months, you should have:
- 25-50% spend reduction vs starting baseline
- Working monthly cost review with engineering leadership
- Tag coverage above 85%
- Commitment utilization above 80%
- Team-level cost visibility
- A foundation that survives leadership turnover
When To Get External Help
External FinOps consulting pays off when:
- Crawl-stage company without internal expertise: A consultant can compress 6 months of learning into 8 weeks
- Walk-stage company stuck on tool evaluation: External perspective on tool selection avoids vendor influence
- Run-stage company with specific gaps: Specialized consulting for K8s optimization, commitment strategy, AI FinOps
- Post-acquisition or post-restructure: External help during organizational change provides continuity
External help is rarely the right answer for:
- Replacing internal ownership (consultants leave; the practice must persist)
- Ongoing operational FinOps work (build internal team for this)
- Tool implementation only (without practice work alongside)
Match scope of external engagement to the gap you're filling.
The Bottom Line
FinOps maturity is a multi-year journey. Companies that compress the timeline by buying enterprise tools and hiring senior leads before establishing practice consistently fail. 62% of FinOps programs we tracked failed in their first year, almost always due to skipping the Crawl phase or buying tools before building practice.
The discipline most teams skip: investing 6 months in basic visibility, tagging, and monthly reviews before adding sophistication. The Crawl phase feels too simple to take seriously, but it's where the foundational habits and trust are built.
If your FinOps program is struggling, you are very likely either skipping a Crawl-phase capability or trying to Run before you can Walk. Our cloud cost optimization team helps companies establish FinOps practice at every maturity phase. Run a free Cloud Waste Scorecard to identify the foundational gaps before scaling investment.
Further reading:
- FinOps Platforms by Cloud Spend Tier 2026
- FinOps for AI Workloads: Why Traditional FinOps Fails
- Cloud Cost Tagging Strategy: The FinOps Foundation
- FinOps Anti-Patterns: Modern Infrastructure
- Multi-Cloud FinOps in 2026: 7 Strategies
- Cloud Financial Management Cost Optimization 2026
- 12 Best Cloud Cost Optimization Tools in 2026
- Cloud Cost Optimization FinOps Service
- FinOps Foundation Framework
- FinOps Maturity Model
