- Right-sizing means matching each license, its seat count and its plan tier, to how the app is actually used.
- Unused seats get removed; underused seats get downgraded to a cheaper tier that still covers real needs.
- The signal you need is usage depth, not just whether someone logged in once.
- Right-sizing sticks when you review it on a cadence tied to each contract's renewal.
You right-size SaaS licenses by matching the seats and plan tiers you pay for to how each app is actually used. Where a seat goes unused, you remove it. Where a seat is used but only for basic features on a premium plan, you downgrade it to a tier that still covers the real need at a lower cost.
The hard part is not deciding to right-size, it is having the usage depth to do it safely. A login count tells you a seat is active; it does not tell you whether that person needs the premium tier. This guide covers how to measure usage well enough to right-size without cutting access people rely on.
What is license right-sizing?
License right-sizing is the practice of matching what you pay for to what you use, on two axes. The first is seat count: how many licenses are active versus how many you bought. The second is tier: whether the plan level matches the features people actually use.
Right-sizing is broader than reclaiming unused seats. Reclaiming handles the seats nobody touches. Right-sizing also handles the seats that are touched, but on a plan richer than the work requires. Both reduce spend, but the fix differs: unused seats are removed, underused seats are downgraded.
Where over-provisioning hides
Over-provisioning is quieter than an unused seat because the license looks active. A premium seat used only for basic tasks still shows sign-ins, so it never trips a simple unused-license report. You only catch it by comparing the tier you pay for against the features that get used.
Seat counts drift the same way. A team buys twenty seats, shrinks to twelve, and the contract still renews at twenty because nobody revisited the number. Neither problem is visible without a usage view that goes deeper than a login.
How to right-size your licenses
The goal is to size every license to real usage, then make the changes at the moment they can take effect.
Baseline real usage per user
Measure how each seat is actually used, drawing on sign-ins from your identity provider and a desktop signal for apps that bypass single sign-on. A login count is not enough to judge a tier.
Compare usage against the plan tier
For each app, line up the features people use against the plan you pay for. A premium seat that only ever touches basic features is a downgrade candidate.
Separate remove from downgrade
Sort every seat into one of two actions. No activity means remove the seat. Active but shallow usage means downgrade the tier. Mixing the two leads to cutting access someone needs.
Batch the changes at renewal
Group your remove-and-downgrade list by contract and act just before each renewal date, when the seat count and tier are still negotiable.
Re-check on a cadence
Usage shifts as teams grow and shrink, so revisit right-sizing every quarter or at each renewal rather than treating it as a one-time cleanup.
How License Logic supports right-sizing
License Logic gives you the usage depth and cost context right-sizing needs, in one view alongside the contract.
- Usage depth, not just a login. Sign-ins from Entra, Okta, and Google Workspace, plus a macOS desktop agent that captures direct-login activity, give you a real read on how much a seat is used, not just whether it is active.
- Per-seat cost from the contract. Each app shows active users and cost per seat next to the plan you pay for, so a downgrade or seat cut comes with the dollar impact attached.
- Microsoft 365 reclamation and provisioning. For Microsoft 365, License Logic can reclaim and reassign licenses based on real usage and manage provisioning through SCIM, so seat counts track the team automatically.
- Price benchmarks for the renegotiation. Price intelligence on select vendors gives you a reference point when you move tiers or renegotiate a renewal.
Right-sizing is a habit, not a project
A one-time right-sizing pass saves money once. The teams that keep spend under control treat it as a recurring review tied to each renewal, because usage never stops shifting. A team that was right-sized in January can be over-provisioned by summer.
When usage depth, per-seat cost, and renewal dates live in one place, that recurring review is quick, and the savings compound instead of leaking back.
License Logic shows usage depth, per-seat cost, and renewal dates together, so you downgrade what is underused instead of overpaying.
Frequently asked questions
What does it mean to right-size a software license?
Right-sizing a license means matching its seat count and plan tier to how the app is actually used. If a seat goes unused, you remove it. If a seat is used but only for basic features on a premium plan, you downgrade it to a cheaper tier that still covers the real need. The aim is to pay for what you use, no more.
What is the difference between reclaiming and right-sizing licenses?
Reclaiming targets seats with no activity and removes them. Right-sizing is broader: it also covers active seats that sit on a richer plan than the work requires, which get downgraded rather than removed. Reclaiming fixes waste from unused seats; right-sizing fixes waste from both unused seats and over-provisioned tiers.
How do you know if a license tier is too high?
Compare the features people actually use against what the plan includes. A premium seat that only ever touches basic functionality is a downgrade candidate. This requires usage depth, not just a login count, since an over-provisioned seat still shows sign-ins and looks active on a simple report.
Will right-sizing licenses disrupt the people using them?
It should not, if you measure real usage first. Seats with no activity are removed, and active seats are only downgraded to a tier that still covers what they use. The risk comes from acting on shallow data, which is why usage that includes off-SSO activity matters before you change anything.
How often should you right-size licenses?
Treat it as a recurring review rather than a one-time project. Usage shifts as teams grow and shrink, so a quarterly pass or a review tied to each contract's renewal keeps licenses matched to real use and stops waste from creeping back in.