Pre-launch: Audience and Waitlists

Launch day is quiet for almost everyone, because they built the product first and thought about the audience second. The founders who launch to something built the audience while they built the product, and the strongest waitlist isn't a list of emails, it's a list of people who already paid.

The concept

Distribution is the real fight (Chapter 48), and it doesn't start on launch day, it starts months earlier, in parallel with building. A pre-launch audience gives you a warm cohort to launch to, early feedback, social proof, and a channel you own.

Three assets to build before you ship:

 AN EMAIL LIST      the one channel you own outright — no algorithm can take it
 A SMALL AUDIENCE   people who already follow your build (social, community)
 EARLY BELIEVERS    a few people invested enough to give feedback and vouch

The waitlist, and what it actually validates

A waitlist collects interested emails before launch. Useful, but be honest about what it proves:

• A free waitlist validates your headline, not your product and not your price. A 5% waitlist-to-paid conversion is common and often optimistic. 1,000 free emails is not 1,000 customers.
• A paid waitlist validates the business. A refundable deposit or a discounted founding offer proves willingness to pay, which is the actual question (Chapter 5).

Ten people paying $5 tells you more than a thousand free signups. If you can take money pre-launch, do, it funds your first costs and produces a real launch cohort with skin in the game.

📐 A free waitlist validates your headline; a paid one validates your business. A signup proves someone will give an email for your promise. Only money proves they'll pay for the product, which is the question the whole business rests on. Collect emails, but chase the payment.

Making a waitlist convert to signups

• A lead magnet beats a bare ask. "Join the waitlist" is a request; "get [free useful thing]" is an exchange. Give something valuable (a guide, a template, a tool) and take an email as payment. It also demonstrates quality before the product exists.
• Name the cohort. "Founding member," "early access," "the first 500", status is free and it converts. It implies belonging and scarcity without a discount.
• State the promise. "We'll email you when it's live", not just "thanks." Set the expectation so the eventual email isn't a surprise, and so people know why they're on the list.
• Confirm immediately. A branded confirmation email (that actually arrives, Chapter 35) closes the loop and starts the relationship.

Building in public

Sharing your build on social as you go builds an audience and demand simultaneously. It works if you can sustain the cadence and if your process is interesting to your target customer. It's a distraction with a deadline if you can't.

The waitlist backend is a public endpoint

A waitlist form posts to something, and that something is on the public internet. Whatever collects emails must have basic protection, rate limiting, bot defence, real validation, or it becomes an abuse vector (Chapter 30). This is easy to skip and expensive to skip: an unprotected endpoint can be flooded, and one that sends email on submission can be turned into a spam relay that spends your domain's reputation.

Every waitlist promise is a launch obligation

"Coming to iOS and Android," "launching in Q2," "you'll get a discount", everything you tell the list becomes a commitment you owe at launch. Promise only what you'll deliver (Chapters 25, 37).

📐 Best practice

Build the audience in parallel with the product, not after.

Take money pre-launch if you can, a founding offer or refundable deposit.

Offer a lead magnet, not a bare ask.

Name the cohort, "founding," "first 500."

State the promise on the form and confirm immediately.

Own the list, email, exportable, not locked in a platform.

Protect the waitlist endpoint, rate limit, bot defence, validation.

Track the source of each signup (UTMs) so you know what worked (Chapter 38).

Keep the list warm with occasional genuine updates, not silence then a launch blast.

Promise only what you'll deliver.

💀 Common mistakes

Building the product first, the audience second. Launch day to silence.

A free waitlist mistaken for demand. It validates the headline, not the price.

A bare "join the waitlist" with no incentive.

Silence between signup and launch, then a cold blast to people who forgot you.

An unprotected waitlist endpoint, flooded, or turned into a spam relay.

No source tracking, you can't tell which channel produced signups.

Over-promising to the list, commitments you can't meet at launch.

A confirmation email that doesn't arrive (Chapter 35).

Relying on one platform's audience you don't own, an algorithm change erases it.

Building in public you can't sustain, starts strong, dies in week three.

The professional workflow

 1. START EARLY — audience-building in parallel with the build

 2. LANDING PAGE with a clear promise + a lead magnet (Chapter 34)

 3. WAITLIST FORM
    named cohort · stated promise · UTM capture · protected endpoint

 4. CONFIRMATION EMAIL — branded, authenticated, arrives (Chapter 35)

 5. TAKE MONEY IF YOU CAN — founding offer / refundable deposit

 6. DRIVE SIGNUPS from your channels (Chapters 46-47)

 7. KEEP THE LIST WARM — occasional genuine updates

 8. TRACK per-channel source and conversion

 9. AT LAUNCH — email the list first; it's your warmest audience (Chapter 45)

Tools, websites & costs

A pre-launch funnel costs ~$12/year (a domain). The lead magnet is your time; the list tools are free at this scale.

Alternatives & trade-offs

Free waitlist vs paid pre-order. Free maximises list size and validates only interest; paid produces a smaller, real cohort and validates price. Do both if you can, a free list with a paid founding tier.

Waitlist vs building in public vs both. A waitlist captures intent; building in public generates it. Together they compound. Building in public demands a sustainable cadence; a waitlist doesn't.

Big list vs engaged list. A huge cold list converts worse than a small warm one. Optimise for engagement (opens, replies), not vanity size.

Lead magnet vs no incentive. A lead magnet raises conversion and costs you the effort of making something good, which doubles as a quality proof. Almost always worth it.

Launch to the list vs launch cold. Emailing a warm list on day one is the single biggest lever on a quiet launch. Cold launches rely entirely on channels you don't control.

Checklist

• Audience-building started in parallel with the build
• A landing page with a clear promise and a lead magnet
• Waitlist form: named cohort, stated promise, UTM capture
• The endpoint is protected (rate limit, bot defence, validation)
• A confirmation email that is authenticated and arrives
• I take money pre-launch if at all possible
• The list is owned and exportable
• I keep the list warm with genuine updates
• Signups are source-tracked
• I only promise what I'll deliver

📓 Case Study: a good funnel with a hole in the bucket

Project: SOLIS. The pre-launch funnel was built thoughtfully, with two real flaws, one strategic, one a security hole.

What was done well. A landing page with a founding waitlist, the cohort was named ("founding," implying early-access status for free), and a lead magnet: a free PDF given in exchange for a signup, turning an ask into an exchange and demonstrating quality before the app existed. The confirmation email was made to actually arrive, which required the full domain-authentication work (Chapter 35). The confirmation copy was fixed to state the promise explicitly, "we'll email you when the app is live", rather than a bare thank-you, and updated to mention both platforms.

That last edit is a quiet lesson: mentioning "iOS and Android" was correct for not alienating Android users, and it created a launch obligation for a platform that was never built (Chapter 37). Every waitlist promise becomes something you owe.

⚠️ Strategic flaw: the waitlist was free, and a paid founding tier was planned but never built. The product plan specified a $79.99 founding-lifetime offer, capped at the first 500, explicitly to "generate cash before the backend exists and create urgency." It was never implemented. So the funnel validated the headline (people will give an email for a Stoic app) and validated nothing about price, the actual business question remained open at the end (Chapter 5). Ten paying founders would have taught more than the entire free list.

🚨 Security flaw: the waitlist endpoint was an open relay, flagged on day one, never fixed. A day-one review found the backend had "no origin check, rate limit, or CAPTCHA," and spelled out the consequence precisely:

An attacker loops requests: thousands of fake addresses flood the list, the mail quota is exhausted in seconds, and the endpoint relays confirmation emails to arbitrary third-party addresses, turning it into an open spam relay with the owner's account as sender.

That's the exact hazard this chapter warns about: an endpoint that sends email on submission, unprotected, spends your domain's reputation on someone else's spam. It was a fifteen-minute fix (a honeypot field, a rate limit, real validation) and it was still open at the end of the project, because the finding lived in a chat message rather than a tracked task (Chapter 30).

🚩 The whole funnel is otherwise unvalidated. With no analytics on the form (Chapter 38), the signup rate, the traffic sources, and the lead-magnet conversion were all unknown. The mechanics were sound, named cohort, lead magnet, stated promise, working confirmation, and whether any of it converted was never measured, because the product never launched and the page was never instrumented.

Lessons

1. Build the audience in parallel with the product. Launch day is quiet otherwise.
2. A free waitlist validates the headline; a paid one validates the business. Take money if you can.
3. A lead magnet beats a bare ask, an exchange, plus a quality proof.
4. Name the cohort and state the promise. Status is free; clarity prevents surprise.
5. Protect the waitlist endpoint. An unprotected one that sends email can become a spam relay that spends your reputation.
6. A finding that isn't tracked stays open. A fifteen-minute security fix survived the whole project in a chat message.
7. Every waitlist promise is a launch obligation. "iOS and Android" is real work owed.
8. Own the list, track its sources, keep it warm.
9. Instrument the funnel, or its mechanics are just hopes.

Next: Chapter 45: Launch →