© 2026 Procr
Published: April 2026 | Category: SaaS Licence Management | Reading time: ~7 min
Every vendor on your invoice list made sense when someone decided to buy it. That's the frustrating part about SaaS licence wastage, it doesn't happen because your team made bad decisions. It happens because buying software is easy and tracking what happens to it afterwards is hard.
The numbers are consistent across every study that's looked at this. Research from Vertice found that 21% of SaaS applications in the average portfolio are completely unused, not just underused, but idle. A further 45% are underutilised, with organisations using less than half the licences they're paying for. Separate analysis from Ramp puts the unused licence rate at 50% across all software spend, costing companies an estimated $45 million per month in aggregate wasted spend.
For a mid-market company managing $3M-$5M in annual vendor spend, even a conservative waste rate of 20-25% represents $600,000-$1.25M in budget that isn't delivering value. That's the number worth understanding before your next renewal cycle.
This post breaks down where SaaS licence waste comes from, how to find it in your portfolio, and what to do about it before it compounds.
SaaS waste isn't primarily caused by poor decision-making. It's caused by the way SaaS is purchased and the way most organisations track it.
Buying is frictionless. Reviewing is not. A department head can spin up a new SaaS tool on a credit card in ten minutes. That same tool will appear on a credit card statement, be paid month after month, and auto-renew annually, with nobody asking whether it's still being used. The ease of purchase that makes SaaS attractive also makes it easy to accumulate tools that nobody owns.
Seat counts are negotiated for growth that doesn't always materialise. Most SaaS negotiations are optimistic. You're buying for where you expect to be in twelve months, not where you are today. A company that expects to grow from 80 to 120 employees buys 120 seats. If headcount holds at 90, 30 seats sit unused and renew automatically. According to analysis from Cafeto Software, the average organisation has 30% of its SaaS licences going unused, largely because seat counts were set at projected headcount and never revised downward.
Offboarding breaks down. When an employee leaves, their SaaS licences should be reclaimed. In practice, this requires someone to know which tools the employee was using, have access to each admin console, and go through a deprovisioning process for every application. At a company running 50-100 SaaS tools, this process rarely happens completely. Orphaned licences, assigned to former employees or inactive accounts, accumulate quietly and renew with the contract.
Duplicate tools proliferate without central visibility. When purchasing is decentralised, different departments solving similar problems independently, you end up paying for multiple tools with overlapping functionality. Research from License Logic found that the average company carries 6.9 duplicate SaaS subscriptions. Common overlap categories include storage (Google Drive, OneDrive, Box), project management (Asana, Monday, Planner), and communication (Slack, Teams). Each represents a category where you're paying for two tools and getting the adoption benefits of neither.
Minimum seat requirements create instant waste. Many enterprise SaaS vendors require minimum seat commitments on their higher tiers, often 25, 50, or 100 seats. A team that needs 15 licences for a specific tool but is forced into a 50-seat minimum has 35 unused seats from day one. The vendor gets their revenue. Your audit will eventually surface the waste.
Understanding where waste lives in your portfolio helps you prioritise where to look first.
1. Shelfware: paid for, never used
Software that was purchased and never meaningfully adopted. This happens most often when procurement outpaces implementation, the tool was bought in anticipation of a use case that never materialised, or the rollout stalled after the first few weeks and nobody went back to fix it. Shelfware is the most visible form of waste once you pull usage data, and usually the easiest to act on.
2. Orphaned licences: assigned, no longer active
Licences associated with employees who have left the company, been transferred to a different team, or simply stopped using the tool. These licences are being billed, appear in the seat count at renewal, and produce no value. The fix requires a cross-reference between your employee directory and each tool's active user list, tedious, but high-return.
3. Over-provisioned seats: more than needed
Contracts where the seat count exceeds actual active usage, either because of optimistic headcount projections or because usage has declined since the last renewal. These seats are technically assigned to active employees; they're just not being used. Identifying them requires usage data at the individual level, not just aggregate login counts.
4. Duplicate subscriptions: paying twice for the same job
Multiple tools performing the same function across different departments. These are harder to surface than orphaned or unused licences because each tool may have active users, they're just duplicating functionality that already exists elsewhere in the stack. Rationalising duplicates requires a conversation about standardisation, not just a data export.
The audit process doesn't need to be elaborate. It needs to be systematic. Here's a practical approach that works for a mid-market team without a dedicated IT asset management function.
Step 1: Build a complete application inventory.
Before you can assess utilisation, you need to know what you're running. Pull from three sources: your contract repository (which tools you're paying for), your SSO or identity provider (which tools are integrated with your directory), and your expense management system or credit card records (which tools are being paid for outside of formal procurement). The gap between these three lists is where shadow IT and forgotten subscriptions live.
Step 2: Pull active user data for each application.
For each tool in your inventory, find out how many licences are provisioned and how many users have logged in within the last 30 days. Most SaaS platforms expose this in their admin console. SSO providers like Okta and Azure AD often aggregate this data across connected applications. Where you can't pull this automatically, request it from the vendor, they are usually obligated to provide usage data under your contract terms.
Step 3: Calculate cost per active user.
This is the metric that makes waste visible. Divide the annual contract cost by the number of active users (not provisioned seats). A $60,000 contract with 100 provisioned seats looks reasonable at $600 per user. If only 40 users are active, the real cost is $1,500 per active user, 2.5x the apparent rate. This metric, applied across your portfolio, immediately surfaces which tools are expensive relative to their actual adoption.
Step 4: Categorise each application.
With usage data in hand, group your applications into four buckets: retain and optimise (high utilisation, critical to operations), reduce and renegotiate (useful but underutilised, right-size the seat count), consolidate or cancel (duplicating functionality that exists elsewhere), and cancel immediately (not in active use, no planned adoption). This categorisation drives the action plan.
Step 5: Act before renewal, not after.
The optimal moment to act on waste findings is during the renewal window, ideally 90-120 days before the contract term ends. At this point you have time to negotiate a seat reduction, present usage data to support a renegotiation, evaluate alternatives if the tool is underperforming, or issue a cancellation notice before the auto-renewal window closes. Acting after renewal means you've committed to another year of the same spend.
Licence utilisation data isn't just useful internally. It changes the dynamic of vendor renewal conversations.
A vendor who knows their product has 40% active usage out of 100 provisioned seats is in a weaker position to defend a price increase than one going into a renewal conversation blind. Your usage data is leverage, it demonstrates that the current contract is overprovisioned, that value delivery isn't matching cost, and that you have a legitimate basis to renegotiate the seat count downward.
Most vendors will negotiate a right-size rather than lose the customer entirely. The key is having the data ready before the renewal conversation starts, not scrambling for it in the final 30 days.
Gartner's analysis suggests that organisations can reduce software costs by up to 30% through three consistent practices: recycling licences when employees leave, right-sizing seat counts at renewal, and actively managing their SaaS portfolio. None of these require sophisticated tooling. They require a process and the discipline to run it before each renewal cycle.
The most expensive dimension of SaaS licence waste isn't the waste in year one. It's what happens when that waste renews.
Most enterprise SaaS contracts include annual price escalation clauses, typically 3-7% per year. If you're carrying 30% unused seats and your contract renews with a 5% price escalation, you're now paying 5% more for the same 30% of seats that nobody is using. Over three or four renewal cycles, the compounding effect on wasted spend is significant.
This is why the timing of a licence audit matters. An audit completed twelve months after the last renewal, with no action taken until the next one, has let one full escalation cycle run on the wasted spend. An audit completed 90 days before renewal, with findings used to renegotiate seat count and price, eliminates both the waste and the escalation that would have compounded on top of it.
Licence waste is a finance problem, an IT problem, and a procurement problem simultaneously, which is exactly why it falls through the cracks at companies that don't have formal ownership of all three.
The most effective approach is to make waste visible as a metric rather than as an audit finding. A monthly or quarterly report that shows cost per active user by application, active licence rate by tool, and estimated recoverable savings by category, sent to the finance lead, IT lead, and relevant department heads, creates the accountability that periodic audits don't.
When the VP of Sales sees that their team's primary sales tool has a 58% active usage rate and their department is paying for 42 seats that nobody logs into, the conversation about right-sizing at the next renewal happens without prompting.
Making waste visible is half the work. The other half is having the renewal process in place to act on it.
Procr
See what Procr does with your real vendor portfolio.