Back to Blog

    November 17, 2026

    Seat-Based Licensing: Named User vs Concurrent Licenses and How to Price Seats

    Pricing a white-label deal? Work out your margin with the profit calculator.

    Looking for SaaS to license? Browse live listings or explore products by category. New to the deal structures? Compare licence and white-label types or check a term in the glossary. Explore the white-label SaaS marketplace, software to license or license vs build. SaaS founder? List your Product for licensing.

    Quick answer: Seat-based licensing charges for the number of people (seats) allowed to use software. With a named user license, each seat belongs to one person; with a concurrent (floating) license, a pool of seats is shared and the limit is how many people use it at the same time. Named user seats suit teams where everyone uses the software daily; concurrent seats suit shift work and occasional users. Seats are simple to price and predict, but they fit poorly when value comes from usage or automation rather than headcount.

    Seat-based licensing is still the most common way business software is sold, and the first model most founders reach for. This guide explains the main seat license types, the named user vs concurrent decision, how to price seats, how seats work when you license or white-label your product to partners, and the license terms that keep a seat model fair for both sides.

    Key takeaways

    • A seat is permission for one person (named user) or one simultaneous session (concurrent) to use the software.
    • Named user licenses are simple and predictable; concurrent licenses need fewer seats when people use the software at different times.
    • Define "user" in the license, ban credential sharing and agree how seats are reassigned and counted.
    • In white-label and reseller deals, price seats wholesale so the partner keeps a margin at their own retail price.
    • AI agents and automation reduce headcount, so many vendors now combine seats with usage credits.

    What seat-based licensing means

    In seat-based licensing, the customer buys a number of seats, and each seat gives one user the right to use the software. Ten seats means ten users. The price usually scales in a straight line (price per seat times seats), often with volume discounts and an annual contract. Seat-based licensing is also called per-user or per-seat licensing, and it is one of the license types compared on our license types page.

    It became the default for business software because it is easy to understand on both sides: the buyer can predict the bill from their headcount, and the vendor's revenue grows as the customer's team grows. The catch is that seats measure people, not value. If a customer gets most of its value from automation, integrations or a handful of power users, a per-seat price can feel either too high or too low.

    Seat-based license types compared

    License typeWhat one license coversCounted byBest for
    Named userOne specific personPeople assigned a seatDaily users, stable teams
    ConcurrentOne session at a time, shared by a groupPeak simultaneous usersShift work, occasional users
    FloatingA shared seat checked out from a license serverSeats checked out at onceDesktop and engineering software
    Device (node-locked)One computer or deviceDevices activatedKiosks, shared terminals, on-premise installs
    Site or enterpriseEveryone at a site or companyA flat fee, sometimes with a capLarge customers that want no counting

    Named user vs concurrent licenses

    The key decision in any seat model is what a seat is tied to.

    Named user licenses

    A named user license is assigned to one person. That person can use the software at any time, from any approved device, and nobody else can use their seat. It is the model most SaaS products use, because the user is already identified by their login.

    • Pros: simple to count, simple to enforce, predictable revenue, and it fits products that people use every day.
    • Cons: customers pay for occasional users as if they were full-time, which pushes them to share logins or keep seats to a minimum.

    Concurrent licenses

    A concurrent license is a shared pool. Anyone in the customer's organisation can log in, as long as the number of people logged in at that moment is no more than the number of licenses bought. When the pool is full, the next person waits or is refused.

    • Pros: fair for shift work and part-time users, and customers can give access to more people without buying more seats.
    • Cons: you need to track sessions, handle idle timeouts and explain peak usage. Vendors usually charge more per concurrent seat than per named seat, because one concurrent seat serves several people.

    Illustrative example: a support team has 30 agents working in three shifts, and no more than 12 are ever logged in at once. Under a named user model they need 30 seats. Under a concurrent model they need about 12, plus a small buffer for shift handovers. Whether concurrent is cheaper depends on the price difference per seat, so compare the total, not the unit price.

    Floating, device and site licenses

    Three other seat-style models are worth knowing:

    • Floating licenses are concurrent licenses for installed software. The application checks a seat out from a license server when it opens and returns it when it closes. They are common in engineering, design and analytics tools.
    • Device or node-locked licenses tie the license to one machine rather than a person. They suit shared terminals, kiosks and on-premise installations.
    • Site and enterprise licenses cover everyone at a location or company for a flat fee, sometimes with a fair-use cap. Large customers like them because nobody has to count seats; vendors use them to land big accounts and agree a price review at renewal.

    Seat-based licensing vs other models

    Seats are one option among several. Usage-based licensing charges for consumption, such as API calls or tasks completed; revenue share ties your fee to the licensee's sales; and perpetual licenses charge once for ongoing use. SaaS license models explained compares perpetual, subscription and usage-based models in detail.

    A simple test: if your customer's value grows with the number of people using the product (collaboration, CRM, helpdesk), seats fit. If value grows with volume (messages sent, documents processed, AI tasks run), a usage or hybrid model fits better. Many products now combine both: a per-seat price that includes a usage allowance, with overage or credits above it.

    How to price seats

    • Start from value per user. Estimate what one user gains each month (time saved, revenue handled) and price at a fraction of it.
    • Use tiers, not one price. Feature tiers (for example basic, pro, business) let customers pay for what they need, and the top tier anchors the others.
    • Set minimums. A minimum number of seats, or a platform fee plus seats, covers your fixed cost of serving each customer.
    • Offer volume discounts in bands. A lower price above set seat counts rewards growth without negotiating every deal.
    • Price viewers and occasional users separately. Free or cheaper read-only seats stop customers sharing logins to save money.
    • Agree an annual true-up. Customers add seats during the year and pay for the extra at renewal or quarterly, rather than you chasing every change.

    Seat-based licensing in white-label and reseller deals

    When you license your product to an agency or reseller who sells it under their own brand, seats work in two ways:

    • Per seat, passed through: the partner pays you a wholesale price for each seat their customers use and sets their own retail price. You need reliable seat reporting, and the partner needs a margin. See how to price a white-label SaaS license.
    • Per end customer: the partner pays a flat fee per client account, with a seat allowance included. This is simpler for agencies that sell fixed packages.

    Either way, agree a minimum monthly commitment if your hosting and support costs are fixed, and test the margins with the white-label profit calculator. If you'd rather share revenue than count seats, see software revenue share agreements. The resale terms themselves belong in a software reseller agreement.

    Terms to put in a seat-based license

    Most seat disputes come from vague definitions. Put these in the license (this is not legal advice; have a lawyer review your terms):

    • Definition of a user: employees only, or contractors and affiliates too? Do bots, service accounts and AI agents count as users?
    • No sharing: one named user per seat, no shared logins.
    • Reassignment: when a named seat can move to another person (for example when someone leaves) and how often.
    • Counting and true-up: how seats are measured, when overages are billed and at what price.
    • Reductions: whether the customer can lower seats at renewal or only add them during the term.
    • Audit or reporting: usage reports from the product, or a right to check seat counts with notice.
    • Scope: where the software may be used and whether the license is exclusive. See exclusive vs non-exclusive licenses.

    Seats in the age of AI agents

    AI agents complicate seat-based licensing. If an agent handles work that five people used to do, the customer needs fewer seats while getting more value, and the vendor's revenue falls as the product gets better. Vendors are responding with hybrid models: seats for people plus credits for AI tasks, separate "agent seats", or fees tied to outcomes such as resolved tickets. If you sell AI products, read AI agent pricing models before you default to seats.

    Where LicenseSaaS fits

    LicenseSaaS is a marketplace where founders list software, AI tools, APIs and datasets for licensing and white-labeling, and buyers find products to license under their own terms, whether per seat, per customer or revenue share. Listing is free; see pricing for the optional Growth Engine plans. List your product with the license models you offer, or browse software available to license.

    Frequently asked questions

    What is seat-based licensing?

    It is a software licensing model where the customer pays per seat, meaning per user allowed to use the software. A seat can be tied to one named person or shared, with the limit set by how many people use the software at the same time.

    What is the difference between a named user and a concurrent user license?

    A named user license is assigned to one person, who can use it at any time, and nobody else can. A concurrent license is a shared pool: anyone in the group can log in as long as the number of people using it at that moment is below the number of licenses bought.

    Is a floating license the same as a concurrent license?

    Mostly. Both are shared seats limited by simultaneous use. Floating usually describes desktop software that checks a seat out from a license server and returns it when closed, while concurrent is the broader term used for any shared-seat model.

    Is seat-based pricing dying because of AI?

    It is changing rather than disappearing. When AI agents do work that people used to do, customers need fewer seats, so vendors are adding usage credits, outcome-based fees or agent seats alongside per-user prices. Seats still work well when value grows with the number of people using the product.

    How do I price seats in a white-label deal?

    Agree a wholesale price per seat or per end customer that leaves the partner a margin at the retail price they plan to charge, add a minimum commitment if your costs are fixed, and agree how seats are reported and trued up. A profit calculator helps test the numbers before you sign.

    Take the next step

    Discover SaaS products to license, browse by category, or list your own product on LicenseSaaS.