The Complete Guide to SaaS Pricing Models

Pricing is a product decision, not just a commercial one

SaaS pricing determines who can access your product, what incentives they have around usage, and how your revenue grows as your customer base grows. It is also one of the decisions that is hardest to change once your customer base has expectations set around it. Getting it right — or at least getting it to a defensible place — matters.

This guide covers the main SaaS pricing models, their genuine strengths and weaknesses, and a framework for choosing the right one for your business.

Flat-rate pricing

One price, one product. Every customer pays the same amount regardless of how much they use the product or how many users they have.

Advantages: Extremely simple to communicate, sell, and bill. The customer knows exactly what they are paying and there are no surprises. Sales conversations are straightforward because there is nothing to negotiate.

Disadvantages: Leaves money on the table from large, high-usage customers who would pay more. Creates friction for small customers who might not need — or be able to afford — the full price. Makes it hard to grow revenue from existing customers without raising prices across the board.

When it works: When your product has a narrow use case with consistent value across customers, or when simplicity of sales and billing is a primary competitive advantage. Basecamp has historically used flat-rate pricing effectively as a deliberate market positioning decision.

Per-seat pricing

Customers pay per user on the account. Common in business software where the primary value unit is team adoption — Slack, Notion, and many others use this model.

Advantages: Revenue scales naturally with organisational adoption. Larger organisations pay more, which feels proportionate to both vendor and customer. Simple to understand and communicate.

Disadvantages: Creates incentives for customers to share logins rather than pay for each seat. Can create friction when a team wants to add a new user but has to go through a purchasing decision each time. In some products, the value does not actually scale linearly with user count.

When it works: When collaboration is a core value proposition and more users genuinely means more value — for both the customer and the vendor. Per-seat pricing works less well for solo products or tools where adding users adds cost without adding proportionate value.

Usage-based pricing

Customers pay based on how much they use the product — API calls, data processed, emails sent, storage used. Twilio, AWS, and Stripe all use variations of usage-based pricing.

Advantages: Aligns cost with value delivered. Customers with low usage pay less, which reduces barrier to adoption. High-usage customers naturally pay more. Revenue grows with customer success.

Disadvantages: Revenue is harder to predict for both vendor and customer. Customers worry about surprise bills, which can cause them to use the product less than they otherwise would (the so-called "usage anxiety" problem). Billing complexity is significant — you need metering infrastructure from day one.

When it works: When usage is a reliable proxy for value delivered, and when customers can control and predict their usage reasonably well. Works well for infrastructure products and APIs where the relationship between usage and value is direct and intuitive.

Tiered pricing

Multiple pricing tiers (typically called something like Starter / Growth / Enterprise or Basic / Pro / Business) with different feature sets or limits at each tier. The most common SaaS pricing model.

Advantages: Allows different customer segments to self-select into the right tier. Creates an upsell pathway — customers start at a lower tier and upgrade as their needs grow. Gives customers perceived choice and control.

Disadvantages: Designing the tiers correctly is genuinely hard. Too many tiers confuse customers. Tiers with the wrong feature gates create friction. Features in the "wrong" tier create customer dissatisfaction. The packaging decisions require ongoing maintenance as the product evolves.

When it works: Almost always — tiered pricing is the default model for good reasons. The key is setting the tier boundaries based on customer value, not on what is easy to build or arbitrary round numbers.

Freemium

A free tier with meaningful limitations, alongside paid tiers with full functionality. Dropbox, Notion, and Slack all use freemium models.

Advantages: Dramatically lowers the barrier to acquisition. Free users drive word of mouth and can be converted to paid over time. Creates a large user base that provides product feedback and brand awareness.

Disadvantages: Free users cost money to serve — infrastructure, support, and operational overhead. Conversion rates from free to paid are typically low (2–5% is common). The product has to be good enough to convert free users to paid, and the free tier has to be compelling enough to drive adoption without cannibalising paid.

When it works: When the product has strong viral or word-of-mouth characteristics, when serving free users is genuinely cheap, and when the conversion economics work out — which requires careful modelling before committing to the model.

A framework for choosing your model

Ask these questions:

1. What is the primary value unit of your product? Is it time saved, users served, data processed, or something else? Price against the value unit your customers intuitively understand.
2. Who are your customers and how do they buy software? Self-serve SMEs care about low starting prices and simplicity. Enterprise buyers care about predictability and negotiating room.
3. What behaviour do you want to incentivise? Per-seat pricing incentivises broad team adoption. Usage-based pricing incentivises efficient use. Think about the downstream effects of your pricing on customer behaviour.
4. How predictable does your revenue need to be? Flat-rate and tiered pricing give the most predictable revenue. Usage-based is most variable.
5. What are your competitors doing? Customers have expectations set by your category. A pricing model that is dramatically different from the norm requires customer education.

Most SaaS businesses will land on some variant of tiered pricing with a possible freemium entry point. The details — what goes in each tier, where the tier boundaries are, what the prices are — require careful thought and ongoing experimentation.

One final note: do not let perfect be the enemy of good. Launch with a defensible pricing model, monitor conversion and expansion revenue, and adjust based on data. Pricing is not a one-time decision.