A waitlist page is the only landing page where the product is not the point. There is nothing to buy, nothing to try, and often nothing to show. What you are asking for is a small act of belief: an email address in exchange for a promise. Done well, it tells you whether anyone wants what you are building before you finish building it. Done badly, it collects a list of people who will not remember you by launch.
The mistake most pre-launch pages make is describing the product. Features that do not exist yet are not persuasive; they are a to-do list. What a stranger can respond to is a problem they recognise and an outcome they want. So the page should promise the outcome, name the problem precisely, and be honest that the product is on its way.
A workable headline formula for a waitlist page is the problem plus the change: "Stop rebuilding the same report every Monday" or "Get your inbox to zero without reading everything." The subhead then says what the thing is in one plain sentence and when, roughly, it will exist. A visitor who recognises the problem will sign up to hear the solution; one who does not would not have bought the product either.
Be careful with the word "soon." If you do not know the launch window, say what you do know: "We are testing with a small group now" or "First invites go out in the spring." Vague timing turns a waitlist into a dead list, because people forget why they joined.
A waitlist page has one action, and it should cost the visitor almost nothing. Everything else either supports it or should not be there.
Email, and nothing else, visible without scrolling on a phone. Name, company and "how did you hear about us" can be asked later, from people who have already said yes. Every extra field on a pre-launch page is a reason to postpone a decision that was already marginal.
"Join the waitlist" is acceptable; "Get early access" or "Save my spot" is better, because it names the benefit of joining rather than the act. Avoid "Submit" and anything that sounds like a newsletter when you are offering a product.
Under the button: how often you will email, what the first email contains, and that they can leave at any time. This removes the fear of being marketed to indefinitely, the most common silent objection on a pre-launch page.
You do not need a finished product, but you need more than a logo. A screenshot of a working prototype, a short screen recording, or a sketch of the core flow tells the visitor that this is a real thing being built by real people. A page with no evidence of progress reads as a domain someone registered.
A pre-launch page has no customer proof, so the builders are the proof. A short line about who you are, what you did before, and why you are building this covers more trust ground than design polish.
After the email goes in, confirm the spot, repeat when they will hear from you, and offer one next thing to do: share, answer one question, or follow progress. A bare "Thanks!" wastes the most engaged moment the visitor will have.
A referral mechanic can help a waitlist grow, but only if the reward is real and the mechanic is simple.
What a waitlist member wants is to get in sooner. "Refer two people and move up the list" or "Invite a friend and you both get the first release" is a reward you can deliver. Prizes, swag and raffles attract people who want the prize, not the product, and pollute the demand signal the page exists to collect.
A pre-filled message with a personal link, shown on the confirmation page and in the first email, is enough. Do not require an account or a dashboard. If the sharer has to copy a link, find a message, and paste it somewhere, most will not.
"You are number 412 in line" is motivating when the number is true and invites go out in order. It is a liability when you plan to invite by segment or when the list is small. If you are not going to honour the queue, do not show one.
Tell people how often you will write and then write that often. A monthly progress note with one real update, one screenshot and one question beats silence followed by a launch announcement to people who have forgotten you. The list is only worth what it remembers.
A waitlist signup is a weak signal: it costs nothing, commits to nothing, and a well-designed page can collect emails for almost any idea. If the page exists to decide whether to build, make the signal harder to fake and read it honestly.
Three things strengthen it. First, send cold traffic, not friends: a small paid test to strangers who match your buyer tells you something; a post to your own network tells you that your network likes you. Second, ask one real question after signup, such as "What are you using for this today?" or "What would make this a must-have?" The share of people who answer, and what they say, is more informative than the signup count. Third, offer a stronger commitment to a subset: a short call, a paid pre-order, or a deposit, and see who takes it.
Then read the result as a stranger would. A list built from a reward-heavy referral loop measures interest in the reward. A list built from a vague headline measures curiosity, not need. A list built from a precise problem statement, cold traffic, and one honest question is as close to a demand signal as you can get without a product. Score the page on clarity, proof and friction before you run traffic, so a weak result means weak demand rather than a weak page.
Before you spend on traffic to test the idea, run a landing page audit so that a low signup rate tells you about the market rather than about the headline.
A waitlist is a relationship with an expiry date. Every week of silence shortens it. The job between signup and launch is to keep the problem alive in the subscriber's mind and to turn some subscribers into collaborators: people who answer questions, try the prototype, and say what is wrong with it.
Write on the cadence you promised. Each note should have one real update, one thing to look at, and one question. Invite small groups early rather than everyone at once; the first users will find the problems and give you the quotes the launch page will need. Segment by what people told you at signup so the launch email speaks to each group's reason for joining.
At launch, the waitlist is the warmest audience you will ever have, and the page they land on should not be the pre-launch page with the field removed. It needs the proof the first users gave you, a clear offer, and an acknowledgement that they waited. The waitlist page's job was to find out whether anyone cared; the launch page's job is to turn those people into customers.
A headline that names the problem and the change you promise, one plain sentence saying what the product is, honest timing, a line about who is building it, one piece of evidence the product is real such as a prototype screenshot, a single email field with a button that names the benefit of joining, a sentence about what happens next and how often you will write, and a confirmation state that offers one next step such as sharing or answering a question. Everything else can wait until after the signup.
A signup alone is a weak signal because it costs the visitor nothing. Strengthen it by sending cold traffic rather than your own network, by asking one real question after signup and watching how many people answer and what they say, and by offering a subset a stronger commitment such as a call or a pre-order. Decide before you run traffic what signup and reply rates would make you stop. Check the page itself for clarity and friction first, so a weak result reflects the market rather than a weak headline.
Only if the reward is earlier access and the mechanic is one tap. Rewarding referrals with a better place in line or an early invite attracts people who want the product. Prizes and swag attract people who want the prize and distort the demand signal. Give each subscriber a personal link with a pre-filled message on the confirmation page and in the first email, and only show a queue position if you intend to invite in that order.
On whatever cadence you promised on the page, and no less often than roughly monthly. Each note should carry one real update, one thing to look at such as a screenshot or short recording, and one question that invites a reply. Silence followed by a launch announcement reaches people who have forgotten why they joined. Inviting small groups early keeps the list engaged and gives you the first-user stories and quotes the launch page will need.
Run your page through the same diagnostic. The free preview takes about a minute — no signup.
Audit my page