IT budget without transparency: why the numbers diverge from reality
How companies lose control of IT spending, and what it takes for the budget to reflect what is actually happening.
When I ask executives about the structure of their IT spending, I often see the same picture. There is an IT budget - the amount approved for the year. There are actual expenses - the numbers that come from accounting. And there is reality - what was actually bought, why, and whether it is delivering value.
Between these three layers there are almost always gaps.
Where the opacity comes from
The root cause is the way IT spending reaches the books. Some of it goes through subscriptions that nobody revisits each year. Some through project costs that blur across several budget lines. Cloud spending grows with usage and is not tied to specific business objectives. SaaS subscriptions are paid on credit cards across different departments.
As a result, the financial picture the CFO sees differs substantially from what is actually happening in the infrastructure.
Add to this what I call "IT zombies" - systems and services that were once needed but have long gone unused while continuing to cost money. Licences for products that were replaced a year ago. Cloud resources from a finished project. Subscriptions that were never cancelled when an employee left.
Why this is not just an IT problem
Opacity in IT spending has several consequences that directly affect the business.
Misallocated investment. If management cannot see what is consuming the IT budget, it cannot make a sound decision about where to invest additionally. Money for new initiatives is requested from a budget that is already covertly overloaded.
Invisible risk. Systems that nobody maintains but that keep running are a risk. If something breaks, it is unclear who is responsible and what to do.
Difficulty benchmarking. Without a structured view of spending, the question "are we spending more or less on IT than is reasonable for our size and sector?" has no answer.
What normal IT transparency looks like
I am not talking about detailed billing for every byte - that is excessive. Normal transparency means:
- spending is broken down into meaningful categories: infrastructure, licences, development, support, new projects;
- each category has an owner who can explain the trend;
- cloud spending is attributed to specific services or teams, not reported as a single line;
- quarterly reviews identify unused or duplicated resources;
- increases or decreases in spending can be explained by specific decisions, not "that's just how it came out".
How to start
The practical first step is not a comprehensive audit but a few specific actions.
Ask the IT team to produce a list in three categories: what is clearly used and needed, what is unused or questionable, and what we are not sure about. This takes a day or two and immediately surfaces leads.
Then - pull all active SaaS subscriptions with amounts. This comes from the finance team or directly from corporate cards. For each one, ask: who last logged in, and when?
After that - the cloud bill. Ask for a breakdown by service and by team. If that breakdown does not exist, that is itself a problem that needs solving.
The result of these three steps is not a perfect cost management system, but a clear picture to start from.
IT spending transparency is not a technical question. It is a management choice: how well does the company want to understand what it is paying for.