Seat-based pricing ties subscription revenue to the number of users on an account — the default model for much of workplace software.

How it works

The vendor sets a price per seat per month or year. Customers buy a block of licenses or pay as they add users. Some contracts include minimum seats, true-ups at renewal, or automatic charges when active users exceed purchased seats.

Contrast with usage-based pricing (pay per API call or transaction) or flat platform fees. Seat models reward products that spread across a company: more employees on the tool means more ARR without a new sales cycle.

Founders often blend models — a platform fee plus per-seat add-ons, or seat tiers with feature gates — to balance simplicity and capture of value.

Why it matters

• Founders: Seat pricing is familiar to enterprise buyers but can undercharge heavy users who touch few seats. Model expansion assumptions honestly in fundraising decks.
• Investors: They look at average seats per customer, seat growth rate, and whether pricing invites shadow IT or shared logins that suppress revenue.

Common mistake

Assuming every employee is a billable seat when customers routinely share accounts or buy only for a subset of roles.

Related ideas

• Seat expansion
• Average contract value
• Usage-based and consumption pricing