A buyer renewing SysAid was braced for a fight over admin seats and barely glanced at the asset line. That was the mistake. Their admin count had been stable for two years; the asset count had nearly doubled as the agent rolled out across more endpoints, and the asset meter was where the renewal had grown. They had prepared to defend the wrong number. Understanding which meter is moving is the whole game. For the full pricing picture, start with the SysAid pricing guide for 2026.
How does SysAid licensing actually work?
SysAid is typically sold on two axes. The first is the admin: a named user who works and administers tickets, the equivalent of an agent or technician elsewhere. The second is the asset: a managed device that SysAid discovers, inventories and tracks. Both appear on the quote, both carry a per-unit price, and the total is the sum of the two meters plus any add-ons.
The reason this matters is that the two scale independently. Your admin count is a function of how many people staff the service desk, which you control directly. Your asset count is a function of how widely you deploy discovery, which tends to grow on its own as the estate expands. A buyer who negotiates the admin price hard but leaves the asset meter unexamined can still see the bill climb every year. Exact per-unit figures vary by deal size and edition, so confirm both against your own order form.
What is the difference between the admin meter and the asset meter?
Different drivers, different levers. Here is the comparison side by side.
| Dimension | Admin-based | Asset-based |
|---|---|---|
| What it charges for | People who work tickets | Managed devices discovered |
| What makes it grow | Support team headcount | Discovery scope and estate size |
| The control lever | Right-size the admin list | Decide which device classes count |
| Common waste | Dormant and occasional admins | Devices managed but never acted on |
| Where it hides | Headcount-based provisioning | Auto-discovery with no cap |
On the admin side, the waste is the same pattern as every agent-based tool: seats provisioned to headcount rather than to who actually works tickets, plus dormant accounts nobody reclaimed. Reconciling the admin list against real activity is the cleanest admin-side saving, and the method is in how to right-size SysAid admin counts.
On the asset side, the waste is devices that are discovered and billed as managed assets but never actually acted on inside the service desk. A printer or a meeting-room device that is inventoried but never the subject of a ticket may not need to be a billed asset at all. The lever is to decide which device classes genuinely need management and to exclude the rest from the count.
We reconcile both meters and negotiate them as one deal through our contract negotiation service, on fixed fee or gainshare, so neither line grows unchecked.
Which model fits your estate?
It is rarely a choice between the two, because most SysAid deals carry both. The real question is which meter dominates your cost and therefore deserves the most negotiation attention. A people-heavy support operation with a modest device estate is admin-led, and the saving is in seat reconciliation. A lean desk managing a large, sprawling device estate is asset-led, and the saving is in the asset count and the per-unit cap. Diagnosing which you are is the first step, because it tells you where to spend your leverage.
The buyer-side discipline is to map both before the vendor sets a baseline off whichever number happens to be inflated. The cross-platform optimisation method behind this, applied to any seat-plus-asset model, is in our gated ITSM License Optimization Field Guide.
How do you cap the asset meter before it runs?
Three moves. First, agree the asset counting methodology in writing, so what counts as a billable managed asset is defined rather than left to whatever discovery finds. Second, exclude device classes that do not need active management in SysAid, keeping them out of the billed count. Third, cap the per-asset price so that estate growth is priced predictably rather than trued up at list each year. Together these convert an open-ended meter into a bounded one.
The same care applies to the admin line, where the lever is reconciliation rather than capping. Run both before the renewal so you arrive with a true entitlement on each meter, and fold the two into a single negotiation rather than letting the vendor price them separately. The renewal sequence that ties this together is in how to negotiate a SysAid renewal, and the protective contract language is in SysAid contract terms worth negotiating.
How do you keep both meters from drifting between renewals?
The admin and asset counts do not hold still, so the work is not finished at signature. Admins churn as the team changes, and dormant accounts accumulate quietly; assets multiply as discovery reaches further into the estate. A contract negotiated against a clean count in year one drifts back toward overspend by year three unless someone is watching both meters between cycles.
Set a quarterly reconciliation rhythm: reclaim leavers and reassign dormant admin seats, and review the asset count against the agreed counting method so newly discovered device classes that do not need management stay out of the billed total. Carry that evidence into the next renewal so you negotiate from a current, defensible position rather than rebuilding the case from scratch under time pressure. The estates that hold their savings are the ones that treat the two meters as something to manage continuously, not just at the table.
What to do next
Diagnose which meter dominates your SysAid cost, reconcile the admin list against real activity, audit the asset count and exclude device classes that do not need management, then cap the per-asset price and agree the counting method in writing. Negotiate the two meters as one deal. Across 500-plus ITSM engagements since 2019 we average a 30% reduction, and on SysAid the asset line is frequently where the unexamined growth, and the largest single cut, is found.
Book a contract negotiation review →Frequently asked questions
- How does SysAid licensing work?
- On two meters: admins, the named users who work tickets, and assets, the managed devices the platform discovers. The admin meter scales with your support team; the asset meter scales with your device estate. Both are negotiable but move on different curves.
- What is the difference between admin and asset-based pricing?
- Admin-based pricing charges for the people who operate the desk and is controlled by right-sizing the admin list. Asset-based pricing charges for managed devices and is controlled by deciding which device classes need to be billed assets.
- How do you reduce a SysAid bill?
- Reconcile the admin list and reclaim dormant seats, audit the asset count and exclude device classes that do not need management, cap the per-asset price, agree the counting method in writing, and negotiate both meters as one deal.
Negotiate both meters as one deal.
We diagnose which line is moving, reconcile the admins, cap the assets, and take both to the table together. Fixed fee or gainshare.
Book a contract negotiation review →