Waitlist / pre-launch page
A one-purpose page that collects emails for a product that does not exist yet, so launch day starts with an audience instead of silence.
See it
What it is
A waitlist page is a one-purpose page for a product nobody can buy yet. It might be unbuilt, half-built, in private beta, or finished and simply not open yet: say what it does, show a picture of it, take an email. The point is arriving at launch day with an audience instead of silence, and learning whether anyone wants the thing before you build all of it.
What actually belongs on it: a specific promise (not 'the future of work'), one screenshot or mockup so it feels real, one field and one button, a signup count or named early users once you have them, and a confirmation screen that gives people something to do next. Referral positions ('skip 50 places by sharing') are the classic amplifier, the Robinhood trick, and they only work if the queue feels real.
Gotcha: a waitlist signup is cheap, so it is a weak signal, not a worthless one. It tells you the promise is interesting to somebody. It does not tell you anyone will pay, which is why ten thousand emails can convert at 1 percent on launch day. If you want evidence of willingness to pay, raise the price of signing up: ask one question after the email, ask for a reply, or take a small refundable deposit. Second gotcha: lists rot. If launch slips by months and you never email, the list is cold traffic wearing a warm label, so send something every few weeks.
Ask AI for it
Build a single-page waitlist site for [product], a [one-line description] for [audience]. Sections in order: headline stating the specific outcome plus a one-sentence subhead saying what it is, one email field with a button labeled with the benefit (not 'Submit'), a single product mockup, three short 'what you get on day one' bullets, a social proof line whose signup count is read from [waitlist data source], and a one-line FAQ block covering price, timing, and 'will you spam me'. No nav, no footer links, nothing that leads away from the form. After submit, replace the form inline with a confirmation. Show a queue position and a prefilled share link only if [waitlist data source] and [referral rules] supply real values and sharing genuinely moves someone up the queue: otherwise omit the counts and positions rather than fabricating them. Mobile-first, one accent color, loads in under a second.