How to Price Your First SaaS Product When You Have No Customers Yet

Quick answer: Your first price is a hypothesis, not a verdict. Set a cost floor, estimate the value ceiling, and map what buyers already pay. Launch one plan inside that overlap, then learn from real payments.

You have a working product and an empty pricing page. Every guide says "talk to customers and test," but there is nobody to test with yet. Founders raise this exact problem on Indie Hackers and in r/SaaS again and again.

This guide gives you a method you can finish in an afternoon. It also covers the cost that now catches many indie founders off guard: AI and API usage.

At a glance

Make three decisions before you pick a number

Most pricing confusion comes from mixing up three separate questions.

• Get the metric wrong and no number will rescue it.
• A tool one person runs for a team should not charge per seat.
• Metered costs and unlimited flat pricing do not mix.
• Still unsure who the buyer is? Validate your SaaS idea first.

Pick a pricing shape that fits launch

Choose the simplest shape your product allows.

Several r/SaaS founders give the same advice: start with one plan and build tiers from real usage.

The three numbers that frame your price

Each number answers a different question. You need all three.

1. Find your cost floor

List only the costs that grow with each account.

• Payment processing fees (check your provider's current published rates)
• Hosting, database, and storage that scale with usage
• Third-party APIs, including AI model calls
• Per-message services such as email or SMS
• A realistic share of your support time
• Refunds and failed payments

One founder described nearly launching "unlimited" usage, then realising a single heavy user could cost far more than they paid.

• Estimate cost per action.
• Multiply by a heavy user's plausible monthly use.
• Set plan limits that keep you profitable.
• Treat the floor as a minimum, never a target.

2. Estimate the value ceiling

Ask what it costs the buyer to leave the problem unsolved.

• Time: hours per week on a manual workaround
• Money: lost revenue, or a tool or contractor paid today
• Risk: errors, missed deadlines, compliance trouble

You won't charge all of it. It tells you whether $9, $49, or $299 is the right neighbourhood.

3. Map the market reference

List three to five things your buyer would use instead of you.

• Include competitors, adjacent tools, spreadsheets, freelancers, or doing nothing.
• Record each published price with its URL and the date checked.
• Mark "contact sales" as unknown; don't guess.
• A price far below everything can read as a toy.
• Pricing above the range needs a reason buyers see quickly.

Ask better pricing questions

With no customers, you can still talk to 10 to 15 people who match your buyer.

For a structured range, the Van Westendorp method asks at what price the product feels too expensive, expensive but acceptable, a bargain, and suspiciously cheap. Here is one practical walkthrough.

• Treat answers as reported opinions, not demand data.
• Use them to find a range.
• Only a payment tells you what is true.

Worked example (hypothetical)

Every figure in this section is hypothetical, chosen only to show the method.

A founder builds a tool that drafts client status reports for small marketing agencies.

• It clears the floor.
• It sits inside the familiar range.
• It's a small fraction of the estimated value.

The framework, step by step

1. Define one narrow buyer.
2. Choose the pricing metric.
3. Calculate the cost floor, including heavy users.
4. Estimate the value ceiling.
5. Map three to five alternatives with links and dates.
6. Run 10 to 15 buyer conversations.
7. Pick one plan inside the overlap.
8. Charge real money early.
9. Write down what would change the price.

How to charge real money early

Prefer offers where money actually changes hands.

• A paid pilot for a fixed period
• A pre-order or deposit
• A founding-customer price with a stated end date or seat limit

Be careful with lifetime deals when each customer creates ongoing AI or API costs. Year two still costs you money.

Pre-launch pricing checklist

• Buyer described in one sentence
• Pricing metric chosen and justified
• Cost floor calculated for a heavy user
• Usage limits set on metered features
• Value estimate written down
• Alternatives listed with URLs and dates
• One plan on the pricing page
• Trial length and end point decided
• Introductory price end date stated
• Review date in your calendar

Common mistakes and their fixes

Signs to change your price

Decide these before launch so you react to evidence, not nerves.

• Raise it: most trials convert and nobody hesitates on price.
• Raise it: buyers call it cheap.
• Fix messaging, not price: sign-ups but no activation.
• Fix the page, not price: visitors but no trials. See why launches get visitors but no signups.
• Review on schedule: after the first 10 paying customers or 30 days.

FAQ

Should I offer a free tier at launch? Often not. A time-limited trial that ends just after the main result usually teaches you more.

How do I raise prices without upsetting early customers? The common, low-drama approach is new prices for new customers. Give existing ones notice or keep their rate.

Is a lifetime deal a good way to start? Only if each customer costs you little to serve over time. Ongoing AI or API costs make it risky.

Your next step

Write three lines today: your cost floor, your value estimate, and the reference range with links. Pick one plan inside the overlap and put it on your pricing page. Add it to your SaaS launch checklist, and when the page is ready, submit your product to IndieNeed.