The fastest saving on almost any ITSM contract is not a discount, it is a correct headcount. Most estates carry agent licences that no longer match who actually works tickets: leavers never deprovisioned, occasional approvers licensed as full fulfillers, and seats bought for a project that ended. Right-sizing agents means matching paid licences to genuine need before you renew, so you negotiate the price of what you use rather than the price of what you accumulated. This guide explains how to right-size agents on any ITSM platform, whatever the licensing model. Across our work, right-sizing routinely contributes to the 30{'PILLAR': '/blog/manageengine-servicedesk-plus-pricing-2026.html', 'SVC': '/services/contract-negotiation.html', 'RENEW': '/blog/the-complete-guide-to-itsm-renewal-negotiation.html', 'WP': '/white-papers/the-itsm-renewal-timing-playbook.html'}verage reduction we achieve.
It sits under our guide to mid-market and other ITSM platform pricing, and it is the step we run first in any engagement because it removes cost before discounting even begins.
Separate the roles the vendor charges for
Every ITSM platform draws a line between users who work the queue and users who merely interact with it, and the line is where the money is. A full agent or fulfiller licence is the expensive seat; requesters, approvers, occasional contributors and read-only stakeholders usually have a cheaper licence or none at all. The single most common overspend is licensing someone as a full agent when they approve a change request twice a month. Start by classifying every named licence against what that person actually does in the tool over a representative period, not what their job title implies.
Use real usage data, not the org chart
The org chart tells you who should use the platform; the logs tell you who does. Pull login frequency, tickets touched, and last-active dates for every agent licence, and the picture is almost always smaller than the contract. Dormant seats, duplicate accounts and roles that have drifted out of the queue all surface here. Usage data is also the evidence that makes the reduction defensible to the vendor, the broader case for which is in how to use usage data in an ITSM renewal. A reduction backed by logs is a fact; one backed by opinion is an opening offer.
| Signal | What it suggests | Action before renewal |
|---|---|---|
| No login in 90 days | Dormant or departed user | Deprovision or downgrade the seat |
| Approvals only, no ticket work | Over-licensed approver | Move to a requester or lighter licence |
| Shared or duplicate account | Inflated paid count | Consolidate to one correct licence |
| Project seats post-project | Stranded capacity | Drop at renewal, do not carry forward |
Right-size before you lock the term
Timing matters. Reductions are easiest at renewal, when the term resets, and hardest mid-term, when most contracts forbid lowering quantities. If you right-size after signing, you carry the excess for the whole term. Do the analysis in the window before renewal so the corrected number is what you negotiate against, and avoid the opposite error of over-committing to a higher count for a unit discount, covered in our complete guide to ITSM renewal negotiation. A lower true-up baseline compounds across every future renewal.
Our contract negotiation service runs the usage analysis, classifies every seat, and folds the corrected headcount into the renewal so you negotiate the price of genuine need.
The gated ITSM Renewal Timing Playbook includes the seat-classification checklist we use to right-size an estate before the term locks.
A worked example of a right-sizing pass
A two-hundred-seat ITSM contract comes up for renewal and the buyer runs a usage pass before engaging the vendor. The logs show thirty agents with no login in ninety days, a mix of leavers and a project team that disbanded; twenty-five more are pure approvers who touch a change request occasionally but hold full agent licences; and a handful of duplicate accounts inflate the count further. None of this was visible on the contract, which simply listed two hundred seats renewing at an uplift. After deprovisioning the dormant accounts, moving the approvers to a lighter licence, and consolidating duplicates, the genuine requirement is closer to one hundred and forty full agents.
That correction happens before any discount is discussed, and it changes everything that follows. The benchmark is now run against the real number, the target price is set against the real number, and the uplift compounds on the real number for the rest of the term rather than on sixty seats nobody uses. The vendor cannot reasonably object, because the reduction is backed by their own platform's usage data. A right-sizing pass like this is unglamorous and routinely the largest single line of saving in the whole renewal.
One caution: right-sizing is a baseline correction, not a one-off cleanup. Seats drift again the moment the new term begins, as projects spin up, people move teams and accounts are created faster than they are retired. The buyers who hold the lowest cost over multiple renewals treat the usage pass as a standing discipline run every renewal cycle, not a heroic effort done once and forgotten. Build the report into your renewal calendar so the corrected number is re-established each term, and the saving compounds instead of quietly eroding back to where it started.
Book a renewal review.
We match paid licences to genuine need and negotiate the price of what you use. Fixed fee or gainshare, with no fee unless we save you money.
Book a renewal review →Frequently asked questions
- What does it mean to right-size ITSM agents?
- It means matching paid agent or fulfiller licences to who actually works tickets, using real usage data rather than the org chart. That involves deprovisioning dormant seats, moving occasional approvers to lighter licences, consolidating duplicates, and dropping stranded project seats before the term renews.
- When is the best time to right-size?
- In the window before renewal. Most contracts forbid lowering quantities mid-term, so a reduction found after signing is carried for the whole term. Doing the analysis before renewal means the corrected count is what you negotiate against, lowering the baseline for every future renewal.
- Does right-sizing require the vendor's agreement?
- No. Unlike a discount, right-sizing corrects the quantity you buy, which is your decision at renewal. Usage data makes the corrected number defensible, but you are not asking for a concession, you are buying what you actually use.