Software Growth

Per-seat pricing

Per-seat pricing charges a fixed price for each user who has access to the product, so the bill grows as the customer adds people.

Per-seat (or per-user) pricing means the customer pays a set amount for each person who can log in. It is the oldest SaaS pricing model and still the default for collaboration, CRM and support tools. A team of 10 on a $12 per user plan pays $120 a month; hire five more people and the bill is $180.

How to calculate it

If your average account has 8 seats at $15, that is $120 per account. A product with 150 such accounts has $18,000 of MRR. Growth then has two sources: new accounts and more seats within existing ones. That second source is the land and expand motion, and it is why seat-based products can post strong net revenue retention without selling anything new.

Where it works

  • Every user does their own work in the product, so more users really does mean more value.
  • Buyers want a bill they can predict and budget by headcount.
  • Your costs scale with users (support, seat-level licensing).

Where it breaks

The Paddle guide to tiered pricing notes that the number of users is rarely where value is derived for many SaaS products (source). When the value is in output, not in logins, seats punish the wrong behavior:

  • Customers share logins to avoid paying, which hurts your data and security story.
  • Teams keep a few "power users" and leave everyone else on a spreadsheet, so adoption stays shallow.
  • Occasional users (executives, contractors) are too expensive to add, even though adding them would deepen your lock-in.
  • AI features can make each seat far more productive, which means fewer seats for the same outcome.

Variants

  • Active-seat billing. Count only users who did something in the period. Fairer, but revenue is less predictable.
  • Tiered seat prices. The per-seat price drops at 10, 50 and 100 seats.
  • Seat bundles. A plan includes 5 seats, and extra seats cost more. This is a hybrid with tiered pricing.
  • Free viewers. Only editors pay. Used by design and docs tools.

Jason Cohen's A Smart Bear post on raising prices mentions one old example of rethinking the unit: Code Reviewer moved from $34.95 per seat to a $1,300 floating seat (source). Changing what a seat means can change what you earn.

Seat pricing for a small SaaS

Seats are the easiest model to explain on a pricing page and to bill in Stripe, which is why they are a good first choice. Revisit the choice once you see accounts where usage is far above or below what the seat count suggests. That mismatch is the signal that a better value metric exists, or that a hybrid with usage-based pricing would fit.

Sources

Back to the SaaS glossary