Flexera's 2024 State of the Cloud report surveyed over 700 technology leaders. One number stood out: organisations estimate they waste 34% of their cloud spend.
For a company spending $200,000 per year on AWS, Azure, or Google Cloud, that is $68,000 disappearing without delivering any business value. For a company spending $1 million, it is $340,000.
The uncomfortable truth is that most organisations do not know which 34% is being wasted. They know the total bill. They do not know why it is what it is.
Where Cloud Waste Actually Hides
Cloud waste is not one problem. It is five problems that accumulate quietly.
1. Idle and Orphaned Resources Resources that are running but not being used. Virtual machines provisioned for a project that ended six months ago. Development environments left running over weekends and holidays. Databases attached to applications that were decommissioned.
Idle VMs alone typically account for 12–18% of cloud spend in organisations without active FinOps governance.
2. Oversized Instances When cloud resources are provisioned, engineers default to larger sizes to avoid performance issues. This is rational at the time. Six months later, the workload has stabilised and the instance is running at 15% utilisation — but the bill reflects 100%.
Right-sizing analysis consistently finds 20–30% of compute instances are oversized by at least one tier.
3. Unused Reserved Capacity Reserved Instances and Savings Plans offer 30–60% discounts in exchange for 1 or 3-year commitments. Organisations that purchase reservations without proper planning end up with reserved capacity that does not match their actual workload patterns — paying for commitments they cannot consume.
4. Uncontrolled Data Transfer Costs Egress charges — fees for moving data out of a cloud provider's network — are notoriously difficult to track. They do not appear as a line item in the way compute and storage do. They accumulate invisibly in the bill until someone investigates.
5. Storage Tier Mismanagement Object storage left in high-performance tiers when it should be archived. Snapshots retained indefinitely by default. Log data accumulating for years without a lifecycle policy.
Storage waste is slow, predictable, and almost always fixable — but only if someone is actively looking at it.
The FinOps Gap in Most Organisations
FinOps — Financial Operations for cloud — is the discipline of bringing financial accountability to cloud spending. It requires three things working together: visibility into what is being spent, accountability from the teams doing the spending, and optimisation processes to act on what the data reveals.
Most organisations have partial visibility (billing dashboards) but lack accountability structures and optimisation processes. The result is that every team knows the total bill but nobody owns the responsibility for reducing it.
The Flexera report found that only 27% of organisations have a formal FinOps practice in place. The remaining 73% are managing cloud costs reactively — responding to bill shock rather than preventing it.
What a FinOps Maturity Assessment Reveals
A FinOps maturity assessment measures your organisation across four domains:
Cost Visibility Do you have tagged resources across all cloud accounts? Can you attribute spend to specific teams, projects, or products? Do you have automated alerting on spend anomalies?
Governance and Accountability Are there defined budget owners for each cloud workload? Is there a regular cadence for cost review meetings? Are engineers aware of the cost impact of their provisioning decisions?
Optimisation Processes Is there an active right-sizing programme? Are Reserved Instances and Savings Plans reviewed quarterly? Is there a lifecycle policy for storage and snapshots?
Forecasting and Planning Are cloud budgets set based on workload projections or historical trend? Is there a process for reviewing actuals against forecast monthly?
Each domain is scored on a maturity model from Initial (no process) through Developing and Defined to Managed and Optimised. The resulting profile shows exactly where your organisation is losing money and where effort will have the highest return.
The CFO Conversation
Cloud costs have moved from IT budget line to board-level concern. CFOs are now asking specific questions:
- What is our cloud spend per unit of revenue?
- What percentage of our cloud bill is waste?
- What would a 20% reduction require?
Without a structured FinOps assessment, the IT team cannot answer these questions with evidence. With one, they can walk into the CFO meeting with a documented baseline, a waste quantification, and a prioritised optimisation roadmap.
The 90-Day FinOps Quick Win Plan
A FinOps assessment typically produces three tiers of recommendations:
Immediate (0–30 days): Delete identified idle resources. Apply lifecycle policies to storage. These actions alone typically reduce spend by 8–15% with no architectural changes.
Short-term (30–60 days): Right-size oversized instances based on utilisation data. Enable automated shutdown for non-production environments outside business hours.
Medium-term (60–90 days): Purchase Reserved Instances for stable baseline workloads. Implement tagging policies and enforce them via policy-as-code. Establish monthly cost review cadence.
Organisations that execute this plan consistently achieve 20–30% cloud cost reduction within 90 days.
Frequently Asked Questions
What is FinOps? FinOps (Financial Operations) is the practice of bringing financial accountability to cloud spending. It combines people, processes, and tooling to give organisations full visibility into cloud costs and the governance structures to control them.
How much cloud spend is typically wasted? Flexera's 2024 State of the Cloud report found the average organisation wastes 34% of its cloud budget. For mature FinOps organisations, this figure drops to below 10%.
What cloud platforms does FinOps apply to? FinOps principles apply to all major cloud platforms — AWS, Microsoft Azure, and Google Cloud Platform. Multi-cloud environments (using two or more providers) typically have higher waste due to visibility gaps between platforms.
Can a FinOps assessment be done without a FinOps specialist? A FinOps maturity assessment can be completed by an IT consultant or MSP using a structured framework. It identifies gaps and prioritises recommendations. Specialist FinOps tooling (CloudHealth, Apptio Cloudability, AWS Cost Explorer) may be needed for deep cost analytics.
How long does a FinOps assessment take? A structured FinOps maturity assessment takes 10–15 minutes and produces an immediate gap analysis across the four core domains. Full cost analytics and right-sizing analysis require access to billing data and typically take 1–2 weeks.
TACGauge's FinOps assessment gives IT consultants and MSPs a structured way to benchmark their clients' cloud financial management maturity — producing a scored gap analysis and 90-day optimisation roadmap that CFOs and IT directors can act on immediately.