SaaS Spend Management: Find and Cut Wasted Software Spend

SaaS Spend Management: Find and Cut Wasted Software Spend

By DealKeep Team · Published

SaaS spend management is the practice of knowing what software your organisation pays for, what it costs, who uses it, and when each contract renews — and then acting on that knowledge before the renewal date rather than after it.

That definition sounds obvious. The reason it is a discipline at all is that nobody sets out to waste software spend. It leaks through ordinary, reasonable decisions made by people who did not have the full picture.

Two people review a printed spreadsheet with red circles marking specific data points, one pointing at the paper while the other holds a red marker.

Photo by RDNE Stock project on Pexels

How software spend actually leaks

Five patterns account for most of it. None require anyone to be careless.

1. Nobody owns the list. Software gets bought by whoever needs it — a designer expenses one tool, marketing signs up for another, an engineer starts a trial that quietly converts. Each purchase is defensible. No single person can name them all.

2. Renewals are silent. Annual contracts renew automatically. The charge lands eleven months after anyone thought about it, often to a card belonging to someone who has since changed roles. The moment to renegotiate — or cancel — passes without anyone noticing it happened.

3. Seats outlive people. Someone leaves. Their accounts are deprovisioned in the tools IT knows about. The tools IT does not know about keep billing for a seat nobody occupies.

4. Overlap accumulates. Two teams solve the same problem with two products. Both work. Neither team knows the other exists. You pay twice for one capability, and the duplication is invisible unless someone lists everything side by side.

5. Tier drift. A plan gets upgraded for a specific project. The project ends. The plan does not come back down.

Notice what these have in common: every one is a visibility failure before it is a spending failure. You cannot negotiate a renewal you did not know was coming, and you cannot cancel a tool you cannot name.

The five checks that find most of it

Before buying any platform, this is the work. It is unglamorous and it is where the money is.

Check 1: Build one list

Everything, in one place. Tool name, what it does, who owns it internally, what it costs, how it is billed, and when it renews.

Pull from three sources, because no single one is complete:

  • Card and bank statements — catches anything that recurs
  • Expense reports — catches what individuals bought and claimed
  • Your identity provider — if people sign in with Google or Microsoft, the OAuth grant list shows what they connected, including tools finance has never seen

The third source is the one most teams skip, and it is usually where the surprises live.

Check 2: Mark the renewal dates

For each item, write down the next renewal and whether it auto-renews. Then work backwards: most contracts require notice before renewal to cancel or renegotiate. The date that matters is not the renewal — it is the last day you can act on it.

This single column changes behaviour more than any other. A renewal you see coming ninety days out is a negotiation. A renewal you discover on the statement is a fact.

Check 3: Find the duplicates

Group the list by job, not by vendor. "Sends email", "stores files", "tracks tasks". Any group with more than one entry deserves a conversation.

Some duplication is legitimate — teams genuinely have different needs, and forcing consolidation can cost more in disruption than it saves in licence fees. But you cannot make that call until you can see the overlap.

Check 4: Check usage against seats

For each paid seat, ask whether a real person used it in the last quarter. You will not have clean data for every tool. Start with the expensive ones — per-seat costs are where unused licences hurt most.

Check 5: Question the tier

For anything on a plan above entry level, ask why. Often the answer is a limit hit once, a feature needed for a launch, or a sales conversation that upgraded the account. Sometimes the reason still holds. Sometimes it ended two years ago.

Three people work on laptops at a desk covered with colorful pie charts, documents, pens and coffee cups, collaborating on data analysis.

Photo by olia danilevich on Pexels

Tooling: what to use, and when

There is a real ladder here, and most teams should start lower on it than vendors suggest.

A spreadsheet

Good for: under roughly twenty tools, one person maintaining it.

It costs nothing, holds every field you need, and is honest about its limits. Its real weakness is not capability but decay — a spreadsheet does not remind anyone of anything, so it goes stale within a couple of quarters unless someone owns it as a job.

A dedicated tracker

Good for: small teams and individuals who want the renewal and refund dates to chase them instead of the other way round.

This is the tier we build for. DealKeep tracks the tools you own, their costs, their renewal dates, and their refund windows, and it alerts before those dates rather than after — including for software bought once rather than subscribed to, which transaction-based tools cannot see.

Being straight about the boundary: it does not connect to your bank or your identity provider, so it will not discover software you have not told it about. Discovery is exactly what the enterprise platforms below do well. If your core problem is "we do not know what we are running", you want discovery, not a tracker. Our pricing page has the details on what we do cover.

A SaaS management platform

Good for: organisations past roughly fifty or a hundred employees with procurement and compliance requirements.

Platforms in this category — Zylo, Torii, Zluri and others — connect to your identity provider, your finance system, and often the applications themselves. They discover shadow IT automatically, track utilisation from real login data, run access reviews, and support renewal negotiation with benchmark pricing.

They are genuinely better than anything lighter at that scale, and it is worth saying so clearly. Automatic discovery across hundreds of applications is not something a manual tracker can approximate. The trade-off is cost and implementation effort: these are priced for organisations where a percentage point of software spend is a large number, and they typically involve a real onboarding project rather than an afternoon.

The mistake is buying at this tier to solve a problem a spreadsheet would have solved, and then not doing the work anyway. The platform makes the list; someone still has to act on it.

Building the habit

Spend management fails when it is a project. It works when it is a recurring, small, scheduled task.

A workable rhythm:

  • Monthly: review new software purchases. Add them to the list on the way in, not in a cleanup six months later.
  • Quarterly: run checks 3, 4 and 5 — duplicates, unused seats, tier drift.
  • Ninety days before each renewal: decide deliberately. Renew, renegotiate, downgrade, or cancel. The default is renew, and defaults are expensive.

The compounding effect comes from the last one. Every renewal you meet prepared is a decision. Every renewal that surprises you is a charge.

What to do first

If you do nothing else from this article, do check 1 and check 2. Build the list, add the renewal dates. Most of the savings people attribute to spend management tooling comes from that pair — the tool mainly stops the list from going stale.

Related reading

SaaS spend management at a glance