how to reduce unused SaaS licenses is not another training plan. It is a count: seats you pay for versus screens people open when work is urgent. Vertice's Q2 2026 tracking puts about 65% of licenses unused or underused. Most of that growth is underuse, not fully abandoned shelfware. Finance still pays. Tuesday still happens in email.
This guide is for operators, IT, and founders who renewed a stack last year and cannot explain who uses it. You will get a cost audit you can paste into a budget thread, a five-step reclaim-or-rebuild loop, and the test we use on live products: if the helper is not in the job, people skip it.
Contents
- Key takeaways
- What unused SaaS licenses actually are
- A cost audit you can run this week
- Why training and "one more platform" fail
- Five steps: reclaim, then decide whether to build
- When custom software development is the cheaper path
- FAQ
- Conclusion
Key takeaways
- Start with last-login and seat count, not a vendor demo. Unused software at work is a usage problem first.
- Vertice's Q2 2026 numbers put about 65% of licenses unused or underused. Underused seats are growing faster than fully abandoned tools.
- Reclaim zombie seats (people who left) before you argue about product fit.
- If people still live in email after a clean audit, you do not have a license problem. You have a job-shape problem.
- Custom software development only pays off when it sits inside the screen people already click. A fifteenth login becomes more shelfware.
What unused SaaS licenses actually are
Unused SaaS licenses are paid seats with little or no real use: no last login, a login that never happens when a customer is waiting, or a tool the deck calls "rolled out" while the work still lives in a spreadsheet.
SaaS-management vendors (Iden, OptyStack, and similar 2026 guides) treat this as an IT hygiene job: inventory, inactivity thresholds, deprovision on offboarding. That work is real. It is also incomplete if the remaining seats exist and people still skip the product.
Software license waste has two layers:
- Zombie seats: assigned to people who left, or never onboarded.
- Shelfware in production: the product is live, trained, and still loses to the old path.
Layer 1 is a reclaim. Layer 2 is a product decision. Mixing them is how companies cancel a tool that was never in the job, then buy a replacement that fails the same way.
A cost audit you can run this week
You do not need a SaaS-management platform to start. You need three lists.
| What to count | Where to get it | What "bad" looks like |
|---|---|---|
| Seats purchased | Invoice / admin billing | Headcount and seats do not match |
| Logged in last 30 days | Admin last-login export | Far fewer than seats paid |
| Where urgent work actually happens | Five honest interviews | Email, spreadsheet, phone, personal tab |
| Renewal date | Contract | You are 30 days from auto-renew with no usage story |
Worked example (illustration, not a customer quote): 40 seats purchased, 7 people logged in last month, urgent work still in email. You are not "rolling out." You are funding unused software at work.
Ask the three questions out loud:
- When it is urgent, which screen do people open?
- How many seats did we buy, and how many logged in last month?
- If we cancelled the tool tomorrow, would Tuesday change?
If you cannot answer those, you do not have a rollout. You have a line item.
Why training and "one more platform" fail
Teams hear shelfware and book another webinar. Training helps a willing person. It does not fix a product that adds clicks when a queue is ringing.
The other myth is consolidation: buy one more platform to unify everything. Sometimes that is right. Often it is a fifteenth login. Consolidation only works if the new screen is where the work already lives. For the rewrite-or-not decision, see our comparison of AI retrofit vs a full rewrite.
SaaS-management playbooks (30/60/90-day inactivity, SCIM offboarding) will catch zombies. They will not make dispatchers open a dashboard they hate. That is why how to reduce unused SaaS licenses has to include a product test, not only a license reclaim. Unused tabs fail the same way we described in why AI projects fail.
Five steps: reclaim, then decide whether to build
1. Inventory seats and last login
Export every paid app. Match seats to current employees. Anything assigned to a departed person is an immediate reclaim. This is the same first move every 2026 license-audit guide recommends. Do it before you debate strategy.
2. Watch one urgent workflow
Pick one job: ticket replies, ride booking, leave questions, invoice chase. Sit with the person who does it. Note the screen they actually use. Believe them even if it is ugly.
3. Reclaim what is clearly dead
Cancel or downgrade zombie seats before the next invoice. Do not wait for annual renewal if the vendor allows a mid-cycle change. Flag the renewal date either way.
4. Test the remaining product against the job
If last-login is healthy and Tuesday is still email, the product is beside the work. More licenses will not fix that. Neither will a second copilot in a new tab.
5. Build or retrofit inside the job, or stop buying
This is the Solvefy line. We build and modernize custom software development, SaaS products, and MVPs. We retrofit into systems that already run the business when a rewrite would throw away permissions and integrations. We do not pretend a new tab is a transformation. See our guide to adding AI without a rewrite.
If usage does not move after the helper is in the job, stop adding licenses. Measure last-login again in 30 days.
When custom software development is the cheaper path
Reclaiming seats is cheaper than a build when the tool is a genuine fit and waste is mostly zombies. A build (or a retrofit) is cheaper when people have already rejected the official screen.
On AICO, medical transport staff still had to sound calm on the phone. Voice and chat help sat on the booking work they were already doing. Public numbers we can stand behind: about 75% less call-handling load, about 98% scheduling accuracy. The schedule engine stayed. People stayed in the loop for the parts that should not be silent.
On IbisHR, letters, leave, and policy answers sat on records HR already trusted. Admin work dropped about 60%. Self-service hit about 95% in 90 days. Nobody had to remember a second HR product when a person was waiting.
That is the test for custom software development: will seven people still be the only ones in the room after month three, or does the screen earn the Tuesday?
We will not invent a customer who cut 65% overnight. Vertice's 65% is a market average for unused or underused licenses, not a promise about your stack.
Frequently Asked Questions
How do you reduce unused SaaS licenses without a management platform?
Export billing seats, last-login, and current employees. Reclaim departed users first. Then watch one urgent workflow. Most of the savings in the first pass come from zombies, not from a new dashboard.
Is unused software at work the same as too many apps?
Related. Too many apps makes people paste between tools. Unused SaaS licenses make you pay for a screen they skip. Both mean the system of record is not the system people trust.
What inactivity window should we use?
SaaS-management guides often use 30, 60, or 90 days. Seasonal roles need a longer window. A financial close tool that is quiet for 80 days is not always waste. A daily dispatch tool with no logins in 30 days is.
Can custom software fix license waste?
Only if it replaces the job, not if it sits beside it. Custom software people skip is just more shelfware.
Should we block personal tools if people skip the official one?
Blocking without a better box trains people to hide. Fix the job-shaped product first. Then set policy.
Conclusion
How to reduce unused SaaS licenses is a two-part job. Reclaim the seats nobody should have. Then stop paying for a product that loses to email.
Count last-login this week. Put help inside the job people already do. That is the bar we used on AICO and IbisHR, and it is the one we still use.
If you are heading into a renewal, bring the seat table, not a feature comparison. The comparison does not matter if seven people are the only ones logging in.
Sources: Vertice, Unused SaaS applications, Q2 2026 accessed 2026-08-31; Vertice, Wasted SaaS spend accessed 2026-08-31; Ramp, Unused software subscriptions accessed 2026-08-31; Iden, SaaS license audit and reclamation accessed 2026-08-31; OptyStack, How to find unused SaaS licenses accessed 2026-08-31.
Heading into a renewal with unused seats?
Bring the seat table, not a feature comparison. We help teams reclaim waste, then put help inside the job people already do, instead of buying another unused login.