Guides / Ideas and launching

How to Price a SaaS Product: Models, Trade-offs and a First Price

How to price a SaaS product: flat, tiered, per-seat, usage-based and freemium models compared, how trials work, and how to set and test a first price.

Mythex Team · 2026-09-29 · 6 min read

To price a SaaS product, start from the value it creates for one specific customer, choose a pricing model that grows with that value (flat, tiered, per-seat or usage-based), and pick a first price you can defend — then test it with real buyers and adjust. For most new products, two or three simple tiers and a free trial are a sensible default. Your first price will be wrong; the goal is to be wrong in a way you can learn from.

Start with value, not cost

There are three ways to anchor a price:

Use all three, in this order of importance: value sets the ceiling, competitors show what buyers are used to paying, and cost sets the floor.

To estimate value, ask customers during validation what the problem costs them today: hours per week, money lost, the tool they already pay for, or the person they'd otherwise hire. A tool that saves a business owner several hours a month is worth a meaningful share of what those hours are worth to them.

Know your cost floor

Software is cheap to run per customer, but not free. Add up, per customer per month:

• Hosting, database and storage for their data
• Paid APIs they trigger — AI models are the usual surprise
• Email sending
• Payment processing fees

Stripe's standard US rate, for example, is 2.9% + 30¢ per successful domestic card charge (Stripe pricing, as of September 2026; other countries differ). On a $5 monthly plan, fees take a much bigger share than on a $50 one. Very cheap plans can lose money once fees, support and refunds are counted.

Choose a value metric

A value metric is the unit you charge for: per user, per project, per invoice sent, per contact stored. A good one:

• Grows with the value the customer gets. More invoices sent means more money collected.
• Is easy to understand. Customers can predict their bill.
• Is hard to game. Sharing one login shouldn't make the product nearly free.

Picking the metric matters more than picking the exact number, because it decides how revenue grows as customers grow.

The main pricing models

Flat-rate pricing

One price, one plan, everything included.

• Good for: Simple products with one type of customer.
• Pros: Easiest to explain and sell; no confusion.
• Cons: Small customers may find it too expensive and large ones get a bargain. There's no natural upgrade path.

Tiered pricing

Two to four plans — for example Starter, Pro and Business — with more features or limits at each level.

• Good for: Most early SaaS products, when customers vary in size or needs.
• Pros: Serves different budgets; gives customers a reason to upgrade; lets you anchor with a higher tier.
• Cons: Deciding which features go in which tier is hard, and too many tiers confuse buyers. Keep the differences obvious.

Per-seat pricing

A price per user, per month.

• Good for: Collaboration tools where value grows with the number of people using it.
• Pros: Predictable and grows as teams grow.
• Cons: Teams share logins to save money, and it discourages inviting occasional users — which can slow adoption. Some products charge only for active users or for "editors" while viewers are free.

Usage-based pricing

Customers pay for what they use: API calls, messages sent, gigabytes stored, credits spent.

• Good for: Products where usage varies widely, or where your own costs rise with usage (AI features, messaging, data processing).
• Pros: Fair; small customers start cheaply; revenue grows with heavy users; your costs are covered.
• Cons: Bills are harder to predict, which makes some buyers nervous. Offer included amounts, spending caps, alerts and clear usage dashboards.

Hybrid pricing

A base subscription plus usage above an included allowance — for example, a monthly plan that includes a set amount and charges for extra.

• Good for: Products with both steady and variable value.
• Pros: Predictable base revenue with protection against heavy use.
• Cons: More to explain; needs usage tracking and clear billing.

Freemium

A permanently free plan with limits, and paid plans above it.

• Good for: Products that spread by sharing, invites or public output, where a free user costs little to serve.
• Pros: Lowers the barrier to trying the product; free users can bring in paying ones.
• Cons: Most free users never pay, and they still cost hosting and support. Set limits that a serious user will hit, and keep the free plan's running cost low.

Free trials

A trial gives full or near-full access for a limited time, then asks for payment.

Match the trial length to how long it takes a new customer to reach their first real result. If that takes a week of setup, a very short trial won't work. Remind users before the trial ends and say clearly what happens next.

Pricing models compared

Setting your first price

1. List what customers pay now to solve the problem — tools, time, people.
2. Pick your value metric and a model from above.
3. Draft two or three tiers. The lowest covers a single user's core need; the middle is the one you expect most people to choose; the top adds what larger customers ask for.
4. Check the floor. Make sure the cheapest plan covers the cost of serving a heavy user, including payment fees and paid APIs.
5. Put the price in front of people. Show it in interviews and on your landing page. Hesitation and questions tell you more than compliments.
6. Offer annual billing with a discount for paying up front. It improves cash flow and reduces churn, but make the monthly option genuinely available.

Testing and raising prices

• Test on new customers first. Change prices for new sign-ups and compare conversion over a meaningful period.
• Grandfather existing customers or give them plenty of notice when prices rise. Honesty keeps trust.
• Raise prices when you add real value, not only when you need revenue, and explain what changed.
• Watch why people leave. If price is rarely mentioned, you may be charging too little.

Pricing page basics

• Show prices publicly for self-serve plans.
• Highlight the plan most people should choose.
• List the differences between tiers, not every feature.
• Answer the common questions on the page: can I cancel, what happens at the limit, is there a trial.
• Keep the call to action the same on every plan.

Pricing and billing with Mythex

If you build your SaaS on Mythex, you connect your own Stripe account for checkout and subscriptions — the Stripe recipe in the docs shows the steps — and your pricing is entirely yours. Mythex's own plans are an example of a hybrid model: a free tier with daily credits and a flat Pro subscription with included credits and top-ups, as shown on the pricing page. For the build itself, the SaaS MVP guide covers what to include first, and adding payments walks through Stripe checkout and webhooks.