A license right sizing roadmap gives the work a shape. Without one, license cleanup tends to happen in bursts, usually triggered by a renewal panic, and the savings leak straight back. With one, you move in order from a clear baseline, to measuring real use, to recovering seats at the right moment, to the governance that holds the lower number in place. This page lays out that roadmap so a finance or IT leader can see the whole path before committing to it.
The principle behind the sequence is simple. Right size first, before you negotiate or buy anything new, because a smaller, cleaner seat count changes every downstream decision. The roadmap is the operating version of that principle, and it sits at the centre of SaaS license right sizing as a discipline.
What is a license right sizing roadmap?
It is a phased plan that orders the work so each phase produces what the next one needs. The baseline produces the inventory that measurement reads. Measurement produces the gap that recovery acts on. Recovery produces the lower number that governance defends. Skip a phase and the later ones wobble: recover seats without a baseline and you cannot prove the saving; cut seats without governance and they quietly return. The roadmap exists to stop those failures.
What are the phases of license right sizing?
Most engagements run in four phases. The detail varies by stack, but the order rarely does.
Phase one: build the baseline
You cannot right size what you cannot see. The first phase is a complete inventory of every product you pay for, the seat count and tier on each, the annual cost, and the renewal date. This is the foundation, and it is where many programmes are quietly let down, because the picture is incomplete and the savings cannot be trusted. A thorough baseline also surfaces duplicate tools and forgotten subscriptions that belong in a wider digital workplace cost optimization review.
Phase two: measure utilisation
With the baseline set, pull real usage and lay it against what you pay for. Last login, last meaningful action, and tier feature use all matter here. The output is a ranked list of gaps: inactive seats, over specified tiers, and products with near zero adoption. This is the analytical heart of the roadmap, and the method is set out in measuring SaaS license utilisation. The quality of this phase decides how much you can confidently recover.
Phase three: recover and right size
Now you act, and timing is everything. Reassign idle seats immediately to defer new purchases. Remove surplus seats and downgrade over specified tiers at each renewal, because most committed contracts only release savings at the renewal date. That makes the renewal calendar the spine of this phase: every contract has a window, and the analysis has to be ready before each one. This connects directly to right sizing before a renewal, where the prepared lower number gets locked in rather than rolled over.
Phase four: govern
The final phase makes the saving permanent. Tie seat removal to offboarding so leavers lose access automatically. Review utilisation before every renewal rather than after. Give one owner clear accountability for the whole stack, because shared ownership is why the waste accumulated in the first place. Without this phase the roadmap becomes a one time cut that erodes; with it, the lower baseline holds and improves over time.
Where do you start with license right sizing?
Start with the baseline, always. It is tempting to jump to the obvious cut, the tool everyone knows is underused, but acting before the inventory is complete means you cannot prove the saving or spot the larger structural waste. Build the full picture first, even though it is the least glamorous phase, because every later decision rests on it. To put numbers behind the case for action, pair the baseline with quantifying shelfware for the business case.
How long does license right sizing take?
The analysis can move quickly once usage data is in hand, often within a few weeks for a mid market stack. The recovery, though, is paced by renewal dates spread across the year, so the savings land in steps rather than all at once. And governance never ends, because new joiners, leavers, and purchases keep the stack moving. The honest framing is that this is a programme, not a project. The first cycle delivers the headline savings; the governance keeps them.
How do you keep license savings from returning?
By building the controls into normal operations rather than relying on willpower. Automated deprovisioning through your identity provider, a standing review tied to each renewal, and a single accountable owner together close the loops that let waste creep back. This is the same governance logic that underpins the broader spend programme. To run the full roadmap as a managed engagement, see how we deliver license right sizing for mid market buyers.
Followed in order, the roadmap turns license cost from something you react to at renewal into something you manage continuously. Build the baseline, measure the gap, recover at the right moment, and govern so it holds. That sequence is what separates a one time cut from a permanently leaner stack.