What Right-Sizing Is — and Isn't
Right-sizing enterprise software means adjusting each user's licence tier — and each system's capacity — to match verified usage rather than the level originally bought. It is distinct from reclamation: reclamation removes seats nobody uses, while right-sizing keeps access in place and downgrades the over-provisioned licences to the tier the user actually needs. That distinction matters because the fastest savings often come from right-sizing, not removals — downgrading to real usage preserves productivity while cutting the bill.
Industry studies consistently show 20–35% of licences are unused or underused at any time, and a large share of those are over-tiered rather than fully idle. Right-sizing is the lever that captures that middle band, and it sits alongside licence reclamation as a core move in the enterprise IT cost optimisation framework.
Where Over-Provisioning Hides
Over-provisioning accumulates because buying the premium tier for everyone is administratively simpler than matching tiers to roles. The table shows the most common patterns and the typical downgrade opportunity.
| Over-Provisioning Pattern | Example | Downgrade Opportunity |
|---|---|---|
| Premium tier, basic use | E5 seats using only E3 features | 20–40% of premium seats |
| Full suite, single module | Full platform, one app used | 15–30% |
| Power-user tier, light use | Editor licence, viewer activity | 20–35% |
| Standard tier, dormant | Assigned, sub-monthly use | Reclaim, don't downgrade |
The classic case is the premium productivity suite. A 5,000-seat estate where 30% of premium seats are used at the basic level is carrying a six-figure annual overspend — recoverable with a downgrade that no user would even notice.
The highest-value patterns are in expensive, tiered SaaS. A Microsoft estate where E5 seats run E3-level activity is the textbook example, but the same dynamic applies across design, analytics, and CRM platforms — anywhere a premium tier is bought as the default.
The Right-Sizing Method
Right-sizing runs in three steps. Measure real feature-level usage per user, not just login activity — a user who logs in daily but touches only basic features is a downgrade candidate. Match each user to the lowest tier that covers their actual usage, building a target tier mix for the estate. Move users to the correct tier, with a light-touch exception path so genuine power users can request an upgrade. The discipline is to drive off verified feature consumption — surfaced through IT spend analytics — rather than self-reported need, which always over-states.
Sequence matters. Run reclamation first to strip out the genuinely idle seats, then right-size the remainder. Together they typically take 15–30% out of software spend within a year, and because no one loses access in the right-sizing step, the productivity risk is minimal. This is also the largest reuse line in most software asset management ROI models.
Infrastructure and Cloud Right-Sizing
Right-sizing is not limited to per-seat SaaS. The same principle applies to infrastructure: over-provisioned virtual machines, idle reserved instances, and unattached storage carry the same waste pattern as an over-tiered licence. FinOps right-sizing routinely takes 20–35% out of cloud spend by matching instance sizes and commitment coverage to actual consumption. The mechanics differ but the logic is identical — pay for what is used, not what was provisioned at peak.
Bringing both together — SaaS tier right-sizing and infrastructure capacity right-sizing — under a single usage-driven discipline is what turns right-sizing from a one-off clean-up into a standing capability, reinforcing the broader cut-cost-not-capability approach.
Locking It In at Renewal
A downgrade only becomes a saving when the contracted baseline reflects the new tier mix. Feed the right-sizing data into the renewal 6–9 months early and negotiate the reduced commitment, or vendors quietly re-load premium tiers at the next true-up and the saving reverses. This is why right-sizing and renewal negotiation are inseparable — our SaaS contract optimisation practice takes the verified tier mix into the renewal so the lower baseline is contracted, not just internally tracked. The SaaS optimisation guide sets out the full operating model.
Done once, right-sizing is a clean-up; wired into the renewal cycle, it is a permanently lower run-rate that protects productivity. To map your tier mix against real usage and take the saving into your next renewal, request a confidential briefing.