SaaS Pricing: Models, Examples and How to Pick Yours
SaaS pricing is how a software product charges for access: usually a recurring subscription, sometimes usage, seats or a one-time payment. The right model is the one that matches how your customer gets value, so a tool used daily fits a monthly plan and a tool used once fits a pack. For a first product, pick one simple model, one or two plans, and a price you can explain in a sentence.
What are the main SaaS pricing models?
Most SaaS products use one of a handful of models, or a mix of two. Here is the map I keep in my head.
| Model | How it charges | Fits when | Watch out for |
|---|---|---|---|
| Flat rate | One price, everything included | One clear use case, one type of buyer | Leaves money on the table with heavy users |
| Tiered | Two to four plans with growing limits | Buyers differ in size or depth of use | Too many tiers confuse people |
| Per seat | Price times number of users | Team tools where value grows with headcount | Teams share logins to save money |
| Usage based | Pay for what you consume (credits, calls, minutes) | Costs scale with use, like AI or rendering | Bills feel unpredictable |
| Freemium | Free plan plus paid upgrades | Product spreads by being used and shared | Free users cost server time and support |
| One-time | Pay once for a pack or a license | Value is a single job, not an ongoing habit | No recurring revenue to plan around |
Slack is the classic per seat example. Stripe charges per transaction, which is usage based. Many small tools use tiers with a credit allowance in each tier, which is a hybrid of tiered and usage based.
How do you choose a SaaS pricing model?
Start from how the customer gets value, not from what other companies charge.
The problem: founders copy a pricing page from a bigger company. The cost: the model does not match their product, so customers either feel overcharged or the founder loses money on heavy users. The fix: answer three questions first.
- How often does the customer use it? Daily or weekly use points to a subscription. A job done once, like a report or a logo, points to a one-time pack.
- What does each use cost you? If every action calls an AI model or renders a video, your costs move with usage, so your price needs a limit or credits. If the marginal cost is close to zero, a flat or tiered plan is fine.
- Who pays, and who uses it? If a company pays for a team, per seat or tiered by team size works. If one person pays for themselves, keep it simple and personal.
I run a mix across my own products, which shows this in practice. Most of the products I built are subscriptions with a trial, because people use them every week. One of them sells one-time idea packs, because you validate an idea once, not every month. Two have free plans, because free use is how they spread. Same founder, different models, chosen by how each product is used.
How much should you charge for your SaaS?
Charge based on the value of the job, then check it against your costs.
Start from value, not cost
Ask what the customer would pay to get the job done another way: hiring a freelancer, spending a day on it, or using a bigger tool. Your price should be a clear saving against that alternative. If your tool replaces two hours of work a week, a monthly price far below the value of those hours is an easy yes.
Then check your costs
Add up what one active customer costs you each month: hosting, AI calls, storage, payment fees, email. Your cheapest plan has to cover a heavy user of that plan with room to spare. If it does not, add a limit, raise the price, or move the expensive part into credits.
Avoid the too-cheap trap
Very low prices attract buyers who churn fast and leave you working for almost nothing. A price that is a little uncomfortable to say out loud is usually closer to right. Discounting later is easy; doubling a price is not.
Should you offer a free plan or a free trial?
Both lower the risk for the buyer. They solve different problems.
A free trial gives full access for a fixed time, then asks for payment. It works when the product shows its value quickly and the buyer needs to feel the real thing before paying. Seven or fourteen days is common. A trial with a card upfront converts fewer signups but brings more serious ones.
A free plan never expires but has limits. It works when free users bring in paid users, for example by sharing what they made or inviting teammates. The cost is real: free users use your servers and send support email. Put a clear limit on the free plan, like a number of exports per month, so it stays a taste and not a replacement.
How many pricing tiers should a SaaS have?
For a first product, two or three. One plan is fine too.
Every extra column on the pricing page is another comparison the buyer makes before saying yes. A common shape that works:
- Starter: the core job, with a limit that fits one person.
- Pro: higher limits and the features power users ask for.
- Team or higher tier: only if you actually have teams asking for it.
Make the difference between tiers about one or two things a buyer understands immediately, like the number of projects or the monthly credit allowance. A feature matrix with thirty checkmarks looks thorough and converts worse.
What are the most common SaaS pricing mistakes?
These are the ones that cost solo founders the most time and money.
- Charging nothing for too long. A free beta that never ends teaches you nothing about willingness to pay. Ask for money early, even a small amount. My notes on how to get your first customers go deeper on this.
- Surprising people with a charge. If an action costs credits or money, show the price and ask before it runs. In my own products, any paid action confirms the price first. It prevents angry emails and refunds.
- Pricing for the wrong buyer. A tool for companies priced like a hobby app signals that it is not serious. A tool for hobbyists priced like enterprise software gets ignored. If you are unsure which side you are on, read what B2B SaaS means.
SaaS pricing FAQ
Is a hybrid pricing model a good idea?
Often, yes. A subscription with a monthly credit allowance gives the buyer a predictable bill and protects you when one user runs far more jobs than the rest. Keep the allowance generous enough that most people never think about it.
Should I offer monthly or yearly billing?
Start with monthly, since it is easier to say yes to. Add a yearly plan with roughly two months free once you have a few paying customers: you get cash upfront and the buyer gets a clear discount.
How do I raise prices without losing customers?
Keep existing customers on their current price and charge the new price to new signups. That is called grandfathering. Announce the change ahead of time and explain why in plain words.
Should I show my prices publicly?
For a small self-serve tool, yes. “Contact us” works for big contracts, but for a product people can sign up for alone, a hidden price mostly loses the buyer.
What should you do next?
Write your pricing in one sentence: who pays, for what, how often, and how much. If you cannot, the model is too complex. Then put that sentence on a pricing page with two plans at most, add a trial or a free plan based on how your product spreads, and ask your first users to pay.
If you are still choosing what to build, start with these SaaS ideas or the smaller micro SaaS ideas, and think about the pricing model while you pick. The idea and the price are easier to get right together than one at a time.