Named Users vs. Concurrent Users: Pricing Out an ERP License

Most ERP vendors offer at least one of two licensing models: named-user, where every individual who might ever log in needs their own paid seat, and concurrent-user (sometimes called "floating"), where you pay for the maximum number of people using the system at the same instant, regardless of how many total employees have access. Picking the wrong one for your usage pattern can cost tens of thousands of dollars over a contract term.

The company: 90 people who could need access

A distribution company has 90 employees across warehouse, sales, customer service, and finance who might need to log into the ERP system at some point — checking an order, updating a customer record, running a report. Not all 90 are in the system constantly; a warehouse supervisor might log in for ten minutes a shift, while an order-entry clerk is in it all day.

Option A: named-user licensing

Every one of the 90 people gets a named seat, whether they use it for eight hours a day or eight minutes. At $68 per user per month over a 24-month term with a $15,000 setup fee:

Monthly cost: 90 × $68 = $6,120
Subscription cost over 24 months: $6,120 × 24 = $146,880
Total cost: $146,880 + $15,000 setup = $161,880

Option B: concurrent-user licensing

The company's own usage logs from its current system show that no more than about 40 people are ever logged in at the same instant — the 90 potential users' access is spread across shifts and roles, so peak simultaneous usage is well under the total headcount. Concurrent licensing is priced higher per seat ($110/month, reflecting the shared-pool value) but you need far fewer seats:

Monthly cost: 40 × $110 = $4,400
Subscription cost over 24 months: $4,400 × 24 = $105,600
Total cost: $105,600 + $15,000 setup = $120,600

For this company, concurrent licensing saves $41,280 over the two-year term — roughly a 26% reduction — because usage is genuinely spread out and peak concurrency is well below total headcount. Run your own scenario in the license cost calculator once you have a real per-seat price and user count from a vendor quote.

When named-user licensing is actually the better deal

The result flips for companies where usage is concentrated rather than spread out. If the same 90-person company ran two full shifts with almost everyone logged in simultaneously during working hours — a manufacturing floor where every operator clocks transactions constantly, for example — concurrent usage might run to 75-80 of the 90 potential users at peak, and at that point the higher per-seat concurrent price no longer buys you enough of a discount on seat count to beat named-user pricing. Named-user licensing also has an advantage that's easy to overlook: it's simpler to administer and audit, since access maps directly to a person rather than to a shared, contended pool.

How to find your real concurrency number before you negotiate

Don't guess at peak concurrent usage — pull it from your current system if you have one, or from a comparable proxy (a CRM, time-tracking system, or even VPN login logs) if you don't. Most systems can report "maximum concurrent sessions" over a trailing 30 or 90 days. If that number comes in well under 60-70% of your total user count, concurrent licensing is worth quoting seriously. If it's closer to 90%+ of headcount, don't bother — named-user pricing will usually win once you account for the concurrent model's premium per seat.

The negotiating point most buyers miss

Vendors will often quote named-user by default because it's simpler for them to forecast revenue. If your usage pattern favors concurrent licensing, ask for it explicitly and bring your own concurrency data to back up the request — a vendor is far more willing to structure a deal around real usage numbers than around a generic request to "make it cheaper."

A hybrid approach many vendors now offer

Increasingly, ERP vendors offer a third option that blends the two models: a base tier of named users for roles that need guaranteed, constant access (finance, core operations staff) combined with a smaller pool of concurrent/floating licenses for roles with intermittent access needs (occasional approvers, warehouse staff who log in briefly per shift, external accountants). For the 90-person distributor in this example, a hybrid model might license 35 people as named users (the core team who are in the system most of the day) and pool the remaining usage across 20 concurrent seats for the other 55 potential users, rather than choosing purely named or purely concurrent for the whole company. Ask vendors specifically whether hybrid licensing is available — it's often not advertised up front but is negotiable, especially for a company whose usage pattern doesn't fit neatly into either pure model.

The administrative cost difference that doesn't show up in the price sheet

Named-user licensing is simple to audit: a report of who has an account tells you exactly who's licensed and who isn't, and offboarding an employee is a one-step deactivation. Concurrent licensing requires more active management — someone needs to monitor peak usage over time (concurrency creeps up as a company grows, and a pool sized correctly at signing can become undersized eighteen months later without anyone noticing until users start getting locked out during peak hours), and diagnosing "why can't I log in" support tickets is genuinely harder when the answer might be "the shared pool is full" rather than "your account isn't active." Factor a modest amount of additional IT administrative overhead into a concurrent-licensing decision — it's real, even though it doesn't appear as a line item on the vendor's quote.

Revisiting the decision after year one

Whichever model you choose at signing, pull actual usage data after the first year and re-run the comparison. Usage patterns shift as a company grows, reorganizes, or changes how work is distributed across shifts — a concurrent-licensing decision that saved $41,280 at signing based on 40 peak concurrent users can erode or reverse if actual peak usage climbs toward 60 or 70 as the company adds headcount without adding proportional capacity to the concurrent pool. Most ERP contracts have an annual renewal or true-up point; use it to make sure the licensing model you chose still fits the company you've become, not just the company you were at signing.

Frequently asked questions

Can we switch from named to concurrent licensing (or back) after signing?

Most vendors allow this at a renewal or contract amendment point, though some charge a fee or require a minimum commitment period first. Ask about the switching process and any associated cost before signing, especially if you're uncertain which model fits and want the flexibility to correct course after seeing real usage data.

Does concurrent licensing risk locking users out during peak periods?

Yes, if the pool is undersized for actual peak demand — this is the main operational risk of the model. Size the concurrent pool with a buffer above your measured peak (10-15% headroom is a reasonable starting point) rather than exactly at peak, since usage naturally fluctuates day to day.

Is one model easier to budget for than the other?

Named-user licensing is more predictable — cost moves in lockstep with headcount changes you already know about. Concurrent licensing cost is stable as long as usage patterns don't shift, but a change in shift structure, a new department going live on the system, or simply organic growth can push peak concurrency higher without a corresponding, obvious trigger — budget a review of actual usage at least annually if you choose this model.