The hidden cost of outdated software

The invoice is correct. Vendor, amount, the depreciation running neatly through the ledger: it is all right. Only the question underneath rarely comes up. Are you still using what you pay for?

The cost of outdated enterprise software almost never sits as a single line on the budget. It is spread out. A per-user licence that keeps running. A tool someone requested three years ago that nobody opens anymore. The hours your IT team spends on systems that have had their day. Each piece looks too small to make a fuss about. Together they are not incidents, but a leak that comes back every month.

The bill nobody adds up

Start with the licences. Enterprise software typically charges per user, and that model has a property you only feel once it is too late: it keeps counting, whether that user works in the system or not. Someone leaves, but the seat stays in the count. A department buys a package for a project that stalls after a year. The spend? It just keeps running.

How much this adds up to has been measured. According to the Flexera State of ITAM report (2024), organisations waste an estimated 20% to 30% of their IT spend. The teams that, in that same report, are best at measuring this arrive at figures that offer no reassurance: 30% waste on desktop software, and more than half of SaaS licences going unused. More than half. That is not a margin. That is a cost line half made of air.

The number of tools makes it worse. BetterCloud (2024) calculated that the average company used around 106 SaaS applications in 2024. One hundred and six applications, each with its own contract and its own place where company data ends up. Who keeps that list complete? Usually nobody. That sprawl does not come from poor management. It comes from every separate package coming in easily and rarely going back out.

Maintenance is a cost, even when nothing changes

Alongside what you buy sits what you keep standing. An older system demands maintenance that delivers nothing new. Connections that break with every update. A version that no longer receives support and so becomes an exception in your security. And the knowledge about it, which often sits with one external party or one person, who one day retires. No incidents. A fixed burden.

That burden has a name: technical debt. McKinsey (2020) calculated that CIOs estimate it at 20% to 40% of the value of their entire technology landscape. For anyone defending a budget, this is the figure that hurts: 10% to 20% of the budget for new products goes, according to that same study, toward clearing old debt. Every euro that goes there builds nothing. It pays a bill from the past.

Why the cost grows with you, not with your value

The sting is in the direction. In a model that charges per user, your software cost grows with your headcount. Things go well, you hire ten people, and the licence invoice rises with them, whether those ten ever open the more expensive modules or not. The spend hangs on your size. Not on what it returns to you. For years this feels normal, until someone asks why growth should cost more than the infrastructure that carries it.

What changes when the platform is yours

There is another way to build up the bill. One platform instead of dozens of separate packages, with the code in your own repository and not in a vendor's possession. The cost moves with the servers and the storage you actually use, not with the number of names on a user list. Growth then burdens the machine, not the person.

This does not suddenly make software free, and it does not solve everything on its own. What it does change is the shape of the bill. You pay for use instead of for access. If you are locked into one vendor today, the code now sits ready to be taken over by another party. And the more than a hundred contracts from earlier become one.

• Your invoice follows servers and storage, not the number of heads on the payroll.
• One stack instead of dozens of tools, with one place for your data and one party you can call when something breaks.
• The code sits in your own repository, transferable to any integrator you choose.
• What runs, runs visibly, instead of sinking into sprawl that nobody can survey anymore.

The first step is not to migrate. It is to add up. Put three amounts side by side: what you pay for licences this year, how many of those seats are actually used, and what share of your IT budget goes to maintaining the existing rather than to something new. Almost nobody knows those three numbers by heart. Whoever does know them sees at once what the conversation about outdated software is really about. Not about technology. About money that leaves every month without anyone having approved it.