The pre-launch phase is the 4 to 8 weeks before your public launch. It is the window that separates founders who arrive at launch day with a tested product, a clear message, and an audience from those who arrive with something half-baked and a vague plan.
For indie and solo founders, this phase does not look like a corporate launch plan. You are not coordinating a PR agency, a paid media budget, and a VP of marketing. You are trying to make six weeks of focused work count.
This checklist organizes the pre-launch phase into six weekly priorities. Each week has one main goal. If you run behind, the goal tells you what to protect and what to defer.
Before week one: define what "launched" means
Write a single sentence that completes this: "I will consider this launched when a stranger can..."
For most indie SaaS products, "launched" means:
- A new visitor understands who the product is for and what it does.
- The main workflow runs end to end without breaking.
- Pricing and the signup call to action are visible.
- Someone can pay and get started without your help.
That is a smaller definition than most founders expect. Keep it. You can add features after launch. You cannot undo a launch built on a product that does not work.
Week 1: Sharpen your positioning
The first week is not about building. It is about deciding exactly who you are building for, what problem you solve, and why your answer is better than the current workaround.
Write one sentence using this structure:
[Product name] helps [specific person] [specific outcome] without [painful alternative].
Then answer:
- Who is the first person you want to hear from?
- What is the one thing they need to accomplish immediately after signing up?
- What do they use today instead of your product?
If you cannot answer all three cleanly, your positioning is not ready. Spend the week on this before writing a word of copy.
By the end of week 1, rewrite your homepage headline, subheading, and primary button using these answers. All of your pre-launch copy should repeat the same promise, not introduce new ones on each channel.
Week 2: Validate with real people
Find three to five people who resemble your intended customer. Do not ask your LinkedIn network who "might be interested." Find people who actually feel the problem your product solves.
Ask them to complete the main workflow without guidance. Watch where they hesitate. Record their exact phrasing, not a paraphrased summary. Hesitations reveal product and copy gaps. The exact questions they ask become your FAQ content.
Two things to listen for:
- Where do they say "I thought this would..." followed by disappointment?
- What do they do after they get stuck, rather than pushing through?
Lighthouse Build's pre-launch checklist for indie SaaS recommends running at least five user interviews before launch and treating each hesitation as a product decision, not a user error. That framing is correct.
If you are building a waitlist landing page this week, add two or three survey questions: what tool they use today, what they most want from a new option, and what price range they would consider. These answers shape your launch copy more reliably than any competitor analysis.
Week 3: Get the product to "demonstrably works"
By the end of week 3, a stranger should be able to complete the full core workflow and get real value without your help.
That does not mean every feature is built. It means the essential path works: account creation, the main action, the result, and the exit point that ends a session with something useful accomplished.
This week:
- Run through the entire flow yourself on a fresh account, clearing your session first.
- Fix every broken step. Note everything rough but acceptable and add it to a post-launch backlog you will not touch until after launch.
- Test your payment flow with a real transaction if you are charging at launch. Build Voyage's SaaS pre-launch checklist lists payment testing separately because payment errors on launch day are both common and difficult to recover from socially.
- Set up error monitoring so you know immediately when things break in production.
Do not extend week 3 for features. Rough-but-working beats polished-but-incomplete at every launch.
Week 4: Pricing, copy, and legal
Week 4 is where you turn a working product into a product people can buy.
Pricing. Research what similar products charge. Examine your lowest viable tier: does it cover your real costs? A common pitfall for solo founders is pricing below what the product is worth because the build felt small. A product that saves someone two hours a week is worth meaningful money.
If you are unsure, start higher than instinct says. You can offer a launch discount later. Raising prices after launch is harder. Lowering them sends a negative signal.
Copy. Rewrite everything on your marketing site using the positioning from week 1. Each page should have one primary action. The homepage drives signups. The pricing page drives plan selection. Competing calls to action on the same page dilute both.
Legal. Add a privacy policy and terms of service. A template generator is fine. What matters is that they exist, they say something accurate about your data practices, and they are linked from the footer before you collect a single email address.
Week 5: Prepare your launch assets
This is the week many indie founders realize they have nothing visual to show. Build these now, while time still allows iteration.
Demo video. A screen recording of you completing the main workflow, under two minutes, narrated in your own voice. Edit out the pauses. The goal is showing the product working, not producing a film.
Screenshots. Three to five images of the product in a state showing what the user gets. Avoid empty dashboards with no data. Use realistic example data that reflects how an actual customer would use the tool.
Launch copy drafts. Write the core message you will post on launch day: the email to your waitlist, your first social post, and whatever you plan to share in communities where your audience lives.
A shareable artifact. The launches that spread are the ones that give people something to link to and replay after the initial day. This could be a live demo link, a before-and-after example, or a distinct launch moment people remember. saasrocket.space creates a permanent cinematic replay page and a star on the galaxy map as one way to give your launch a shape that persists past the first twenty-four hours.
Week 6: Final checks and countdown
Week 6 is not for new work. It is for verifying the work already done.
Run through these in order:
- Fresh account flow: create a new account and complete the main workflow without skipping anything.
- Payment: complete a test transaction end to end and check the receipt email.
- Transactional emails: trigger every automated email and confirm it arrives, renders on mobile, and links to the right destination.
- Analytics: verify your key events are firing (signups, first meaningful action, conversions).
- Legal pages: confirm they are live and linked from every page footer.
- Launch assets: verify every link works, every image renders, every post draft is finalized.
If you find a real bug, fix it. If you find something rough but working, write it down and keep moving. Launch day will surface more; save your energy for those.
Two days before launch, send your waitlist a short heads-up: "Launching in 48 hours. Here is what you will be able to do." Nothing more elaborate than that.
What a finished pre-launch phase looks like
By the end of week 6, you should have:
- A product a stranger can use without your help.
- A clear and repeating positioning message across all copy.
- An audience who knows the launch is coming.
- Launch assets ready to post within the first hour.
- A plan for what you will monitor and respond to on launch day.
The launch is a starting gun, not a finish line. Most real feedback comes in the first seven days after launch. Plan to be present and responsive during that window, not recovering from the pre-launch sprint.
For a detailed look at how to structure launch day itself and the two weeks around it, see The 2-Week SaaS Launch Plan for Indie Founders.