How to Right-Size SaaS Licenses Before Renewal
Pull real usage, confirm it with the teams, and bring the reconciled number rather than the contracted one.
I spent years on the vendor side of enterprise software, and the short answer is: pull real usage data, confirm it with the actual team using the tool, and bring the reconciled number, not the original seat count, into the renewal conversation.
Turning a seat count into a defensible number
Real usage data
- Active logins over 60 to 90 days
- Not seat assignments
- Per team where possible
Roster and team leads
- Catch leavers and role changes
- Confirm occasional but real users
- Reconcile disagreements
The reconciled count
- State the new number
- Show how it was derived
- Do not open with a discount ask
A specific reduction the vendor has to respond to is a different conversation from a general request for a better price.
Step by step
- Pull actual usage data: active logins over a meaningful window of 60 to 90 days, not just current seat assignments, which do not tell you who is actually using the tool.
- Cross-reference against your current employee roster, to catch licences tied to people who have left or changed roles.
- Confirm with team leads, since usage data alone can miss context: someone with low login frequency might still genuinely need access for occasional but important use.
- Reconcile the numbers. Where usage data and team confirmation disagree, dig a bit deeper before finalising.
- Bring the reconciled seat count into the renewal conversation directly, rather than accepting the existing contract's seat count as the default starting point.
Why this changes the negotiation, not just the invoice
A renewal conversation that opens with "we are reducing from 150 to 94 seats based on confirmed usage" is a materially different conversation from a general request for a discount. It is a fact-based position the vendor has to respond to specifically.