How to Build a Waitlist Form in One Prompt

You had the idea on Tuesday. By Thursday you want a page collecting emails, because the only thing separating "an idea" from "a thing people want" is a list of people who raised their hand. What usually happens instead: you spend an afternoon picking a tool, fighting a drag and drop canvas, and arguing with yourself about whether to ask for company size.

The form is not the hard part. The hard part comes six weeks later, when you have 400 emails and no idea what to say to any of them. This guide covers both halves: getting the form live in one prompt, and building the list so it is actually usable on launch day.

What a waitlist form should actually ask

Three fields, maximum. Email, one qualifying question, and a first name if you plan to write emails that use it.

Every extra field costs you signups. That is not a hot take, it is arithmetic. Each field is one more decision, and someone who landed from a tweet 11 seconds ago has very little decision budget left. A waitlist is a low-commitment ask, so it should look like one. If your form has a scrollbar, you have already lost people.

The usual ways founders ruin it:

• Asking for a phone number. Nobody gives you their phone number for a product that does not exist yet.
• Asking about budget. You have no product. This reads as "we are about to sell you something", and it is the single fastest way to halve your signups.
• An open text box: "tell us about your use case." Fifteen percent will fill it in, and you will get fifteen percent of answers you cannot sort. Save it for the follow-up email.
• Company, role, team size, and industry as four separate fields. That is a sales qualification form wearing a waitlist costume.
• Making anything required except the email. If a field can be skipped, let it be skipped.

The one question worth adding

The most useful extra question is the one that tells you which bucket someone is in. Two shapes work:

• Who are you? A single select with four to six options that map to the segments you already suspect exist. Freelancer, small team, agency, in-house, something else.
• What brought you here? The problem they showed up with, not the feature they want. This one is usually better, because people are honest about pain and speculative about features.

Make it a single select, five or six options, one of them "Something else". Not a multi-select: if everyone ticks three boxes, you cannot segment anything. Options need to be mutually exclusive and written in the words your users would use, not your internal category names.

If you have EU visitors, add the native GDPR consent field. It is one checkbox, and it means the list you build is one you can legally email later.

Build it in one prompt

Brieform has no drag and drop builder. That is deliberate. The interface is an MCP server, so you build the form by describing it to the AI client you already have open. Connect https://brieform.app/api/mcp/mcp to Claude, ChatGPT, Cursor, VS Code, Le Chat or Perplexity, then write something like this:

I'm launching a waitlist for a tool called Roomtone, a browser extension that mutes background noise on video calls. Create a form in Brieform called "Roomtone early access" with exactly three fields: email (required, with email validation), first name (short text, optional), and a required single select called "What are you hoping Roomtone fixes?" with these options: "Noisy home, kids or roommates", "Coworking space or cafe", "Open plan office", "I record podcasts or video", "Something else". Add the GDPR consent field at the bottom, with text saying we will email them when early access opens and nothing else. Keep it single step, no progress bar. Theme it dark with a warm orange accent, rounded corners, and a geometric font. Headline: "Get early access to Roomtone". Button text: "Join the waitlist". Show me the preview URL before you publish anything.

The client calls create_form and hands back a preview URL. The form is a draft, not public, so open the link on your phone and read it as a stranger would. Anything that makes you hesitate, delete. Ask for changes in plain language ("make the accent softer", "shorten the subtext to six words") and the client calls update_form or set_form_theme.

When it looks right, say "publish it". That calls publish_form and the form is live. Drafts are unlimited on every plan, and the quota only counts published forms, so you can build three variants and only ship one.

Publish, then grab the share assets

Ask for the share assets and the client calls get_form_share_assets: the public link you can drop into a tweet or a Discord, and the embed snippet you paste into your landing page. If you already have a landing page in Webflow, Framer or WordPress, embed it there so the whole thing sits above the fold. If you do not have a page yet, the hosted form is your page. Plenty of waitlists have launched with nothing else.

Two things to know before you ship it. The form lives on a brieform.app URL, because custom domains are not supported and slugs cannot be renamed. And spam protection is a honeypot, not a captcha, so nobody gets asked to identify a crosswalk, but a determined bot is not stopped cold either. Public forms are capped at 25 submissions per hour per IP, which handles the usual junk.

Now the part most guides skip

A waitlist is not a number. It is a set of segments you have not looked at yet. Two weeks in, go back to the same AI client and ask:

Pull all responses from the Roomtone early access form in Brieform. Count signups per option of "What are you hoping Roomtone fixes?" and give me the percentage split. Tell me which segment grew fastest in the last 14 days compared to the two weeks before. Then for the top three segments, write a launch email of 120 words or less each: same offer, same link, but the opening line and the problem framing should be specific to that segment. Plain text, no marketing voice, signed from me. List the email addresses for each segment in a separate block so I can paste them into my email tool. Skip anyone who did not tick the consent box.

That is get_responses plus reasoning over the result. If you have more than 50 responses, ask for the CSV URL instead so the raw data does not flood the conversation. CSV export works on every plan.

Half the time the biggest segment is not the one you designed the product for. That is the most valuable thing a waitlist can tell you, and you only find it if you actually look.

On Starter and above, get_form_analytics adds the other half: views, submissions, conversion rate, daily breakdown and top referrers over 7, 30 or 90 days. If 1,000 people saw the form and 40 signed up, your problem is the page copy, not the form. If 120 saw it and 60 signed up, your problem is distribution. Those are completely different fixes, and without the view count you are guessing.

What Brieform will not do here

Be clear about this before you build your launch plan around it.

• No email sending. No confirmation email, no autoresponder, no drip sequence, no "you are number 47 in line" counter. Brieform collects, it does not send. You still need Resend, Buttondown, ConvertKit or similar for the actual emails.
• No outgoing webhooks and no native integrations. The bridge is your AI client: connect Brieform and your email tool to the same client, and ask it to push new signups over as tagged contacts. It works on every plan including Free, and it needs no Zapier, but it runs when you ask, not automatically at 3am.
• No file uploads. If your waitlist involves portfolios or screenshots, this is the wrong tool.
• No payments. Planning a paid preorder or a refundable deposit? Use a Stripe payment link or a checkout-first tool instead. A waitlist form cannot take money.
• No referral loop. If the entire point is viral position-in-line mechanics, use a dedicated waitlist product.

For the plain version, which is most versions, three fields and a segment question will get you further than any of that.

🚀 Try it now — Build your waitlist form with Brieform →

Free to start. No credit card required.

FAQ

How many questions should a waitlist form have?

Two or three. Email, one segmenting question, and optionally a first name. Everything else you want to know is a better fit for the first email you send them.

Can Brieform send a confirmation email when someone joins?

No. There is no autoresponder and no email sequence. You collect signups in Brieform and send from an email tool, and your AI client can move the contacts across on request.

Can I take deposits or preorders on the waitlist?

No, there are no native payments and no file uploads. For a paid preorder, use a checkout link and keep the waitlist form for the free signups.

Do I need a paid plan to run a waitlist?

Free at $0 gives you one published form, 50 responses a month, and 11 of the 12 MCP tools, with Brieform branding on the form. Starter is $29/mo ($23/mo annual) for 20 published forms, 2,000 responses a month, analytics, and no branding. Pro is $69/mo for unlimited.

Can I embed the form on my own landing page?

Yes. Ask for the share assets and paste the embed snippet into Webflow, Framer, WordPress or your own HTML. The form itself stays on a brieform.app URL, since custom domains are not supported.