What is SaaS license right sizing? A definition
Right sizing is the gap between what you pay for and what you use, closed deliberately. Every subscription has two dimensions you can get wrong. The first is quantity, meaning how many seats you hold versus how many are active. The second is tier, meaning how rich a plan each user sits on versus what their role needs. SaaS license right sizing corrects both. It reclaims inactive seats and moves over specified users to a lower tier that still does their job.
It is not a one off cull. Estates drift. People join, leave, and change roles. Vendors add tiers and bundles. Right sizing is the ongoing alignment that keeps spend tracking real need rather than peak headcount from two years ago.
How is right sizing different from cutting seats?
Cutting seats is blunt. You reduce a number and hope nobody complains. Right sizing is precise. It starts from usage evidence, separates genuinely inactive accounts from quiet but legitimate users, and distinguishes a wrong tier from a wrong quantity. The Microsoft 365 estate is the classic example. A user on E5 who never touches the advanced security and compliance features is not a seat to delete. They are a seat to move to E3. Cutting would break their access. Right sizing keeps them working at lower cost.
Why does right sizing save so much?
Because the waste is structural, not occasional. The common sources of digital workplace overspend are over licensing, unused or inactive seats, the wrong plan tier, duplicate tools, auto renewals nobody reviewed, and shelfware. Right sizing attacks the first three directly. Microsoft 365 is usually the largest single line item, so tier corrections there often deliver the biggest single saving. But every per seat tool in the stack carries some slack, and the totals add up fast across a mid market estate.
The right sizing process step by step
1. Build a usage baseline
You cannot right size what you cannot see. Pull entitlement counts for every application and match them to real activity data: last login, feature use, and license assignment. This baseline is the foundation for every decision that follows and the same data that protects you in a vendor review.
2. Separate inactive from over specified
Two different problems need two different fixes. Inactive accounts, including leavers and dormant seats, get reclaimed. Active users on a richer tier than their role requires get downgraded. Treating both as deletion breaks things. Treating both as downgrade leaves money on the table.
3. Validate with the business
Usage data flags candidates. Owners confirm them. A seat that looks dormant may belong to a seasonal role or a critical but infrequent user. Quick validation with the application owner prevents the reclamation that comes back to bite you and builds trust for the next cycle.
4. Time the changes to the contract
Reclamation and downgrades only save money when the contract lets them. Monthly plans flex quickly. Annual and multi year commitments, including a Microsoft Enterprise Agreement, often only allow reductions at renewal. Line up your right sizing so the changes land when they can actually reduce the bill.
5. Govern so it holds
Without governance the slack returns within a year. Assign owners, tie license changes to joiner and leaver processes, and run the right sizing cycle on a schedule. This is the difference between a one time refund and a permanent lower run rate.
Where right sizing fits the bigger picture
Right sizing is usually the first and biggest move in cutting workplace spend, ahead of renewal negotiation and ongoing governance. It also strengthens every later step, because you negotiate from a lean estate rather than a bloated one. For the full discipline, read the digital workplace cost optimization pillar and the license right sizing cluster. Related reading includes quantifying shelfware for the business case, right sizing before a renewal, and inactive user cleanup across the stack. When you are ready to act, see our license right sizing service.
Microsoft 365 tier examples (E3 and E5) and Enterprise Agreement reduction timing reflect Microsoft commercial licensing as of June 2026. Vendor plans change often, so confirm current terms before acting.