© 2026 Procr
SaaS stacks expand quickly and contract slowly. A 200-person company that provisioned seats aggressively during a growth phase can easily carry 30 to 40 percent unused licenses by the time the next renewal arrives, and most of those seats will roll over automatically unless someone intervenes. The reclamation window is narrow and requires specific preparation, but the return is immediate: recovered budget, a cleaner vendor relationship, and a stronger position at the renewal table.
Licenses accumulate faster than they get cleaned up for structural reasons. Procurement approves a new tool, seats get provisioned, and no one is formally responsible for reviewing utilization until renewal. When an employee leaves or changes roles, their access is often disabled for security reasons but the license keeps billing. When a project ends and a tool is no longer needed, the monthly charge continues invisibly.
Zylo's 2026 SaaS Management Index found that the average organization uses just 54 percent of its provisioned licenses, meaning nearly half of what companies pay for sits idle. For a mid-market company with $2M in annual vendor spend, that translates to roughly $600,000 to $800,000 in wasted budget per year, budget that gets locked into renewed contracts unless teams act before the renewal date.
The problem compounds at renewal because most enterprise SaaS agreements renew at the contracted seat count, not the actual usage count. Vendors do not prompt you to reduce. Research from SeatCompress found that 60 percent of SaaS contracts renew at inflated counts because buyers do not complete a usage review before signing.
The reclamation window should open 90 days before any renewal. That is enough lead time to complete a usage audit, prepare a right-sized seat count, give the vendor formal notice of any reduction (most contracts require 30 to 60 days advance notice), and negotiate the new terms.
Starting at 30 days is too late. Vendor notice windows alone will consume most of that time, and you will be negotiating from a weaker position because the vendor knows the deadline is close.
For teams managing more than 20 vendors, a rolling calendar that flags 90-day windows automatically is the difference between a managed renewal cycle and a reactive one.
Most enterprise SaaS tools expose usage data within the admin dashboard. Before using any third-party management tool, start here.
What to look for:
Any user with zero logins in 90 days is a strong reclamation candidate unless there is a documented exception: a seasonal employee, a board member with infrequent access, or an integration account. Flag those users for review, not automatic removal.
Users with low activity (logging in once or twice a month, using only one feature) may be candidates for a tier downgrade rather than removal. Track both categories separately.
Usage reports only show accounts that exist in the system. They do not automatically reflect organizational reality. A user might have been offboarded from HR six months ago but their license is still active and billing.
Pull a current employee list and compare it against the active user list in each tool. Accounts belonging to former employees should be removed immediately. This single step typically returns 5 to 15 percent of provisioned seats, depending on how long it has been since the last audit and how much staff turnover the company has had.
Accounts belonging to contractors, consultants, or project-specific hires need separate review. Determine whether the engagement is ongoing and whether the access level is still appropriate.
Before contacting the vendor, prepare a one-page summary documenting:
This document does two things: it forces internal alignment on the right-sized number before the vendor conversation begins, and it gives you a factual basis for negotiation that is difficult for the vendor to dispute.
A company with 150 Slack seats, 90 of which have had zero logins in 90 days, has a clear and documentable case for reducing to 90 at renewal. That is a 40 percent reduction in per-seat spend with no functional impact on active users.
Not every underutilized user should be removed. Some users have legitimate but infrequent access needs. For those users, the relevant question is whether they need the current license tier or whether a lower tier covers their actual usage.
Many enterprise SaaS tools support mixed-tier billing, meaning you can maintain different plan levels for different users on the same account. Adobe Creative Cloud, Salesforce, Zendesk, and HubSpot all support some version of this. If a user only needs read-only access or a limited feature set, downgrading their seat reduces cost without removing access.
A practical benchmark: in most enterprise tools, 20 percent of users consume 80 percent of advanced features. The remaining 80 percent are candidates for downgrade review.
A concrete example: a 250-person company paying for 180 Salesforce Enterprise licenses at $165 per seat per month discovers through a usage audit that 55 users only access contact records and basic pipeline views. Downgrading those 55 seats to Professional at $80 per seat per month saves $85 per seat per month, or $56,100 per year, without disrupting any active workflow.
With the reclamation case documented, contact the vendor's account manager 60 to 90 days before the renewal date. Lead with usage data.
The framing matters. Rather than asking for a discount, you are proposing to right-size the contract based on documented usage. Most enterprise SaaS agreements include a true-down provision or allow seat reduction at renewal. What vendors do not volunteer is that you have to initiate it.
If the vendor resists reducing the seat count, you have several options:
Teams that present usage data at renewal consistently achieve 20 to 35 percent reductions in per-renewal costs on tools they would otherwise have renewed at full count.
A single reclamation effort yields one year of savings. A standing process yields savings every year and prevents waste from rebuilding.
The components of a repeatable process:
A renewal calendar that surfaces every renewal 90 days in advance, with the assigned owner and the date of the last usage audit.
A 90-day inactivity rule applied consistently: any account with zero logins in 90 days is flagged automatically and reviewed before the next billing cycle.
An offboarding checklist that includes license deprovisioning alongside IT access removal, so former-employee seats are recovered within days of departure rather than months later.
Quarterly reviews for top tools by spend. Monthly reviews are impractical at scale. Annual reviews are too infrequent given how quickly team composition changes.
Zylo's 2026 SaaS Management Index found that organizations waste an average of 46 percent of their provisioned licenses. A mid-market team that completes a structured audit and right-sizes its ten largest contracts by spend can realistically recover 10 to 20 percent of the annual cost of those contracts through seat removal and tier downgrades alone. For a company spending $1.5M per year on vendor software, that is $150,000 to $300,000 in recoverable budget, independent of any price negotiation benefit.
Savings depend on stack size and how long it has been since the last audit. Most mid-market teams completing a structured reclamation exercise for the first time recover 10 to 20 percent of annual SaaS spend. Zylo's 2026 data shows organizations waste an average of 46 percent of provisioned licenses, so companies that have never run a formal review often find more. For a company with $1.5M in SaaS spend, that range translates to $150,000 to $300,000 in recoverable budget.
Most enterprise SaaS contracts allow seat reduction at renewal, but you must initiate it. Vendors will not offer it unprompted. The requirement is giving formal notice within the window specified in your contract, typically 30 to 60 days before renewal. If you miss that window, you are generally committed to the current count for another full term.
Ninety days with no login is the standard threshold and is conservative enough to avoid removing people with legitimate but infrequent access. Thirty days is more aggressive and may create friction with occasional users. The important thing is to apply the threshold consistently and document exceptions, rather than exclude them without review.
If the contract does not allow a true-down at renewal, you have two options: use the renewal as a forcing function to negotiate a better per-seat rate even at the current count, or decline to renew at the current count and move to a right-sized contract at expiration. In practice, most vendors prefer retaining you at a lower seat count over risking a non-renewal. Usage data makes that case clearly.
Low-activity accounts (users who log in once a month and use one feature) are candidates for tier downgrade rather than removal. Check whether the user genuinely needs their current plan or whether a lower tier covers their actual workflow. Many enterprise tools support per-user tier mixing, so you can maintain the access and reduce what you pay for that seat without disrupting anything.
Procr
See what Procr does with your real vendor portfolio.