What Is License Right-Sizing?
Adjusting the seats on a SaaS contract to match actual usage rather than the count you originally bought.
Seat counts are set once and rarely revisited. Right-sizing is the correction.
I spent years on the vendor side of enterprise software, and license right-sizing is the process of adjusting the number of licenses or seats on a SaaS contract to match actual usage, rather than the originally purchased count, typically ahead of a renewal.
Right-sizing, measured rather than guessed
Only removable while the term is still open to change.
An across-the-board cut
- Blunt reductions get reversed mid-term
- Usually at a worse unit price
Matching entitlement to activity
- Per tier and per team, not one blended number
- Documented before the quote arrives
Why the original count usually stops being accurate
Seat counts get set at a point in time, often during onboarding or a growth phase, and rarely get revisited as headcount, roles, or team needs shift afterward. People leave, projects end, tools get replaced, and the seat count on the contract stays the same unless someone deliberately changes it.
How right-sizing typically works
- Pull actual usage data, active users over a meaningful window, not just current seat assignments.
- Confirm with the relevant team leads whether specific users still need access, since usage data alone doesn't always capture context.
- Reconcile the confirmed number against the current licensed count.
- Bring the reconciled number into the renewal conversation, rather than accepting the existing seat count by default.
Why it matters beyond direct cost savings
Right-sizing also changes the negotiation itself. A renewal conversation that opens with a specific, usage-based number is a fundamentally different conversation than one that opens with a general request for a discount, it's a fact the vendor has to respond to.
Common mistakes
Right-sizing based on login data alone, without confirming with the actual team, can cut seats that still matter for reasons the data doesn't capture. The most reliable process combines both: real usage numbers and a direct check with the people using the tool.