Quick version: the specialist license is the cost driver, the basic user is not, so the money is in the split between them. Most estates carry specialists who only raise or approve requests, which means they should be basic users, and reclassifying them removes a paid seat without removing access. Get the mix right and the rest of the Xurrent bill follows. For the full pricing picture, start with the Xurrent pricing guide for 2026.
Book a contract negotiation review →What is a Xurrent specialist?
A specialist is a member of staff who works the service management process inside Xurrent, formerly 4me. They pick up requests and tasks, update and resolve them, manage problems and changes, and use the full functionality of the platform. Each specialist consumes a paid license, and the specialist count is the primary number the contract is priced on. If someone resolves tickets, manages a queue, or owns process steps, they are a specialist and the seat is justified.
Your move: define "specialist work" for your estate in one sentence, owning or resolving process items, then hold every paid seat against it.
What is a Xurrent basic user?
A basic user is everyone else, the wider population who interact with the service desk without working the process. They submit requests, track their own tickets, and approve items routed to them, using a much lighter set of functions. Basic users are licensed at a far lower cost than specialists, and in many deals are effectively the broad employee base served by the few specialists. The distinction matters because a basic user misclassified as a specialist is pure overspend, repeated every year.
| Capability | Specialist | Basic user |
|---|---|---|
| Submit and track own requests | Yes | Yes |
| Approve requests routed to them | Yes | Yes |
| Pick up, work, and resolve tickets | Yes | No |
| Manage problems, changes, and tasks | Yes | No |
| Full process functionality | Yes | No |
| Cost | Paid specialist license (the cost driver) | Far lower cost or included |
Your move: run your user list against this table. Anyone whose real activity sits only in the top two rows is a basic user, not a specialist.
Who actually needs a specialist license?
Only the people who work the process. The common pattern across estates is a specialist count inflated by three groups: managers and approvers who only sign off requests, occasional contributors who were given full access for a project and kept it, and leavers whose seats were never reclaimed. Each of these is a paid specialist who does basic user work, and each is a saving once reclassified or removed. Sometimes a borderline user genuinely needs specialist functionality occasionally, and that is a real judgment call, but most of the inflation is clear once you look at activity rather than job title.
Your move: pull specialist activity for the last three to six months and flag anyone with no process work in that window for reclassification.
How do you right-size the specialist-to-basic mix?
- Export the specialist list with activity data. You need who holds a specialist license and when they last worked a process item, not just the headcount.
- Reclassify the request-and-approve crowd. Move anyone who only raises or approves to basic user. They keep their access and stop consuming a paid specialist seat.
- Reclaim leavers and stale seats. Remove specialists who have left or changed role, the cleanest saving of all.
- Time-box temporary specialists. Put an end date on project and contractor seats so they cannot drift into the next renewal.
- Lock the corrected mix before renewal. Present the reconciled specialist count as the baseline and get it written into the order, not promised on a call. The method generalizes in the license optimization field guide.
Your move: finish the reclassification before the renewal quote is built, so the corrected mix is your starting point rather than a discount you have to argue for. The wider buyer-side sequence is in how to negotiate a Xurrent renewal.
Our gated ITSM License Optimization Field Guide includes the specialist-versus-basic reconciliation worksheet behind this method.
Where the licensing mix fits the negotiation
The specialist count is the number the Xurrent contract is priced on, so right-sizing the mix is the foundation every other ask sits on. We run the reconciliation inside the full negotiation rather than as a standalone cleanup, because the corrected count is also the evidence that anchors the price. When you are ready to act, the engagement runs through our contract negotiation service on fixed fee or gainshare. Across 500+ ITSM engagements the firm averages a 30 percent reduction, and the specialist-to-basic split is usually the first and cleanest contributor on this platform.
Frequently asked questions
- What is the difference between a specialist and a basic user?
- A specialist works the process, resolving tickets and managing tasks, and consumes the paid license. A basic user only raises, tracks, and approves their own requests at a far lower cost. The cost decision is keeping paid specialists to genuine specialist work.
- How is Xurrent licensed?
- Primarily by specialist user, with basic users covering the wider request-and-approve population. Pricing is quote-based and varies by specialist count, term, and scope, so confirm the rate on your order form.
- How do you reduce Xurrent licensing cost?
- Reconcile specialists against real process activity, move request-and-approve users to basic, remove inactive seats, and lock the corrected mix before renewal.
Right-size the specialist mix.
We reconcile specialists against real work, reclassify basic users, and lock the count before you sign. Fixed fee or gainshare.
Book a contract negotiation review →