Build a waitlist page with AI

What a waitlist page is for

Before a product exists, the only thing you can offer a visitor is a reason to wait and a way to hear when the wait is over. A waitlist page does both on one screen. It isn't a smaller version of the eventual homepage: it has no feature tour, no pricing table and no team page, because none of those exist yet in a form you can stand behind. What it does need is a sentence that makes the right person lean in, and a form short enough that they finish it.

That narrowness is also why waitlist pages built by AI so often fail. A model asked for a "startup landing page" fills the space with the sections it has seen most: three feature cards, a testimonial from nobody, a pricing grid with invented tiers. Every one of those is a claim you can't support before launch. Anticode's Architect asks what the product actually is and who it's for before it plans a single section, and the Critic flags the stock phrases that make pre-launch pages read as filler.

The four parts that matter

1. A specific promise. Name the outcome and the person. "Invoices that chase themselves, for freelance designers" gives a reader something to say yes to; "The future of finance" doesn't.
2. One sign-up field, usually email. Every extra field costs sign-ups. Ask for a name or a role only if you'll actually use it to decide who gets in first.
3. What happens next. Say when you expect to launch, how often you'll write, and that people can unsubscribe. Vague timing is fine; silence isn't.
4. Proof you exist. A real founder name, a link to where you post updates, or a screenshot of the work in progress. Invented logos and user counts do the opposite once anyone checks.

What Anticode builds for a waitlist

Using Anticode as a waitlist page builder starts with one sentence about the product, such as "a waitlist page for Tallyroll, an app that sends invoice reminders for freelance designers". The Architect turns that into a short plan and asks up to three questions where the answer changes the page: whether you have a launch date, whether you want a name field, and which design direction fits. You tap an answer or type your own.

The design engine then lays out a landing page with the newsletter sign-up as its main action, held to one of seven design systems so the type, colour and spacing agree. For a software product the Technical direction (IBM Plex Sans, amber on graphite) is a common pick; a consumer product might suit Playful or Organic. The page ships as plain HTML and CSS with no scripts, so there's nothing in it that can track visitors or break when a third-party service changes.

The form

Sign-ups are saved to your project and sealed at rest. You can have each one emailed to you, and you can send them on to Mailchimp, Kit, Google Sheets, Airtable, Notion, HubSpot, Slack, Discord, Telegram or any webhook from the dashboard.

The checks

Before the page can be published, Sentinel scans the exact HTML for the twelve security rules (the form's destination, the Content-Security-Policy, links and anything that looks like a key) and the design gate checks basics such as a visible keyboard focus, alt text and a page language.

The address

Publish to a free anticode.dev address straight away, or connect your own domain on a paid plan. Free sites carry a small "Made with Anticode" badge.

Writing the headline and the line under it

The model drafts the words from your sentence, and it's worth editing them yourself, because only you know what the product will really do. A useful test: read the headline with your product's name removed. If it could belong to a competitor or to a business in another industry, it's too general. Replace adjectives with specifics: the task the product removes, the time it saves, the kind of person who's been asking for it.

Keep the button honest too. "Join the waitlist" or "Get launch news" says what happens. "Get early access" promises something; use it only if early sign-ups really will get in first, and say how many places there are if you know.

After people sign up

A waitlist goes cold quickly. Send a short confirmation by hand or from your email tool the same day, then a real update at least once a month, even if it's only what you built this week. If you connect Kit or Mailchimp, new sign-ups arrive there as subscribers and you can write to them from the tool you already use.

When the product launches, you don't need a new site. Ask for the change in a sentence ("turn this into a launch page with pricing and a sign-in button") and the page is rebuilt from the same project, with your most recent versions kept in the version history in case you want to go back.

Where Anticode stops

• No referral queue. There's no built-in "move up the list by inviting friends" mechanic. Tools built only for waitlists do that; if it's central to your launch, use one of them and link to it.
• No automatic emails from Anticode. Anticode can email you each sign-up, but it doesn't send messages to the people on your list. Connect an email tool for that.
• No A/B testing. You can publish a new version at any time, but there's no built-in split test or analytics beyond page views per day.
• English pages. The builder and the pages it generates are in English today.

Questions people ask

How quickly can I build a waitlist page with Anticode?

A preview build runs in your browser with no account, and you can watch each step in the build log. A model-written build needs an account; the builder streams its progress while it writes, so you can follow it from the first section to the last check.

Can I export the sign-ups?

Yes. Sign-ups are listed in the dashboard and can be sent on as they arrive to Google Sheets, Airtable, Notion or your email tool through a connector.

Do I need my own domain?

No. You can publish to a free anticode.dev address and add your own domain later on a paid plan; the page and its sign-ups stay the same.