Almost every organisation knows it’s paying for software it doesn’t use. Seats assigned to people who’ve left, tools bought by one team that duplicate tools bought by another, premium tiers on products used at their most basic level, contracts that renewed automatically because nobody was watching the date.

And almost every organisation keeps putting off a software licence audit. They’re tedious, they cut across budget holders, and they rarely feel urgent.

They should. A licence review is one of the quickest ways to find money already being spent without return – and it usually reveals much more about how technology is governed than about software alone.

Why the licence audit keeps slipping

Software spend is spread across many budgets and many owners. Subscription and usage-based pricing mean costs grow quietly rather than arriving as a single visible purchase. Teams can often buy tools on a company card without going through procurement at all.

And the information you need – contracts, renewal dates, actual usage – sits in different places, owned by different people. Nobody has the full picture, so nobody feels responsible for it.

“Nobody has the full picture, so nobody feels responsible for it.”

Where the waste usually hides

Unused seats. Licences assigned to leavers, role-changers or people who logged in once.

Over-tiering. Premium or enterprise editions bought for features almost nobody uses.

Overlapping tools. Several products doing the same job across different teams – project management, file sharing and survey tools are common examples.

Auto-renewals. Contracts that rolled over because the notice period passed unnoticed.

Orphaned products. Tools nobody will admit to owning, still billing every month.

A licence review in weeks, not months

You don’t need a large programme. A focused review can be done in a few weeks if you keep it practical.

1. Build the inventory. Pull together every software contract and subscription: what it is, who owns it, what it costs, how many licences, which tier, and when it renews. Check finance and card spend as well as procurement records – that’s where the unknowns live.

2. Get the usage data. Most modern products can tell you who is actually logging in and which features they use. Compare that with what you’re paying for.

3. Find the owner for each. Every product should have a named business owner who can say whether it’s still needed. Products nobody will claim are your first candidates for retirement.

4. Sort into 4 groups. For each product, decide whether to keep it as is, right-size it to actual use, consolidate it with an overlapping tool, or retire it.

5. Build a renewal calendar. List every renewal in the next 18 months with its notice period, so decisions happen before contracts roll over rather than after.

6. Check your compliance exposure. The same review that finds over-licensing can find under-licensing – use that exceeds what you’re entitled to. Far better to find that yourself than in a vendor audit.

What you’ll learn beyond the savings

The most valuable output is often not the immediate saving. It’s what the review reveals about how decisions are made: who can buy software, how new tools are approved, whether anyone checks value after purchase, and how much of your technology estate has no clear owner.

Fix those, and you won’t need to do the same audit again in 2 years. A light-touch process – an owner for every product, an annual usage check and a renewal calendar someone actually watches – keeps the estate clean.

Start with the next renewal

If a full review feels too big, start with whatever renews next. Ask 3 questions before signing: who uses it, how much, and what would happen if we reduced or stopped it? Then do the same for the one after that.

Who should own software licence management?

Licence audits fail to stick when nobody owns the result. Ownership works best in 2 layers.

Each product has a business owner. The person who decides whether it’s still needed, how many licences are justified and whether it should renew. They don’t need to be technical; they need to understand the work it supports.

The estate has a single steward. Someone – often in IT, procurement or finance – who maintains the inventory and renewal calendar, prompts owners before notice periods and reports on spend and usage. In smaller organisations this can be part of an existing role; in larger ones it’s usually a software asset management function.

Licences in the age of AI

AI is adding a new layer to software spend. Many products now offer AI features as a per-seat add-on or a premium tier, and some AI services charge by usage rather than by user. Both can grow quickly and quietly.

Treat them the same way as any other licence: a named owner, a clear reason for each seat, a check on actual usage after the first few months, and a decision before renewal. AI add-ons bought for everyone “to encourage adoption” are among the easiest places for unused spend to accumulate.

Common questions

What is a software licence audit?

A review of every software product an organisation pays for – contracts, licences, tiers, costs, renewals and actual usage – to identify waste, overlaps and compliance risk.

How often should you audit software licences?

A full review every year or 2, with lighter checks before each significant renewal. Organisations with fast-growing SaaS estates may need more frequent usage reviews.

What’s the difference between over-licensing and under-licensing?

Over-licensing means paying for more licences or higher tiers than you use. Under-licensing means using more than you’re entitled to, which creates compliance and financial risk if a vendor audits you.

How do you reduce software costs quickly?

Remove licences from leavers and inactive users, downgrade over-tiered licences, retire orphaned tools, and review every contract before its notice period rather than after renewal.

What this looks like in practice

For a global packaging leader, a review of IT strategy, application portfolio and operating model identified application rationalisation and data-centre consolidation as major sources of savings, which the client then asked us to help implement. Read the case study →