Share with your CFO/COO
Twenty-seven percent of enterprise cloud spend is wasted, according to Flexera’s 2025 State of the Cloud report, and the companies closing that gap fastest are treating cost as an operational discipline, not a one-time audit. Across five real-world FinOps deployments, outcomes ranged from a 60% cloud cost reduction at Brazilian fintech Ouribank to 10-30% waste recovery at enterprises implementing basic tagging and governance. Advisory firms Everest, Kearney, and Protiviti each report that 12-18 months is the realistic window to reach meaningful maturity.
What this means for your business
The story sorts cleanly by where you are in the maturity curve. If your cloud costs are still allocated at the account or department level rather than the workload or product level, you’re in the same position Ouribank was before it scaled cost tagging from 0% to 94% and cut its bill in half. The companies seeing 5-10% savings from centralized FinOps, and 20-60% from mature programs, aren’t running exotic playbooks. They’re doing the unglamorous work of tagging every resource, assigning ownership, and building chargeback, the internal billing process that makes each team accountable for what it consumes.
The most practically interesting case here is the digital media company that embedded cost data directly into developer tooling and saved millions within months. Cost as an engineering signal, treated with the same weight as latency or system reliability, is a different organizational posture than cost as a finance report. Most enterprises structure FinOps as a cost-control mandate handed down from finance, which is precisely why it stalls. When developers see spend data inside the tools they already use, they optimize without being told to. That behavioral shift is harder to buy than any reservation discount and worth more over time.
Protiviti’s Will Thomas puts the governance ceiling clearly: FinOps treated as an IT-only or finance-only function caps its own impact. The programs generating the top-end returns are cross-functional by design, with defined decision rights pushed to mid-level managers rather than routed through a central committee. If your FinOps program lives inside one department, the 20-60% savings range cited by Everest’s Titus M is not your range. The 5-10% figure from the telco case, where cross-functional collaboration was real but still maturing, is a more honest benchmark for programs that haven’t yet made cost a shared accountability. I’d revise that view if enterprises with siloed FinOps structures consistently broke above 15% savings, but the case evidence here runs the other direction.
Concept deep-dive: Chargeback
Chargeback is the internal accounting mechanism that assigns cloud costs to the specific team, product, or business unit that generated them, rather than pooling expenses in a shared IT budget. It exists because shared costs create no individual incentive to reduce consumption. The analogy is a restaurant bill split equally regardless of what anyone ordered. Tagging governance, assigning metadata labels to every cloud resource, is the prerequisite that makes chargeback possible at any useful level of granularity.
Based on reporting from 5 real-world FinOps use cases to maximize ROI, originally published 2026-03-13 03:00:00.
