The FinOps Lifecycle, Maturity and Scopes

FinOps runs as a loop of Inform, Optimize and Operate; each capability matures from Crawl to Walk to Run, and scopes define which kinds of technology spend the practice covers.

FinOps is not done once. Teams cycle through three phases, many times a year, for many capabilities at once.

flowchart LR
  I["Inform: visibility and allocation"] --> O["Optimize: usage and rates"]
  O --> OP["Operate: goals, governance, automation"]
  OP --> I
  M["Crawl → Walk → Run"] -.-> I
  %% step I: Inform answers who spends what, on which product, compared with budget and forecast.
  %% step O: Optimize finds savings: right size, switch off, re-architect, commit to better rates.
  %% step OP: Operate turns lessons into policies, cadences and automation so they stick.
  %% step M: Each capability matures separately: you can Run allocation while still Crawling with forecasting.

The phases

Phase	Questions	Examples
Inform	Who spends what? Is it on plan?	Tagging, allocation, dashboards, anomaly alerts, forecasts
Optimize	Where can we spend better?	Rightsizing, scheduling, storage tiering, Savings Plans
Operate	How do we keep it that way?	Policies, budgets, KPIs, regular reviews, automation

The four domains

The framework groups its capabilities into domains:

Domain	Capabilities (2025 framework)
Understand Usage & Cost	Data Ingestion, Allocation, Reporting & Analytics, Anomaly Management
Quantify Business Value	Planning & Estimating, Forecasting, Budgeting, KPIs & Benchmarking, Unit Economics
Optimize Usage & Cost	Architecting & Workload Placement, Usage Optimization, Rate Optimization, Licensing & SaaS, Sustainability
Manage the FinOps Practice	Executive Strategy Alignment, FinOps Practice Operations, Governance, Policy & Risk, Education & Enablement, Invoicing & Chargeback, FinOps Assessment, Automation, Tools & Services, Intersecting Disciplines

The rest of this course follows these domains.

Maturity: Crawl, Walk, Run

Level	Typical signs (allocation example)
Crawl	Little tagging, monthly reports, a few people care
Walk	Most spend allocated, weekly reviews, some automation
Run	Nearly all spend allocated automatically, teams act on daily data, policies enforced in code

"Run" everywhere is not the goal. Mature the capabilities that matter most for your business first.

Scopes

A scope is a segment of technology spend you apply FinOps to. Public cloud is the main one; the 2025 framework also names SaaS and data centre, and the community adds private cloud, licensing and AI (GPU and model-token spend). Scopes can overlap, and each one decides which personas and capabilities apply.

Traps: trying to reach "Run" in every capability in the first year; and optimising before you can see and allocate costs — you cannot reduce what you cannot attribute.