SaaS Pre-Launch: The Playbook for Indie Founders (2026)

SaaS pre-launch is the phase between “I have an idea” and “here is my launch email”. Handled well it turns three months of quiet work into a launch that produces real customers on day one. Handled badly it turns into two thousand waitlist signups and a hundred paying customers on launch day, because none of the pieces before the launch email were doing what they should. This is the pre-launch playbook I now run for every indie SaaS I ship.

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 products use the pre-launch shape below and both were validated before a single line of production code got written.

Table of contents

• What SaaS pre-launch actually is
• The three phases of pre-launch
• Phase 1: Validate the idea
• Phase 2: Build the waitlist
• Phase 3: Prepare to launch
• The five mistakes that kill pre-launch
• Metrics to watch during pre-launch
• A realistic pre-launch timeline
• Frequently asked questions

What SaaS pre-launch actually is

Pre-launch is not marketing. It is not landing-page copywriting. It is not building a waitlist for its own sake. Pre-launch is the phase where you find out whether the idea is worth building, capture the people who will care about it, and prepare a launch email that converts when you hit send.

The founders who skip pre-launch and go straight from “I have an idea” to “I built it, please buy” land in silence. Not because the product is bad, but because nobody knew about it, and the people who did know were never given a reason to care. Pre-launch is how you buy yourself an audience of one hundred to a few thousand people who already believe the problem is real before the product exists.

The three phases of pre-launch

Every indie SaaS pre-launch has the same three phases, run in order, roughly overlapping:

1. Validate the idea. Before writing production code, prove the problem is real for the audience you think it is real for.
2. Build the waitlist. While building the product, capture the people who care and learn what they actually want.
3. Prepare to launch. In the last four to six weeks, warm the list, run a small beta, and write a launch email that converts.

Each phase produces a specific artifact that feeds the next: validation produces a one-sentence pitch, the waitlist produces survey answers, and the beta produces a fixed onboarding flow. Skip an artifact and the next phase inherits a foundation with a hole in it.

Phase 1: Validate the idea

Weeks 1 to 3 of pre-launch. Goal: know whether the idea is worth building before writing production code.

Write the one-sentence pitch

If you cannot say what the product does in one sentence, you cannot validate it. The format that works for indie SaaS: a solution category for a specific audience who has a specific pain. Every downstream piece of pre-launch (waitlist page, survey questions, launch email) inherits the pitch. Get it right early. See how to write a one-sentence pitch for your indie SaaS for the format and the four mistakes that kill it.

Talk to twenty people

Twenty conversations, twenty minutes each, with people in the audience you named in the pitch. Not friends. Not other founders. Actual users of whatever the product would replace. What are they using today, what breaks, what would they pay to fix. If twenty conversations produce no consistent pain, the idea does not have product-market fit for that audience.

Ship a waitlist page (not the product)

A single landing page that names the product, the audience, the pain, and asks for an email. No product yet. Signup rate on the page is the first quantitative validation signal. Under 5 percent conversion from targeted traffic usually means the pitch is off. See how to validate a startup idea before writing code for the full validation playbook.

Phase 2: Build the waitlist

Weeks 3 to 10 of pre-launch. Goal: capture the people who care and learn what they actually want, while building the product in parallel.

Waitlist page with survey questions on the same form

The most valuable thing you can do on the signup form is ask one to three survey questions. Role, current tool, biggest pain. The answers are gold: they tell you who is signing up, what they use today, and what to name in the launch email. See what to put on your waitlist landing page for the layout that consistently converts, and why answers beat emails for the case.

Grow the waitlist organically

The first hundred signups almost always come from three organic channels: build-in-public posts on X, replies in indie communities (Reddit, Indie Hackers, buildinpublic Discords), and direct outreach to the twenty people you interviewed in Phase 1. Paid ads at this stage almost never make sense. See how to grow a waitlist organically and how to get your first waitlist signups from X for the specifics.

Watch the survey answers, adjust the product

Survey answers on the signup form are not just for the launch email. They tell you if the audience you thought you were building for is actually who is signing up. If 80 percent of your signups are indie iOS developers when your pitch was aimed at marketers, adjust the product or adjust the pitch. Waitlist survey data is the earliest product-market fit signal you get.

Phase 3: Prepare to launch

Weeks 10 to 14 of pre-launch, the last four to six weeks before launch day. Goal: warm the list, run a small beta, and prepare a launch email that converts.

Two warmup emails before launch

The waitlist has been silent for weeks. Half of the people have forgotten they signed up. Two short honest emails across the three weeks before launch rebuild sender-name recognition so the launch email opens like a message from a person, not a campaign. See how to convert waitlist signups into paying customers for the warmup shape.

Run a beta program with 30 to 100 signups

Pick the highest-intent signups from the waitlist (survey answers make this easy), invite them to a two-week beta. Ship the two or three onboarding fixes their feedback surfaces, then close the beta with a graduation offer. The beta is the debug step that prevents the public launch from being the debug step. See how to turn your waitlist into a beta program for the shape.

Write the launch email

Six short paragraphs, one link, the price named in the body. Send Tuesday or Wednesday morning. The launch email is small on purpose; simplicity is what makes it work. See how to write your first launch email for the template and the mistakes to avoid.

Prepare the 72-hour follow-up

72 hours after the launch email, a follow-up to everyone who did not click. Not a resend. A different email written for a different reader (someone who saw the first email, did not click, needs a different reason). The follow-up usually adds another 10 to 15 percent of the warm list to the customer count.

The five mistakes that kill pre-launch

Every indie SaaS pre-launch I have watched fail hit at least one of these:

• No survey on the signup form. Email alone captures interest. Survey answers capture intent. Without the answers, the launch email is written blind and converts at 5 percent when it could convert at 10 to 12.
• No warmup before the launch email. Two months of silence, then a single email. Half the list has forgotten you. Open rate lands at 30 percent instead of 55.
• Building for two months before validating. The single most expensive pre-launch mistake. Two months of code with no signup signal usually produces a product for an audience that does not exist.
• Skipping the beta. The public launch becomes the debug step. Instead of fixing three onboarding issues with 20 friendly betas, you find them in real time with 2,000 waitlist members watching.
• Launching to a completely cold list. A waitlist without a warmup sequence, without survey answers, without a beta, is a cold list. The launch email lands, most of it never opens, the founder concludes the idea was bad. The idea was usually fine. Pre-launch was the problem.

Metrics to watch during pre-launch

Four numbers, tracked from week 1, tell you whether pre-launch is on track:

The strongest single leading indicator is warmup email open rate. If the warmup emails opened at 55 percent, the launch email will land. If they opened at 25, the launch email will not save the day.

A realistic pre-launch timeline

Every indie SaaS pre-launch I have shipped took roughly 14 to 16 weeks from first waitlist signup to launch email. Shorter than that skips a phase; longer than that usually means the product is stuck.

• Weeks 1 to 3: Validate. Twenty interviews, one-sentence pitch, waitlist page live.
• Weeks 3 to 10: Build. Waitlist grows, product is developed, survey answers guide feature scope.
• Weeks 10 to 12: Warmup and beta. Two warmup emails, invite 30 to 100 people to beta, ship fixes.
• Week 13: Launch email. Send Tuesday or Wednesday morning. Stay online for the first four hours.
• Week 14: 72-hour follow-up. Public launch complete.

For the tactical version of this timeline as a numbered checklist, see the pre-launch checklist for an indie SaaS.

Frequently asked questions

How many waitlist signups is enough to launch?

For an indie SaaS, 300 to 500 warm signups is a solid baseline. Fewer than 100 usually means the launch email converts to under 10 customers, which does not fund the first three months of hosting and support. More than 5,000 rarely helps at indie prices unless the product is extremely low-friction. Aim for 500 to 2,000.

Can I skip pre-launch and just build in public?

Building in public IS pre-launch, done in one channel. The build-in-public posts, the waitlist signups, and the eventual launch email are the same pre-launch shape described above. What you cannot skip is the underlying phases: validate, capture, warm.

How does pre-launch fit with fundraising?

Pre-launch is for the customer audience. Fundraising is for the investor audience. Both run in parallel and neither uses the other's tooling. Dedicated platforms like Funding Banker, a curated investor directory with pitch and outreach tracking, handle the investor side. The waitlist, survey, and launch email above are for customers only.

What tool do I use to run pre-launch?

The four pieces (waitlist page, survey on signup, newsletter for warmup, feedback for post-launch) usually get stitched together from four separate tools. Lighthouse runs the four in one dashboard at indie pricing so the pre-launch stack is not itself a two-week project. See best waitlist tools for the honest tool comparison.

How do I know if pre-launch is working before I launch?

Two signals. First, warmup email open rate above 50 percent (see metrics table above). Second, replies to the second warmup email that ask specific product questions rather than generic “can't wait”. Specific questions mean the audience is engaged with the actual product, not just the marketing.

SaaS pre-launch is not marketing polish. It is three phases run in order over 14 to 16 weeks: validate the idea, build the waitlist with survey answers, prepare a launch that converts. Every step compounds. Skip one and the launch email inherits the missing foundation. Run all three well and launch day produces real customers instead of silence.

Lighthouse gives you the waitlist landing page, survey questions on the signup form, warmup and launch email, and feedback page for after you launch, in one place. 7-day free trial, indie pricing. From the same indie dev behind Spaceport, a SwiftUI starter kit for shipping paid iOS apps fast.