SaaS Pre-Launch Marketing Playbook: 0 → 1,000 Beta Users in 90 Days (2026)

Published April 30, 2026Updated November 2, 202623 min read

Ask AI

TL;DR: A SaaS pre-launch plan that can reach 1,000 beta users in 90 days has four phases: sharpen the positioning and ship a waitlist page with a referral loop (days 1 to 21), build an audience by publishing and talking to people (days 22 to 50), earn trust in communities and with partners (days 51 to 75), then spend the last two weeks on a launch-week build-up that turns the list into users. Treat 1,000 as the goal the plan works toward, not a result anyone can promise: it depends on your market, your price and how well the product fits. Every phase below has concrete actions, an example, and what to measure.

Most pre-launch marketing for SaaS fails for a dull reason. The founder tries ten channels for two weeks each, sees nothing compound, and ends up soft-launching to a quiet room. The plan below does the opposite: few channels, one list, and a weekly habit of looking at the same handful of numbers.

For the checklist version of this work, use the pre-launch marketing checklist. This page is the plan around it: what to do when, and why. You will find no conversion benchmarks here: they vary too much by audience, price and traffic to be worth borrowing, so the plan has you set your own baseline instead.

Before day 1: pick a customer and a definition of "beta user"

Two decisions save you weeks.

Pick one customer. "Teams" is not a customer. "Freelance designers who invoice clients in more than one currency" is. A narrow first customer makes every later step easier: you know which communities to read, what to write about, and whose email would be worth getting.

Define a beta user. If you count every email address, 1,000 is a vanity number. A useful definition is someone who confirmed they own their address, matches the customer you picked, and has done at least one thing since signing up: replied, answered a question, shared their link or booked a call. Track total signups and engaged signups side by side, plus signups by source, the share of visitors who sign up, the share who confirm, and the share who refer someone. Set your baseline for each in the first three weeks, then beat it.

Phase 1, days 1 to 21: positioning and the page

The goal of the first three weeks is a live waitlist page, a working referral loop, and a first batch of signups from people who know you. Do not start distribution yet.

Write the promise before you write the page

Fill in this sentence and read it to someone who does not know your product: "[Product] helps [specific customer] [do a specific thing] without [the pain they have now]." If they cannot tell you who it is for and what they would get, rewrite it. A weak sentence here costs you in every channel afterward, because every post, email and DM borrows from it.

Then write the headline from the outcome, not the technology. "AI-powered workflow platform" tells nobody anything. "Close your books on day two of the month" (an invented example) does.

Ship a page with one job

A pre-launch page has one job: get an email address (or whichever identity your customer prefers) from the right person. A working structure:

A headline that names the customer and the outcome.
One or two lines of explanation and a product screenshot, mockup or short clip. A real image beats a stock illustration.
One signup field and one button.
A line saying what signing up gets: early access, a founding price, a say in what you build.
After signup, a screen with the person's referral link and place in line.

Leave out the navigation bar, the pricing table and the feature grid. If you need ideas, the waitlist landing page examples post breaks down real pages. If you are choosing between a page we host and a form on your own site, the hosted vs embedded comparison covers the trade-off.

LaunchList's waitlist landing page builder is the shortest path if you want a hosted page with referrals already attached; the SaaS-specific setup, including the form fields and the invite flow SaaS teams use, is on the waitlist for SaaS page. One detail worth knowing before you point traffic at it: a hosted page on a launchlist.page address stays out of search results until you switch on search indexing, which is available on the Collect plan and above; a page on your own domain is open to search by default (the launch page docs explain both). If you want the page to rank for your topic, put it on your own domain.

Turn the referral loop on before the first visitor

Every signup you collect before the referral loop exists is a missed chance to be shared. Give each signup a unique link and a visible place in line before you invite anyone. The mechanics, and why a reward must wait for a confirmed address, are in the referral program guide and the viral coefficient guide. Dropbox's version of this is the canonical story, and our case study separates what is documented from what is repeated as folklore.

Your first 30 to 50 signups come from people who know you

Message people individually. A short note to a former coworker, a customer from a past job or someone from a community you already belong to works better than a broadcast post. Use this shape:

Hi Dana, I'm building [one line: what it does for whom]. You mentioned [specific thing] last month, which is exactly what it's for. I'm collecting a small first group of people for early access. Want me to add you? If not, I'd still value 10 minutes to hear how you handle it today.

Notice the second ask. In the early weeks, the conversation is worth more than the signup, because it tells you whether your headline matches how real people describe the problem. Our guide to customer discovery interview questions has the questions to bring. For a more detailed plan for these first signups, see how to get your first 100 waitlist signups.

What to measure in phase 1

Signups, and where each came from. Tag every link you share with UTM parameters (for example ?utm_source=linkedin&utm_campaign=week2) from day one, so source data exists when you need it.
The share of visitors who signed up, once you have a few dozen visits; a handful tells you nothing either way. If almost nobody signs up, change the headline before you add traffic.
The confirmed share, and the share who refer anyone.
Conversations booked, and the three phrases people used most to describe the problem. Those phrases are your next headline.

Phase 2, days 22 to 50: audience and content

By day 22 you have a baseline and a page that works. Now build an audience that does not depend on your personal network. Pick two channels and stay on them for the whole phase.

Choose channels by where your customer already is

Eight channels cover most SaaS products. Choose the two where your customer reads, not the two you enjoy.

Channel	Works best when	The rule that matters
X or Bluesky build in public	Developers, indie founders, makers	Show real work: a screenshot, a decision, a mistake. Not "join my waitlist" every post
LinkedIn posts	B2B, operators, marketers, finance and sales roles	One lesson per post, written from your own experience
Reddit	Almost any niche with an active subreddit	Read the rules, answer questions for a couple of weeks first, never drop a bare link
Indie Hackers and similar communities	Founders as customers	Post real numbers and real teardowns, not promotion
Newsletters	Any niche with a good newsletter	Ask whether a short feature or swap fits, rather than start with a paid slot
Podcasts	Products with a strong point of view	Pitch what you will teach, not your product
Directories and launch boards	Almost everyone, as a small steady source	Use the ones that fit your product; the guide at /directories lists what each one is and what it asks
One-to-one outreach	Narrow B2B customers you can name	Fewer, more personal messages beat a long list

Measure each channel with the tagged links from phase 1 and double down on the one that produces signups who confirm, refer and reply.

For a longer list of ways to promote a waitlist, with one tactic per channel, see how to promote your waitlist. If you want to be published on a regular schedule without it taking over your week, build in public covers a cadence that holds up.

Publish what your customer would search for

Three formats do most of the work for a SaaS product with no users yet:

The problem, explained well. One piece a week that helps your customer with the problem you are solving, with no product pitch in the first screen. If your customer would search for it, it can keep bringing traffic after launch.
Behind the build. One post a week on a real decision: why you cut a feature, what a customer said that changed the design, what surprised you. This is what people forward.
A comparison done honestly. Customers will compare you with existing tools anyway. If you write it first and are fair about where the other tool is better, readers trust the rest of your page.

Email the list, and write like a person

Send one short email every week or two with one piece of real progress, and include each person's position and referral link. Wording is in these waitlist email templates. In LaunchList, broadcasts start on the Collect plan and automated emails on the Launch plan; the Free plan has no campaign email.

Keep the list clean while it grows

New waitlist URLs attract bots quickly. Turn on email confirmation, rate limiting and a honeypot field in whichever tool you use, and review suspicious signups before you count them.

What to measure in phase 2

Signups per channel per week, and for each channel the confirmed share. A channel that produces many signups who never confirm is giving you the wrong people.
The share of signups who share their referral link at least once.
Replies to your weekly email. Replies are a better signal of interest than anything else you can count, and you can read every one at this scale.
Hours spent per channel. If a channel eats a day a week and yields little, stop it. The goal is to find two that work.

Phase 3, days 51 to 75: community and partnerships

By day 51 you should know which channels produce engaged people. This phase is about earning trust where your customer already spends time, and about people who can introduce you.

Be useful in two or three communities, then ask

The pattern that works is slow. Join the communities where your customer asks for help (subreddits, Slack and Discord groups, forums, Indie Hackers). Spend a couple of weeks answering questions without mentioning your product. After that, post something that is useful on its own, such as a short teardown of how you solved a problem, and mention the waitlist once, honestly, as the thing you are building. Check each community's rules on self-promotion first and follow them; getting banned from the one place your customer hangs out costs more than any post earns. Datadab makes the same point for B2B: buyers trust review sites, Reddit threads and peer communities more than anything you say about yourself, so show up there to correct misconceptions, not to sell.

Run a small beta now, not on launch day

You do not have to wait until day 90 to let anyone in. Use phase 3 to start a small rolling beta with your most engaged people. Invite a handful, watch what they do, and fix what they trip on. This does three things at once: it gives you real feedback while you can still act on it, it creates the first testimonials and screenshots you can use legitimately, and it keeps the waitlist moving, which makes later emails more believable.

Choose who gets in first by evidence: the people who replied to your emails, referred others, answered your survey or told you in a call that they would pay. In LaunchList, open Audience, Invites, press Invite people and enter a number: it invites that many subscribed people with the most referrals first, each with a personal code by email (early access docs). If you want to choose people yourself, pick them from the signups list instead. For the longer version of this, including how to move from beta to paid, see how to find beta testers and convert your waitlist to paying customers.

Find partners who already have your customer

A partner is anyone who talks to your customer regularly and does not compete with you: a newsletter author, a consultant, a tool that sits next to yours, a community organizer. A good pitch is specific and gives them something:

I'm building [product] for [customer]. I noticed your readers often ask about [problem]. I'd like to offer your audience early access with a code you control, and I'm happy to write something useful for them. Would that be of interest?

Offer value first. A short guest post, a free teardown, early access for their audience with a code they can share, or a feature that fits their product all work better than "can you share my waitlist?". For a partner you want a separate code or link so you can see exactly what that relationship produced. LaunchList's shared invite codes with a seat limit are made for this, and they are available on the Launch plan and above.

Test a price before launch

Ask the engaged people on your list, in a call or one short question, what they pay for something similar now and what they would pay for this. See how to price a SaaS before launch and how to pre-sell a SaaS. A free signup is a hint. A pre-order or a paid pilot is evidence.

What to measure in phase 3

How many beta users invited have actually used the product, and what they did first. A beta that people sign up for and never touch is a warning you want in week 9, not at launch.
The sources of your best signups, now that the first batch has a few weeks of behavior to look at.
What partners produced, per code or link.
How many people said they would pay, and at what price.

Phase 4, days 76 to 90: the launch-week build-up

The last two weeks turn the list into users. The work is mostly preparation and email.

Day 76 to 82: fix the date and prepare the assets

Pick the date. Choose a day you can be fully present for, and avoid days when your customer is least likely to read email. Tell the list the date now.
Pick your launch venues. Product Hunt, Hacker News, relevant subreddits, your communities, launch boards. Check each venue's current rules; some do not allow asking for upvotes, and some treat a thin account as a reason to bury a post. Hacker News's Show HN rules are short and worth reading before you plan anything around that site. Our guide to where to launch lists the launch platforms and directories we have checked, and launch boards covers the ones aimed at new products. If a directory such as BetaList is on your list, check its current terms on its own site before you plan around it, since pricing and review times change.
Prepare the assets. A short demo video or clip, three to five screenshots, a one-paragraph description, a founder note, and a plain explanation of what the waitlist gets for waiting. The Product Hunt checklist and the SaaS launch checklist cover the details.
Line up supporters, one by one. Message the people who have helped, in person, with a specific ask and the date. A mass "please upvote" message looks exactly like one.

Day 83 to 87: warm the list

Send two emails. The first tells the list the date and what is launching. The second, a couple of days before, gives them one thing to do on launch day: try it, share it, or send a question. If you are inviting people early, send those invites to your most engaged people now.

If you are sending campaign email from your own domain, set up and authenticate it well before this week and send small, regular messages first, so the launch email comes from a sender that mailbox providers already know. A new domain that suddenly sends a large batch is a common way to land in spam.

LaunchList's Launch Day screen (Launch and Grow plans) gives you a launch countdown and checklist, a Go live button and ready-made share posts for the day (launch page docs).

Day 88 to 90: launch, then answer everything

On the day, be around and answer every comment. Post in communities where you already have a presence, not new ones. Email the list, open the beta to the next group, and give the waitlist a reason for having waited: a founding price or priority support, with an end date you keep. Have the first-week emails and calls with early users scheduled in advance.

What to measure in phase 4

Signups in launch week and where they came from.
How many invited people activated, meaning they did the first useful thing in the product.
Replies and support questions, which will tell you more than any dashboard.
For the plan as a whole: total signups, engaged signups, and how many of the engaged ones are now using the product. The first is the headline number. The last is the one that matters.

Running the plan on one list in LaunchList

The plan works with any tools. The reason to keep it on one list is practical: the people you collect on day 3 are the people you email on day 85 and invite on day 88, with no exports in between. Here is where each job sits, and the plan it needs (full plan details).

When	Job	In LaunchList	Plan
Phase 1	Launch page with a signup form and referral link	Hosted page, or an embed on your own site	Every plan
Phase 1	Page on your own domain, open to search	Custom domain	Collect and up
Phase 1	Referral link and place in line	Referral status page after signup	Every plan
Phases 1 to 4	Spam and fake-signup protection	Spam guard, trust verdict, held for review	Every plan
Phase 2	Weekly progress emails	Broadcasts	Collect and up
Phase 3	Beta invites, most referrals first	Audience, Invites	Every plan (first 100 invites on Free)
Phase 3	Shared codes for partners and communities	Shared invite codes with seat limits	Launch and up
Phase 4	Countdown, checklist, share posts	Launch Day screen	Launch and up

The Free plan holds 100 contacts. At 500 contacts the Collect plan is $9 a month, the Launch plan $19 and the Grow plan $39, and paying yearly costs ten times the monthly price.

Common pre-launch mistakes

Adding referrals later, or going silent between signup and launch. Both waste the signups you already have.
Changing channels every two weeks. Two channels for six weeks teach you more than six channels for two.
Positioning that fits fifty products. If the headline could describe any competitor, readers cannot tell whether it is for them.
Counting fake signups. Without confirmation emails and basic spam filters, your "1,000" may include many that are not people.
Chasing a big list of the wrong people. Judge channels by who comes through them, not how many.
Treating launch day as the finish. It is when onboarding begins; write the first-week plan before the day.

How the plan shifts by type of SaaS

Developer tools lean on technical posts and developer communities. Sales and revenue software leans on LinkedIn, podcasts and one-to-one outreach. AI products use short demos as content (see the AI startup waitlist guide). Consumer and mobile products lean on short video and creators (see the mobile app waitlist guide and the app launch checklist).

What "1,000 beta users" should mean

A thousand is a good goal because it is round and forces a plan. It is a poor measure of success. If you reach 1,000 signups and 80 of them are the right customer, you have a list; if you reach 400 and 150 are using the product, you have the start of a business.

If launch is more than 90 days away, the goal is not 1,000. It is the next 100, and the one conversation you can have this week.

Frequently asked questions

How long should a SaaS pre-launch waitlist run?

Long enough to build an audience and short enough that people still remember why they joined. Two to four months suits most SaaS products, and 90 days is a workable plan. If the wait stretches past that, send a real update every week or two, because a list that hears nothing goes cold.

How many signups do I need before launching a SaaS?

There is no magic number. What matters is how many of your signups are real, reachable and a fit for the product. A hundred people who match your customer and answer your emails beat a thousand who do not. Treat 1,000 as a goal to work toward, not a threshold you must cross before you launch.

Yes, if it is real and helps you; no, if it is small or you would be tempted to inflate it. Until the total is worth showing, a milestone bar toward a goal frames a small number as progress, and a faked counter destroys trust for good if it is discovered.

How much should I budget for pre-launch marketing?

Most early-stage SaaS can do the whole plan for the price of tooling and a domain, because the main costs are your time and attention. LaunchList's Free plan is $0 for 100 contacts, and the Collect plan starts at $9 a month, adding your own domain, rewards and email broadcasts (see LaunchList pricing).

Do I need a referral program if my product has organic virality?

In pre-launch, yes. Organic virality only starts once people use the product, so before launch the referral mechanic is the only growth loop you have. See the viral loop guide.

What's the best tool to run a SaaS pre-launch waitlist?

A purpose-built tool saves weeks of engineering. LaunchList is pre-launch waitlist software for founders that keeps the launch page, referrals with verified credit, a trust verdict on every signup, email broadcasts and automations, beta invites, Launch Day and analytics on one list, with a REST API, webhooks and an MCP server for AI agents on every plan.

When should I open the beta vs. keep people on the waitlist?

A rolling beta, where you invite a small batch every week, gives steady feedback and lets you reward top referrers first. A big-bang launch gives you one loud day but loses the early feedback, and most teams blend the two. In LaunchList a rolling beta is a number in a box: invite the next 50 and it picks the people with the most referrals first, emails each a personal code and tracks who used theirs.

How do I keep a waitlist warm for 3 months?

Send a short email every week or two with one piece of real progress: a screenshot, a feature decision, something you learned from a customer interview. Include each person's position and referral link, because every update is a chance to share.

Start the plan

Ninety days is not long, so ship the first version of the page this week rather than a perfect one later. LaunchList runs the list from the page to the launch email, on a hosted page or an embed on your own site, and it is free to start. Start free

Related reading: