TLDR: To build a coming soon page with AI, decide the one promise and the one action (join the waitlist), then ask Claude or ChatGPT for a single self-contained HTML file with a hero, an email field, a line of social proof, and an optional countdown. Wire the email field to a form service, an embedded provider box, or a mailto link, because a static page cannot store signups on its own. Then publish the HTML as one live link you can share today and re-publish to the same URL on launch day.
A coming soon page is the highest-leverage page you will build all year. Before you spend a month building a product, you put up a page that makes one promise and asks for one thing, an email, and you find out whether anyone actually wants it. It is the cheapest demand test there is, and building one used to mean a template subscription or a developer. Now you can build a coming soon page with AI by describing it in a few sentences and getting clean, working HTML back in a minute or two.
This guide covers the whole thing: the sections that make a waitlist page convert, a copy-paste prompt that produces a page worth shipping, how to actually collect the emails (the part people skip), and the last step of getting it online as a link anyone can open. It builds on our broader guide to building a landing page with AI, but a coming soon page is its own animal, so we will treat it that way.
What makes a coming soon page different
A full landing page can have ten sections and three calls to action. A coming soon page should have roughly one of each. You do not have a product to demo yet, so the page is not selling features. It is selling anticipation and asking for permission to email someone when the thing is ready.
That constraint is a gift. The fewer decisions on the page, the higher the signup rate. Your job is to make one promise clearly, prove a little credibility, and remove every reason not to type an email address. Keep that in mind and the whole page almost writes itself.
A coming soon page is a promise plus an email field. Everything else on it is either helping someone believe the promise or getting out of the way.
What sections does a waitlist page need?
Here is the short, opinionated anatomy. You can drop any of the optional pieces, but do not add much beyond this list.
- A one-line promise. The headline states the outcome, not the category. “Get your reading list read to you on your commute,” not “An audio app is coming.”
- A one-line subhead. Who it is for and why it is different, in a single sentence.
- The email field. One input, one button. The button says what happens: “Join the waitlist,” not “Submit.”
- A trust line. Something small and true: “Join 400 early readers,” “No spam, one email at launch,” or a founder name.
- An optional countdown. Only if you have a real date. A fake countdown that resets is worse than none.
- An optional teaser. One image, GIF, or three-word feature list. Enough to intrigue, not a full tour.
The prompt that produces a real page
Vague prompts produce vague pages. Hand the AI a brief, the same way you would brief a designer: the offer, the audience, the one action, and the sections in order. This prompt reliably produces a page you can ship. Copy it and swap in your details.
Build a single self-contained HTML file for a "coming soon" waitlist page for
a product called Trailhead. It helps solo hikers plan and share routes.
Audience: weekend hikers who want a simpler alternative to bloated GPS apps.
The one action is joining the waitlist with an email address.
Structure, centered and vertically balanced:
- A hero with a bold one-line promise, a one-line subhead, and an email input
next to a "Join the waitlist" button.
- A short trust line under the form: "No spam. One email the day we launch."
- A countdown timer to a launch date I will set, styled as four boxes
(days, hours, minutes, seconds).
- A tiny footer with the product name and a contact email.
Style: clean and modern, generous white space, one warm accent color, a large
readable sans-serif, and a subtle background gradient. Make it fully responsive
so it looks right on a phone. Inline all CSS and JavaScript, use no external
libraries, and add a simple client-side check that the email looks valid before
showing a "You're on the list" confirmation message.Then iterate. The first draft is a starting point, not the answer. Real pages come from a second and third pass of plain-language feedback:
- “Rewrite the headline to lead with the outcome someone gets, not the product category.”
- “Make the button color pop more against the background, and increase the input height.”
- “The countdown feels heavy. Make the boxes smaller and add labels under each number.”
- “Add a one-line line above the form that says how many people have already joined.”
How do you actually collect the emails?
This is the step that trips people up, so it gets its own section. The page the AI writes is static HTML. Static HTML has no database, which means the email field cannot store a signup on its own. You connect it to something that can. There are three easy paths, and you tell the AI which one you want.
| Method | How it works | Best when |
|---|---|---|
| Form service endpoint | The form posts to a hosted endpoint that emails you each signup and logs it | You want real storage and zero backend code |
| Embedded provider box | You paste a signup snippet from your email tool and the AI styles around it | You already use an email provider and want new subscribers to land there |
| Mailto link | The button opens a pre-addressed email the person sends to you | A quick, tiny launch where a handful of signups is fine |
For most launches, a form service endpoint is the right call. Say to the AI: “Make the form POST to this endpoint URL and show my confirmation message on success.” If you use an email provider, paste its embed snippet and ask the AI to match your page’s styling. The mailto route needs no service at all, but it relies on the person having an email client set up, so keep it for the smallest launches.
Whatever you choose, keep a client-side check so an obvious typo does not sail through, and always show a clear “You’re on the list” state after a signup. A form that gives no feedback feels broken, and a page that feels broken loses the signup you just earned.
Design tips so it does not look like a default template
The reason a lot of coming soon pages look generic is that they use whatever the AI reaches for first: a purple gradient, a centered box, a system font. A few specific instructions fix that fast. Give the AI real direction, the way our guide on feel words to art-direct AI describes.
- Pick one accent color with intent. “Use a warm terracotta accent” beats letting the model default to indigo. Ask for a color that matches the product’s mood.
- Give the type a job. Ask for a large, confident display size on the headline and comfortable line height on the subhead. Cramped text reads as unfinished.
- Add one piece of texture. A soft gradient, a subtle grain, a single illustration, or a slow background animation. One is plenty; three is noise.
- Make the button impossible to miss. High contrast, generous padding, and a label that names the action.
- Respect the phone. Most of your traffic will open the page on a phone, so ask for the mobile layout explicitly and check it. Our notes on making AI pages mobile-friendly go deeper.
Small, specific asks compound. Five sentences of art direction is the difference between a page that looks like a template and one that looks like yours.
From AI output to a live waitlist
Here is the step people skip. The AI wrote a real page, but it is stuck in the chat window. That preview looks finished, and it is a trap, because it only exists in your session with no public URL. Publishing it is the difference between “I designed a coming soon page” and “here is my waitlist, go sign up.” Because you asked for a single self-contained HTML file, this part takes seconds.
How VisiblePage fits
Once the AI has written your page, VisiblePage is the fastest way to get it live. Paste the HTML, or drop a ZIP if the page uses separate images or fonts, and you get a live URL immediately, with no build step, server, or domain to configure. Every part of the page keeps working, the email validation, the countdown, the confirmation message, because you are sharing the real page, not a picture of it. Serve it fast from the edge, and keep it public so anyone can join.
The best part is what happens on launch day. Because the page lives at one canonical link, you re-publish the launched product to that same URL and everyone who bookmarked or shared your coming soon page now lands on the real thing. No dead link, no “here is the new address” follow-up. You can also point a custom domain at the page so your waitlist lives at your own address, and password-protect a private preview while you polish.
Try it now: Publish your AI coming soon page with VisiblePage and get a live link in seconds.
Where to go next
If your waitlist grows into a full launch page, see how to build a landing page with AI. If you want the finished page to look distinctly yours, read make AI pages look less generic. And when you are ready to squeeze more signups from the copy, our guide on how to iterate on AI-generated pages shows how to refine a draft without starting over.
Frequently asked questions
Can AI really build a coming soon page for me?
Yes. A coming soon page is one of the simplest useful pages to build with AI: a headline, a subhead, an email field, and maybe a countdown. Tools like Claude and ChatGPT write it as a single self-contained HTML file from a plain-language description in a minute or two. The output is a real web page, so the last step is publishing that HTML as a live link people can open.
How does the email signup work if the page is just HTML?
A static HTML page cannot store emails by itself, so you connect the form to something that can. The three easy options are a form service that emails you each signup, an embedded signup box from your email provider, or a mailto link that opens a pre-addressed email. Tell the AI which one you want and it wires the form to it.
Do I need to code to build a waitlist page with AI?
No. You describe the page and the offer in normal sentences and the AI writes the markup. Your job is direction and taste: the promise, the tone, and feedback like make the countdown bigger or use a warmer color. The only technical step, hosting, is handled when you paste the finished HTML into a tool that returns a link.
How do I update the page when the product actually launches?
Publish the page to one canonical link, then re-publish the launched version to that same URL. Everyone who bookmarked or shared the coming soon page now lands on the live product, with no second announcement and no dead link. That single updatable link is the main reason to publish a real page instead of a screenshot.
The short version
A coming soon page is the cheapest way to find out if anyone wants what you are about to build. Decide the one promise and the one action, ask the AI for a single self-contained HTML file with a hero, an email field, and an optional countdown, then wire the form to a service so the signups actually go somewhere. The last move is the one that matters: publish that HTML as a live link so people can join today.
Ready? Turn your AI coming soon page into a live link. Your first page is free.