How to Manage SaaS Subscription Spend and Reduce Waste

SaaS is easy to buy, so waste builds up gradually through unused licences, duplicate tools, forgotten trials, and unreviewed auto-renewals. Each looks minor, but together they add up across an organisation. Spendesk research found that 72% of companies using AI tools pay for two or more competing products, and 64% of companies buying design software do the same. Spendesk estimates that tool de-duplication could represent a €3 billion annual opportunity across European businesses with 50 to 250 employees. Overlap is a common pattern, not an occasional slip.

Managing subscription spend takes a repeatable process, not just price scrutiny. This guide is for finance teams, and it covers building an inventory, assigning owners, spotting duplicates, checking usage before renewal, controlling new requests and auto-renewals, offboarding, and reconciling invoices and cards. It also includes a quarterly review checklist to keep the work on track. The payoff is that finance can stop paying for software nobody uses without stopping teams from experimenting.

Key takeaways

• SaaS waste usually builds up gradually through unused licences, duplicate tools, forgotten trials, and unreviewed renewals.

• A complete inventory across invoices, cards, and expense claims is the foundation for every other control.

• Every material subscription needs a named owner in the business, with finance retaining oversight.

• Overlapping tools aren’t automatically waste, but every duplication should be deliberate and tracked.

• Treat each renewal as a decision by reviewing usage early enough to renew, resize, renegotiate, consolidate, or cancel.

Why SaaS subscriptions become difficult to control

Most businesses don’t intentionally build an inefficient software stack. It grows gradually. A department buys a tool independently, and another team that doesn’t know it exists buys something similar. Employees change roles, projects end, and licences remain active.

The problem gets worse when payments are fragmented across invoices and cards, and Employee expenses add another source. Finance can see money leaving the business without necessarily having the context to understand:

• what the tool does;

• who requested it;

• who currently uses it;

• whether another team has an equivalent product;

• or when the contract renews.

The result is recurring spend without recurring scrutiny.

The most common sources of subscription waste

SaaS waste generally comes from a handful of repeatable problems.

Unused licences

The company still pays for seats assigned to employees who no longer use the product.

Duplicate tools

Different departments buy products that solve substantially the same problem.

Forgotten subscriptions

A team lets a trial or small card payment roll into recurring spend that stays below finance’s radar.

Automatic renewals

A contract renews before anyone has reviewed usage and pricing or considered alternatives.

Oversized plans

The business pays for an enterprise or premium tier despite using only a fraction of its features.

Poor offboarding

An employee leaves but their software licences aren’t removed or reassigned.

Uncontrolled purchases

Teams buy software before finance and IT can check security and cost or procurement can check for existing alternatives.

A spreadsheet is a sound place to start, but it doesn’t solve these problems on its own, because they need clear ownership around the data.

1. Build a complete SaaS subscription inventory

Start by answering a deceptively simple question, “What software are we currently paying for?”, by looking across these sources:

• supplier invoices;

• virtual and physical cards;

• direct debits;

• employee reimbursements;

• procurement records;

• expense data;

• and department budgets.

Record at minimum:

The inventory becomes the foundation for everything else.

2. Assign ownership for every tool and licence

A subscription without an owner is hard to challenge, so every material SaaS product should have somebody who can explain:

• why the company needs it;

• who uses it;

• what result it delivers;

• whether the current licence count is appropriate;

• and whether it should be renewed.

Somebody in the business takes responsibility for the spend, while finance retains oversight, and that’s an important distinction. Spendesk CFO Pauline Bellee Babel makes the point that deliberate duplication can be perfectly reasonable if finance knows about it and tracks usage. Each tool must also have a clear purpose. The target is zero unexplained duplication.

3. Identify duplicate and overlapping software

Next, group your subscriptions by function, as in these examples:

Communication

• Slack

• Microsoft Teams

Project management

• Asana and Monday

• Jira

Design

• Figma and Adobe

• Canva

AI

• ChatGPT

• Claude

• Gemini

• Dust

• other specialist AI products

Then ask whether each overlap is intentional. Software duplication is particularly high in fast-growing categories such as AI and design. Multiple products aren’t automatically waste, but multiple products nobody has deliberately chosen to maintain probably are.

4. Measure usage before renewal

Don’t start reviewing a SaaS contract the week it renews, because your negotiating position may already be weak by then. Start early enough to collect evidence, beginning with these questions:

• How many licences did we buy?

• How many have been activated?

• How many people used the product in the last 30 or 90 days?

• Which features are used?

• Has usage increased or decreased?

• Is another tool doing the same job?

• What would happen operationally if we cancelled it?

That lets the business choose between:

Renew: The tool provides clear value.

Resize: Keep it, but reduce licences or the plan.

Renegotiate: Usage is strong but pricing looks excessive.

Consolidate: Another existing product can cover the requirement.

Cancel: The product no longer justifies its cost.

5. Control new subscription requests

The cheapest unnecessary subscription is the one you never start, so a clear approval process should capture new software before payment happens. A request might include:

• software name;

• business purpose;

• department;

• expected users;

• monthly or annual cost;

• existing alternatives;

• required contract term;

• and budget owner.

For larger purchases, finance or procurement can then check whether the company already has an equivalent product. The objective is a proportionate process that introduces the right questions before recurring spend begins.

6. Prevent unwanted auto-renewals

Renewal dates shouldn’t live only inside a vendor’s contract or somebody’s inbox, so track them centrally and, for important subscriptions, create reminders far enough in advance to:

1. review usage;

2. ask the owner whether the tool is still required;

3. investigate alternatives;

4. benchmark pricing;

5. renegotiate if necessary;

6. obtain approval;

7. renew or cancel deliberately.

The larger the contract, the earlier the review should begin. A €100 monthly subscription might need only a lightweight process, but a €100,000 annual commitment shouldn’t get the same treatment.

7. Manage SaaS subscriptions when employees leave

SaaS offboarding should be part of the standard employee exit process, so when somebody leaves, work through these steps:

• identify software assigned to them;

• remove or transfer licences;

• reassign ownership;

• revoke access;

• update billing counts;

• cancel individual subscriptions;

• and check whether the departing employee personally owned any company-paid accounts.

This is particularly important for decentralised card subscriptions, where the payment often sits with an individual employee’s card. If the payment disappears with the card but the business still needs the service, that creates disruption. If the payment continues after the employee leaves, it creates waste. Finance and IT therefore need a shared process with HR.

8. Reconcile SaaS invoices and payment cards

Software can be paid through several different channels, which makes categorisation important because the same vendor might appear:

• on an invoice;

• as a card merchant;

• under a regional legal entity;

• or using a slightly different billing descriptor.

Spendesk’s own research had to normalise these records to create a consistent vendor view across invoice and card payments, and finance teams should do the same conceptually. If the same product appears as three different suppliers in your reporting, your SaaS inventory will underestimate the true relationship.

A quarterly SaaS subscription review checklist

Once a quarter, review your software portfolio by asking these questions about every significant subscription:

• ☐ Is there a named owner?

• ☐ Is the department still using it?

• ☐ How many licences are active?

• ☐ Are we paying for unused seats?

• ☐ Do we have another tool with overlapping functionality?

• ☐ Has the cost changed?

• ☐ Is usage increasing or decreasing?

• ☐ Does the tool still support a current business need?

• ☐ When does it renew?

• ☐ Could the contract be resized or renegotiated?

• ☐ Is the subscription within the appropriate budget?

• ☐ Has finance approved its continuation?

Then prioritise the biggest opportunities, because a finance team shouldn’t spend hours cancelling a €20 subscription while ignoring a €50,000 contract with poor utilisation.

Better SaaS control makes software spending deliberate

With the right software, a company can become more productive. It can then move faster and compete more effectively. The objective is to support those gains through deliberate spending. In Spendesk’s European Spend Report 2026, businesses often pay very different amounts for comparable software, and duplication is widespread. As businesses adopt new categories such as AI, finance teams face additional complexity.

When finance teams manage subscriptions well, they gain visibility without preventing teams from experimenting. Every tool should have a purpose and every major subscription an owner. Above all, finance teams should treat each renewal as a decision rather than an accident.

To put stronger guardrails around purchases, explore Spend controls and approval workflows.

Or book a Spendesk demo to see how Spendesk helps finance teams make company spending visible and controllable.

Frequently asked questions about SaaS subscription spend

How can you stop free trials turning into paid subscriptions?

Capture each trial the day it starts, with a named owner and the end date recorded. That gives someone the chance to decide before the first charge lands. The choice to keep or cancel should sit with the owner, so a subscription never continues by default.

Is a spreadsheet enough to manage SaaS subscriptions?

It can be, particularly at an early stage, and a well-kept spreadsheet has often served finance teams well. It gets harder as payments spread across invoices, cards, and expense claims, and as owners change roles or leave. The spreadsheet only works if someone keeps it current and acts on renewal dates.

What should finance do about software employees pay for personally and expense?

Add any recurring software in expense claims to the inventory and give it an owner. Where the business still needs the tool, the subscription can usually move to a company-paid method, depending on the vendor’s account terms. That way it doesn’t disappear from view or continue unnoticed when the employee who paid for it leaves.

Should you choose monthly or annual billing for SaaS?

It depends on how confident the team is about usage. Monthly billing keeps flexibility while adoption is uncertain, whereas annual commitments may bring better terms, depending on the vendor. Annual plans make renewal review and licence sizing more important, so check each contract’s terms before committing.