Pre-Launch Checklist for an Indie SaaS (2026)
A practical pre-launch checklist for indie SaaS founders. Validate the idea, build the waitlist, run the survey, warm the list, prep the launch email, plan the post-launch loop. Twelve steps, ordered, with the why behind each one.
Posted by
RouzbehRelated reading
How to Add a TestFlight Beta Waitlist to Your iOS App (2026)
A TestFlight beta waitlist is the cheapest way to filter who gets in before you hit Apple's 10,000-tester cap. How to set one up, what two questions to ask on the form, and how to invite people from the list.
Best Product Feedback Tools for Indie Founders (2026)
Best product feedback tools for indie founders in 2026: Canny, Featurebase, Nolt, Frill, Sleekplan and Lighthouse compared on price and fit for a small product.
Waitlist with a Survey: Why Answers Beat Emails (2026)
A waitlist with a survey tells you who signed up, what they want, and what they would pay, before you write a line of code. Why an email-only list is a vanity metric, what questions to ask, and how to read the answers.
Most indie SaaS launches fail before launch day. Not because the product is bad, but because nobody knew it was coming. This is the checklist I wish someone had handed me the first time I tried to ship a web product. Twelve steps, in the order they actually need to happen.
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. The checklist below is the playbook both products run.
Table of contents
Why a checklist (and not vibes)
Building a product and launching it are two different jobs. The first runs on focus and craft. The second runs on cadence and distribution. Indie founders are usually great at the first and quietly bad at the second, which is why so many products ship to crickets even when they are excellent.
A checklist is not a marketing strategy. It is a way to make sure the boring foundational pieces are in place so the launch you actually run lands on prepared ground. Skip them and the cleverest launch tweet has nowhere to send people.
Weeks before launch: validate the idea
The first three steps happen long before you write the first line of production code. If you can, do them before you write a single line at all.
1. Write the one-sentence pitch
Pick the smallest version of what you are building that one real person would pay for. Write the pitch as one sentence. If you cannot, the idea is too vague to validate yet. Indie pitches are often "X for Y people who hate Z". Specificity sells.
2. Talk to five potential users
Five conversations, not a hundred. Ask what they currently do instead of your product and what frustrates them about it. You are not selling, you are listening. If five people in a row cannot articulate a pain you are solving, the idea needs more work. See how to validate a startup idea before writing code for the conversation script.
3. Decide on the goal number
Before the waitlist exists, pick the number that says "yes there is real interest here". 100 signups is the most common indie threshold. It is small enough to be reachable in a few weeks and large enough that you can stop second-guessing whether anyone cares. See how to get your first 100 users for the channel mix.
Get the waitlist up
Steps four through six are about putting a real public page online. This is where most indie founders stall, because the stack feels heavier than it should be.
4. Put a waitlist landing page online
A page with a one-sentence headline, a short paragraph that describes the pain you solve, and a signup form. That is enough. Avoid marketing copy that sounds like marketing copy. Indie audiences smell it. See how to build a waitlist for your app for the layout that converts.
5. Attach survey questions to the signup
An email address is a hint. A survey answer next to it is a signal. Two or three questions on the signup form turn the waitlist from "list of email addresses" into "list of people whose pain you understand". Ask what they currently use, what they want most, and (optionally) what they would pay. More in why answers beat emails.
6. Show a goal counter
A visible "47 of 100 signups" counter on the landing page does two jobs. It tells visitors you have early traction (social proof) and it gives them a reason to share (the bar moves with them). Counters convert better than vague "join the list" buttons.
Days before launch: prep the email
Steps nine and ten happen as the waitlist fills. By this point you have actual people to write to.
9. Draft the launch email
Three sections: a one-line subject that does not look like marketing, two short paragraphs that name what shipped and the problem it solves, and a single clear link. People do not read long launch emails. They scan them. Make the scan path obvious.
10. Stage the launch tweet and post
Write the X post and the LinkedIn post in advance, not on launch day. On launch day you will be debugging something, not writing copy. Schedule or save the drafts. Plain text, no link in the main body for LinkedIn (drop it in the first comment for reach).
Launch day: send and stay close
Step eleven is launch day itself. Keep it small. Do one thing well.
11. Send the launch email and stay online
Send the email to the full waitlist in one batch. Post the social drafts. Then sit at your computer for the next 4 hours and reply to everything that comes in. Bug reports, feature requests, thank-you notes. The replies are worth more than the traffic; they are your first cohort of users actively talking to you.
After launch: feedback loop
Step twelve is the part most checklists skip. The launch is the start of the real work, not the end.
12. Open a feedback page
A simple page where users can report bugs, request features, and say nice things. Triaged in a dashboard, replied to by email. This is what turns the launch into a product that gets better week over week. See best product feedback tools for the lineup.
Frequently asked questions
Do I really need all twelve steps?
No. You need the first three (validation), step 4 (a waitlist page), and step 11 (the launch email). The rest amplify and extend, but the spine is validate, collect, launch. If you only do those four well, you will still beat 80 percent of indie launches that skipped the validation.
What if I am raising capital alongside the launch?
The bottleneck shifts. The launch matters less and the raise matters more. Dedicated tools for investor outreach, like Funding Banker, a curated investor directory with pitch and outreach tracking, become the more important part of the stack. The waitlist still matters for traction proof; the channel mix changes.
How long should the pre-launch phase last?
Four to eight weeks for most indie SaaS launches. Long enough to fill the waitlist, short enough that momentum does not die. If the waitlist stalls at 30 percent of the goal after four weeks, that is a signal the pitch needs sharpening before you build further.
What tools should I actually use for the checklist?
For a no-stitching path: Lighthouse handles steps 4 through 12 in one place (waitlist with survey questions, QR code, newsletter / launch email, feedback page). For a stitched path: Carrd or Framer for the landing, Tally or Typeform for the survey, Mailchimp or Beehiiv for the email, Canny or Featurebase for the feedback. Both work; the stitched path is cheaper to start and costlier to maintain.
When should I write the first line of production code?
After the first five waitlist signups answer the survey questions with answers that make sense for the product you were going to build. Before that, you are guessing. After that, you are validated.
The full checklist looks long. It is twelve steps for a reason: most of them take an afternoon. The hard part is the order, and the discipline to do them before the product is shipped, not after. Indie launches that follow the spine of this list consistently outperform the ones that wing it.
Lighthouse handles steps 4 through 12 in one place: the waitlist with survey questions, the newsletter for keeping the list warm, and the feedback page for after you launch. Free trial, indie pricing. From the same indie dev behind Spaceport, a SwiftUI starter kit for shipping paid iOS apps fast.