Subscription Pricing Models: Tiers, Seats, and Usage

Pricing structure is one of the highest-leverage decisions you'll make. The same product can generate radically different revenue depending on how it's packaged and priced. Most founders spend weeks on feature decisions and hours on pricing — that ratio should be reversed.

Here's what you need to know about the main subscription pricing structures and how to choose between them.

Flat Rate

One price. Full access. Everyone pays the same.

When it works:

• Your product has one clear use case
• Your customers are similar in size, needs, and usage
• You want to minimize sales complexity and support overhead

When it doesn't:

• You serve both small teams and enterprise customers
• Usage varies significantly across your customer base
• You're leaving expansion revenue on the table from high-value customers

Basecamp famously uses flat rate pricing ($99/month for the whole team) and has built a profitable business on it. But Basecamp is also deliberately not a venture-backed growth machine. If you're trying to maximize revenue from a diverse customer base, flat rate will frustrate you.

Per-Seat Pricing

Price scales with the number of users. $X per seat per month.

When it works:

• Your product's value scales with team size (collaboration tools, CRMs, project management)
• Your buyers are in companies where headcount is an obvious value proxy
• You want natural expansion revenue as customers grow

When it doesn't:

• Customers actively limit seat counts to control costs, reducing adoption
• Your value doesn't actually scale with users (one person using it extensively is worth as much as ten people using it occasionally)
• You're selling to individuals rather than companies

Per-seat pricing is the default for B2B SaaS for good reason. It aligns price with value for most collaboration-adjacent tools and creates natural upsell as customers grow.

Watch out for: customers gaming seat counts by sharing logins. Build detection and policies into your contract terms early.

Tiered Pricing

Multiple packages (typically 3) at different price points with different feature sets. Starter / Growth / Enterprise is the classic structure.

When it works:

• Different customer segments have genuinely different needs
• You can create meaningful feature differentiation between tiers
• You want to serve multiple market segments without custom pricing for everyone

When it doesn't:

• The tier boundaries feel arbitrary (customers can't tell why the middle tier is worth the jump)
• Your highest tier isn't actually differentiated from the middle tier
• You have more than 4 tiers (analysis paralysis sets in)

Tiered pricing is almost universally the right answer for SaaS targeting both SMB and enterprise. The key is making each tier feel complete at its price point, not a crippled version of the next tier up.

Packaging Strategy for Tiers

The middle tier should be your target — price it where you want most customers to land. The bottom tier should exist to get customers in the door, with genuine limitations that make upgrading feel natural. The top tier should include everything enterprise customers need: SSO, audit logs, dedicated support, custom contracts.

A common mistake: making the bottom tier so capable that customers never feel the need to upgrade.

Usage-Based Pricing

Customers pay based on what they actually use: API calls, messages sent, data processed, rows stored, emails delivered.

When it works:

• Usage is a clear proxy for value delivered
• Your cost structure scales with usage
• You're selling to developers or technical buyers who think in consumption terms

When it doesn't:

• Usage is unpredictable for customers, making budgeting hard
• Your costs don't scale with usage but your revenue does (a mismatch that destroys margins)
• Customers become usage-anxious and self-limit in ways that reduce the product's effectiveness

Usage-based pricing is explored in depth in a separate resource. The short version: it's powerful for the right products but introduces revenue predictability challenges that pure subscription models don't have.

How to Choose

Ask these questions:

1. What is the natural unit of value in my product? Users? Transactions? Data volume? That unit often points to the right model.

2. How similar are my customers? High similarity favors flat rate. High diversity favors tiers or usage-based.

3. Do I want natural expansion revenue? Per-seat and usage-based models grow with customers automatically. Flat rate doesn't.

4. How price-sensitive are my customers? Usage-based rewards efficient users, which can be a selling point in cost-conscious markets.

5. What does my competitive landscape look like? Pricing radically differently from the category norm requires strong justification — customers compare.

Most mature SaaS products end up with a hybrid: a base subscription (tiered or per-seat) plus usage-based components for the parts of the product where consumption varies significantly. This gives you predictable base revenue plus upside from power users.

Start simple. You can always add complexity. Removing it is much harder once customers are used to a structure.