SaaS pricing strategy

A SaaS pricing strategy is the set of decisions that fixes what you charge for and how much you charge. It also sets how the price grows as each customer gets more value from the product. For an early-stage team it doubles as a learning tool: every price you show is a question you are asking the market. This guide covers the main pricing models, how to pick a value metric and how to build a tiered pricing strategy that buyers can read in seconds. It also shows when usage pricing fits and how to test a price change without breaking trust.

We wrote it for founders who have a product in use and a price that was set before anyone had much evidence. If you are still asking whether anyone needs the product at all, pricing work comes second, and the last section explains why the order matters.

What a SaaS pricing strategy decides

A SaaS pricing strategy decides four things. First, the value metric: the unit you charge for, such as seats, projects, contacts or API calls. Second, the packaging: which features and limits sit in which plan. Third, the price level for each plan. Fourth, the rules around the price: annual discounts, trials, how existing customers are treated when prices move, and who is allowed to negotiate. Most early pricing problems come from skipping the first decision and arguing about the third. A team that charges per seat for a product whose value comes from automation will fight its own customers, because buyers will share logins to keep the bill down. Get the unit right and the price level becomes a tuning exercise you can test. Get it wrong and every price you try will feel too high to some customers and too low to others at the same time.

The main SaaS pricing models

Billing platforms work from a short list of models. Stripe's documentation on recurring pricing models names flat rate, per seat, tiered and usage-based pricing. It splits tiered pricing into two kinds. In volume pricing, every unit costs the rate of the tier the total falls in. In graduated pricing, each band of units has its own rate. These are the core software monetization models for subscription software, and most real price lists combine two of them.

Usage pricing is easiest to see in infrastructure. AWS Lambda, for instance, charges by the number of requests and the time code runs, measured in GB-seconds. That works because the buyer is technical, the meter is visible, and spend tracks the work done. Usage pricing fits less well when buyers cannot forecast their own usage. It also fits badly when a busy month is a bad month for them, such as a support tool that bills per ticket during an outage.

Pick a value metric before you pick a price

The value metric is the unit that links your price to the customer's gain. A good one passes four checks:

• It grows with value. When the customer gets more out of the product, the metric goes up too.
• The buyer can predict it. A finance lead should be able to estimate next quarter's bill without calling you.
• You can measure it cleanly. If engineering cannot count it reliably, invoices will be disputed.
• It is hard to game. Customers should not save money by using the product in a worse way.

Take a hypothetical seed-stage team selling booking software to physiotherapy clinics. It might start with per-seat pricing because it is familiar. Now say that in discovery calls, clinic owners talk about booked appointments, not logins, and front-desk staff share one account. The number of practitioners whose calendars the product manages would track value far better than seats. A change of unit like that can matter more than any price level the team could choose.

Value-based pricing strategy in practice

A value-based pricing strategy sets the price from what the product is worth to the buyer, not from your costs or a competitor's page. Cost tells you the floor. Competitors tell you what buyers have already seen. Value tells you the ceiling, and the price should sit below it, so the buyer keeps most of the gain.

To estimate value, we work through three questions with real customers rather than guessing in a spreadsheet:

1. What do they do today without you? The current workaround, whether staff time, another tool or an outside contractor, is the reference point every buyer will use.
2. What does the problem cost them? Hours lost, revenue missed, errors fixed or risk carried. Ask for their numbers, not yours.
3. Who feels the gain, and who pays? In many B2B deals the user who saves time is not the person who signs, so the value story has to work for both.

Value-based pricing does not mean charging the most a buyer will tolerate. It means the price makes sense in the buyer's own terms. If a customer can explain your price to their manager using their own numbers, you have priced on value.

How to design a tiered pricing strategy

A tiered pricing strategy packages the product into a small set of plans, each built for one kind of buyer. Three plans is a common shape, with an entry plan, a main plan and a top plan for larger accounts, but the number matters less than the logic. Each tier should answer one question: who is this for?

• Start from buyer groups, not features. List the two or three customer types you meet in sales calls, then decide what each one needs.
• Use a few clear fences. Limits on the value metric make the step between plans easy to see. So do a handful of features that larger teams need (single sign-on, audit logs, admin roles) and support levels.
• Make the main plan the obvious choice. Most buyers should land on one plan without building a comparison spreadsheet.
• Put custom terms in a top plan. Security reviews, contracts and invoicing belong in a plan priced through a conversation, not a checkout.

The common failure is a grid of features where every row has a tick in a different column. Buyers stop reading and pick the cheapest plan. If you cannot describe the reason to upgrade in one sentence, the tier is not doing its job.

B2B pricing strategy: who signs and how they buy

A B2B pricing strategy has to fit how companies buy, not only what the product does. The person who finds the product is rarely the person with the budget, and larger customers bring procurement, security questionnaires and legal review. A price that works for a five-person team paying by card will stall in a long approval process if the contract terms are unclear.

Three choices shape most B2B pricing pages. Decide which plans can be bought by card and which need a quote. Decide whether you offer annual billing, and what a buyer gets for committing. Decide the currency and how you show tax, which matters for a Canadian company selling into both Canada and the United States.

Show the full price of each plan. In Canada, the Competition Bureau treats drip pricing as a deceptive practice. Drip pricing means advertising a price that cannot be paid because mandatory fees are added later. The only exception is charges the government imposes, such as sales tax. Keep add-ons optional in fact as well as in name.

Free plan, free trial or neither

A free plan and a free trial solve different problems. A free plan is a distribution choice: people use a limited version for as long as they like. It pays off when free users invite paying ones or when the product spreads inside a company. A free trial is a sales choice: it gives full access for a set period so the buyer can reach value before paying. Neither is required. Some B2B products sell through a guided pilot instead, because setup needs help.

If you run a trial, decide early whether to ask for a card at the start. Billing tools support both. Stripe's trial documentation, for example, covers free and paid trials and reminder emails before a trial ends. It also covers whether a trial with no payment method should cancel, pause or create an invoice at the end. Whatever you choose, tell the buyer plainly what happens on the last day.

How to test a price change

Price tests in early-stage SaaS rarely look like a clean A/B test, because traffic is low and B2B buyers talk to each other. These methods work better at small scale, roughly in order of risk:

1. Test in conversations first. Quote the new price on sales calls for a few weeks and track how often it ends the conversation, starts a negotiation or passes without comment.
2. Change the price for new customers only. Compare the cohort that bought at the new price with the one before it: trial-to-paid rate, average revenue per account, discount requests and early cancellations.
3. Give it a full billing cycle. A monthly product needs at least one renewal before you judge churn, and an annual one needs patience or a proxy such as expansion and usage.
4. Move existing customers last. Give clear notice under your terms, explain what changed in the product, and decide in advance who keeps the old price and for how long.

The billing side needs planning too. In Stripe, a price's amount cannot be edited after it is created. The product and price documentation recommends creating a new price, switching to it and archiving the old one. Existing subscriptions on an archived price stay active until they are cancelled. That is how grandfathering works in practice, and it makes every price change a small engineering task. Put it on the roadmap like any other release, with its own date. Our product roadmap examples show how dated commitments sit next to open bets.

One rule for launch offers: if you show a discount, the regular price has to be real. The Competition Bureau's guidance on fake sales and discounts says an inflated price cannot be called the regular price. It also warns about false urgency cues such as countdown timers that reset. A launch discount should end when you said it would.

A one-page pricing review

When we review pricing with a founder, the output fits on one page, so the whole team can read it and argue with it. It covers:

• The value metric, with the evidence for it from customer conversations and usage data.
• The buyer groups and the plan built for each one, with the reason to upgrade in one sentence.
• The price of each plan, the reference points behind it and the discount rules.
• The trial or free plan policy, and what happens on the last day of a trial.
• The next price test: what changes, for whom, what you will measure and the date you will decide.

A pricing review cannot rescue a product that is not yet wanted. If retention is weak and buyers are lukewarm at any price, work through a product-market fit framework first, then come back to pricing.

Frequently asked questions