Blog
How to price your SaaS before launch: a step-by-step plan for indie builders
A practical plan to set your first SaaS price before launch, from value math and two-tier pricing to asking early users what they would pay and when to raise it.
Nov 21, 2026 · All posts

Pricing is the decision most builders push to "after launch". Then launch day comes, the pricing page says "Free while in beta", and months later nobody knows whether anyone would pay. This guide shows how to price your SaaS before launch in a few focused hours, so your first users meet a real price.
You do not need the perfect number. You need a defensible first number, a way to test it, and a date to revisit it.
Why you should price your SaaS before launch
A price is part of how your product is described. "Free beta" tells people it is unfinished. "$12 a month for freelancers who send more than five invoices" tells them who it is for and what it is worth.
Pricing early also gives you better feedback:
- A free signup tells you someone was curious.
- A paid signup, even a small one, tells you the problem is real.
- A "too expensive" reply tells you exactly who you are talking to and what they compare you with.
Decide what you are charging for
Before any number, pick the unit people pay for. Common choices:
- Per seat - fits team tools where value grows with each person.
- Per usage - fits tools where cost or value scales with volume (emails sent, minutes processed).
- Flat monthly - fits solo tools where one person gets one clear result.
Pick the unit your customer already thinks in. If they say "we have 3 people on support", seats make sense. If they say "we send about 2,000 messages a month", usage does.
Step 1: Do the value math on paper
Write down the result your product gives one customer in a month, then put a rough money value on it.

Start from the value a customer gets, not from your costs.
A simple way to do it:
- Time saved: hours saved per month multiplied by what that person's hour is worth.
- Money earned or kept: extra revenue or avoided losses your tool makes possible.
- Cost replaced: the tool, freelancer, or spreadsheet setup you replace.
Then aim your price at roughly a tenth to a fifth of that monthly value. That range leaves the customer an obvious win while still pricing on value rather than on your server bill.
Your costs only set the floor. If your hosting and API costs are $2 per user, never price below that, but do not use it as the anchor.
Check the alternatives
List the three things your customer would use if your product did not exist, including "do nothing" and "a spreadsheet". Note what each one costs. Your price should make sense next to them: clearly cheaper than hiring help, and worth more than the free option because it saves real effort.
Step 2: Start with two tiers, not five
Big pricing tables are for companies with sales data. Before launch, keep it simple:
- One paid plan that solves the core problem for your ideal customer.
- One higher plan for heavier users (more seats, more usage, priority support).
Optionally add a free trial instead of a free forever plan. A trial keeps the signal clean: people who stay are choosing to pay.
Choose between monthly and annual
Offer monthly first, so trying you is low risk. Add an annual option with a discount (two months free is a common pattern) once a few customers have stayed for more than one billing cycle.
Step 3: Ask early users what they would pay
Your first conversations are the cheapest pricing research you will ever get. If you are still finding those people, the plan in how to get your first 10 users when you build in public shows where to look.

Ask about price on the call, while the problem is fresh in their mind.
On each call, after they describe the problem:
- Ask what they use today and what it costs them, in money or time.
- Show your price and ask, "Would this be an easy yes, a maybe, or a no?"
- If it is a no, ask, "What would make it worth it?" and write down the exact words.
- Offer a founding-user deal: the launch price locked for life if they pay now.
Track answers in a simple sheet with three columns: easy yes, maybe, no. If almost everyone says easy yes, your price is probably too low. If almost everyone says no, check whether you are talking to the right people before you cut the price.
Step 4: Put the price where people decide
A price nobody sees cannot be tested. Show it in every place someone first meets your product:
- Your landing page and pricing page.
- Your product page on launch directories. The checklist in what to put on a product page before a directory submission covers pricing and the rest.
- Your profile on ibuildinpublic builders and your listing in ibuildinpublic products, so other builders and early adopters see what it costs.
Write the price in one plain sentence next to what it includes, for example "$15/month: unlimited projects, weekly reports, email support."
Step 5: Set a date to raise it
Most first prices are too low. Plan for that from day one:
- Put a review date in your calendar, around 60 to 90 days after launch.
- On that date, look at three numbers: trial to paid conversion, churn in the first month, and how often people mention price when they cancel or say no.
- If price rarely comes up as the reason for a no, raise it for new customers and keep early users on their founding price.
Share the change in public. A short post explaining why you raised prices and what you added is good build-in-public content, and it shows the product is growing.
A one-page pricing checklist
- [ ] Unit chosen: seat, usage, or flat.
- [ ] Monthly value per customer estimated on paper.
- [ ] Three alternatives and their costs listed.
- [ ] Two tiers written, plus a trial or not.
- [ ] Price asked about in at least five user calls.
- [ ] Price visible on your site and product listings.
- [ ] Review date in the calendar.
When your price is live, add your product to ibuildinpublic so builders and early users can find it, and browse the blog for the next launch decision.