To price a SaaS as a solo founder: launch with one paid plan, price it above what feels comfortable, tie it to something that grows as the customer gets more value, and offer an annual option. Then treat that first number as an experiment. You will change it, and nobody will remember the launch price except the customers you grandfather.
Most solo founders underprice for the same reason freelancers do: the number is decided by nerves rather than arithmetic. A low price feels safe, but it attracts the customers who are most expensive to support, and it leaves you needing far more of them than you will get in the first year. This post goes through the decisions in the order that matters.
Your costs set the floor, not the price
Start with the floor, because some products have a real one.
If every user costs you money to serve (AI calls, video processing, storage, SMS), work out what a heavy user costs per month and make sure your cheapest plan clears it with room to spare. AI products in particular can lose money on their most enthusiastic customers, which is the worst kind of success.
For most SaaS the floor is low and not very useful. Hosting a small product for a few hundred users rarely decides the price. So once you know the floor, ignore costs and look at value.
Price against the problem, not against your effort
The question is not "what did this take to build?" It is "what is the alternative costing the customer?"
- If your tool saves a freelancer three hours a month of invoicing, those hours have a price, and it is not $3.
- If it replaces a spreadsheet a team is already living with, the alternative is free, so the value has to be obvious in the first session.
- If it replaces another product, that product's price is the anchor, whether you like it or not.
Write down, in one sentence, what the customer would do if your product did not exist. The price follows from that sentence far more than from any competitor's pricing page.
The small-price trap
Very cheap plans have a problem that is easy to miss: payment fees have a fixed part. A merchant of record that charges 5% plus 50 cents takes 75 cents from a $5 sale, which is 15% gone before tax. Stripe, Paddle or Lemon Squeezy for an indie product has the current numbers.
A low price also sets the customer's expectation of support. Someone paying $4 a month will still email you when something breaks, and that email costs you the same twenty minutes as one from a customer paying $40.
Pick what the price grows with
The pricing metric is the unit the bill scales with. Choosing it well matters more than the exact number, because it decides whether your revenue grows when your customers do.
| Metric | Works well for | The risk |
|---|---|---|
| Flat monthly fee | Tools used by one person, simple products | Your biggest users pay the same as your smallest |
| Per seat | Tools teams use together | Teams share logins to save money |
| Per usage (credits, runs, minutes) | AI, processing, API products | Bills feel unpredictable, which makes buyers nervous |
| Per project or workspace | Agencies, freelancers, multi-client tools | Hard to explain if "project" is fuzzy |
| Tiers by limits | Most SaaS once it has a few hundred customers | Too many limits make the pricing page a puzzle |
For a first launch, flat or simple tiered pricing is almost always right. You can move to a usage metric once you know what heavy use actually looks like in your product.
How many plans to launch with
One paid plan, possibly two. Not three.
Three tiers exist to serve three kinds of customer, and at launch you do not know who your customers are. A single plan makes the pricing page a sentence, makes the decision yes or no, and makes it obvious when somebody asks for something you should charge more for. That request is how you discover the second tier.
Free plan or free trial?
A free trial gives people a fixed time with the full product, then asks for money. It works when the value shows quickly.
A free plan gives people a limited product forever. It works when free users bring you something: they invite paying colleagues, they make content that markets you, or the free product is a real acquisition channel. Otherwise it is a support queue and a hosting bill with no revenue attached.
If you cannot say what your free users bring you, start with a trial.
Offer annual, and price it so people take it
An annual plan gives you cash up front and removes eleven chances a year for the customer to cancel. The common convention is to price it at ten times the monthly price, framed as "two months free". It is a convention, not a law, but customers recognise it, which saves them doing arithmetic on your pricing page.
Do not hide the monthly option to push annual. People who are not sure yet will simply leave.
Write the pricing page plainly
A pricing page needs to answer five things without anyone having to email you:
- What each plan includes, in words the customer uses.
- What happens when they hit a limit: blocked, warned, or charged.
- Whether tax is included in the price shown.
- How to cancel, and what happens to their data when they do.
- Whether there is a trial, and whether it needs a card.
If you sell through a merchant of record, the checkout handles tax. Say so on the page anyway, because "plus tax" surprises at checkout lose sales.
Changing the price later
You will. When you raise prices, keep existing customers on their current price for a fixed period, or permanently if you can afford it, and tell them in one plain message with a date. New customers simply see the new price. The same principle applies to freelance rates, and how to raise your freelance rates without losing clients walks through the wording.
Discounts are a separate decision, and a dangerous one for a small product. If you are thinking about a sale this month, read Black Friday for a SaaS without training buyers to wait first.
The honest summary: the right price is the one some people say no to. If nobody ever objects, you have not found it yet.