What ITSM actually costs: the license price is the small number

Ask what ITSM software costs and you get a per-agent, per-month figure. It is the easiest number to find, the easiest to compare, and a minority of what you will actually spend.

This is the full cost structure, and the one metric that makes the comparison meaningful.

The pricing models, and what each one really charges for

Per agent. The most common model: you pay for the people working the desk. Published examples, as of August 2026, include Freshservice at $19, $49 or $99 depending on tier, and SysAid Professional at $89.

What per-agent pricing actually charges for is the size of your support team. A desk that resolves twice the work with the same headcount pays exactly the same, and a desk that grows because demand grew pays more. If your goal is to need fewer agents, the pricing model is indifferent to your success. Ask any vendor how the price changes if your ticket volume halves; the answer tells you whose interests the model serves.

Per employee. Common in products led by employee experience. Predictable, it scales with the company rather than the desk, and it can be more expensive at large headcounts with low support ratios.

Consumption, or metered AI. Increasingly common as a layer on top of seats. This model changes budgeting behavior, because it taxes adoption: the more successful the deployment, the higher the invoice. Usage-based pricing is spreading quickly as AI spending grows, and Gartner forecasts that worldwide spending on AI models and platforms will reach $64 billion in 2026, up 63.4% on 2025. If anything is metered, get the unit defined in writing, with a worked example at your expected volume.

Tiered enterprise agreements. Platform-level contracts where the unit price means little on its own. What matters is the entitlement schedule and the renewal escalator.

The lines that are not in the quote

For a midsize or enterprise deployment, these routinely add up to more than the subscription over three years.

Implementation. Configuration, workflow design, service catalog definition, forms and approval routing. Usually the largest first-year line after licensing.

Data migration. Proportional to how much history you insist on carrying, which is usually far more than anyone needs. Migrating three years of closed tickets is a common way to spend real money on data nobody will query.

Integration. Identity provider, HR system, endpoint management, monitoring, finance, and whatever internal system holds something important. Each integration is a build plus a permanent maintenance obligation.

Internal administration. The most consistently underestimated line. Someone has to own the workflows, the catalog, permissions and upgrades. At enterprise scale that is one to several full-time roles, and it appears in no vendor's cost calculator. Ask a reference customer of similar size rather than the vendor.

Training and change management. For the desk, and for employees, who need to know the service exists and works.

Knowledge upkeep. If you are deploying anything AI-driven, answer quality depends on your content staying accurate. That does not mean rewriting it before launch: current AI reads existing content well. It means an ongoing routine for finding contradictions, stale articles and unanswered questions, the routine our AI knowledge base piece describes. Budget for that routine, not for a one-time cleanup.

The renewal escalator. Check the uplift terms. A 7 percent annual increase compounds to more than a fifth over three years.

Exit cost. What it takes to leave: data export, knowledge portability and integration rebuilds. Rarely evaluated at purchase, which is exactly when your negotiating leverage is highest.

Why cost per ticket has stopped working

The traditional efficiency metric is total desk cost divided by ticket count. It made sense when every request became a ticket.

It breaks in a specific and misleading way once resolution is automated: requests resolved before a ticket is created disappear from the denominator. Automate the routine third of your volume and cost per ticket can rise sharply while total cost falls and every user outcome improves. The metric reports a regression.

The fix is to use cost per resolved request: the total cost of service delivery divided by every request resolved, whether or not it ever became a ticket. That single change makes the comparison fair, and it is the number to put in a business case. It also makes the pricing question concrete. Under per-agent pricing, cost per resolved request falls as automation grows. Under consumption pricing, it may not fall at all.

A three-year model worth building

Not a vendor's spreadsheet. A short one you control.

Model three years. For each year, include licenses at the agent or employee count you actually expect (not today's), implementation spread over the period, integration build and maintenance, internal administration headcount, training, knowledge upkeep, any metered AI consumption, and the renewal escalator. Ask each vendor for an itemized all-in first-year figure for your profile, and for what year two looks like, so the escalator and true-ups are visible.

Then divide by the requests you expect to resolve, including the ones you expect never to become tickets.

Run the model twice: once at flat volume, and once at the volume growth you actually expect. The second run is where pricing models separate.

Where the real savings are

License price is the number that gets compared and the one least worth optimizing. The difference between a $49 and a $99 per-agent tier is real, but it is smaller than the difference between an implementation that takes six weeks and one that takes nine months, and much smaller than the difference between a product that needs two full-time administrators and one that needs a quarter of a person.

How Rezolve.ai is priced against that model

We are a vendor in this market, so check our numbers the way you would check anyone's.

Rezolve.ai is priced per user rather than by AI consumption, so resolving more requests does not raise the bill, and cost per resolved request falls as automation grows. The savings in the model above come from Agentic Sidekick resolving routine requests outright, and a short implementation keeps the first-year line small. It can run as your service desk or alongside the ITSM system you already have, which keeps migration and exit costs low.

Reload preview

Evaluate on cost per resolved request over three years, with every line included. It is a harder number to produce, and it is the only one that answers the question you are actually asking.

Individual vendor breakdowns: ServiceNow · BMC Helix · Freshservice · SysAid · HaloITSM · ManageEngine · TeamDynamix