We Auto-Renewed $180K of Software Nobody Used

The audit started because a new CFO asked a simple question at her first leadership meeting: “Can someone give me a full list of our software spend, with renewal dates and who owns each contract?”

Nobody could. There was a partial spreadsheet maintained by the IT manager, a folder of PDFs in Google Drive, and a handful of entries in the accounting system - but no single source of truth. Pulling together a complete picture took three weeks and involved chasing down five different department heads.

When the list was finally assembled and cross-referenced against actual usage data from each vendor, the results were uncomfortable. Of 47 active vendor contracts, six had no active users whatsoever. All six had auto-renewed within the previous 12 months. None had been reviewed before renewal.

The six tools and their annualised costs broke down as follows:

• Project management platform - $38,400/year. Originally purchased for a client delivery team that was later absorbed into a different workflow. The team stopped using the tool but nobody cancelled the contract.
• Business intelligence suite - $42,000/year. Bought during a data transformation initiative that stalled. The initiative was quietly shelved. The BI licence was not.
• Design tool (team plan) - $18,600/year. The designer who requested it left the company. Her replacement used a different tool already covered under a separate licence.
• Video conferencing add-on - $24,000/year. A premium tier purchased during remote-first working. The company had since standardised on a different platform included in their Microsoft agreement.
• HR onboarding software - $31,200/year. The HR lead who implemented it moved on. Her successor had no visibility into the contract and assumed the tool was still in use somewhere in the business.
• Sales enablement platform - $29,200/year. The sales team had migrated to a new CRM that included equivalent functionality. The standalone tool was abandoned but not cancelled.

Each of these made sense when originally purchased. None of them were reviewed before they renewed. The common thread: ownership disappeared, usage data was never connected to the renewal process, and the auto-renewal clauses did exactly what they were designed to do.

This is not a story about careless procurement. Most of these purchases had solid justification at the time. The problem is structural, and it plays out the same way across almost every mid-market company.

No central register

When software purchases are spread across departments, approved through different budget holders, and tracked in different systems, nobody has a complete picture. The cost of managing contracts in spreadsheets is precisely this: gaps accumulate faster than anyone can close them.

Ownership disappears

The person who championed a tool, understood its value, and would have flagged a renewal decision - they leave. The contract stays. Nobody inherits accountability. The tool goes dark but the invoice keeps arriving. This is directly related to the broader question of who actually owns SaaS renewals in your organisation.

Usage data is never connected to contracts

Most companies could pull usage reports from their vendors if they asked. Most never do, at least not in time to act on the information before a renewal window closes. By the time usage data gets into a renewal conversation, the contract has already rolled over.

The vendor has no incentive to flag it

Vendors are not going to call you and say: “We noticed nobody is using your licences - do you want to cancel?” Auto-renewal is built into their revenue model. The obligation to review, the obligation to give notice, the obligation to act - all of it sits with the customer. The vendor's job is to process the renewal.

Once the audit was complete, the company contacted all six vendors. The outcomes varied significantly.

Two vendors agreed to early termination without penalty. Both were smaller companies in competitive markets where customer retention mattered more than enforcing a contract against a customer with zero usage. They also had renewal dates still several months away.

Two vendors waived remaining fees after the company provided documentation showing zero usage and a formal written request. In both cases, the company had enough relationship capital with their account managers to make the conversation productive.

Two vendors enforced the contract in full. Both pointed to the auto-renewal clause, both had already invoiced for the next term, and both declined any credit or early exit. The company had no legal basis to dispute the charges. The contracts were valid. The renewals were binding. They paid.

The split is fairly representative. Goodwill conversations sometimes work. But you cannot build a vendor management strategy on the hope that suppliers will voluntarily refund money they are contractually entitled to keep.

You do not need a three-month project to start closing this gap. Three actions this week will put you ahead of most organisations your size.

1. Pull every SaaS invoice from the last 12 months

Ask finance for a line-item export of all software-related spend. Cross-reference against what your IT team has on record. The gap between those two lists is where the risk lives. Any tool appearing on invoices but not in your IT register is an immediate priority to investigate.

2. Request usage reports from your top 10 vendors by spend

Every major SaaS vendor will provide usage data on request. Email your account manager or log into the admin console. Ask for monthly active users over the last 90 days. Any tool showing under 20% of licensed seats actively used is a candidate for renegotiation or cancellation at next renewal.

3. Set notice window alerts for anything renewing in the next six months

Find every contract renewing in the next six months and identify the notice period required to cancel or renegotiate. Set a calendar alert at the start of that window - not the end. If you're not sure how to approach the forecasting side of this, SaaS renewal forecasting for finance teams covers the process in detail.

None of this requires new software. A spreadsheet and two hours of time will get you further than doing nothing. The difference is that once you've done it once, you need a system to keep it current - because the problem restarts the moment you stop paying attention.

Shelfware is not a procurement failure. Every one of those six tools was purchased for a legitimate reason by someone who intended to use it. The original purchase decisions were probably fine.

Shelfware is a visibility failure. It happens when nobody is watching the gap between what you purchased, what you are using, and when the contract renews. That gap is invisible unless you build something to surface it - and it gets wider every time someone leaves the company, every time a team restructures, every time a project is deprioritised.

The $183,400 was not lost in one bad procurement decision. It was lost in six separate moments where the renewal happened without anyone asking whether the tool was still needed. That is not a question vendors will ask for you.

It is the one question you need to be asking - continuously, automatically, before every renewal.