SaaS Seat Pricing: What Counts as a User and What the Real Per-Seat Cost Is
A per-seat price looks simple, but the real cost depends on how the provider defines a seat, when they count it, and whether removing a user mid-term actually reduces your bill. This guide explains the difference between named, active, and concurrent users, the four common counting methods, and the hidden seats that turn a $15 plan into a $300 plan.
Quick verdict
Treat the headline per-seat price as the starting point, not the final number. Before committing to an annual seat-based plan, confirm how seats are counted, what happens to seats when a user leaves mid-term, whether guest and service accounts are included or billed, and whether your audit of real seat usage matches the number on the invoice.
What a seat actually means
Named users: every invited account is billable
The strictest model. If a user has been invited to the workspace, even if they have never logged in, they count as a seat. Removing access is the only way to free the seat, and historical invites can keep showing up on the invoice.
Active users: only accounts that logged in recently
Some providers charge based on distinct users who logged in during the billing period. A user who was invited but never signed in may not count. A user who logged in once six months ago usually does.
Concurrent sessions: simultaneous logins at the same time
Less common in SaaS, more common in collaboration and design tools. A single user can keep the same seat open on laptop, phone, and tablet without paying more, until a second human tries to log in at the same time.
Why the same seat price produces different bills
The first price comparison is almost always the headline number: $15 per user per month, $99 per user per month, $25 per workspace per month. The real gap shows up after adoption. A team that was sized at fifteen may end up billed for twenty-three, because a departing engineer's seat was never reassigned, a contractor was added for a two-week sprint, and a marketing intern's read-only access quietly stayed on for a quarter.
How providers actually count seats
Login-based counting
A seat is any unique login that authenticated during the period. Two humans sharing one login is allowed; one human logging in from three devices is also allowed. This is the model most collaboration tools use.
Session-based counting
A seat is one active session at a time. If a user signs out, the seat becomes free. If a second human signs in, the bill increases. This is rare in pure SaaS but common in shared dashboards and live tools.
SSO-based counting
A seat is any identity that your identity provider has provisioned into the workspace, whether the user has logged in or not. This is the most expensive model in practice, because offboarding in your IdP usually happens weeks after offboarding in HR.
Device-based counting
A seat is any device that registered or paired with the account. A user with a phone, tablet, laptop, and a shared family computer can rack up multiple seats in a single billing cycle.
How each billing model handles real seat changes
| Billing model | How seats are counted | Mid-month add | Mid-month remove | Annual plan behavior |
|---|---|---|---|---|
| Per named user, monthly | Every account with workspace access | Usually prorated to the day | Access ends immediately; no refund for unused days | Less common; usually the annual version of the same model |
| Per active user, monthly | Distinct users who logged in during the period | Counts as soon as the new user logs in | Stops counting at the next invoice cycle | Often pre-bought in tiers; unused activity is not refunded |
| Per seat, annual prepaid | Seats purchased up front for the year | Adds a new seat, often at a higher per-seat rate | Typically no credit; some providers prorate the unused portion | Seats that are removed rarely refund; some providers allow seat reassignment |
| Per concurrent session | Active sessions at the same time | Counts the moment a new session begins | Counts the moment a session ends | Often combined with a minimum seat count, not a true annual commitment |
| Per workspace or tier | Up to a fixed number of users per plan | Cross the limit and the plan upgrades | Plan may downgrade on the next cycle | Annual prepay for the plan tier; overages are billed separately |
The real math when someone leaves
A 12-person team on a $20 per seat per month annual plan pays $2,880 for the year. If one person leaves in month three and is not replaced, the team is now 11 people paying for 12 seats. The provider keeps the prepaid amount. The team has spent $540 for a seat no one is using, and the only ways to recover that money are reassignment, a mid-term downgrade request (often denied), or letting the seat ride unused until renewal.
The same team on a $20 per seat per month monthly plan loses $20 the month the seat is removed. The loss is small, the timing is clean, and the next invoice reflects the new headcount. Monthly billing is more expensive per month, but the per-seat flexibility is what actually saves money when team composition changes.
This is the per-seat math that the pricing page never shows. Read the seat removal policy before signing, not after the first invoice.
How to audit your actual seat usage
Open the admin panel, export the user list, and tag every account with a name, a status, and a reason. The audit usually surfaces three categories: people who are still on the team and using the tool, people who left but were never removed, and people who were added for a project and never removed after the project ended. The third category is where most of the savings live. The second is where the security risk lives.
A simple seat audit, in seven steps
- Export the full user list from the admin panel, including status, last login, role, and account type.
- Sort by last login and flag any account that has not logged in for 30, 60, and 90 days.
- Match every account against your current team roster and current contractor list.
- Identify accounts that belong to former employees, finished projects, or completed engagements.
- Decide for each flagged account whether to reassign, remove, or downgrade to a free tier.
- Check whether guest users, external collaborators, and service accounts are included in the seat count.
- Compare the cleaned count against the current invoice, and against the plan tier the team is actually paying for.
Buyer checklist: before you sign up for a seat-based SaaS plan
- Ask the provider exactly how a seat is defined: named user, active user, concurrent session, or device, and confirm the definition in writing.
- Ask what happens to a seat when a user is removed mid-term on an annual plan: full refund, prorated credit, no credit, or seat reassignment only.
- Count guest users, external collaborators, contractor accounts, and service or bot accounts, and ask whether each category is included in the seat count or billed separately.
- Check whether API-only access requires a seat, or whether API keys are billed on usage instead.
- Confirm the billing date and the day seats are counted. A monthly invoice that closes on the 28th can include an extra user who joined the day after the previous close.
- Audit current usage 30 days before any renewal: export the user list, sort by last login, and remove or downgrade every account that is no longer needed.
- Compare monthly vs annual per-seat pricing using a realistic 12-month team size, not the current headcount, and not the size at the start of the year.
- Plan seat removal in advance. Offboarding in HR should trigger offboarding in every SaaS tool, ideally through SSO or SCIM rather than by hand.
Affiliate disclosure: PriceGap is an independent buyer-education site. This article contains no advertiser checkout links, does not claim a current sponsor relationship with any SaaS provider, and does not quote fixed live prices or per-seat rates. Always verify current seat definitions, mid-term removal terms, and renewal pricing directly with the provider before purchasing or renewing.