Most people managing SaaS tools encounter the same handful of licensing structures repeatedly across different vendors, often without a clear mental model for how they actually differ. Understanding the three dominant types — named user, concurrent, and site licenses — makes every future SaaS contract easier to evaluate correctly.

Named User Licensing

A named user license is tied to a specific individual, typically by email address or user account, and remains assigned to that person regardless of how frequently they actually log in. This is the most common SaaS licensing model, prized by vendors for its simplicity and predictable billing tied directly to a headcount number.

The trade-off: You pay for every assigned license whether or not that person uses the software regularly. A named user license sitting dormant because someone changed roles or is on leave still counts as a full-price seat until someone actively reassigns or removes it.

Concurrent Licensing

A concurrent license is shared across a pool of potential users, with a cap on how many can be actively using the software at the same time. If you have 15 concurrent licenses among 40 potential users, up to 15 people can be logged in simultaneously, with others needing to wait or being blocked once that limit is reached.

Where this fits: Software used occasionally or in shifts by a larger pool of people, rather than something everyone needs constant access to simultaneously — common for specialized tools used by a subset of a larger team at different times.

The trade-off: Predicting your actual peak concurrent usage is harder than predicting headcount, and underestimating it means people get locked out exactly when demand is highest.

Site Licenses

A site license covers an entire organization, location, or defined group, typically for a flat fee regardless of the exact number of individual users, as long as usage stays within the defined scope (an office location, an entire company, a specific department).

Where this fits: Software with very broad, hard-to-individually-count usage across an organization, where per-user tracking would be impractical or where the vendor prefers simplified, predictable billing at scale.

The trade-off: Site licenses typically carry a higher flat cost that’s only cost-effective once usage is broad enough to justify it — for a smaller or narrower usage scope, a per-user model often works out cheaper.

A Comparison Table

Factor	Named User	Concurrent	Site License
Unit of billing	Per assigned individual	Per simultaneous active user slot	Per site/organization, flat
Best for	Consistent individual daily users	Occasional or shift-based shared use	Broad, hard-to-count usage
Cost predictability	High	Moderate	High, but at a higher baseline
Risk of overpaying	Unused assigned licenses	Underestimated peak concurrency	Paying flat regardless of actual scope used
Administrative overhead	Moderate — requires active reassignment	Higher — requires usage monitoring	Low — simple scope-based tracking

How to Identify Which Model a Specific Tool Uses

Check the vendor’s pricing page language carefully — “per user” or “per seat” typically signals named user licensing; “concurrent users” or “simultaneous sessions” signals concurrent licensing; “site license” or “organization-wide” signals a site license. When genuinely unclear, ask the vendor directly before assuming, since the financial implications of each model differ significantly at scale.

Frequently Asked Questions

Can a single vendor offer more than one licensing model across different products or tiers? Yes, commonly — a vendor might offer named user licensing for its core product and a site license option for larger enterprise customers, or concurrent licensing specifically for less frequently used premium features layered on top of a base named-user product.

Which model is generally the cheapest? It depends entirely on your actual usage pattern, not the model itself — there’s no universally cheapest structure. A team where everyone logs in constantly typically does fine with named user licensing; a larger pool of occasional users often does better with concurrent licensing; very broad, hard-to-count usage often favors a site license.

Is it common to negotiate which licensing model applies, rather than accepting the vendor’s default? For larger deals, yes — vendors sometimes have flexibility to offer an alternative licensing structure for a significant enough customer, particularly if your usage pattern doesn’t fit their default model well. It’s worth asking directly during larger negotiations.

How does licensing model choice affect compliance risk? Each model carries its own compliance risk profile — named user licensing risks exceeding your contracted seat count as headcount grows; concurrent licensing risks exceeding your contracted simultaneous-user cap during peak periods; site licenses risk exceeding the contracted scope (using it beyond the defined site or organization boundary).

Does licensing model affect how easy it is to audit your own usage? Named user licensing is generally easiest to audit, since it maps directly to identifiable individual accounts. Concurrent licensing requires monitoring peak usage patterns over time, which is somewhat more complex. Site licenses are often the simplest to audit since they don’t require per-user tracking at all, within the defined scope.

Why This Foundational Understanding Matters Beyond Any Single Purchase

Once you understand these three models clearly, every future SaaS pricing page becomes faster to evaluate — you’ll recognize immediately which model a vendor is using and what questions to ask about it, rather than treating each new vendor’s pricing structure as a fresh puzzle to decode from scratch. This foundational literacy pays dividends across every software purchase decision your organization makes going forward, not just the one currently in front of you.

Next Step

Identify the licensing model for your three or four most significant SaaS tools, confirm your actual usage pattern genuinely matches what each model is billing you for, and flag anything that seems like a mismatch worth revisiting at your next renewal conversation. and confirm your actual usage pattern genuinely matches what each model is billing you for — a mismatch between usage pattern and licensing model is a common, easily corrected source of SaaS overspend.