To build a waitlist, explain who your launch is for, collect a contact address, say what happens next and plan how you will invite people. A short form can do the collection. You still need a way to send updates and manage access. Count signups as expressions of interest, then learn whether those people respond, accept an invitation and use what you launch.
This guide is for a product, course or project that is not ready for everyone yet. If people can buy or register now, send them to the actual next step instead of adding an unnecessary waiting period.
1. Give people a concrete reason to join
Write four things before designing the page:
- Who is this for?
- What specific problem will it help them solve?
- What will joining the list get them?
- How and when will you contact them next?
Here is original landing-page copy for a fictional product:
Plan volunteer shifts without chasing five spreadsheets.
We’re building a shared rota for small community teams. Join the waitlist for an invitation to the first pilot and occasional progress updates. We’re starting with a small group of coordinators; joining does not reserve a place or commit you to buying anything.
Join the waitlist
The point is the specificity, not the wording. Replace the audience, problem and invitation policy with your actual plan. If you do not know the launch date, say that. If entry is first-come, first-served, explain it; if you are choosing pilot participants by use case, say that instead of displaying a queue position you cannot honour.
A waitlist is one input into research. The SBA’s market-research guidance (opens in a new tab) also covers demand, alternatives and direct research with potential customers. Our practical interpretation: an email address can open a conversation, but it cannot settle pricing, usability or willingness to pay by itself.
2. Keep the signup form small
Start with a required email address and, if you will use the answer, one optional question about the person’s situation. For example:
What would you like to use this for?
That is the question in whatayarn’s waitlist template. For a discovery conversation later, consider asking about a recent example of the problem: “How did you organise your team’s last rota?” is more concrete than “Would you use an amazing new rota app?” NN/G’s survey guidance (opens in a new tab) explains why predicted behaviour is a weak basis for product decisions.
Add role, team size or another category only when it changes how you will run the pilot. A long qualification form may be appropriate for a managed beta, but call it an application and explain the selection process. Do not hide a substantial application behind a button promising a quick signup.
Waitlist template
Try it here. Nothing is sent or saved.
The preview above stores nothing. In the editor you can replace the introduction, optional question and thank-you copy. Build and preview before signing up; an account is needed to publish a live form and collect responses.
3. Make the confirmation match the promise
After signup, say what happened and what happens next. Here is an original thank-you message for the fictional rota pilot:
You’re on the interest list. We’ll contact you at the email you supplied when we’re ready to invite another pilot group. We haven’t reserved a place yet. If you have a recent rota you’d like to talk through, reply when you receive our invitation.
Use “Check your inbox to confirm” only when you have actually configured a confirmation email. A thank-you screen, a saved form response and a verified email address are different states.
For example, Mailchimp’s double opt-in process (opens in a new tab) asks a person to follow a confirmation link after signup. Its documentation specifies the supported signup paths. Collecting an address in whatayarn does not perform that process, create a Mailchimp subscriber or automatically send a welcome email.
whatayarn’s respondent confirmation emails and integrations are coming soon. If email verification and immediate welcome sequences are essential from day one, use an email platform’s supported signup form or a dedicated waitlist tool that provides the flow you need. A whatayarn form can still suit a small list that you review and follow up manually.
4. Put the invitation where the intended audience will see it
Start with channels where the problem is already being discussed: your existing newsletter, a relevant community where promotion is welcome, a product page or a conversation with a potential customer. Describe the problem and pilot honestly rather than sending the same generic pitch everywhere.
Use the form’s public link, or embed it in your website. Check the complete destination on a phone before posting: the headline, fields, confirmation and any external email step should agree. A QR code can work for an in-person event, provided the printed size scans and the destination explains the project without your verbal introduction.
If there are several sources, record which links you used and which period you shared them in. Use the source information your analytics actually captures; a direct visit or missing referrer is not proof of a particular campaign. Keep traffic counts and completed form responses separate.
5. Plan the follow-up before the list grows
Decide who will review signups, who will send updates and what makes someone ready for an invitation. For a small pilot, an ordinary tracking sheet can be enough:
| Field | What it records |
|---|---|
| Contact address | Where the person asked to hear from you |
| Signup date and source | When and where the interest was recorded, when known |
| Use case | Their actual explanation or a reviewed category |
| Invitation status | Not invited / Invited / Accepted / Declined |
| Last contact and next action | What you sent and what you intend to do next |
These are suggested fields for your own process, not a built-in whatayarn waitlist dashboard. whatayarn collects and exports the responses; it does not provide automatic queue positions, referral rewards, subscriber deduplication or an invitation scheduler.
You can review and export responses, then move selected contacts into your sending process. Mailchimp’s import instructions (opens in a new tab) distinguish importing contacts from its signup process: subscribed imports do not go through that signup flow. Check the status and permission you are recording rather than treating every email in a CSV as a confirmed subscriber. Keep the signup promise with the record so your updates match what the person requested.
An original pilot invitation could read:
You joined the interest list for our volunteer rota pilot. We’re inviting another small group to try the first version. It currently supports [the tasks you have shipped], and we would value a conversation after you’ve tried it. If you’d like an invitation, reply by [date]. If the timing doesn’t suit, that’s fine too.
Replace the placeholders with real information. Send through your own email process; this example is not an automated whatayarn message. A response saying “yes” is an accepted invitation, not proof that the person has started using the product.
6. Measure the next step, not just the list size
Here is a constructed example for one launch period. It is not a recommended conversion target:
- 400 landing-page visits led to 40 completed signups: 10% visit-to-signup conversion.
- You invited 20 of those people and 8 accepted: 40% invitation acceptance.
- Of the 8 who accepted, 5 completed the first useful task: 62.5% activation among accepted invitations.
The denominators change at each step. You cannot use 5 out of 400 as the acceptance rate, or infer that the 20 people you have not invited rejected the product. Define the first useful task before measuring it: publishing a rota, attending a lesson or completing setup may fit different projects.
Review where people stop. Many visitors and few signups may prompt a closer look at the audience or promise. Many signups and few replies may mean the interest was casual, the timing changed or the email did not arrive. These are hypotheses to investigate, not conclusions from a funnel alone.
Once people have tried the product or attended the course, ask about that real experience. Our customer feedback questions help you move from “interested” to learning what worked. For an ongoing publication rather than staged access, use the newsletter signup template.
