Where Your Cloud Budget Actually Goes — and Why IT Can't Fix It Alone
Where Your Cloud Budget Actually Goes — and Why IT Can’t Fix It Alone
A mid-sized manufacturing company in Baden-Württemberg discovered they were spending €120,000 per month on AWS. When they dug deeper, they found that a development team had provisioned a high-memory database instance for testing 18 months ago. The database was never used but had been running continuously. Another team was exporting data to cold storage monthly, but nobody was actually accessing it. A third had spun up 40 virtual machines for a proof-of-concept that concluded six months prior. The machines were still running.
The engineering team wasn’t careless. They simply had no mechanism to understand who was spending what, why, or who was accountable for optimising it. IT knew the cloud estate was inefficient. Finance knew the bill was high. Neither could explain the gap to the other.
This pattern repeats across organisations of every size. Gartner reports that enterprise companies waste 23-40% of their cloud budget. For mid-market companies, the figure is often higher. The waste falls into predictable categories: underutilised resources (30%), over-provisioning (25%), forgotten resources (20%), poor purchasing decisions (15%), and misconfigured storage (10%). But the root cause is always the same: governance failure. Not technical failure—governance failure.
The Visibility Problem
The first problem is visibility. Most organisations have little idea where their cloud spend is actually going.
CFOs see a monthly AWS or Azure bill and ask engineering teams to “explain the spike.” Engineering teams respond with architecture diagrams and utilisation metrics. Neither side is wrong, but they’re answering different questions. Finance wants to know: What business value are we getting for €120,000? Engineering wants to know: Are our systems performing well?
These are related but distinct questions, and answering them requires different information. Finance needs allocation to business units or projects. Engineering needs visibility into resource utilisation. Neither has it.
In practice, most organisations have some form of cost monitoring—AWS Cost Explorer, Azure Cost Management, third-party tools. These tools provide visibility within the cloud platform. But they don’t connect cloud spend to business outcomes. A cost report showing €50,000 spent on EC2 tells you nothing about whether that EC2 is worth what you’re paying.
The visibility problem is compounded by how cloud works. Traditional IT asset management was straightforward: you bought a server, it lived in a data centre, you knew what it was for. Cloud resources can be spun up and torn down instantly, often without formal approval. A developer can provision a database in five minutes. Unless there’s active monitoring, nobody knows about it.
Most organisations don’t have active monitoring at the required level. Cost centres don’t have budget ownership. Teams don’t have chargeback models. Resource tagging is inconsistent. When you don’t know who owns what, optimisation becomes impossible.
The Accountability Gap
The second problem is accountability. When IT provisioned all hardware, IT was accountable for efficiency. Cloud breaks that model, but organisations often don’t update their governance to reflect it.
In cloud-first organisations, business units request and consume resources. But they’re often not charged for them directly. IT absorbs the cost and allocates it broadly to departments. This decouples the cost from the decision-maker. If a product team provisions infrastructure, they don’t see the impact on their budget. If they see it at all, it appears as a vague “IT allocation.”
This creates perverse incentives:
- Over-provisioning becomes risk-free. If I don’t know what I’ll need, I provision conservatively high. The cost is hidden in shared IT budgets.
- Deprovisioning becomes invisible. When a project ends, do we remember to shut down the infrastructure? If it doesn’t directly impact the team’s budget, probably not.
- Optimisation is someone else’s problem. IT can suggest optimisation. But if the business unit that provisioned the resources doesn’t benefit from cost reduction, why would they prioritise it?
The governance failure manifests as this accountability gap. Someone needs to be explicitly responsible for cloud cost within each business unit. That person needs to see their usage and their costs clearly. And there needs to be a mechanism to translate cost into allocation or chargeback.
This doesn’t require complex IT systems. It requires clear ownership and transparent visibility. But it does require intentional design.
The Structural Problem
A third problem, more subtle, is structural: the people who optimise cloud costs are often not the same people who can authorise purchases.
In a typical enterprise, the cloud procurement decision is made by IT leadership or architecture teams. They negotiate contracts, select vendors, set up accounts. They’re optimising for reliability, security, and governance. Once purchasing decisions are made, optimisation shifts to operational teams: DevOps, platform engineering, and occasionally finance.
But purchasing decisions affect optimisation opportunities. If you’ve committed to reserved instances for certain resources, your ability to right-size is constrained. If you’ve selected a vendor ecosystem, migration to cheaper alternatives becomes expensive. If your security or compliance requirements are built into the architecture, optimisation might require re-architecting.
The people making long-term purchasing decisions often don’t bear the cost of inefficiency. The people bearing the inefficiency cost often lack authority to renegotiate purchasing decisions.
Effective cloud cost governance requires these functions to be aligned. Procurement needs to understand operational constraints. Operations needs visibility into purchasing decisions. And someone in the middle needs accountability for the total cost, not just the optimisation piece.
Four Structural Fixes
Most organisations we work with successfully reduce cloud costs by 20-35% without reducing utility. It’s not magic. It’s governance.
First: Establish clear cost ownership. Assign a person or team (often from finance, sometimes from IT, ideally shared) to own cloud cost. Give them visible budget authority. Make them accountable for efficiency. This person sits between business units and IT, translating between “we need more infrastructure” and “we can achieve that €X cheaper.”
Second: Implement chargeback or showback. Business units need to see, clearly and regularly, what their cloud consumption costs. This doesn’t require charging them directly. It can be “showback”—showing them what they spend, even if the cost is absorbed centrally. But visibility is non-negotiable. Monthly cost reports to each business unit, clear about what’s being consumed and why.
Third: Establish tagging discipline. Most organisations have tagging strategies. Few execute them consistently. Cloud resources need clear metadata: which business unit owns this, what project it’s for, what cost centre should it be charged to, is it still active? Without this, allocation and reporting become guesswork. With it, you can identify orphaned resources, track costs by business unit, and hold people accountable.
Fourth: Create a regular optimisation process. Someone needs to regularly review the cloud estate and identify opportunities. This might be quarterly reviews led by the cost owner, monthly reports from your cloud vendor, or a dedicated cost optimisation project. The key is regularity and a feedback loop: identify opportunities, implement them, measure the savings, and reinvest some of the savings in further optimisation.
This is governance, not technology. You don’t need new tools. You need clear ownership, visible allocation, and regular review.
Why IT Alone Can’t Solve It
Most organisations that struggle with cloud cost have a capable IT department. The problem isn’t technical incompetence. It’s that IT can’t solve a governance problem by itself.
IT can suggest right-sizing a database. But they can’t force a business unit to right-size if the cost isn’t visible to that unit. IT can implement tagging discipline. But they can’t enforce chargeback if finance doesn’t have budget structures to support it. IT can identify orphaned resources. But they can’t delete them if nobody has authority to do so.
Cloud cost governance requires cross-functional alignment: IT needs to understand business context, finance needs technical literacy, and business units need accountability for their choices. None of these functions can succeed alone.
When we work with organisations on this, the pattern is consistent: the first meeting includes engineering, finance, and often procurement. Within 90 days, we’ve usually improved visibility significantly. Within six months, most organisations have reduced costs by 20-30%. But none of that happens if IT tries to solve it alone.
The DACH Approach
In German-speaking markets, cloud cost governance often reflects broader cultural values around cost discipline and transparency. German engineering culture emphasises precise measurement and accountability. Financial governance in these regions tends to be formal and clearly structured.
This creates an advantage: companies in DACH markets often establish clearer cost ownership earlier than their European counterparts. Finance teams are accustomed to detailed cost allocation. IT teams are comfortable with structured documentation. The cultural expectation is that costs are explainable and allocated fairly.
However, the same cultural emphasis on stability can slow cloud adoption. If cloud is perceived as unpredictable or uncontrolled, adoption is slower. Establishing clear governance first—before significant cloud investment—can accelerate adoption by addressing the primary concern: cost predictability and accountability.
Bottom Line
Cloud cost optimisation is 80% governance and 20% technical optimisation. If your governance is broken, better tools won’t help. If your governance is clear, optimisation follows naturally.
Start with ownership: who is responsible for cloud cost in your organisation? Move to visibility: what is each team spending, and do they know it? Then to accountability: are teams incentivised to optimise their own usage? Finally, to regular review: is there an established process for identifying and implementing cost reductions?
The team in Baden-Württemberg saved €30,000 per month—€360,000 per year—not by adopting new technology, but by answering these questions. They assigned cost ownership. They implemented monthly showback reports to each team. They established tagging discipline. They created a quarterly optimisation review.
That money went back into accelerating feature development. IT became more trusted because they could explain costs. Finance got the clarity they needed. And the business moved faster, not slower.
That’s what clear governance delivers. And it costs almost nothing to implement.
This article is based on extensive research. The full evidence base with sources is available upon request.