Ask a finance leader how much enterprises overpay on the SaaS stack and you usually get a shrug, then a guess. The guess is almost always low. The reason is structural. Software spend is spread across many vendors, many owners, and many renewal dates, so no one sees the whole picture at once. Each contract looks defensible on its own. The waste only becomes visible when you add the stack up and compare what is paid against what is used.
In our buyer side reviews the recoverable share of digital workplace software spend is consistently a double digit percentage of the total, before a single renewal is renegotiated. That number comes from three quiet sources working together: seats nobody uses, plans richer than the work requires, and tools that duplicate each other. None of them is dramatic. Together they are expensive.
Why the SaaS stack overspend stays hidden
The collaboration and productivity stack grew tool by tool, often during a few years when adding software was easy and questioning it was not. A team needed a meeting tool, so one was bought. Another team preferred a different one, so that was bought too. Storage, signing, notes, project tracking, and chat each arrived the same way. The result is a portfolio nobody designed and nobody owns end to end.
That fragmentation is exactly why the overspend persists. A vendor account manager negotiates one renewal and moves on. A procurement lead sees the contracts but not the usage. An IT admin sees the usage but not the price. The finance team sees the total but not the detail. The waste lives in the gaps between those views. Mapping it is the first move, which is why we start with mapping your full digital workplace spend before sizing anything.
The five places the money leaks
SaaS overspend is not one problem. It is five, and they compound. Understanding each separately is what keeps the savings estimate credible rather than wishful.
Inactive and unused seats
This is the largest and cleanest category. Organizations buy seats in advance, headcount shifts, people leave, and the licenses stay assigned. A seat assigned to someone who never signs in is pure waste. Counting paid seats against genuinely active users over a ninety day window usually exposes a surprising gap. The full method sits in quantifying SaaS waste across the stack.
The wrong plan tier
Premium tiers are sold as the safe default. Most users never touch the premium features. Microsoft 365 is the textbook case, where the gap between a mid tier and a top tier plan is paid across thousands of users for capabilities only a fraction need. That tier mismatch is one of the biggest recoverable numbers on any large stack.
Duplicate and overlapping tools
Running two meeting platforms, two storage products, or two signing tools at once is common and costly. The overlap is rarely deliberate. It accumulates as teams pick their own favorites. The waste is the cost of the redundant tool, less any genuine residual need, and removing it is the heart of SaaS tool rationalization and consolidation.
Unused add ons and modules
Vendors bundle add ons into deals, and those add ons quietly renew whether or not anyone adopted them. Phone modules, advanced security packs, and analytics tiers are common examples. They look small line by line and add up across the portfolio.
Auto renewals nobody reviewed
An auto renewal that fires without a review is a decision made by inertia. It locks in last year's seat count, last year's tier, and often a price increase, with no chance to right size first. A disciplined SaaS renewal calendar is the simplest guard against this single source of waste.
How much enterprises overpay on the SaaS stack in practice
There is no universal figure, and any advisor who quotes a fixed percentage without seeing your data is guessing. What is reliable is the pattern. Inactive seats and tier mismatch usually account for the largest share, duplicate tools the next, and add ons the long tail. When these are measured rather than estimated, the recoverable total on a mid market digital workplace stack is routinely material enough to fund other priorities.
The right way to present the number is as a dated range anchored to current pricing, not a single figure. SaaS pricing and plans change often, so an undated precise number ages badly and undermines the business case the moment a vendor adjusts a price list. A dated range survives the next renewal cycle and holds up in a budget review.
Why the bundled view beats the vendor by vendor view
The reason this overspend is worth a dedicated engagement is that it is invisible to the people closest to each contract. A single vendor negotiation can trim a price. It cannot see that you are paying for a meeting tool you already own inside another suite, or that a storage product duplicates one bundled with your productivity license. Only a stack wide review catches the cross vendor duplication and the tier mismatch that sit between products. That is the difference between shaving a contract and redesigning the spend.
This is also why the order of operations matters. Right sizing and rationalization come first, because there is no point negotiating a better price on seats you should not be buying at all. Renewal negotiation comes second, on a stack already trimmed to what you use. Governance comes third, to stop the waste rebuilding. The choice between a single cleanup and a continuous program is covered in one time vs ongoing SaaS optimization.
What to do with the number once you have it
A credible overspend figure is leverage. It turns a budget conversation from opinion into evidence and gives procurement a defensible target to negotiate toward. It also reorders priorities: the largest, cleanest recoveries get tackled first, the structural ones get sequenced behind them. The end state is a single table where every tool shows its annual cost, its measured waste, and a recoverable range, so leadership can see at a glance where the money is going and where it should not.