How Do You Design a Waitlist Page That Converts?

How do you design a waitlist page that converts?

Say what the product does in one sentence, show one piece of evidence that it is real, and ask for one thing. A waitlist page fails when it hides the product behind mystery, or when it asks a stranger for a company size before it has told them anything.

We build these for pre-launch B2B products, and the same three mistakes come up every time: too much hype, too many fields, and no reason to believe the thing exists.

Here is the structure we use, and the research behind each decision.

What is a waitlist page actually for?

Getting permission to email someone, and learning who cares. It is not a product launch and it is not a brand exercise. If you treat it as either, you end up with a beautiful page and a list of people who do not remember signing up.

The second job matters more than most teams admit. The pattern of who signs up, and what they say when you ask one optional question, is the cheapest audience research available before launch.

So design for two outputs: an email address, and one sentence about their situation. Everything else on the page exists to earn those.

What goes above the fold?

A plain headline naming the product and the job it does, a subhead with the specifics, the form, and one credibility element. That is it. No carousel, no video, no three-column benefits grid that pushes the form below the screen.

The reason is how people read. Jakob Nielsen's research for the Nielsen Norman Group, published in September 1997, found that 79 percent of test users always scanned any new page they came across, while only 16 percent read word by word. That behaviour has not reversed.

Write for the scanner. Our guide to above the fold design covers how much you can reasonably fit before the first scroll on a phone.

How much should you explain before the form?

Enough that a stranger could describe your product to a colleague afterwards. In practice that means a headline, two sentences and one concrete example of the job it does. Then the form. Then the longer explanation further down the page, for the smaller group who want the detail before they commit.

Cut the hype hard. The same Nielsen Norman Group study measured versions of a page against a promotional baseline and found concise text improved measured usability by 58 percent, a scannable layout by 47 percent, objective language by 27 percent, and all three combined by 124 percent.

That last number is the strongest argument we know against marketing language on an early-stage page. Promotional wording makes the reader do work, and a reader doing work is a reader leaving.

How many fields should the form have?

One, in almost every case. Email address, then submit. Every extra field is another reason to close the tab, and anything else you want to know can be asked in the confirmation email or on the confirmation page, once the person has already said yes to the first thing.

If you genuinely need to segment the list at signup, add one optional field with a short option list, not a free text box and not a required one. Role or company size works. Both is greedy.

Name the button after the outcome. "Join the waitlist" is fine, "Get early access" is better if it is true, and "Submit" tells nobody anything. Our notes on form design UX cover the label and error patterns.

Should you use placeholders as labels?

No. Nielsen Norman Group's guidance, published in May 2014 and last reviewed in September 2018, sets out why placeholder text as a label fails: users forget the hint once they start typing, they cannot review their answers before submitting, error recovery means deleting text to see the instruction, and keyboard users cannot study a field before moving on.

The accessibility problems are just as concrete. That article flags poor contrast on placeholder text, extra burden for people with cognitive or motor impairments, and inconsistent screen reader support.

Floating labels are the popular compromise, and Nielsen Norman Group notes they still carry some of the same problems. On a one-field form you do not need the space saving anyway, so use a visible label above the field.

What proof works when you have no customers?

Evidence that the product exists and that people you respect are involved. A real screenshot beats an illustration. A named founder with a real background beats a logo wall of investors. A short demo clip beats a promise of one.

Numbers are only worth using if they are true and checkable. "Join 1,200 others" works when it is real and looks absurd when your launch is next week and the number never moves.

Buyer research supports the unglamorous version. TrustRadius, surveying 1,862 buyers and 444 vendors for its 2026 report, found buyers ranked product demos, free trials, prior experience and user reviews as the most influential resources. Every one of those is a form of seeing the thing work.

What should the confirmation say?

What happens next, and when it happens. "You are on the list" is the bare minimum. Much better is a specific promise, along the lines of "you are number 340, we onboard 20 people a week, expect an email from us in February", provided every part of that sentence is actually true.

This is also the right place for the question you did not ask on the form. One line: what are you hoping this replaces? The answers you get in the first week will shape the product page you eventually write.

Keep the page itself, not just an inline message. A real confirmation URL gives you something to measure and somewhere to put the next step. Our guide to thank you page design covers what belongs there.

How do you keep the list warm?

Email them long before you need anything from them. A short note every three or four weeks showing real progress keeps a waitlist alive, and silence kills it faster than bad news ever does. People will forgive a slow launch. They will not forgive being forgotten.

Write those emails like updates rather than campaigns. What we built, what we learned, what is next, one link. The people who reply are your first design partners.

Set the expectation on the page itself so the emails are welcome. Saying "occasional progress updates, no marketing" makes the first email land better and reduces the unsubscribe spike.

Does the page need to be fast?

Yes, and it is the easiest win on the list. A waitlist page is text, one image and a form, so there is no excuse for missing Google's thresholds: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint at 200 milliseconds or less, and Cumulative Layout Shift at 0.1 or less, measured at the 75th percentile.

Most of the damage comes from a hero video, a font loading late, or a form embed that drags in a whole script bundle. Check the page on a phone on a normal connection before you launch it.

A slow waitlist page is a particularly expensive mistake, because almost all of its traffic arrives in a burst from a launch post or a newsletter, and you never get that moment back.

What would we build first?

One page, one headline, one sentence of specifics, a single email field with a visible label, a real screenshot, and a confirmation page that asks one question. Ship that in a day and spend the rest of the week writing the first update email.

Then leave it alone and watch what people write back. That is the part of the waitlist that actually pays for itself, long before the product ships.

If you want a second opinion on a pre-launch page before you send traffic to it, we are happy to look. You can see how we design and build at phoenix.studio.