Coming Soon Page Builder — Do You Need One?

Updated September 2026

Do you actually need a coming soon page builder?

Often, no. A launch page is one screen: a sentence, a date, and a field. That is a small enough job that the tool matters less than three decisions nobody makes on purpose — where the domain points, what status code the page returns, and where the email addresses end up.

We sell one of these tools. Below are five routes including ours, ranked by how long each takes to get live, with the case against each — including the case against paying anyone.

What matters Five routes When to skip it FAQ

Before choosing anything

Three decisions the tool will not make for you

Builders compete on templates. Launch pages fail on these three, and every route below has to answer them somehow.

Where the domain points

A launch page nobody can reach at your actual address is a design exercise. Decide whether it lives on the apex, a subdomain, or a temporary host you will repoint later.

Custom domains →

What status code it returns

A launch page should answer 200 so it gets indexed. A maintenance screen should answer 503. Most builders never mention which one they send, and getting it backwards is invisible until it is expensive.

200 or 503? →

Where the emails go

In a downloaded template the field posts nowhere at all. Whatever route you take, confirm an address you typed yourself actually arrived somewhere you can read.

Email capture →

The options

Five ways to put one screen on a domain

Ordered by time to live. The times assume you already own the domain and know what the page should say — which, honestly, is the part that takes longest.

A static file on hosting you already have

~20 min

Download a template, edit the headline and date in a text editor, upload the folder. No account, no subscription, and the page is yours in a form nobody can take away.

Pick it when: The page is up for weeks rather than months, and you have somewhere to put a file.
The case against: The email field posts nowhere until you wire an endpoint to it, and every copy change means editing HTML and re-uploading.

A one-page site builder

~30 min

Carrd, Framer, Wix and the rest will all do a launch page well. They are general tools with big template libraries and mature editors.

Pick it when: You expect the page to become the real site, or you already pay for one of them.
The case against: You are configuring a general website tool for a single screen, and the launch-specific pieces — countdown behaviour at zero, the status code — are yours to work out.

A plugin on the CMS you already run

~15 min

If WordPress is already installed and serving, a maintenance or coming-soon plugin puts a screen in front of it without touching DNS.

Pick it when: The site exists and you are hiding it, rather than launching something that does not exist yet.
The case against: Requires the CMS to be installed and running — useless before it exists. And most plugins do not say which status code they send.

A hosted launch page

~5 minours

A tool that only does this one screen. The form is connected on arrival, the countdown knows what to do at zero, and the page answers 200 because that is the only thing a launch page should do.

Pick it when: The page must stay up for months, collect addresses reliably, and change without a deploy.
The case against: It is another subscription, and the page lives on someone else’s platform until you export it. Check the export works before you rely on it — here, every design also downloads as a .zip.

Nothing at all

~2 min

One HTML file with a sentence and a mailto link, served from anywhere. No form, no clock, no build.

Pick it when: You are not collecting emails and the page is a placeholder, not a campaign.
The case against: No list, no measurement. If the launch matters, you are giving up the audience you could have had waiting for it.

The honest case

When a builder is the wrong purchase

The page will be up for under a fortnight. A static file on hosting you already pay for is fine. Nothing about two weeks justifies a new account and a subscription you will forget to cancel.

You are not collecting emails. If there is no list, the page is a sign. Signs do not need dashboards. Write the HTML, upload it, move on.

The real site already exists behind a login. You want maintenance mode on your existing stack, not a second product with a second domain to point. That is a different thing with a different status code — and getting it backwards is the most common launch-page mistake there is.

A builder earns its keep when the page has to stay up for months, collect addresses reliably, and change without a deploy. Below that line, you are buying convenience you will use twice.

If the line is above you

14 templates, each with a live demo you can submit a real address into before deciding. 8 of them also download as a plain .zip — no account, no email wall — so you can take route one instead if that suits you better.

See the templates Publish one free

Questions

Straight answers

Do I need a page builder for a coming soon page?

Not if the page is up for a couple of weeks, you are not collecting email addresses, and you have somewhere to put a file. A builder earns its keep when the page has to run for months, capture a list reliably, and change without a deploy.

What is the fastest way to get a launch page live?

A hosted page, at roughly five minutes, because nothing needs wiring. A static file is about twenty once you count editing and uploading — and longer if you then connect a form endpoint.

Can I use Carrd or Wix instead?

Yes, and they do it well. They are general site builders, so you get a bigger editor and a bigger template library, and you work out the launch-specific details — what the countdown does at zero, which status code the page returns — yourself.

Is a free coming soon page builder good enough?

For one page, usually. Read what the free tier caps: number of pages, number of subscribers, and whether the addresses can be exported. A free plan you cannot export from is the expensive kind.

What if WordPress is not installed yet?

Then a plugin cannot help, which is the case most comparison articles skip. Point the domain at a hosted page or a static file, collect addresses while you build, and repoint once the real site is ready.