Start with the unit, because the savings live there. In BMC Helix the human license is the fulfiller, a person who resolves work, and it is the priciest seat in the agreement. The trouble is that fulfiller lists grow by accretion and shrink only by deliberate effort, so over a couple of renewal cycles they fill with people who left, accounts nobody uses, and occasional approvers who never needed a full license. Every one of those is a seat you pay for and do not use. This article sits under our BMC Helix pricing guide for 2026, and for how the fulfiller meter fits the wider agreement see BMC Helix licensing models explained.
Fulfiller versus request user
The distinction that decides the bill is fulfiller versus request user. A fulfiller resolves work: agents, technicians, problem managers, change approvers acting on records. A request user only submits and views requests, and is typically unlimited or counted at a far lower rate. The expensive mistake is licensing people as fulfillers when their actual behaviour is that of a request user. An executive who approves a change twice a quarter does not need a full fulfiller seat; an analyst who reads dashboards but never touches a ticket does not either. Sorting the list on real behaviour is the heart of right-sizing.
The reconciliation, step by step
The work is methodical rather than clever. Pull the current fulfiller list and the platform's own activity data, then work through four passes.
| Pass | What you look for | Action |
|---|---|---|
| Leavers | Accounts for people who have left | Remove; they should never bill |
| Dormant | No resolver activity over a defined window | Challenge and reclaim |
| Misclassified | Occasional approvers and read-only users | Reclassify as request users |
| Duplicates | One person, multiple accounts | Consolidate to one seat |
Define dormancy before you start, for example no work resolved in ninety days, so the conversation about each account is grounded in a rule rather than an opinion. The cleaned list that survives all four passes is your genuine resolver count, and it is almost always materially smaller than the list the vendor quotes from.
Negotiate against the cleaned number
The sequence matters as much as the cleanup. Reconcile first, then negotiate, never the other way round. A buyer who negotiates a rate on the inflated list has won a discount on seats they should not be buying at all. A buyer who cleans the list first negotiates both a smaller quantity and, with benchmark evidence, a better rate on what remains. That order is the difference between a cosmetic discount and a real reduction, and it is the same discipline we apply across platforms in the complete guide to ITSM license optimization.
Our gated BMC Helix Buyer Guide includes the fulfiller reconciliation worksheet and the dormancy rules we apply before a Helix renewal.
Holding the count down after the renewal
A cleaned list drifts back up unless there is a process to keep it clean. Tie fulfiller provisioning to a joiner-mover-leaver workflow so accounts deactivate when people leave, review dormancy on a fixed cadence rather than only at renewal, and require a justification when someone is provisioned as a fulfiller rather than a request user. None of this is heavy governance; it is a few checkpoints that stop the list from silently refilling. Without them, the next renewal inherits the same inflation you just removed, and the saving is one-off rather than durable.
The protection also belongs in the contract. Where you can, hold the fulfiller rate with a cap so growth in genuine resolvers does not arrive at a higher unit price, and keep the right to true down at defined points rather than only true up. The mechanics of writing that in sit in how to negotiate a BMC Helix renewal.
The data you need, and where it lives
Right-sizing is only as good as the data behind it, so it helps to know which sources to pull before you start. The fulfiller roster itself comes from the platform's license administration view, which lists every named seat. Last-login and last-resolved-activity data, the evidence that separates active resolvers from dormant accounts, comes from the platform's own audit and reporting. The joiner-mover-leaver feed from HR or identity management tells you who has actually left, which is the fastest source of seats to reclaim. Cross-referencing these three is what turns an argument about individuals into a defensible, rule-based list.
Expect some friction on the reclassification cases, because a person being moved from fulfiller to request user occasionally protests. Pre-empt it by framing the change around behaviour, not status: the question is whether the person resolves work or only submits and reads it. Bring the activity data to that conversation so it is grounded in what the account actually did over the review window rather than in how someone perceives their role. Handled this way, the reclassification is a routine hygiene step rather than a political one, and it holds up when the vendor asks you to justify the reduced count at renewal.
One practical caution: run the reconciliation against a representative window, not a quiet month. A holiday period or a seasonal lull can make active resolvers look dormant, so anchor the review to a normal operating stretch and, where roles are genuinely seasonal, note that and keep the seat. The aim is an accurate count you can defend, not the smallest possible number, because a reduction the vendor can puncture by pointing to one wrongly cut resolver costs you credibility on the rest of the list.
Where this fits with our service
We reconcile the fulfiller list, reclassify what should be request users and negotiate against the cleaned count, from the platform hub at BMC Helix through our license optimization service, on fixed fee or gainshare with no fee unless we save you money. Across more than 500 engagements and over 420 million dollars of ITSM contract value negotiated, the average reduction is 30 percent, and on the human meter the cleanup is often where it starts.
Frequently asked questions
- How do I right-size BMC Helix agent counts?
- Pull the fulfiller list and reconcile it against real activity: remove leavers and dormant accounts, reclassify occasional approvers as request users, and consolidate duplicates. Negotiate the renewal against the cleaned resolver count.
- What is the difference between a fulfiller and a request user?
- A fulfiller resolves work and is the human meter you pay for. A request user only submits and views requests and is typically unlimited or charged far less. Many estates pay fulfiller prices for request-user behaviour.
- How much can right-sizing save?
- It depends on accumulated slack, but the fulfiller line is usually the largest human cost, so cleaning it is often the fastest reduction. Removing dormant seats and reclassifying occasional users can take a double-digit percentage off before any rate negotiation.
Book a BMC Helix review.
We reconcile the fulfiller list and negotiate against the real count. Fixed fee or gainshare.
Book a BMC Helix review →