Most CRM buyers assume licensing is simple: you pay per person who uses the system. In practice, “per person” can mean three meaningfully different things depending on the vendor, and the distinction matters both for cost and for how your contract behaves as your team’s usage patterns change.

Named User Licensing

A named user license is assigned to a specific individual, by name or account, and that license stays reserved for them regardless of how often they actually log in. If Sarah has a named user license, that seat belongs to Sarah until someone with administrative access reassigns it — whether Sarah uses the system daily or once a month.

Why vendors favor this model: It’s simple to administer and predictable to bill, since the number of licenses directly maps to a headcount number that’s easy to track.

Where it costs you: You pay for every assigned seat regardless of actual usage. A named user license sitting unused because someone changed roles, went on leave, or simply doesn’t need daily access is still a full-price line item until someone actively reassigns or removes it.

Concurrent Licensing

A concurrent license is shared across a pool of users, but only a limited number of people can be actively logged in and using the system at the same time. If you have 20 concurrent licenses and 50 total potential users, up to 20 people can use the system simultaneously — the 21st person attempting to log in either waits or is blocked, depending on how the vendor implements the limit.

Why this model exists: It suits situations where not everyone needs access at the same time — shift-based teams, or roles where CRM access is occasional rather than constant.

Where it gets complicated: Predicting your actual peak concurrent usage is harder than predicting headcount, and underestimating it means people get locked out during your busiest periods — exactly when CRM access matters most.

Usage-Based Licensing

Rather than tying cost to a number of people, usage-based licensing scales with actual activity — API calls, records created, automation runs, or similar usage metrics. This model is less common for core CRM seats but increasingly common for add-on features like marketing automation or AI-driven capabilities layered on top of a CRM.

Why vendors use this model: It aligns cost more directly with the value delivered, particularly for features where usage varies enormously between customers of similar size.

Where it creates risk: Usage-based pricing makes monthly costs less predictable, and a usage spike — a marketing campaign, a data import, a busy sales period — can produce a cost spike that’s hard to anticipate without close monitoring.

Comparing the Three Models

Factor	Named User	Concurrent	Usage-Based
Cost predictability	High	Moderate	Lower
Best for	Teams where most people need daily access	Teams with partial, rotating access needs	Features with highly variable usage
Administrative overhead	Requires active seat management	Requires monitoring peak usage	Requires usage monitoring and alerts
Risk of overpaying	Unused assigned seats	Underestimated peak concurrency	Unexpected usage spikes

A Hybrid Reality

Many CRM platforms don’t use a single pure model — the core CRM seats might be named user, while a marketing automation add-on layered on top is usage-based by contact volume or email sends. Understanding which parts of your contract follow which model matters for budgeting, since a single “per user” mental model applied across a hybrid contract will miss real cost drivers hiding in the usage-based components.

What to Ask a Vendor About Their Licensing Model

Before signing, get explicit answers to: Which licensing model applies to which part of the platform? If named user, how easily can seats be reassigned when someone leaves or changes roles? If concurrent, what happens when the limit is hit — a queue, a block, or an automatic upgrade prompt? If usage-based, what are the specific metrics that drive cost, and is there a way to set spending alerts before an unexpected spike becomes an unexpected bill?

Frequently Asked Questions

Which licensing model is generally cheapest? It depends entirely on your usage pattern, not on the model itself. A team where everyone logs in daily will usually find named user licensing straightforward and fairly priced. A team with significant part-time or rotating access needs may find concurrent licensing meaningfully cheaper for the same functional access. There’s no universally cheaper model — only a better or worse fit for your specific usage pattern.

Can we switch licensing models with the same vendor later? Sometimes, though it typically requires a conversation at renewal rather than a mid-contract change, and not every vendor offers more than one model to switch between in the first place. Ask about this explicitly if you’re unsure your initial usage pattern assumption will hold.

Is usage-based licensing becoming more common for core CRM functionality, not just add-ons? It’s a developing trend, particularly as AI-driven features (which have variable underlying compute costs) become more embedded in CRM platforms. Core contact and deal management remains predominantly named-user or flat-rate priced as of this writing, but it’s worth checking whether any given vendor’s roadmap signals a shift, especially for AI-related capabilities.

How do we know if we have more named user licenses than we actually need? Pull a usage report showing login frequency by seat, if your vendor provides one, and look for seats with little to no recent activity. This is also the starting point for a broader license audit, which is worth doing on a regular schedule rather than only when costs feel high.

Does the licensing model affect how easy it is to switch CRM vendors later? Indirectly, yes. Named user licensing tends to make your actual usage patterns easy to document and carry into a negotiation with a new vendor, since you have a clear historical record of how many people genuinely needed access. Usage-based licensing can make this comparison harder, since the underlying usage metrics (API calls, automation runs) often aren’t directly comparable across platforms that measure things differently — worth keeping in mind if switching vendors is a realistic possibility within your planning horizon.

Next Step

Identify which licensing model applies to each component of your CRM contract — not just the headline seat price — and match that understanding against your team’s actual access patterns before your next renewal conversation.