Introduction: The Cloud Cost Reckoning
Cloud spending crossed $669 billion globally in 2024. By 2026, analysts project it will exceed $840 billion. That growth rate would be exciting if organizations were getting full value from every dollar. Most are not.
The Flexera 2025 State of the Cloud Report found that 84% of organizations cite cloud spending as their top challenge. More pointedly, 78% of organizations estimate that 21 to 50% of their cloud spend is wasted. A Harness report put the number at $44.5 billion in preventable waste in 2025 alone.
This is not a budgeting problem. It is a visibility, accountability, and culture problem. And it is exactly what FinOps was designed to solve.
What FinOps Actually Means
FinOps is not a tool. It is not a software category or a vendor pitch. The FinOps Foundation, the governing body that defines the practice, describes it as a cultural practice that enables organizations to get maximum business value from their cloud investments by bringing engineering, finance, and business teams together around a shared model of cloud accountability.
The word itself is a contraction of “Finance” and “DevOps.” That etymology matters. FinOps borrows DevOps’ core principle: break down silos between teams that need to work together, establish shared ownership, and build feedback loops that make decisions faster and better.
In cloud cost management, those silos between engineering and finance are expensive. Engineering teams build and scale without cost context. Finance teams receive cloud invoices they cannot decode. Neither team can act effectively without the other. FinOps creates the bridge.
The Scale of the Problem
Before examining how organizations improve their FinOps maturity, it is worth pausing on why this problem is so persistent.
Cloud cost waste does not come from carelessness alone. It comes from the structural disconnect between how cloud resources are provisioned and how financial decisions are made in most organizations. In traditional IT, procurement was a deliberate, slow process. Buying a server required purchase orders, approvals, and delivery timelines. The friction itself enforced discipline.
Cloud removed that friction entirely. An engineer can provision $50,000 worth of compute in minutes, often without any approval. That same engineer is rarely accountable for what the instance costs when idle at 3 AM on a Sunday. The provisioning decision and the cost consequence are separated by organizational distance.
The result: idle compute resources account for 35% of cloud waste. Overprovisioned instances account for another 25%. A 2024 State of Cloud Cost Intelligence Report found that only 30% of surveyed organizations knew exactly where their cloud budget was going.
The Maturity Model as a Framework
The FinOps Foundation developed the FinOps Maturity Model to give organizations a structured path forward. It is not a certification or a one-time assessment. It is a continuous improvement framework.
The model organizes FinOps capabilities across four domains: understanding cloud usage and cost, quantifying business value, optimizing cloud usage and cost, and managing the FinOps practice itself. Within those domains sit 22 distinct capabilities, and each capability can be practiced at three maturity levels.
Those three levels are Crawl, Walk, and Run.
Crawl is where most organizations begin. Costs are tracked reactively. Tagging is inconsistent. Accountability is unclear. The finance team gets a monthly invoice and nobody in engineering feels responsible for it.
Walk is where cost optimization becomes an active practice. Teams start using the visibility from Crawl to take action. Budget controls go in. Rightsizing recommendations get implemented. Cross-functional meetings between finance and engineering happen regularly.
Run is where cloud cost is woven into architecture decisions before code ships, not after invoices arrive. Optimization is automated. Unit economics connect cloud spend to business outcomes. Cost avoidance is measured alongside cost reduction.
What This Book Covers
This book is organized to take you through each dimension of that journey.
The Background chapter explains the history of how FinOps emerged as a discipline and how the FinOps Foundation codified the framework. It covers the four domains in detail and introduces the personas who make FinOps work.
The Analysis chapter examines each maturity stage in depth. What does Crawl actually look like inside an organization? What are the failure modes that keep teams stuck there? What does the transition to Walk require? What separates Walk from Run? This chapter provides the diagnostic lens to understand where an organization stands and what holds it back.
The Case Studies chapter draws on documented examples: WPP saving $2 million in three months and reaching a 30% annual cost reduction, a global insurer uncovering $17 million in annual savings, and an adtech company cutting AWS costs by 62%. These are not hypothetical scenarios. They are repeatable patterns with identifiable causes.
The Conclusion chapter synthesizes the key principles and offers a practical starting framework.
One Principle to Carry Forward
Before diving in, one principle from the FinOps Foundation deserves emphasis. It is counterintuitive and important.
The goal of the FinOps Maturity Model is not to reach Run stage across all capabilities. The FinOps Foundation explicitly states this: “There are no runners.” Getting to Run is not the goal, and it is not the finish line.
The goal is to practice each capability at the maturity level appropriate for your specific environment, team size, and business context. A startup with three engineers and a single AWS account does not need the same level of FinOps sophistication as a Fortune 500 company running workloads across AWS, Azure, and GCP.
Maturity is not a competition. It is a calibration.
That calibration, done well, is how organizations stop losing 30% of their cloud budget to waste and start directing that money toward the workloads that actually move the business forward.