Beermat Software All articles
Startup Strategy

The Ghost in the Spreadsheet: Hunting Britain's Phantom Software Seats

Beermat Software
The Ghost in the Spreadsheet: Hunting Britain's Phantom Software Seats

Every British organisation has a spreadsheet called something like Software_Subscriptions_FINAL_v3_USE_THIS_ONE.xlsx. It is maintained by a person who left in March. It lists 47 tools. Finance is paying for 63. Nobody knows where the other 16 came from, but three of them have a renewal date next Tuesday and one is called AcmeSync Pro with a monthly charge that looks like a typo.

Welcome to licence sprawl: the quiet epidemic of seats nobody sits in.

The renewal nobody owns

Software licences are the ideal expense for a busy organisation. They are small enough to escape scrutiny, regular enough to look normal, and boring enough that no one volunteers to own them. A departmental card payment here. A trial that converted because the cancellation page was designed by a sadist. A contractor who needed a design tool for six weeks in 2024 and whose account is still active because the offboarding checklist had a gap where 'SaaS' should have been.

By 2026, the average small British firm has a subscription estate that looks less like a strategy and more like a car boot sale. The problem is not the money, although the money is not nothing. The problem is that every phantom seat is a small act of institutional forgetfulness. It says: we do not know what we own.

How phantom seats breed

There are four common species.

The departed employee. Their account is still active because deactivating it required a ticket to IT, and IT was busy migrating the intranet. The licence renews annually. The person now works for a competitor and has not thought about you in months.

The abandoned trial. It started as a 14-day free trial. It ended as a monthly direct debit. The product is used by one person, twice a year, to open a file they could have opened in something else.

The departmental card payment. A team lead bought a tool because it solved a Tuesday problem. The tool is now part of the furniture. Finance sees the charge but not the tool. The team sees the tool but not the charge. Everyone is happy. Nobody is accountable.

The duplicate. Two teams bought the same category of software from different vendors because they did not know the other team existed. This is not a technology problem. It is a seating plan problem.

The annual seat audit ritual

You do not need a procurement transformation. You need an afternoon, a bank statement, and the willingness to send slightly awkward emails.

  1. Pull the money. Get twelve months of card and bank statements for every account that could plausibly buy software. Include the petty cash card. Include the founder's personal card if they have been 'just expensing it'.
  2. List every recurring charge. Ignore what it is for now. Just get the names and amounts.
  3. Match each charge to an owner. Not a department. A person. If no person claims it, it is already a finding.
  4. Ask the owner three questions. Who uses it? What happens if we cancel it? When did anyone last log in?
  5. Check the identity provider. Your single sign-on logs are a guest list. Compare it to the billing list. The difference is your phantom seats.
  6. Look for the zombies. Tools with no SSO, no admin console, and a password stored in a shared document called passwords.docx. These are the ones that will outlive us all.

The output is not a beautiful dashboard. It is a list with three columns: keep, cancel, investigate. That is enough.

Cancelling without summoning procurement

Here is where the fury arrives. Cancelling a software subscription should be a button. In practice, it is a quest. The cancellation page is hidden behind a chat widget. The chat widget asks you to speak to your account manager. The account manager offers a discount. The discount requires a new purchase order. The purchase order requires a procurement process that was designed for buying aircraft carriers.

A few rules help.

A small ceremony for a small problem

The fix is not a new tool. The fix is a ritual. Once a year, before the new financial year, someone with a clipboard and a mild sense of grievance sits down and asks: what are we paying for, and who is using it?

It will take a day. It will save money, but that is not really the point. The point is that a company should know its own front door, its own tools, and its own bills. Phantom seats are not a finance glitch. They are a small symptom of a team that has grown faster than its memory.

So open the spreadsheet. Find the ghost. Cancel the ghost. Then rename the spreadsheet. It is 2026. We can do better than FINAL_v3_USE_THIS_ONE.

All Articles

Related Articles

The Lock-In That Never Ended: Retiring Features Without a Riot

The Lock-In That Never Ended: Retiring Features Without a Riot

The Buffering Village: Designing for the Places the Fibre Forgot

The Buffering Village: Designing for the Places the Fibre Forgot

The Council Contract Gauntlet: A Survivor's Field Guide to Selling Software to Local Government

The Council Contract Gauntlet: A Survivor's Field Guide to Selling Software to Local Government