HaloITSM is priced per agent, and the per-agent rate steps down as the agent count rises, so the volume break you land in is as important as the count itself. A team sitting just below a break can sometimes pay less by rounding up to the next tier, while a team that over-bought to reach a break is paying for agents it never uses. Knowing where the thresholds fall, and asking for the next tier's rate even when you are slightly under it, is one of the most reliable savings on a HaloITSM deal. This article explains how the rate and the breaks work. It sits under our HaloITSM pricing guide.
How the per-agent rate is set
The per-agent price is not a single published figure that applies to everyone. It is a rate that depends on the number of agents licensed, the licensing model chosen, the term committed, and the discount negotiated. The volume relationship is the structural part: more agents, lower unit rate. That is standard for seat-based software, but on HaloITSM it carries extra weight because the agent line is effectively the whole bill, with the full product included. There are no module lines to spread cost across, so the agent rate and count are where almost all the money is.
Why the volume break is a negotiating lever
Volume breaks create thresholds, and thresholds create opportunities. If your active fulfiller count sits a handful of agents below a break, the marginal agents to reach it may cost little, while the lower rate applies to the whole population, so the total can fall even as the count rises. Conversely, if a previous purchase rounded the count up to clear a break and the extra agents were never used, you are carrying licences purely to hold a rate, which is rarely the cheapest outcome once you model it. The lever is to map your real count against the break points and negotiate from there.
Map your count to the breaks before you negotiate
The preparation is straightforward and it is where the leverage comes from. Establish the active fulfiller count, not the provisioned seat total, using the method in how to right-size HaloITSM agent counts. Then position that count against the rate tiers and identify which side of the nearest threshold you sit on. A count that is genuinely growing toward a break is an argument for the better rate now; a count that was inflated to reach one is an argument to drop agents and re-rate. Either way, you negotiate from a real number rather than the vendor's assumption.
| Situation | The play |
|---|---|
| Just below a volume break | Ask for the next tier's rate without buying up to it |
| Growing toward a break | Negotiate the better rate now against the forecast count |
| Over-bought past a break | Drop unused agents and re-rate to true usage |
| Stable, well inside a tier | Focus leverage on the renewal cap and term instead |
Named and concurrent change the count that matters
The volume break applies to the number of licences, so the choice between named and concurrent licensing directly affects which break you land in. A shift-based team that switches from named seats to concurrent can need materially fewer licences, which may move it into a different tier or simply lower the bill at the same rate. Getting the licensing model right is therefore a prerequisite to the volume conversation, not a separate one. The trade-off is set out in the pricing pillar and the right-sizing guide.
Hold the rate across the term
A keen per-agent rate is only worth what it is worth at renewal. If the rate is negotiated for year one but the agreement allows an open uplift, the volume break you fought for erodes. Lock the negotiated rate, or a capped uplift on it, across a multi-year term so the break holds. That is the subject of HaloITSM price protection and multi-year deals, and the broader saving discipline is in the complete guide to ITSM license optimization.
The gated HaloITSM Buyer Guide includes the volume-break math and the rate asks we make at each threshold.
The bottom line on per-agent pricing
On HaloITSM, the agent rate and count are the whole game, and the volume break is the lever inside it. Establish the active fulfiller count, map it to the thresholds, ask for the next tier's rate, and lock it across the term. We run that analysis for clients through our license optimization service and against the HaloITSM platform, on fixed fee or gainshare.
Frequently asked questions
- How does HaloITSM per-agent pricing work?
- HaloITSM licenses agents at a per-agent rate that steps down as the agent count rises, with the full product included for every agent. The rate also depends on the licensing model, the term and the negotiated discount, but volume is the structural driver.
- Can I get a better HaloITSM rate without buying more agents?
- Often yes. If you sit just below a volume break, vendors will frequently grant the next tier's unit rate to win or hold the deal without requiring you to buy up to the threshold. The lever is to map your real count to the breaks and ask.
- Does named versus concurrent affect the volume break?
- Yes. The break applies to the number of licences, so switching a shift-based team from named to concurrent can reduce the licence count and move you into a different, cheaper tier. Settle the licensing model before negotiating the volume rate.
Book a HaloITSM review.
We map your agent count to the volume breaks and negotiate the rate. Fixed fee or gainshare.
Book a HaloITSM review →