Your cloud bill arrived last month. It was higher than expected. Again. Nobody can fully explain why, and the finance team is left trying to forecast a number that seems to move on its own.
If this sounds familiar, you're not alone. And you're exactly the kind of organisation that FinOps was built for.
What Is FinOps, Exactly?
FinOps stands for Financial Operations, specifically for cloud. It's the practice of bringing financial accountability to cloud spending - giving finance, engineering, and leadership a shared language and shared responsibility for what the organisation spends on cloud infrastructure.
Think of it this way: before cloud, you bought servers. They had a fixed cost. You could depreciate them, budget for them, and predict what IT would cost next year with reasonable accuracy. Cloud changed all of that. Now, any engineer with the right permissions can spin up resources that cost real money, and the bill doesn't land until the end of the month.
FinOps is the discipline that closes that gap. It's not a tool or a product - it's an operating model that helps organisations understand, control, and optimise their cloud spend.
Why Your CFO Should Care
Here's the uncomfortable truth: cloud spending is the fastest-growing line item in most IT budgets, and it's one of the least well-understood by finance teams.
The numbers tell the story. Industry research consistently shows that 32% of cloud spend is wasted - resources running that nobody needs, services sized far larger than necessary, and commitments that don't match actual usage. On top of that, organisations exceed their cloud budgets by an average of 17%.
For a company spending £500,000 a year on Azure, that's potentially £160,000 going to waste. That's not a rounding error. That's headcount. That's investment. That's profit.
CFOs care about three things when it comes to any cost centre: predictability, accountability, and return on investment. Cloud, left unmanaged, fails on all three.
The Frustrations We Hear From Finance Teams
Every conversation we have with finance leaders about cloud costs circles around the same pain points:
"The bills are unpredictable." One month it's £40,000, next month it's £52,000, and nobody warned finance it was coming. There's no way to forecast accurately because consumption fluctuates and there's no governance in place.
"We can't see the ROI." The business moved to cloud for agility and cost savings, but the savings never materialised. Nobody can point to specific business outcomes tied to specific cloud costs.
"Engineers deploy without thinking about cost." Development teams spin up resources, run experiments, and move on. The resources keep running. The bills keep climbing. Nobody owns the clean-up.
"We don't know what we're paying for." A single Azure invoice can contain hundreds of line items across dozens of services. Without tagging, cost allocation, and clear ownership, it's a wall of noise.
Sound familiar? These aren't edge cases. They're the norm for organisations that haven't adopted FinOps.
FinOps Is NOT Just About Cutting Costs
This is the biggest misconception. FinOps is not about slashing your cloud bill to the bone. It's about spending wisely - understanding what you're paying for, ensuring every pound delivers value, and making informed trade-offs.
Sometimes FinOps means spending more, not less. If a workload needs higher-spec infrastructure to meet SLAs, that's a valid business decision. The difference is that with FinOps, it's a conscious decision with visibility into the cost impact, not something that happens by accident.
The goal is not the lowest possible cloud bill. The goal is the right cloud bill - one where every line item maps to a business outcome and someone owns it.
The Three Phases of FinOps
The FinOps Foundation - the industry body that defines FinOps best practices - breaks the journey into three phases. Most organisations we work with are stuck somewhere in the first.
Phase 1: Inform (Visibility)
You can't optimise what you can't see. The first phase is about getting clear, accurate visibility into where the money goes.
This means:
- Tagging resources so you can allocate costs to teams, projects, and environments
- Showback and chargeback - showing departments what their infrastructure actually costs (showback) or billing them directly for it (chargeback)
- Dashboards and reporting that finance and leadership can actually understand, not just raw consumption data
Most organisations think they've done this because they have Azure Cost Management open. They haven't. Having the data and having actionable visibility are very different things.
Phase 2: Optimise (Reduce Waste)
Once you can see the spend clearly, you start acting on it. This is where the savings come from:
- Right-sizing - matching resource sizes to actual usage. Most VMs are oversized because someone provisioned them for peak load that never came
- Reserved Instances and Savings Plans - committing to predictable workloads for 1 or 3 years and saving 30-60%
- Automated shutdowns - stopping dev/test environments outside working hours instead of paying 24/7 for 8 hours of use
- Storage tiering - moving rarely accessed data to cheaper tiers instead of paying premium prices for cold data
- Deleting orphaned resources - cleaning up the disks, IP addresses, and load balancers left behind when someone deleted a VM but not its dependencies
Phase 3: Operate (Continuous Governance)
This is where FinOps becomes self-sustaining. Instead of periodic reviews, cost management becomes part of how the organisation operates:
- Automated policies that prevent waste before it happens
- Budget alerts that flag anomalies in real-time
- Regular cost reviews built into sprint cycles and business planning
- Engineering teams that own their costs as naturally as they own their code quality
Very few organisations reach Phase 3 fully. But even getting partway there transforms how cloud spend is managed.
The FinOps Foundation and Why It Matters
The FinOps Foundation, part of the Linux Foundation, has formalised FinOps as a discipline with frameworks, certifications, and best practices. It's not just a buzzword - it's a recognised operational model adopted by organisations from startups to FTSE 100 companies.
Why does this matter to a CFO? Because it means there are established playbooks, benchmarks, and maturity models. You're not inventing something new. You're adopting a proven approach that thousands of organisations have already validated.
Why Most Organisations Start Too Late
Here's the pattern we see repeatedly: an organisation migrates to cloud, enjoys the flexibility, lets spending grow organically for 12-18 months, and then someone in finance notices the trend line. By the time they react, there are months of accumulated waste, no tagging strategy, no cost ownership, and a culture where engineers have never had to think about what things cost.
The best time to implement FinOps was when you first moved to cloud. The second-best time is now - before the next "bill shock" moment forces a reactive, painful cost-cutting exercise instead of a measured, strategic one.
Where to Start
If you're a CFO or finance leader reading this, here's what we'd suggest:
- Get visibility first. You need to know what you're spending, broken down by team, project, and environment. If your resources aren't tagged, start there.
- Assign cost ownership. Every resource should have an owner. Every team should see what their infrastructure costs.
- Look for quick wins. Right-sizing, shutting down unused resources, and deleting orphaned infrastructure typically saves 20-40% with minimal effort.
- Build it into governance. Cost review should be a standing agenda item, not an annual panic.
You don't need a massive FinOps team to start. You need visibility, accountability, and someone who knows where to look.
Not sure where the waste is hiding in your cloud spend? Our free assessment gives you a clear picture of your Azure costs and shows you exactly where the savings opportunities are - no commitment, just visibility.