How to Build a Waitlist Page That Collects Real Sign-Ups
How to build a pre-launch waitlist page: the copy that gets sign-ups, saving emails to a database, confirmation emails, referral links and avoiding spam.
Mythex Team · · 6 min read
A waitlist page is a one-page site with one job: get people who want your product to leave their email before it exists. To build one, write a headline that says who it's for and what it does, add a single email field that saves to a database you control, show a clear thank-you state, and send a short confirmation email. Referral links, counters and position numbers are optional extras you add once the basics work.
Why a waitlist page is worth building properly
A waitlist does two jobs. It gives you a list of people to tell on launch day, and it tells you whether anyone cares before you build the full product. The second job only works if the page is honest and the numbers are real. If you're using it to test an idea, read how to validate an app idea alongside this guide: sign-ups are a useful signal, but a weaker one than people paying or replying.
What the page needs
| Part | What it does | Tips |
|---|---|---|
| Headline | Says what the product does, for whom | "Invoicing for freelance translators" beats "The future of work" |
| Subheadline | The main outcome or pain it solves | One sentence |
| Email form | One field, one button | Ask for only the email. Every extra field lowers sign-ups |
| Button text | Says what happens | "Join the waitlist" or "Get early access" |
| Thank-you state | Confirms it worked and sets expectations | "We'll email you when the beta opens, likely in spring" |
| What they get | Three short points, or a screenshot or mockup | Show, don't hype |
| Privacy line | How you'll use the email | "One email when we launch. No spam, unsubscribe any time." |
| Admin list | Where you see sign-ups | Private, with CSV export |
Optional parts:
- A short FAQ answering "when?", "how much?" and "who is this for?"
- A founder note — a line or two about why you're building it
- Referral link on the thank-you screen
- Sign-up counter, but only if the number is real and flattering enough to show
Decisions to make before you build
A form tool or your own page
| Option | Good for | Trade-off |
|---|---|---|
| A form tool (Google Forms, Tally and similar) | Testing interest in an afternoon with no design | Generic look; limited control over the page and follow-up |
| Your email marketing tool's sign-up page | You already use one and just need a list | Limited design; referral features vary |
| Your own page with a database | You want your brand, your domain, referrals or custom questions | More to build and test |
If you'll eventually launch on your own domain, building your own page early means the URL you share today still works on launch day.
What happens after someone signs up
Decide this now, because it changes what you build:
- Nothing until launch. Simplest, but people forget who you are after a few weeks.
- An instant confirmation email. Recommended. It confirms the address is real and reminds them what they signed up for.
- Double opt-in (they click a link to confirm). Gives you a cleaner list and is expected or required in some regions. Check the rules where you and your audience are.
- Occasional updates. A short progress note every few weeks keeps the list warm.
Referrals: yes or no
A referral system gives each person a unique link and moves them up the list when friends sign up with it. It can work well for consumer products with a real reason to be early (limited beta spots, launch pricing). For B2B tools it often adds complexity without many shares. If you add it, you need:
- A unique code per sign-up, and a link that includes it
- A count of confirmed referrals per person
- Rules against cheating: only count confirmed emails, and watch for bursts of sign-ups from one source
- A thank-you page that shows the link and position clearly
Build it step by step
Step 1: Write the copy before the design
Write the headline, subheadline, three benefit points and the thank-you message in plain text first. If you can't explain the product in two sentences, the page won't either. Our guide on landing pages that convert covers structure and copy in more depth.
Step 2: Write the first prompt
Name the product, the audience, what's saved and what the visitor sees after signing up:
Build a waitlist page for Ledgerly, simple invoicing for freelance translators. Headline: "Invoices in any currency, done in two minutes." Three short benefit points, a product mockup placeholder, and one email field with a "Get early access" button. Save each email with the sign-up time to a database, reject duplicates and invalid addresses, and show a thank-you message saying we'll email once when the beta opens. Add a private admin page that lists sign-ups and exports CSV. Calm, minimal design, looks great on phones.
Step 3: Test the form properly
Submit your own email. Then try the same email again, an obviously fake address, an empty field, and a very long input. Check each sign-up appears once in the admin list, and that the export opens cleanly in a spreadsheet.
Step 4: Protect it from spam
Public forms attract bots. Cheap defences that don't annoy real people:
- A hidden "honeypot" field that humans never see and bots fill in
- A limit on sign-ups per IP address in a short period
- Server-side email validation, not just in the browser
- Keep the admin page behind a login or a secret you control, and out of the site's navigation
Step 5: Add the confirmation email
Sending email needs an email provider (such as Resend, Postmark or SendGrid), a verified sending domain and an API key stored as a secret, never in the page. Keep the email short: what they signed up for, roughly when to expect news, and how to unsubscribe. See how to send emails from your app.
Step 6: Publish and share it
Publish on a domain you'll keep, add a proper page title and a share image so the link looks good in messages, then share it where your audience already is. How to launch an app and get your first users has ideas for where to post.
Common mistakes
- A vague headline. "Something big is coming" gives nobody a reason to sign up.
- Too many fields. Name, company, role and phone number on a waitlist form will cut sign-ups. Ask later if you need to.
- Fake counters and fake scarcity. "4,219 people ahead of you" when there are 30 destroys trust the moment someone notices.
- No way to export. On launch day you need the list in your email tool in minutes.
- Silence for months. A list that hasn't heard from you since sign-up responds poorly to the launch email.
- No privacy line. People are more willing to give an email when they know what you'll do with it.
What it costs
A waitlist page is one of the cheapest things you can build. The main costs are a domain name, hosting (small for a page that's mostly static plus a tiny database), and an email provider once you send confirmations. Several email providers offer a free or low-cost starting tier for small volumes; check their pricing pages for current limits.
When a ready-made product is the better choice
- You're testing an idea this afternoon. A form tool is fine. Move to your own page if the idea holds up.
- You already run an email newsletter tool. Its sign-up form may be enough, and the list is already where you'll send the launch email.
- You want a polished referral programme with prizes and leaderboards. There are hosted waitlist and referral tools built for exactly this. Compare their current pricing with the time it would take you to build and test your own.
Building it with Mythex
A waitlist is one of the quickest things to build in Mythex: describe the product and audience, and it builds the page in a live preview. Ask for sign-ups to be saved and it adds a database to the project (or type /database). You can run /test to have it click through the form in the preview before you share the link. Publishing is available on the Free plan at yourname.mythex.ai; a custom domain needs Pro. Mythex doesn't include email sending or a Mailchimp-style connector, so confirmation emails use a provider you bring, with the key stored in project secrets.
The waitlist landing page template gives you a ready-written first prompt. The docs cover the same flow in build a waitlist and send email from your app.
Questions
What should a waitlist page include?
A headline that says what the product does and who it's for, a short list of what people get when it launches, a single email field with a clear button, a thank-you message after sign-up, and a line on how you'll use their email.
Where should waitlist emails be stored?
In a database you control, or in an email marketing tool you can export from. Avoid anywhere you can't easily download the full list later, because you'll need it on launch day.
Should I add a referral system to my waitlist?
Only if people have a reason to share, such as earlier access or a limited number of spots. A referral system needs unique links, counting and anti-cheating rules, so add it after the basic page works.
Do I need to send a confirmation email?
It's strongly recommended. A short 'you're on the list' email confirms the address is real, reminds people what they signed up for, and makes your launch email less likely to be ignored or marked as spam.