SaaS

SaaS pricing models: how to choose the right one

Flat, per-user, tiered, usage-based or hybrid: compare SaaS pricing models, pick a value metric, choose a trial and raise prices without losing customers.

You are about to launch a SaaS (software as a service), or your first price list no longer fits the customers you have. Some pay too little for what they use; others leave because the entry plan is too dear. Choosing among SaaS pricing models is not only a marketing question: each model shapes who buys, how revenue grows and what the product must be able to do.

Here we compare the five common models, the unit your price should follow, the ways customers start, how to raise prices, and what each choice asks of your code.

The five SaaS pricing models compared

Flat price

One product, one price for everyone. It is the easiest model to explain and to bill, and it suits a narrow product with customers of similar size. Its limit: a firm of five and a firm of 200 pay the same.

Per user

Each account, or “seat”, is billed. Customers understand it, and revenue grows with their team. The catch: it encourages shared logins and penalises customers for rolling the tool out widely, which is what makes them stay. It fits tools where each person gets value alone, such as a CRM (customer relationship management) used by every salesperson.

Tiered plans

Two to four plans, each with more features or higher limits. Tiers serve different customer sizes with one product. The risk is a grid nobody can read: if a prospect needs a long comparison table to choose, you have too many tiers or too many differences.

Usage-based pricing

The customer pays for what they consume: documents processed, messages sent, storage, API (application programming interface) calls. Usage-based pricing ties revenue to the value delivered and lowers the entry barrier. In return, revenue is harder to forecast and customers dislike invoices they cannot predict, so it needs a visible counter, alerts and caps.

Hybrid

A base subscription that includes a volume, with a price for anything beyond it. Hybrid models combine a predictable base with growth tied to usage. They are also the most demanding to build.

Model Easy to explain Predictable for the customer Revenue grows with value What the product must do
Flat Very Very No Very little
Per user Very Yes Partly Count active users
Tiered Fairly Yes Partly Enforce limits and features per plan
Usage-based Less Less Yes Measure usage reliably, show it, cap it
Hybrid Fairly Fairly Yes All of the above

Choosing a value metric: what your price should follow

The value metric is the unit your price rises with: users, projects, documents, locations, transactions. It matters more than the price itself, because a good metric lets you start low and grow with the customer. It should pass four tests:

  1. It follows the value the customer perceives. If your tool saves time on each file, “per file” speaks to the customer; “per gigabyte” does not.
  2. The customer can predict it. They should be able to estimate next month’s bill in a minute.
  3. It grows with the customer’s success, not with their caution. A metric that punishes use leads to less use.
  4. You can measure it without dispute. If you and the customer could count it differently, you will argue about invoices.

When two metrics pass, take the simpler one. Adding a dimension later is easy; removing one from existing customers is not.

Freemium vs free trial vs demo: how customers start

How a prospect first touches the product is part of the price.

Free trial

Full or near-full access for a limited time. It works when the product shows its value quickly and the customer can set it up alone. Ask for the essentials only at sign-up and guide the first steps: a trial nobody completes teaches you nothing.

Freemium

A permanently free plan with limits, and paid plans above it. Freemium vs free trial comes down to one question: can free users cost you little and still bring paying ones? Freemium needs a product that is cheap to serve, a large market and a clear limit worth paying to remove.

Demo

A guided session before any access. It suits products with a complex set-up, a sensitive data import or a longer purchase decision, as often in software for professional firms.

Monthly or annual plans

Offer both once you have a few customers. Monthly lowers the barrier; annual, usually with a discount, steadies your cash flow. Selling abroad adds currencies and local taxes: see SaaS internationalisation.

A decision grid for your SaaS pricing strategy

Answer these questions in order. A contradiction between two answers usually points to a hybrid.

Question If yes If no
Do your customers vary widely in size? Tiers, per user or usage Flat price
Does each person get value on their own? Per user Per account or usage
Is there a countable unit the customer cares about? Usage or hybrid, with that unit Tiers by features
Do your costs grow with each customer’s volume (artificial intelligence, storage, messages)? Usage or hybrid, so margins hold Per user or tiers
Does the customer need a predictable budget? A volume included in the base, with caps Pure usage is acceptable
Can the value be seen alone in a few days? Free trial, or freemium if free users cost little Demo

Illustrative example (fictitious figures). A document tool for accounting firms charges 30 per user per month, in its local currency. Its customers point out that some firms of three process as many files as firms of ten. The team moves to a hybrid: 200 per month per firm, including 500 documents, then 20 per extra block of 100. Small busy firms pay for what they use, and large firms stop sharing logins.

At launch, keep it simple, as our guide to launching a minimum viable product (MVP) explains; this grid is for when you have real customers.

What each pricing model asks of the product

A price list is a promise the software must keep:

  • Plan limits: the product must know each customer’s plan and enforce it on the server, not only in the screens.
  • Usage metering: every billable event counted once, stored with its date and visible to the customer.
  • Upgrades and downgrades: billing services can calculate a pro rata, but you set the rules: immediate upgrade, downgrade at renewal, what happens to data above a lower limit.
  • The billing service: subscription platforms handle cards, invoices, failed payments and taxes. Your product must stay in sync: a failed payment changes access according to rules you have written down.

When an installed product moves to subscriptions, this is a large part of the work, as we explain in moving installed software to SaaS.

Raising prices without losing customers

Launch prices rarely stay right as the product grows. Raising them is normal; doing it badly is what costs customers.

  1. Add value first, or at the same time.
  2. Give notice. Explain why, with the date and the new amount, well before the change.
  3. Protect loyal customers. Keep their price for a period, or let them lock it in with an annual plan. This means the system must handle several price lists at once.
  4. Change one thing at a time. A new metric and a new price together make invoices impossible to compare.
  5. Watch what follows. Track cancellations, downgrades and support questions in the following months, along with monthly recurring revenue and revenue churn, to see whether the change paid off.

Your terms of service and local law may restrict how and when a subscription price can change, especially for consumers and fixed-term contracts. This is practical guidance as of October 2026, not legal advice: have a lawyer confirm the rules in each country where you sell.

Frequently asked questions

Should a SaaS publish its prices on its website?

For products customers can buy alone, yes: hidden prices make prospects assume the worst. For products sold after a demo, with set-up or custom volumes, many businesses publish their entry plans and keep “contact us” for large accounts.

How often should you review your SaaS prices?

At least once a year, and after any change in the value delivered: a major feature, a new customer segment, a sharp rise in your own costs. Often the price is fine, but a limit is badly placed or a plan nobody chooses should go.

Can you charge per user and per usage at the same time?

Yes, that is a hybrid: a price per user that includes a volume, and a charge per block beyond it. It works when both dimensions really drive value or cost. Keep the invoice readable, show usage in the product as it happens, and test the model on your current customers’ real data before announcing it.

In short

Flat, per-user, tiered, usage-based and hybrid models each favour a different kind of customer and growth. Choose the value metric first, one that follows what customers value and that you can measure without dispute, then how customers start: trial, freemium or demo. Every pricing rule must be built into the product, from plan limits to metering. And raise prices with notice, with value, and one change at a time.

Is your price list ready, but not your product’s billing? Book a free 30-minute discovery call: we look at your pricing model together and at what it asks of your SaaS, which our SaaS development team can then build.

Related servicesSaaS products

Have a project in mind?

Let’s talk about it on a 30-minute discovery call, free and with no obligation.

Book a discovery call

Further reading

All articles