What is seat-based pricing?

A pricing model that charges a fixed amount per named user per month, however much or little that user does in the system.

An admin approves every new account by hand. Nothing is created until then. We reply by email; no newsletter, no sequence.

app.salescrew.io/inbox
The unified reply inbox with classified threads

Seat-based pricingSeat-based pricing charges per named user per month, so the bill grows with headcount whatever the usage. It is the dominant CRM model and the main reason teams limit who gets a login.

Why it matters

Seat-based pricing ties the bill directly to headcount. Each named user with a login costs a fixed amount per month. The total grows in a straight line as more people are added, however heavily any individual seat is used. It is the model most CRMs default to. It is simple to explain and simple to bill, and it has been the standard since long before usage-based alternatives became practical to meter.

The predictable side effect is that teams start rationing logins. A sales manager gets one. A rep gets one. But the ops person who needs to check a record now and then, or the support lead who wants to see a customer's history, often does not. Another seat means another line on the invoice. The undercount is easy to miss. Seats end up counted as reps only. The real list of people who need to read or touch a record, managers, ops, support, anyone doing occasional lookups, is usually longer than the headcount a team first budgets for.

How seat-based pricing is calculated

  1. 1

    Count named users

    Every person with a login is counted as a seat, active or not.

  2. 2

    Apply the per-seat rate

    Each seat is billed at a fixed monthly rate.

  3. 3

    Multiply by headcount

    The total bill is the per-seat rate times the number of seats.

  4. 4

    Add seats as the team grows

    New hires with a login increase the bill immediately.

  5. 5

    Review seats no one uses

    Inactive logins still cost the same as active ones unless removed.

The mistake to watch for

Counting only sales reps. Managers, ops, support and anyone who needs to read a record become seats.

Questions

How is seat-based pricing different from usage-based pricing?
Seat-based pricing charges a fixed rate per named user, whatever the activity. Usage-based pricing charges for measured consumption, such as messages sent or model calls. The bill then reflects real activity instead of headcount.
Why do teams under-count how many seats they need?
Seats are often budgeted around active sales reps alone. The full list of people who need at least occasional access, managers, support, ops, is usually longer than that first count.
Does an inactive seat still cost money?
Yes. In a seat-based model the charge is tied to the login existing, not to how often it is used. An unused seat costs the same as a heavily used one until it is removed.