The FinOps Crawl / Walk / Run Model
The FinOps Foundation defines three maturity phases for cloud financial management. Each phase has distinct goals, costs, and expected waste reduction outcomes.
Crawl
Visibility and Accountability
5-12%
waste reduction
Walk
Optimisation and Workflow
15-25%
waste reduction
Run
Automation and Engineering Ownership
25-35%+
waste reduction
Crawl
/ Visibility and AccountabilityPhase Goals
- ✓Establish cloud cost visibility across all accounts
- ✓Implement tagging standards (owner, environment, project, cost centre)
- ✓Set up monthly cost reporting and showback
- ✓Identify top 10 cost drivers
- ✓Enable basic budget alerts
Key Activities
- →Activate Cost Explorer / Azure Cost Management / GCP Billing
- →Define and enforce mandatory resource tags
- →Map cloud accounts to business units
- →Create shared cost allocation model
- →Document top 10 rightsizing candidates
Success KPIs
- ●Tagging coverage above 80%
- ●Monthly cost reports delivered to all teams
- ●Budget breach alerts active
Walk
/ Optimisation and WorkflowPhase Goals
- ✓Automate rightsizing recommendations and implement 50%+ of them
- ✓Achieve 40-60% Reserved Instance or Savings Plans coverage
- ✓Implement chargeback to business units
- ✓Establish FinOps rituals (monthly reviews, quarterly planning)
- ✓Integrate cost data into engineering workflows
Key Activities
- →Purchase or evaluate dedicated FinOps platform
- →Run first Reserved Instance purchasing cycle
- →Set up anomaly detection and alerting
- →Build cost per microservice or product tracking
- →Run first cloud cost review with engineering leads
Success KPIs
- ●Reserved Instance coverage above 50%
- ●Monthly waste reduction tracked
- ●Chargeback reports sent to department heads
Run
/ Automation and Engineering OwnershipPhase Goals
- ✓Engineering teams own cloud cost as a first-class product metric
- ✓Real-time cost anomaly detection with automated remediation
- ✓Continuous rightsizing with auto-approval workflows
- ✓Cloud unit economics tracked per product and feature
- ✓Forecasting accuracy within 5% of actual spend
Key Activities
- →Build internal developer platform cost integrations
- →Automate Savings Plans and Spot instance management
- →Implement cost-per-customer or cost-per-transaction metrics
- →Run quarterly commitment optimisation cycles
- →Establish cloud cost KPIs in engineering OKRs
Success KPIs
- ●Forecast accuracy within 5%
- ●Cloud cost per unit improving QoQ
- ●Savings Plans coverage above 80%
How Long Does FinOps Take to Pay Back?
Most organisations see positive ROI within the first 90 days of the Crawl phase simply by turning off idle instances and applying basic rightsizing recommendations. Full programme ROI is typically achieved within three to six months.
The Walk phase compounds returns as Reserved Instance purchases and Savings Plans deliver 30-45% discounts on committed spend. The Run phase makes savings structural by embedding cost ownership into engineering culture.
Where Do Organisations Get Stuck?
The most common failure point is the Crawl-to-Walk transition. Teams achieve good visibility but struggle to translate it into action because engineering teams are not incentivised to reduce spend. Chargeback changes this dynamic.
The Walk-to-Run transition requires cultural change. Engineering must own cloud cost as a first-class metric alongside reliability and performance. This is a leadership challenge as much as a technical one.
Calculate your FinOps ROI by maturity phase
Enter your cloud spend and team size to see projected savings at each phase.
Open ROI Calculator →