SaaS spend optimization does not reward the team that closes the most tickets. It rewards the team that finds the one contract, renewal, or license opportunity that moves EBITDA, and acts before the renewal window closes.
Six weeks into most cost programs, the tracker looks great. Twenty-odd tickets are closed and another dozen are moving. Idle seats have been cancelled, two survey tools that did the same job are now one, and somebody found a design subscription nobody remembered buying. The steering committee sees a slide full of green. Meanwhile, the contract that could have moved EBITDA by itself hasn’t been touched. On the board it’s just one more ticket, no bigger than any of the others, so it never looks urgent enough to pull forward. That’s the quiet way SaaS spend optimization goes wrong: the effort gets spread across the queue, and the savings stay stuck in one place.
The instinct to chase the queue
Most SaaS spend management programs are set up like a service desk. Every opportunity becomes a ticket, every ticket gets an owner, and progress gets reported as a count. We understand why. A count is easy to track and easy to put in front of a committee every Monday.
Small wins close quickly, too. Cancelling 14 unused licenses on a project management tool is an afternoon’s work. There’s no negotiation, no sponsor to recruit and no call with the vendor’s account manager. Do twenty of those and the program feels like it’s flying.
But a ticket count only tells you how busy the team has been. It says nothing about how much money came back, and that’s the one thing IT cost optimization is supposed to deliver.
Nobody in a cost review asks why the team closed thirty tickets. They ask why the savings number is short of forecast. By then, the gap is usually sitting in a line item nobody got to.
The math behind vendor cost recovery: one opportunity, half the savings
Sort opportunities by value instead of volume and the pattern is hard to miss.
Take one company we work with, an Oracle customer. We identified 22 savings opportunities there, worth $1.48M in total. One of them, a license audit and right-sizing on a $1.9M Oracle contract, was worth $900K on its own. That’s 61 percent of the entire pipeline in a single line. The other 21 opportunities added up to about $575K between them, and nine were worth less than $10K each.
A second company, which we’ll call the cloud customer, had 39 opportunities worth $508K. The largest, at $276K, was 54 percent of the total, and it sat on a $2.76M cloud services bill.
These two aren’t outliers. At another company we work with, one contract-term negotiation carried 65 percent of the savings on a list of 14. At a fourth, there were only five opportunities, and one of them, moving billing to a new supplier, was worth 93 percent of the total.
When we looked across 20 companies we work with, each with a meaningful savings pipeline, the single largest opportunity made up at least a quarter of the total in 12 of them. In six, it was more than half. Five had flatter lists, where the top item was under 20 percent.
So concentration is common, but it isn’t a law. That’s exactly why it’s worth checking before the team decides where to spend its time.
Why the biggest opportunity usually looks boring
If one line is worth more than the rest of the list put together, why does it sit there for weeks? Mostly because it doesn’t look like waste. It looks like infrastructure.
These opportunities are rarely the forgotten tools and shadow IT that most people picture when they hear “SaaS waste.” They sit on the large, established contracts: the database platform, the ERP, the cloud bill. Both of the big examples above were attached to contracts worth well over a million dollars a year.
What they actually involved is telling. At the Oracle customer, the $900K came from checking licenses against real use and right-sizing the contract. Nothing new or exotic, just the kind of review that’s easy to push to next quarter. At the cloud customer, Saasrooms flagged the $2.76M cloud services bill, bought through a managed services partner, and found there was no contract on file for it at all. The single largest line of spend in the portfolio was also the one with the least paperwork behind it.
Neither would get anyone excited in a meeting. On the backlog, work like that gets a title such as “Review license tiers,” and it looks no more important than “Cancel unused webinar tool,” even though it’s far harder to close.
Several things keep it sliding down the list. The system is mission-critical, and nobody wants to be the person who broke the platform finance runs on. It usually has a senior owner, so changing it means a real conversation with a department head. It can’t be wrapped up in a sprint, because it needs usage evidence, a negotiation and the right renewal window. And the percentage often looks ordinary. The cloud opportunity was worth about 10 percent of its contract value, which is the kind of number that blends into a list.
That’s where instinct lets people down. At the Oracle customer, a Proofpoint renewal was also worth about 10 percent of its contract: $3K on a $30K spend. Same percentage as the cloud opportunity. The cloud one was worth 92 times as much.
The case for quick wins, and where it stops
There’s a fair argument for clearing the small tickets first. Early wins give the board something to see. They earn goodwill with budget owners, and they buy the patience a hard SaaS contract negotiation needs. A program that spends two months on one contract with nothing to show can lose its mandate before the big deal closes.
We agree with all of that, and it’s a good reason to run quick wins alongside the big one. It just isn’t a reason to let them set the pace.
Quick wins only buy time if the big opportunity is moving in the background. When they become the whole program, there’s nothing left for that time to pay for. And the renewal date on the large contract won’t wait for the queue to clear.
How to triage SaaS spend optimization for concentration, not count
The small stuff still matters. The $575K spread across the other 21 opportunities at the Oracle customer is real money. Some of it was handled well, too. On one BlackLine renewal, the team turned down a proposed 12 percent price increase and cut seats from 70 to 60 because usage didn’t support the higher count. That’s exactly the kind of work that should keep happening. It just shouldn’t eat up the best negotiator’s week or decide what gets worked first.
Here’s what a concentration-first approach to SaaS cost optimization looks like in practice.
- Sort by value first. Rank every opportunity by estimated savings before looking at who owns it or when it was logged. The order of work should follow the money.
- Check how concentrated the list is. Work out what share of total savings the top one and top three opportunities represent. If a single item carries 40 percent or more, give it its own workstream, a named owner and a deadline set by the vendor’s calendar rather than the sprint.
- Make sponsorship automatic. Agree upfront that anything above a set share of the pipeline, say 20 percent, gets an executive sponsor from day one. Nobody has to decide whether to escalate, so the politics never get a chance to stall it.
- Size on the contract, not the percentage. Annual contract value times a realistic reduction is a better guide than percentage savings. Saasrooms shows purchased, assigned and active licenses side by side for every contract, which turns a vague “review license tiers” into a defensible number and makes software license optimization something a CFO can sign off on.
- Work back from the notice period. The real deadline on a big contract is the notice window, not the renewal date, and good SaaS renewal management starts there. Saasrooms tracks renewal dates and auto-renewal terms so that window shows up months before the invoice does.
- Give the long tail its own lane. A smaller team or an automated workflow can handle license cleanups while senior people focus on the one or two contracts that decide the result.
- Report money, not tickets. Steering updates should show savings recovered against savings identified, with the biggest opportunities named. A board can’t do anything with a ticket count.
None of this is complicated. Sticking to it is the hard part, because every week there will be ten easy tickets and one difficult contract, and the easy tickets will always feel like progress.
The number that gets missed
At the Oracle customer, one opportunity was worth more than the other 21 combined. It wasn’t hidden. It sat on the same board as everything else, on the same size card, with the same status label as a renewal worth a few thousand dollars.
That’s how the biggest number in a SaaS spend optimization program slips through. Nobody ignores it on purpose. It just gets sorted by ticket count, or by the date it was logged, or by how fast it can be closed, and lands somewhere below the line of what the team gets to this quarter.
Vendor cost recovery doesn’t reward the team that closes the most tickets. It rewards the team that spots the one opportunity worth more than the rest combined, and gets to it before the renewal notice does.
