Pricing model decisions get made for the wrong reasons.
Companies pick seat-based pricing because it is familiar and easy to explain in a spreadsheet. They pick usage-based pricing because competitors are doing it or because an investor said it aligns incentives. Neither is a strategy. Both choices end up in the same place: a pricing model that does not fit the product, creates friction with the buyer, and produces unpredictable revenue.
The right pricing model is the one that reflects how your product creates value. If value scales with the number of people using it, seat-based pricing is correct. If value scales with the volume of activity or outcome the product produces, usage-based pricing is correct. This sounds simple. Making it work requires understanding the second-order effects on your revenue model, your sales motion, and your CS capacity.
How Seat-Based Pricing Works
Seat-based pricing charges a flat rate per user per month (or year). The unit of value is the individual user's access to the product. Revenue is predictable — you know exactly what a customer pays based on the number of seats on their contract.
Seat-based pricing works well when:
- Value is primarily individual — each user gets a benefit proportional to their personal access and usage
- Usage is relatively uniform across users — the difference between a heavy and a light user is not so large that seat pricing feels unfair to either
- Adoption is social — adding more seats means more people using the product, which creates internal momentum and makes churn harder
- Procurement is straightforward — the buyer knows how many seats they need upfront and the conversation is predictable
Classic examples: CRM software, collaboration tools, project management, sales engagement platforms. The value is proportional to how many people in the team have access.
Where seat-based pricing creates problems:
- Customers cap seat numbers to control spend, which limits adoption and reduces the product's actual impact
- Expansion revenue stalls when organisations reach full team coverage and there are no more seats to add
- Power users subsidise light users, creating internal friction when the company tries to expand the licence
How Usage-Based Pricing Works
Usage-based pricing (also called consumption-based or pay-as-you-go) charges based on how much of the product's core value metric is consumed — API calls, records processed, emails sent, data stored, events tracked. Revenue scales with customer success: the more value the customer gets, the more they pay.
Usage-based pricing works well when:
- Value is clearly tied to volume — the customer's outcome scales with how much they use the product
- Usage varies significantly across customers — a startup processing 10,000 transactions per month and an enterprise processing 10 million deserve to pay different amounts
- You want a low barrier to entry — starting free or at minimal spend removes purchase friction and lets customers experience value before committing to a larger contract
- Product-led growth is the primary acquisition motion — usage data creates a natural upsell trigger as customers grow
Classic examples: API infrastructure (Stripe, Twilio), data platforms, cloud storage, email delivery. Value scales directly with volume of consumption.
Where usage-based pricing creates problems:
- Revenue becomes harder to predict — a customer that reduces usage or has a bad month generates less revenue with no notice
- Enterprise procurement teams dislike variable spend — the CFO wants a fixed number to put in the budget
- Sales cycles become more complex — the ACV is not fixed, which makes quota management and forecasting harder
- CS becomes more complex — you need to actively manage customer growth to ensure the usage trajectory stays healthy
The critical question: what is the natural value metric?
The right pricing metric is the one that scales most directly with value delivered. Ask your best customers: "As your usage of this product grows, what grows with it?" Their answer is usually the right metric. If they say "the number of people using it," seat-based is right. If they say "the number of [records/transactions/outcomes]," usage-based is right.
The Revenue Model Implications
| Dimension | Seat-Based | Usage-Based |
|---|---|---|
| Revenue predictability | High — contracted seats = known MRR | Lower — actual usage determines revenue each period |
| Expansion motion | Add seats — often requires new budget approval | Natural growth as customer scales — no new approval required |
| CAC payback | Faster for enterprise (larger upfront contracts) | Slower initially (low entry ACV), improves as usage grows |
| Gross margin profile | Stable — seat costs are largely fixed | Variable — infrastructure costs often scale with usage |
| NRR potential | 100–115% typical — growth requires seat additions | 120–150%+ possible when customer growth drives natural expansion |
| Churn risk | All-or-nothing on renewal — harder to partially churn | Gradual reduction in usage is an early churn signal |
Hybrid Models: When Neither Is Pure
Most mature SaaS companies end up on a hybrid: a platform fee or minimum commit that provides predictable base revenue, combined with usage-based overage above a threshold. This model attempts to give the buyer budget predictability while giving the vendor a natural expansion mechanism.
The hybrid model works well when:
- Enterprise buyers need a number to put in the annual budget (addressed by the committed minimum)
- The product has both fixed-value components (access, integrations, support) and variable-value components (volume of processing)
- The customer base varies significantly in scale — a startup and an enterprise should logically pay different amounts for the same product
The hybrid model creates problems when the threshold is set at the wrong level. If the committed minimum is too high, it becomes a barrier to entry for smaller customers. If it is too low, too many customers live inside the committed range and the expansion upside disappears.
GTM and Positioning Implications
Pricing model choice affects how you position and sell, not just how you invoice.
With seat-based pricing: The sales conversation is about breadth of adoption. You are selling access for the whole team. The ROI case is built on value per user multiplied by number of users. Sales enablement focuses on stakeholder expansion — getting more team members enrolled — as the primary expansion lever.
With usage-based pricing: The sales conversation is about depth of value. You are selling the ability to scale. The ROI case is built on what becomes possible as usage grows. Sales enablement focuses on activation and time-to-value — getting customers to their first significant usage milestone quickly, because that is when the expansion curve starts.
The positioning difference: Seat-based positioning often leads with team-level outcomes ("give every sales rep visibility into..."). Usage-based positioning often leads with scale outcomes ("as your business grows, so does the value you get from..."). These are different positioning frames for different buyer motivations.
Which Model Fits Your Product?
Work through these questions before deciding:
- Does value scale more with the number of users or with the volume of activity? If users, seat-based. If activity, usage-based.
- How variable is usage across your existing customers? If two customers at the same seat tier use the product by a factor of 10 differently, usage-based is probably more equitable and more expansive.
- What does your target enterprise buyer's procurement process look like? Large enterprises with annual budget cycles often resist usage-based pricing at the enterprise tier. Build a committed contract option if enterprise is a key segment.
- Is product-led growth part of your acquisition strategy? Usage-based pricing enables PLG better. A free tier with usage-based growth creates a natural acquisition path. Seat-based pricing requires more friction to start.
- What does the competitive landscape charge? If every competitor in your category uses seat-based pricing, moving to usage-based is a differentiation move that requires careful positioning. If competitors use usage-based, seat-based may actually be the differentiation through predictability.
There is no universally correct model. There is a correct model for your product's value delivery mechanism, your buyer's procurement psychology, and your current stage. Getting this right — and being willing to change it as the product and market mature — is one of the most important GTM decisions a founder or product marketing leader makes.
Hybrid Model: A Worked Example
A B2B SaaS company builds a document automation platform used by legal and finance teams. Their current seat-based pricing (£200 per user per month) is working well at SMB level but is creating friction at enterprise. Procurement teams want a predictable annual cost. Usage varies dramatically across enterprise accounts — some process 5,000 documents a month, some process 80,000. At the same seat count, they are leaving significant value on the table for high-volume customers while overcharging low-volume ones.
They move to a hybrid model:
- Base platform fee: £2,000 per month, which includes up to 10,000 document processes. This gives enterprise procurement a number to budget against and covers the cost of the integrations, access controls, and support that every enterprise customer uses regardless of volume.
- Usage overage: £0.08 per document above the 10,000 threshold. High-volume customers (processing 80,000 documents) pay £2,000 + £5,600 = £7,600 per month. Low-volume customers stay at the base fee.
- Annual commit discount: Customers who commit to a minimum annual volume receive 15% off the overage rate. This gives the vendor revenue predictability and gives the buyer a pricing incentive to consolidate usage on the platform.
The result: average enterprise ACV increases from £28,000 to £51,000 in the first year after the model change. Churn drops slightly because the base fee creates a low-stakes entry point. High-volume customers feel the pricing is now fair relative to the value they are getting. PMM's role in this transition was significant: the new model required entirely new sales collateral, a revised ROI calculator, updated objection handling for procurement conversations about variable costs, and new onboarding materials that helped customers understand what would drive their monthly bill.