# Seat-based pricing: definition, examples and where per-user billing breaks

Source: https://leverprice.com/glossary/seat-based-pricing
Updated: 2026-11-17

> Seat-based pricing charges a fixed amount per user each month or year, so the bill grows with the size of the team. It is easy to understand and grows revenue as customers hire, but it encourages shared logins and keeps occasional users off the plan. Some vendors bill only for active users to reduce that.

Seat-based pricing charges per person with access. GitHub Team costs $4 per user per month, so a 12-person engineering team pays $48 a month and a 40-person team pays $160, as of November 2026 ([GitHub](https://github.com/pricing)).

## How it works

```text
MRR           = seats × price per seat
expansion MRR = added seats × price per seat
```

Revenue grows without a new sale. If that 12-person team hires 8 more engineers, the bill moves from $48 to $80 a month.

Seat plans often add rules for the edges:

- A minimum number of seats, such as a 3-seat floor on a team plan.
- Seat bands, where 1 to 10 users pay one price and larger teams another.
- Free roles for people who only view or comment.
- Active-user billing. Slack's fair billing policy stops charging for members who haven't used Slack in more than 28 days and credits the unused time ([Slack](https://slack.com/help/articles/218915077-Slacks-fair-billing-policy)).

The difference can be large. A 50-person company with 30 regular users pays for 50 seats under plain per-seat billing and for 30 under active-user billing: at $10 a seat, $500 against $300 a month.

## Why it matters for pricing

The seat price also changes how many seats each customer buys. Raise it and some teams leave occasional users off the plan or share one login, so the average team that pays gets smaller even when conversion holds.

That makes conversion rate the wrong yardstick for a seat-priced test. Compare [revenue per visitor](https://leverprice.com/glossary/revenue-per-visitor), including the seat count chosen at checkout, and check how seat counts move in the months after.

## Common mistakes

- Charging for every invited person, including people who only view.
- A seat price high enough that teams share a single login.
- Judging a price test on conversion rate and ignoring how many seats each buyer took.
- No volume step for large teams, which sends them to negotiate anyway.

## Related terms

[Usage-based pricing](https://leverprice.com/glossary/usage-based-pricing) charges for consumption instead of people, and [tiered pricing](https://leverprice.com/glossary/tiered-pricing) covers seat bands and volume steps. Seat growth and seat cuts both show up in [MRR](https://leverprice.com/glossary/mrr) and [ARPU](https://leverprice.com/glossary/arpu) before a customer ever cancels.

## Frequently asked questions

### Should viewers count as seats?

Making view-only access free lets more people inside the customer's company see the work without inflating the bill. Charge for the roles that create the value.

### How do you raise a per-seat price?

Raise it for new customers first, then decide whether existing teams keep their old seat price for a period. On large accounts a few dollars per seat multiplies quickly, so run the break-even math with the [price increase calculator](https://leverprice.com/tools/price-increase-calculator) first.

### What is the difference between per-seat and per-active-user pricing?

Per-seat billing charges for every user with access. Per-active-user billing charges only for people who used the product in the period, as Slack does with members active in the last 28 days.
