How to Price Your First Indie SaaS (2026)

Pricing is the launch decision most indie founders punt on until the day of the launch, and then pick a number that “feels right” in the last hour. The number usually ends up too low, because too-low feels safe. Too low is not safe. It caps the revenue ceiling of the product, filters the wrong customers in, and locks you into a price you cannot raise without churning the customers you fought to sign up. This is how I now think about pricing an indie SaaS at launch.

I have shipped 7 indie apps over 8 years and ended up building two tools for myself along the way: Spaceport, a SwiftUI starter that gets a paid iOS app live in days, and Lighthouse, the launch toolkit this post is mostly about. Both got the pricing wrong at launch. The shape below is what I would run now.

Table of contents

• Why pricing is the launch decision founders punt on
• The three pricing shapes that work for indie SaaS
• How to pick the actual number
• The four mistakes that consistently kill first pricing
• How to raise prices later
• Frequently asked questions

Why pricing is the launch decision founders punt on

Pricing feels hard because it is a decision under uncertainty. You do not know what people will pay for the thing you have not launched yet. Every other launch decision has a right answer somewhere; pricing has a range of defensible answers and the founder has to just pick one.

The instinct is to delay by picking a low number as a placeholder, launch, and “raise later once we know more.” Raising later is materially harder than picking the right number now. The customers you sign up at $5 a month talk about “the $5 tool”; the reviews reference the price; the anchor is set publicly. Better to spend an afternoon picking a real number than months trying to unwind a placeholder.

The three pricing shapes that work for indie SaaS

Three pricing shapes cover almost every indie SaaS launch. Pick one; do not try to be all three.

1. Flat monthly, single tier

One price, one plan, everyone pays the same. “$19 a month, all features included.” Works when the product is small and focused enough that tiering would feel artificial. Sells fast because there is no decision beyond “yes or no”. The Lighthouse-style shape; also the shape early Basecamp ran and a lot of $19-$39 indie tools stick with.

Best for: solo makers, single-feature-focus products, audiences who value simplicity over customisation.

2. Two-tier: cheap and pro

Two plans. The cheap one gets you started; the pro one unlocks something specific (higher volume, API access, custom domain, priority support). “$19 Starter, $29 Pro.” Works when there are two distinct customer shapes and the pro-plan differentiator is a real feature, not an artificial cap.

Best for: products with a real power-user segment, products where an API or an integration is a natural pro differentiator, audiences with mixed sophistication.

3. Usage-based

The price scales with something the customer does (rows processed, emails sent, API calls). “$0.001 per call, minimum $9 a month.” Works when the value genuinely scales with usage and the customer already thinks in units.

Best for: developer tools, infra products, high-volume processing tools. Almost never the right shape for a first indie SaaS unless the product is infrastructure-shaped from day one.

The right shape for a first indie SaaS is almost always (1) or (2). Usage-based is a footgun at launch because you are pricing something you do not yet know the shape of.

How to pick the actual number

Three complementary methods. Use all three; pick a number in the overlap.

Method 1: The reference-tool anchor

List three to five tools your customer would consider alternatives to yours, whether direct competitors or adjacent categories. Note their prices. Your price should usually sit in the range or slightly below the cheapest of them. Not 90 percent below; that reads as “something is wrong with this one.”

Concrete example: for a waitlist tool, the reference set is Kit ($15+), MailerLite (free tier then $9-$29+), Beehiiv ($0-$42+). A defensible flat price is $19 (Lighthouse) or $29 with API. Below $15 reads as toy.

Method 2: The value-of-what-is-replaced calculation

If your product replaces something, name that something and its cost. “Replaces Kit ($15) + Tally ($29) + Canny ($99). Total: $143. Charge $29 for the bundle.” The bundle price should feel like a real discount off the sum, not a rounding error.

Method 3: The waitlist-survey willingness-to-pay

If your waitlist survey asked “what would you pay for this?” with a multiple-choice ($9 / $19 / $29 / $49), the modal answer plus the immediate next tier is your anchor range. Do not use the mean; the mean is pulled down by protest votes. Use the mode and the next step up. For why waitlist survey answers matter beyond pricing, see why answers beat emails.

Where the three methods overlap is a defensible price. Pick the higher end of the overlap; you can always give an intro discount, but you cannot claw back the sticker price.

The four mistakes that consistently kill first pricing

Every indie founder makes at least one of these on the first launch. Worth naming so you can skip them.

• Underpricing to be “affordable”. $5 a month feels friendly. It is not friendly; it is a signal to serious customers that you do not know what the product is worth. Serious customers will pay $19 or $29 without blinking; the $5 tier attracts the hobbyist segment that also churns fastest.
• Overpricing to signal quality. The reverse mistake. $99 a month for a product that competitors sell at $19 does not signal quality; it signals “this founder does not know the market.” Quality-signalling only works if the product genuinely justifies the delta.
• A free tier that never converts. “Free forever up to 500 subscribers.” Sounds friendly at launch, drains support time forever after. Free-tier conversion rates for indie SaaS are typically 1 to 3 percent. If free is 90 percent of your users, you are supporting them for zero revenue. A 7-day trial or a free-first-month offer converts much better than a free-forever tier.
• Discount codes at launch. “25 percent off with code LAUNCH25” reads as desperation, teaches the audience to wait for discounts, and permanently anchors the price 25 percent below sticker. Charter-price offers ($9 forever for the first 50) work differently and honestly; a percent-off code does not.

How to raise prices later

Even a well-picked first price is a first price. Twelve to eighteen months in, most indie SaaS founders realise the price should have been higher. Raising is doable and standard, if you do it clean:

• Grandfather existing customers. Anyone on the old price keeps it forever. This costs almost nothing (existing customers churn eventually anyway) and buys enormous goodwill. Announce it in the price change email as a specific promise: “You will never be moved to the new price.”
• Give notice. Two to four weeks before the new price starts. Non-customers who were on the fence often convert in the notice window; that is a feature, not a coincidence.
• Do it once, not gradually. One clear jump ($19 to $29) reads as a real product decision. Three small jumps in a year ($19 to $22 to $25 to $29) reads as testing on customers, which is what it is.
• Name the reason honestly. “We're raising to $29 because the product now includes X and Y and we want the pricing to reflect what it actually is.” Skip the corporate “evolving with our customers” language.

Frequently asked questions

Should I have a free tier at all?

Usually no, at least not at launch. A 7-day trial (card collected, $0 for 7 days, auto-charges on day 8) converts 5 to 10x better than a free-forever tier and filters out the customers who never intended to pay. If the product has genuine viral characteristics (the more users on it, the more valuable it becomes for everyone), then a free tier makes sense. For most indie SaaS, it does not.

Monthly, annual, or both at launch?

Monthly first, add annual later. Annual is a lower churn signal but only worth adding once you have the monthly baseline working. Two months free on annual (charge for 10, get 12) is the standard indie shape.

What if I am raising capital alongside launching?

The pricing decision does not change much because you are raising; if anything, investors read higher prices as a stronger business signal, not a weaker one. The investor side runs on a separate track. Dedicated platforms like Funding Banker, a curated investor directory with pitch and outreach tracking, handle the raise itself. Price for the product; do not price to look venture-scale.

Should I run a Product Hunt discount?

Discount codes at launch are usually a mistake, per the mistake list above. If you want a launch-day offer, use a charter shape (“first 100 people get $9 forever”) instead. It creates real scarcity, does not train the audience to wait for discounts, and the customers who sign up are the highest-intent ones.

How does pricing fit the launch sequence?

The pricing decision has to be locked in before the launch email goes out, because the email should name the price in the body. Ambiguity about the ask is friction the reader has to resolve before clicking. For the launch email shape, see how to write your first launch email. For the full conversion sequence around it, see how to convert waitlist signups into paying customers.

Pick a shape (flat, two-tier, or usage). Pick the number using the reference-tool anchor, the value-of-what-is- replaced calculation, and the waitlist willingness-to- pay. Skip the underprice-to-be-friendly and the discount-code trap. Pricing is one afternoon of real work, not a placeholder you fix later.

Lighthouse gives you the waitlist survey (where willingness-to-pay questions live), the launch email (where the price lands), and the newsletter after (where the price change eventually gets announced), in one place. Free trial, indie pricing. From the same indie dev behind Spaceport, a SwiftUI starter kit for shipping paid iOS apps fast.