Home/Journal/How to Right-Size TOPdesk Operator Counts
TOPdesk · How to

How to Right-Size TOPdesk Operator Counts

Right-sizing a TOPdesk operator base means replacing the entitlement you pay for with the count you actually use: dormant seats removed, requesters reclassified, and the rest split into named and floating licenses against real concurrency. The gap between entitled and active operators is the saving, and on estates that have not been reconciled in a few cycles it is rarely small. Here is the method, in finance terms.

A TOPdesk operator seat is a fixed annual cost whether the operator works the desk or not. That is the whole reason right-sizing pays: you are not chasing a discount, you are stopping yourself paying for capacity nobody uses. Do this before the renewal quote arrives and you negotiate from a reconciled baseline; do it after, and you are arguing down from TOPdesk's inflated starting number. The pricing context is in our TOPdesk pricing guide, and the named-versus-floating mechanics that this method feeds are in TOPdesk operator and floating licenses explained.

Why does the operator count drift above real need?

Operator counts inflate quietly, between renewals, through ordinary churn. Staff leave and the seat is not reclaimed. Someone is added as an operator for a one-off project and never removed. Approvers and managers are given operator access so they can comment, when a requester role would serve. None of these are decisions anyone made on purpose, which is exactly why they accumulate. The finance consequence is a base that is several percent larger than the team that works it.

How do you right-size the operator base? The method

The sequence is the Map step of our Map · Benchmark · Leverage · Close method, applied to operators. Run it in order.

  1. Export the data. Pull a representative period of operator login frequency and peak simultaneous logins, plus last-login dates for every operator.
  2. Cut the dormant. Flag operators who have not logged in within a defined window. These are the cleanest seats to reclaim because activity data settles the argument with no judgement call.
  3. Reclassify the requesters. Anyone who only comments, approves or reads should be a requester, not an operator. Requesters are licensed differently and cost far less, so each reclassification removes an operator-seat cost.
  4. Segment what remains. Split the genuine operators into always-on full-time staff and occasional, shift or part-time users.
  5. Re-fit the licenses. Name the always-on group; size a floating pool to the peak concurrency of the occasional group, with a small buffer. This is where the named-versus-floating split turns measurement into money.
The figure that goes in the board pack is the gap between entitled operators and reconciled operators, valued at the per-seat rate. That number is your reclamation target, and it is defensible because every line behind it comes from login data, not opinion.
Book a contract negotiation review →

How do you model the saving for finance?

Build it bottom-up. Start from entitled operators at their current cost. Subtract dormant seats reclaimed. Subtract operators reclassified to requesters, valued at the difference between the two license types. Then re-price the survivors under the corrected named-and-floating mix, where moving occasional users to a right-sized floating pool usually lowers cost again. The total of those reductions, expressed as an annual figure and a percentage of current spend, is your case.

Where any input is uncertain, model it as a range and confirm against the export, rather than presenting a single number you cannot stand behind. A defensible range survives vendor pushback; a false precision does not. The reclamation worksheet behind this is in our gated ITSM Shelfware Reclamation Toolkit.

When should you do this, and what do you do with the result?

Start three to six months before the renewal date. That runway lets you reconcile the base and, if needed, manage any change to operator access before TOPdesk quotes. Then take the reconciled count into the renewal as your baseline, hold the right to convert between named and floating as your team shape changes, and cap the annual uplift so the saving does not erode. When you are ready to run it with us, the commercial hub is the TOPdesk platform page and the engagement runs through our contract negotiation service on fixed fee or gainshare.

One proof point, plainly stated

Across 500+ ITSM engagements and $420M+ of contract value since 2019, our average outcome is a 30% reduction. On TOPdesk, right-sizing operators and re-fitting the named-and-floating mix is usually the single largest contributor.

Frequently asked questions

How do you right-size TOPdesk operator counts?
Pull login and activity data, remove dormant operators, reclassify requesters, then re-split the base into named seats for full-time staff and a floating pool sized to peak concurrency. The reconciled count becomes your renewal baseline.
How many TOPdesk operators do you actually need?
Fewer than the entitlement, almost always. The honest number is the people who actively work the desk, split by how many are logged in at once. It varies by team shape, so measure it from login data; the gap is the saving.
When should you right-size before a renewal?
Three to six months out, so the reconciled count is ready before TOPdesk sets a baseline off your entitlement. Right-sizing after the quote means negotiating down from an inflated number instead of up from the truth.

Book a contract negotiation review.

We reconcile your operators against login data, re-fit the license mix and take the corrected count into the renewal. Fixed fee or gainshare, no savings no fee.

Book a contract negotiation review →

The ITSM Negotiation Brief

Vendor moves, benchmark data, and renewal alerts for ITSM buyers.

ITSM Negotiations

Independent, buyer-side ITSM contract negotiation. Fixed fee or gainshare. Not affiliated with any ITSM vendor.

Services
NegotiationRenewal AdvisoryOptimization
Platforms
ServiceNowTOPdeskIvanti
Company
AboutContactJournal
Independent. Not affiliated with ServiceNow, BMC, Atlassian, TOPdesk, or any ITSM vendor.Privacy · Terms · Disclaimer · Editorial Standards · Newsletter · Glossary · Est. 2019