Should I launch a waitlist or keep building?

Launch a waitlist or keep building is the wrong question, and it is the one almost every pre-launch founder gets stuck on. The real question is whether you have enough evidence that anyone wants this — and building longer does not produce that evidence.

Why "is it ready?" is unanswerable

Readiness has no threshold. There is always another feature, another edge case, another polish pass — and every one of them feels like the last thing standing between you and launch.

The reason the question never resolves is that you are the wrong person to answer it. You know every flaw. A prospective customer knows none of them and is comparing you to a spreadsheet, not to your mental image of the finished product.

Replace it with an answerable question: can someone get one useful outcome from this today? Not the full workflow. One outcome, once. If yes, you are past the readiness threshold that matters.

What a waitlist actually tests

Not demand for your product. Demand for your description of the problem — which is a more useful thing to test at this stage, because if the description does not land, the product cannot save it.

A waitlist page needs four things and nothing else: the problem in the customer's language, who it is for, what it replaces, and an email field. No feature list, no screenshots you are embarrassed by, no launch date.

The description work here is the same work as positioning, done early and cheaply. Most founders do it after launch, when it is expensive.

The number that matters

Signups are the vanity metric of waitlists. Two hundred emails from a launch post means almost nothing — people subscribe to things at near-zero cost and forget within a day.

The real test comes next. Email everyone on the list one question: what are you using for this today? Then count replies.

Ten replies describing the same painful workaround is worth more than a thousand unengaged signups, and it is the input you need for setting a price before launch.

When to keep building instead

Two situations genuinely justify it, and neither is "it does not feel ready".

The product cannot produce one useful outcome yet. If nobody could get anything out of it even with you sitting beside them, a waitlist is premature — you have nothing to describe. Build the single path that produces one outcome, then stop.

The demo would actively damage trust. For products handling money, health data or client records, a visibly broken first impression is expensive with exactly the professional audience you want. Even then: waitlist page yes, product demo no.

Everything else — missing features, unpolished design, incomplete settings — is not a reason to wait. It is a reason to be clear about what the early version does.

The version most founders should run

Waitlist page and continued building, in that order, with one difference: what you build is now decided by what the repliers tell you rather than by what you imagined.

A concrete week: put the page up, share it in the two places your buyers gather, email everyone who signs up with the one question, and interview the first five who reply. Then build for a month knowing something.

The alternative — another month of building on assumptions — costs the same month and produces no new information. That is the entire argument.

Once the waitlist is working

Ship to the repliers before you feel ready. Early users who told you their problem are the most forgiving audience you will ever have, and they convert far better than strangers.

Then run the actual launch as a separate event once you have a handful of paying customers and some evidence — the launch playbook covers that sequence, and it works far better with existing users than from zero.

If the waitlist produces nothing after two attempts in different places, that is real information about the idea rather than the page. Knowing when to kill an idea covers reading that honestly.

Waitlist or keep building FAQ