clement13.net
Original photo: A piggy bank
Description
A piggy bank
Source
stevepb · original page
Licence
CC0 Public domain
Original photo, unretouched. The background is a version of it stylised by the site.

Cloud costs — FinOps

How do you manage cloud costs without slowing innovation? FinOps answers with a collaborative practice, measured capability by capability.

≈ 3 min readReading
At a glance
  • Crawl / Walk / Run, assessed per capability.
  • 4 domains, about twenty capabilities.
  • Don't aim for “Run” everywhere: aim for value.
On this page
  1. Profile
  2. Why this matrix matters in my field
  3. The maturity scale
    1. Crawl
    2. Walk
    3. Run
  4. The dimensions assessed
    1. Understand Usage & Cost — Data Ingestion
    2. Understand Usage & Cost — Allocation
    3. Understand Usage & Cost — Reporting & Analytics
    4. Understand Usage & Cost — Anomaly Management
    5. Quantify Business Value — Planning & Estimating
    6. Quantify Business Value — Forecasting
    7. Quantify Business Value — Budgeting
    8. Quantify Business Value — KPIs & Benchmarking
    9. Quantify Business Value — Unit Economics
    10. Optimize Usage & Cost — Architecting & Workload Placement
    11. Optimize Usage & Cost — Rate Optimization
    12. Optimize Usage & Cost — Usage Optimization
    13. Optimize Usage & Cost — Sustainability
    14. Optimize Usage & Cost — Licensing & SaaS
    15. Manage the FinOps Practice — FinOps Practice Operations
    16. Manage the FinOps Practice — Governance, Policy & Risk
    17. Manage the FinOps Practice — FinOps Assessment
    18. Manage the FinOps Practice — Automation, Tools, & Services
    19. Manage the FinOps Practice — FinOps Education & Enablement
    20. Manage the FinOps Practice — Invoicing & Chargeback
    21. Manage the FinOps Practice — Intersecting Disciplines
    22. Manage the FinOps Practice — Executive Strategy Alignment
  5. How to use it
  6. Limitations and precautions
  7. Sources and verification

Profile#

Organization
FinOps Foundation (Linux Foundation)
Framework
FinOps Framework: principles, domains, capabilities, maturity
Scale
3 stages per capability: Crawl, Walk, Run
Dimensions
4 domains and their capabilities (list consulted in October 2026)
Particularity
Maturity is assessed per capability; reaching “Run” everywhere is not a goal
Access
Free, published online

Why this matrix matters in my field#

A cloud project without a proof of concept or prior efficiency tests can quickly run away in costs. FinOps formalizes the opposite: visibility first (who spends what), then forecasting and budgeting, then continuous optimization, with the engineering, finance and business teams around the same table. For anyone managing cloud resources (clusters, SQL or analytics capacities, scheduled start and stop), it is the common language with finance.

The maturity scale#

Three stages, applied to each capability separately. The definitions follow the FinOps Foundation website.

  1. Crawl#

    Very few reports and tools. Basic measurements, elementary processes defined around the capability. Goals are modest.

  2. Walk#

    The capability is understood and tracked in the organization. Automation covers most needs; medium-to-high metric goals.

  3. Run#

    The capability is understood and tracked by all teams. Very ambitious goals; automation is the preferred approach.

The dimensions assessed#

The framework is organized into four domains, each grouping capabilities. Each capability has its own maturity level.

  • Understand Usage & Cost — Data Ingestion#

    Data Ingestion

  • Understand Usage & Cost — Allocation#

    Allocation

  • Understand Usage & Cost — Reporting & Analytics#

    Reporting & Analytics

  • Understand Usage & Cost — Anomaly Management#

    Anomaly Management

  • Quantify Business Value — Planning & Estimating#

    Planning & Estimating

  • Quantify Business Value — Forecasting#

    Forecasting

  • Quantify Business Value — Budgeting#

    Budgeting

  • Quantify Business Value — KPIs & Benchmarking#

    KPIs & Benchmarking

  • Quantify Business Value — Unit Economics#

    Unit Economics

  • Optimize Usage & Cost — Architecting & Workload Placement#

    Architecting & Workload Placement

  • Optimize Usage & Cost — Rate Optimization#

    Rate Optimization

  • Optimize Usage & Cost — Usage Optimization#

    Usage Optimization

  • Optimize Usage & Cost — Sustainability#

    Sustainability

  • Optimize Usage & Cost — Licensing & SaaS#

    Licensing & SaaS

  • Manage the FinOps Practice — FinOps Practice Operations#

    FinOps Practice Operations

  • Manage the FinOps Practice — Governance, Policy & Risk#

    Governance, Policy & Risk

  • Manage the FinOps Practice — FinOps Assessment#

    FinOps Assessment

  • Manage the FinOps Practice — Automation, Tools, & Services#

    Automation, Tools, & Services

  • Manage the FinOps Practice — FinOps Education & Enablement#

    FinOps Education & Enablement

  • Manage the FinOps Practice — Invoicing & Chargeback#

    Invoicing & Chargeback

  • Manage the FinOps Practice — Intersecting Disciplines#

    Intersecting Disciplines

  • Manage the FinOps Practice — Executive Strategy Alignment#

    Executive Strategy Alignment

How to use it#

  1. Identify the capabilities that matter for your context (visibility, allocation, forecasting, optimization…).
  2. Assess each one as Crawl, Walk or Run.
  3. Aim for the stage suited to business value, not the highest: a capability that is sufficient at “Walk” does not justify additional investment.
  4. Reassess regularly; the framework itself evolves.

Limitations and precautions#

  • The list of capabilities changes from one version of the framework to another: check the current version on the FinOps Foundation website.
  • FinOps is not just a cost-cutting tool: it aims at the value obtained per euro spent.
  • Maturity measures the practice, not the savings achieved.

Sources and verification#