Waitlist Form Template

A waitlist page looks like marketing, but the form behind it is two instruments in one: a promise to the visitor — you will hear before anyone else — and a demand meter for you. This template keeps the promise cheap to accept (one required field and one tap) while reading the demand honestly, which is what separates a list you can plan a launch around from a pile of addresses that opens nothing.

Why these fields. The email comes first and its label stays plain, because momentum matters more on a waitlist than on any other form — the visitor arrived with exactly one intention, and every second between intention and confirmation taxes it. The first name is optional and explains itself ("so we can greet you properly"); optional-with-a-reason collects better than required-without-one. "How did you find us?" looks redundant next to the hidden UTM field riding underneath, and the redundancy is deliberate: link tags catch the channels you planned, self-report catches the ones you didn't — the podcast mention, the group chat, the screenshot a friend sent. The eagerness question is the demand meter itself. Five hundred signups is a vanity number; three hundred who chose "the first day" is a forecast you can size a launch email, a server bill, and a support rota against. And the referral line turns the list into its own distribution — someone who joined a waitlist four seconds ago is at peak willingness to name the next person who should.

The invisible field. A hidden utm_source travels with every signup. Share yourlink?utm_source=twitter in one place and ?utm_source=newsletter in another, and each response arrives stamped with its origin — respondents never see the plumbing, and your CSV export gains the column that settles every "which channel is actually working" debate.

What we left out. Phone numbers (nobody wants a call about a product that doesn't exist yet), feature-preference surveys (worth running later, to the people who already proved they care), and company or role fields that make joining feel like applying. A waitlist should feel like raising your hand, not filing paperwork.

Who uses this. Founders with a landing page and nothing behind it yet, makers announcing v2 to v1's audience, newsletter writers gauging a paid tier, and anyone who keeps saying "launching soon" and wants the soon to have witnesses.

Make it yours. Turn on duplicate prevention in Settings — per device or per IP — so enthusiasm doesn't double-count your demand. If scarcity is part of your story, close the form automatically after a set number of responses and write a closed message worth screenshotting. On launch day, export the CSV into whatever you send mail with; the eagerness column tells you who gets the first batch. Keep Focus mode on so the whole exchange stays a ten-second conversation, and let the built-in honeypot, timing checks, and invisible proof-of-work challenge keep bots from inflating the meter.

The quiet rule. Every question after the email must earn its place by changing what you do at launch. These three do. Anything more belongs in the follow-up conversation this list exists to start.