Direct answer: Every application in an estate costs money to keep: it has to be patched, tested, packaged and supported, and it slows every programme that has to work around it. The hidden cost sits in four kinds of application: those with no named business owner, those nobody uses, those out of vendor support, and forgotten tools such as old remote-access software. Find them, confirm use, name an owner or a removal date for each, and retire what nobody needs before year-end renewals and the change freeze lock the estate in for another year.
Every application carries a cost that rarely appears as one line in a budget:
That cost is the same whether anyone decided to keep the application or not. Which is why the applications nobody chose are the most expensive ones to have.
An application without a named business owner turns every patch, renewal and migration decision into an investigation. Who uses it? Can we update it? Can we remove it? Nobody can say yes, so nothing changes.
Some applications have no active users at all. They still need patching, testing and packaging, and they still sit in every migration plan.
Unsupported applications don't stop running. That's the problem. They keep working, so they escape risk registers, while they miss security fixes and block upgrades to the platforms around them.
Some of the riskiest applications are the smallest: old remote-access tools installed for a one-off support job, utilities left behind by a project, trials that never ended. Forgotten remote-access tools in particular are doors into the estate, and they're rarely patched.
At Halloween it's tempting to call these zombie applications, and the name fits. Nobody's looking after them, and they don't go away on their own.
Two deadlines make the next few weeks the right time to act.
Renewals. Automatic renewals let an estate grow without anyone deciding it should. Many contracts renew at year end. Before anything renews, an owner should confirm it's still used, still needed and correctly sized.
The change freeze. Most enterprises freeze change over the year-end period. Decisions not made before the freeze wait until the new year, and applications not packaged and tested before December wait with them. A decision made in October is in place for January; one left until November often isn't.
Start from what's actually installed, not what the asset register says. Strip out the runtimes, drivers and components that aren't really applications, so the list reflects the estate the business runs.
Start with the most-patched and most-expensive applications, where an owner makes the biggest difference. If nobody will own an application, that's an answer in itself.
For each application, check whether anyone is actually using it. No users and no owner usually means it can go.
For every application, check whether the vendor still supports the version in use. Each unsupported one needs a decision: upgrade, replace, isolate or retire, with an owner and a date.
List everything that renews before the end of the year. Have each owner confirm it's used, needed and correctly sized before it's renewed.
The output is an owned list: what to keep, what to fix and what can go.
Removing an application is a change, and it deserves the same care as installing one. Retiring properly means:
Done well, retirement removes the cost for good. Done badly, the application reappears next year.
We help enterprises cut the estate they pay for, using our Sync, Align, Optimise approach.
Confirm use, name an owner, retire the rest, and next year starts with an estate you chose.
Request a 30-minute discovery conversation with our team. We'll help you find the applications nobody owns, before they renew into next year.