How to Right-Size Ivanti Analyst Counts

The fastest saving on most Ivanti contracts is the analyst seat you stopped using but never removed. To right-size Ivanti analyst counts, pull a login report for the last 90 days, separate the people who actually work the queue from the dormant and duplicate accounts, switch shift-based teams to concurrent licensing, and reset the entitlement to that real number at renewal. Because Ivanti bills by the analyst, every seat you cut comes straight off the recurring cost, which is why this is the first number we check. It sits under the Ivanti Neurons pricing guide.

Why analyst counts drift upward

Analyst entitlements grow for reasons that have nothing to do with current need. A reorganization adds a team and the seats are provisioned but never deprovisioned when people move on. A project spins up temporary analysts who keep their licenses afterward. Departed staff leave accounts behind that no one disables. Over three years, the gap between licensed seats and working fulfillers widens quietly, and the renewal simply carries the inflated number forward because nobody questioned it. The drift is the default; right-sizing is the deliberate correction.

Step 1: pull the usage data

Start with evidence, not opinion. Export a login and activity report from Neurons for the last 90 days and, ideally, the last twelve months to catch seasonal patterns. You are looking for three populations: active analysts who log in and work tickets regularly, occasional users who touch the system rarely, and dormant accounts that have not logged in at all. The dormant set is your immediate reclaim; the occasional set is the one to investigate, because some are legitimate part-time fulfillers and others are seats that should be released.

Step 2: separate named from concurrent need

The biggest structural win is often the licensing model rather than the raw count. If your service desk runs in shifts or follow-the-sun, you may be paying for named seats when concurrent would cost far less, because concurrent counts only the analysts logged in at once rather than the total roster. A 60-person desk that never has more than 25 working simultaneously is a clear candidate. Map your peak concurrency from the usage report and compare it to your named-seat count; the gap is the saving. The mechanics of the two models are explained in Ivanti Neurons for ITSM licensing explained.

Step 3: reconcile against entitlement

Now compare the real, right-sized number to what you are entitled to and paying for. The difference is your reclaim target. Be careful here: if usage has grown past entitlement, you want to find that before the vendor does, because an unmanaged overage can become a true-up charge at renewal. Reconciling in both directions, releasing the seats you do not need and surfacing any overage on your own terms, is what keeps the renewal from holding a surprise. This is the same reconciliation discipline behind Ivanti discovery and asset licensing, where device and node counts drift in the same way.

A worked example

Consider a desk licensed for 80 named Ivanti analyst seats. The 90-day report shows 58 accounts logging in and working tickets regularly, 9 occasional users, and 13 that have not logged in at all. Of the 9 occasional users, investigation finds 4 are genuine part-time fulfillers and 5 are seats left behind by a reorganization. That is 13 dormant plus 5 stranded, 18 seats with no working owner, before the model question is even asked. Then concurrency: the desk runs across three shifts, and peak simultaneous logins never exceed 34. A move from 80 named seats to a right-sized concurrent pool sized for peak, with headroom, is a far smaller number than the 80 on the order form. Neither figure required guesswork; both came straight from the usage data. The point of the example is not the specific counts, which vary by organization, but the method: every reduction is evidenced, so it survives the vendor's pushback at renewal rather than collapsing into a negotiation of opinions. In our experience the recovered seats divide roughly into thirds: accounts for people who have left, seats provisioned for projects that ended, and capacity bought against a forecast that never materialized. Naming which third each seat falls into is what makes the reduction easy for the vendor to accept, because the story behind every released seat is concrete rather than a blanket demand for fewer licenses.

Step 4: lock the right number at renewal

A right-sized count only saves money if it makes it into the contract. Bring the documented number to the renewal, reset the entitlement to it, and switch the licensing model where concurrent wins. Resist the common vendor move of holding the old seat count as a floor; your usage data is the answer to that. The wider discipline of cutting entitlement to real need across every vendor is covered in the complete guide to ITSM license optimization.

How we right-size Ivanti seats

We pull the usage data, classify every account, model named against concurrent, and reset the entitlement to the real number at renewal, through our license optimization service and against the Ivanti platform page, on fixed fee or gainshare. Across 500 engagements and a 30 percent average reduction, the analyst count is the single most reliable place we find Ivanti savings, because the seat roster almost always outlives the team it was provisioned for.

Frequently asked questions

How do I know how many Ivanti analyst seats I actually need?

Pull a 90-day login and activity report from Neurons, then count the analysts who regularly log in and work tickets. Dormant and duplicate accounts are immediate reclaims; occasional users need investigation. For shift-based desks, also measure peak concurrency, which is usually well below the named-seat count.

Will Ivanti let me reduce analyst seats at renewal?

Yes, but they will often hold the current count as a floor unless you bring evidence. A documented usage report showing dormant seats and real concurrency is what justifies the reduction and counters the vendor's instinct to carry the inflated number forward.

Is concurrent licensing always cheaper for Ivanti?

Not always. Concurrent wins when your desk runs in shifts and peak simultaneous use is well below total headcount. For a desk where most analysts are online at the same time, named seats can be equivalent or better. Model both against your usage data before deciding.