Finding SaaS waste is easy. Recovering it is where value is created. The companies that win are not the ones with the longest list of savings opportunities, but the ones with the visibility, benchmarking, and execution discipline to turn those findings into measurable results.
Most SaaS spend management tools are good at finding problems. A duplicate tool here, an over-licensed seat count there, a contract that quietly auto-renewed. What they’re rarely good at is making sure any of it actually gets fixed. The finding gets logged, an email goes out, and it competes for attention with everything else on someone’s plate. Three months later, a similar-looking finding shows up again, not because the tool failed, but because knowing about waste and recovering it are two completely different jobs.
That gap, between what gets flagged and what gets fixed, is where most SaaS spend management programs quietly stall. Closing it takes more than better reporting. It takes contract data that’s actually reliable, benchmarking that runs continuously instead of once a year, and a way to act on findings without every single one requiring someone’s full attention.
Contract visibility is the part that has to come first
Every renewal decision, every benchmark, every negotiation starts from the same question: what does the contract actually say. In practice, that’s the part most teams can’t answer with confidence. Across live SaaSrooms workspaces, roughly 89 percent of tracked applications have no formal contract on file the day a workspace first connects. Not shadow tools nobody approved, live paid software with no document anyone can point to for the renewal date, the notice period, or the price agreed to last time it was negotiated.
This is why automated contract collection matters more than it sounds like it should. When contracts are ingested and key terms extracted automatically, without someone manually logging renewal dates into a spreadsheet, two things change at once. Renewal alerts start arriving early enough to actually act on, instead of a few days before an auto-renew clause locks the company in for another year. And every downstream step, benchmarking, negotiation, risk assessment, finally has accurate data to work from. Contract visibility isn’t a feature sitting next to the others. It’s the layer everything else depends on to work at all.
Continuous benchmarking catches what annual reviews miss
Once contract data is reliable, the next question is whether the price being paid still makes sense. Pricing that looked competitive at signing rarely stays that way, and most teams only revisit it once a year, if that, because checking properly takes time nobody has for every single tool in the stack.
Continuous benchmarking against real market pricing data removes that dependency on someone remembering to check. Across 18 workspaces currently live on the platform, close to 200 flagged savings opportunities represent a combined recoverable value approaching a million dollars, against roughly 8.6 million dollars of contract spend those opportunities touch, close to 11 percent of flagged spend sitting there as recoverable savings on average. In one estate alone, 18 separate opportunities added up to more than 260,000 dollars in identified savings, a scale that’s hard to catch through a manual quarterly review, and easy to miss entirely if benchmarking only happens once.
Finding the gap is still only half the job, and it’s worth saying plainly that not every flagged opportunity gets closed quickly. Of the opportunities logged so far, roughly a third have been carried through to completion, the rest sit somewhere between scoping and contracting, which is a realistic pace for renegotiating live vendor relationships rather than an instant fix. For the ones that do close, it takes an average of about 59 days from the point a saving is flagged to the point it’s actually recovered. That’s meaningfully faster than the typical rhythm of an annual review, but it’s not instantaneous, and treating it as instantaneous would be misleading. The value isn’t that every finding turns into savings overnight. It’s that the gap between what a company pays and what the market actually charges gets caught continuously, and worked continuously, rather than once a year if someone remembers.
Negotiation is where visibility either turns into savings or doesn’t
Finding an overpayment and recovering it are not the same milestone, and this is usually where SaaS spend management programs lose momentum. Someone has to build the case, gather comparable pricing, open the conversation with the vendor, and see it through, on top of everything else already on their plate.
Automating that step doesn’t remove the person from the decision. It removes them from doing the manual legwork. For routine renewals, the negotiation runs end to end: the case gets built from the benchmark and usage data, the exchange runs with the vendor, and a decision comes back rather than a task that still needs doing. For more complex contracts, it works the tactical positioning and runs multi-bid comparisons across competing suppliers, then presents the options. One part of this is worth being precise about, because it’s also the one part that never changes: every action that commits the company to anything still passes through a single human approval. The system builds the leverage. The person still signs. That distinction matters more as negotiation gets faster and more automated, not less, since speed is exactly what makes a shortcut tempting.
Shadow IT and ungoverned AI use follow the same pattern, just with higher stakes
The same logic that applies to overpayment applies to risk, just with more urgency behind it. An application nobody formally approved gets adopted by a team, it sits without a contract or a data processing agreement, and it stays invisible until an audit, a renewal, or a breach disclosure forces the question. Shadow IT detection built around continuous discovery, rather than a periodic audit, catches this while it’s still a manageable fix rather than after it’s become a compliance finding, cross-referencing what’s uncontracted against live breach intelligence and mapping the exposure against frameworks like GDPR, ISO 27001, Cyber Essentials and NIS2.
AI adoption is following an almost identical curve, just faster. Teams pick up AI tools through personal accounts well before anyone responsible for governance has visibility into where AI is actually running or what it’s doing to productivity. AI governance built the same way, tracking deployment by application and department rather than waiting for a survey or an incident, means that visibility turns into a managed rollout before the ungoverned version becomes the default one across the company.
What automation doesn’t remove
None of this replaces judgment, and it’s worth being direct about where a person still has to do the thinking. A benchmark can tell you a price is above market, but it can’t tell you that a vendor relationship matters for reasons that don’t show up in a spreadsheet, a longstanding integration, a support relationship that’s actually saved a team during an outage, a roadmap commitment the company is relying on. Those calls stay human, and they should. Complex, multi-stakeholder contracts still benefit from someone in the room who understands the politics of the relationship, not just its price. And a completion rate sitting around a third is a fair reflection of how renegotiation actually works: some of it moves fast, some of it sits in scoping longer than anyone would like, because vendors have their own timelines too. Automation narrows the gap between flagged and fixed. It doesn’t erase the fact that closing a deal still takes two parties agreeing to something.
Where SaaS license optimization goes next
Everything above still runs through one central view, one team acting on findings, one risk posture managed from the top. The next stage in SaaS license optimization pushes the same intelligence down to the people actually using the tools day to day, and it changes who’s responsible for catching waste in the first place.
Individual teams get visibility into their own applications, licenses, and spend directly, inside limits set centrally, instead of every request routing through IT or finance. Before anyone sources something new, they see what the company already runs for that exact job, since most new purchase requests turn out to be answered by a tool that already exists somewhere in the stack, and catching that at the point someone considers buying is worth more than catching it a year later at renewal. Idle licenses get surfaced to whoever’s holding them and returned to a shared pool instead of prompting another purchase order. And usage feedback from the people actually working in these tools every day feeds directly back into the next benchmark and the next negotiation, so a renewal decision reflects how well something performs, not just what it costs on paper.
The effect compounds in both directions. Teams get faster answers and more autonomy over their own tools. The organization gets consolidated demand, a tighter license pool, and stronger evidence walking into every negotiation that follows.
None of this changes what the original problem was. SaaS spend management was never short on findings. What it needed was a way to make sure the ones already found didn’t keep sitting there, quietly repeating themselves, one quarter at a time.
