A pre-launch waitlist people can actually join

A waitlist stores an address someone chose to give you, under a promise you can keep. A signup means the promise was worth an email. It does not mean the person will buy, reply, or remember you. People join lists they never open.

Say what is not ready yet, and say what they will receive. A useful promise names a concrete event: a note when they can try the product on their own file, or a single question about how they handle the job today. "Be first in the future of the category" cannot be kept. A discount you are unsure you will honor is a worse offer than silence. Do not add them to a newsletter, a drip, or a launch blast they did not ask for.

**Hypothetical: a podcast clip editor.** The page says: "Send a recording when we open. You get three short clips back with the pauses cut. We will write when the first version can take your file. No other mail unless you reply and ask." That offer can be checked later. "Weekly tips from the AI media revolution" is a second product they did not request.

The form has to answer

The page needs the promise, who it is for, an email field, and a button that names what they get. After submit, three things should happen:

• The visitor sees a confirmation on the page, in the same words as the promise.
• The address receives one email that repeats the promise and states that nothing else will be sent unless they ask.
• You receive one alert with the address and the time, so the signup is not trapped in a dashboard you forget.

The confirmation is an ordinary message to the address just submitted. Resend's send-email reference documents one API for sending a single email. It is a mechanism you can study, not a tool that comes with LaunchBuddy, and not the only way to do it. Whatever you use, you approve the sender, the template, and the first live send. An agent can draft the wiring. It should not turn sending on by itself.

Test with your own address before you share the URL. You want five things true at once: the page states the promise, the test address is stored somewhere you can export, the on-page confirmation appears, the confirmation email matches the promise, and your alert arrives. Export matters. A list you cannot take with you is a login, not an asset.

Use a waitlist page on infrastructure you control, with storage and an explicit confirmation. Keep promotional email sequences separate from the signup itself.

Read the first replies as conversations

You do not need a crowd before a signup can teach you something. When someone replies, ask what they did the last time this problem showed up, and what they used instead. George (nurijanian) has suggested discovery questions that stay with past behavior and existing workarounds. A story in that post about another company is secondhand. Borrow the question style. Do not treat the post as evidence about your buyers. It is on X, from @nurijanian, dated 21 October 2026.

Using agents for customer discovery covers preparing those conversations. An agent can sort replies you already have. It should not email the list, invent quotes, or announce the product.

When there is something to try, the product launch checklist is a separate pass over the public launch. The waitlist does not substitute for it.

Prompt

Draft a waitlist page and two short emails from the facts below.

Email A is the confirmation to the person who just signed up. Email B is my founder alert.

State the promise, who it is for, and that we send no further email unless they reply and ask. Do not add a drip, a discount, a testimonial, or a subscriber count. Do not send anything.

Facts:
- Who it is for:
- What will be ready:
- What "ready" looks like to them:
- What I will not do with the address:
- From-name I approve:

The page is fit to share when those five plumbing checks pass and a stranger can repeat the promise after one read. Ten signups and a hundred signups are both interest, not a purchase. If you later take money before the product exists, say what the payment buys and what you will do if you do not ship. That is a heavier promise than an email, and it deserves its own decision.

Once the waitlist URL is public, run it through the free scan. The scan reads the page. It cannot tell you that anyone wants the product. It can show whether the promise, the person it is for, and the button are visible before you ask for an address.