Blog
The vendor licenses identities, not sessions. The buyer side question is not which metric to pick but how tightly your named user count matches the people who truly need access.
The ServiceNow named user vs concurrent question comes up on almost every first renewal, and the short answer surprises most buyers: ServiceNow does not sell concurrent licenses for its core platform. It licenses by named user. A named user is a specific, identified person who is provisioned access, not a floating seat shared across a shift. If you arrived expecting to buy a pool of concurrent sessions and pay only for peak usage, the model works differently, and understanding that difference is the first step to controlling cost.
This matters because the two models price risk in opposite directions. A concurrent model lets a buyer cover a large population with a smaller seat count, paying for simultaneous use. A named user model charges for every provisioned identity whether that person logs in daily or twice a year. On the ServiceNow platform the named user model is the one you negotiate, so the lever is not session pooling, it is how tightly your named user counts match the people who genuinely need access.
ServiceNow built its commercial model around named users because the platform is a system of record, not a kiosk. Access is tied to identity, workflow, approvals, and audit trails, all of which assume a known person behind each action. That design choice flows straight into the contract. You commit to a quantity of named users by type, and the unit price is set against that quantity. There is no concurrent counter that throttles you at peak and frees seats overnight. For the broader picture of how the platform charges, our pillar on ServiceNow licensing sets out every license type and how they interact.
The practical consequence is that overprovisioning is invisible until you look for it. Every named user you created for a project that ended, every contractor who left, every duplicate account, is still a billable identity at the next true up. Concurrent buyers worry about peak load. Named user buyers should worry about dormant identities, because those are the seats quietly inflating the renewal.
The named user model splits into two populations that price very differently. Fulfillers are the people who do the work inside the platform, the agents, approvers, and administrators who create and resolve records. They carry the heavy unit cost. Requesters are the much larger population who raise tickets, seek approvals, and consume services, and they are licensed far more cheaply or covered under broad employee access. The single most expensive mistake in the named user vs concurrent debate is classifying a requester population as fulfillers, because the unit gap between the two is large and compounds across the whole estate.
When buyers ask us for a concurrent model, what they usually want is relief from paying full fulfiller price for occasional users. The answer is rarely a different licensing metric. It is correct classification: move genuinely light users to the requester tier, reserve fulfiller seats for the people who actually fulfill work, and stop paying agent economics for a population that only requests. Our ServiceNow license types explained guide walks through each role and where the boundaries sit.
Buyers who model a concurrent assumption tend to undercount, because they imagine paying only for people logged in at once. On a named user platform that produces a painful gap at renewal when the real identity count is reconciled. The reverse error is just as costly: buyers who give up on right sizing because they assume every provisioned account is fixed. Named user counts are not fixed. They are the most reducible line in the contract, because dormant and duplicate identities can be reclaimed before the count is locked.
The discipline that replaces concurrent pooling is usage based reclamation. Pull the last login data, flag every identity inactive for ninety days or more, confirm with the owning team, and deprovision before the true up. Buyers who run this pass routinely find that a meaningful share of their fulfiller seats are dormant, and reclaiming them resets the quantity the renewal is priced against. For the cost mechanics of those seats, see our work on ServiceNow user license cost.
Start twelve months out, not at the quote. Build a clean inventory of every named user by type, then reconcile it against active usage rather than the count your account team holds. Separate the population into genuine fulfillers, genuine requesters, and dormant identities. Reclaim the dormant, reclassify the mislabelled, and only then size the renewal commitment to the population that remains. The result is a quantity you can defend with data, which is the strongest position in any negotiation.
This is where the named user model becomes an advantage rather than a trap. Because you are charged per identity, every identity you remove is a direct, permanent saving, not a one off rebate. A typical enterprise reclamation pass surfaces single digit to low double digit percentage reductions in billable fulfiller seats, and that reduction carries through every future year and every uplift. Our buyer side ServiceNow license negotiation service builds this inventory with you and takes the right sized number to the table.
The named user vs concurrent comparison is less a choice than a clarification. ServiceNow licenses identities, so the path to lower cost is not finding a concurrent metric that does not exist on the platform. It is classifying every user correctly, reclaiming the dormant ones, and sizing the commitment to the people who truly need access. Do that work before the quote lands and the named user model stops being the reason your renewal grew and becomes the reason it shrank.
For its core platform ServiceNow licenses by named user, not concurrent sessions. A named user is a specific identified person provisioned with access, so there is no shared concurrent pool to size against peak usage.
Because every provisioned identity is billable whether or not the person logs in. Dormant accounts, departed contractors, and duplicates all count, so overprovisioning inflates the renewal until you reclaim those seats.
Reconcile your identities against real login data, reclassify light users from fulfiller to requester, and deprovision dormant accounts before the true up so the renewal is priced against a right sized count.
By the NowNegotiations Advisory Team. Independent advisors, buyer side in hundreds of enterprise software negotiations, with benchmark data from real enterprise renewals. Based on real enterprise renewal engagements. Last updated 2026-06-01.