A waitlist before you build
Find out if anyone wants it, before you spend a month on it.
Build time ~1 hr
The cheapest possible version of your product is a page describing it and a box to type an email into. If nobody signs up, you've saved a month. If people do, you have their addresses and a reason to keep going.
1. Describe the finished thing honestly
Write the page as though it exists. Not vague futurism — the actual thing, the actual benefit, ideally a screenshot or mockup even if it's fake. Vagueness is what makes waitlist pages fail to convert; people sign up for something specific.
Say plainly that it's not built yet. It costs you almost no signups and buys you enormous goodwill.
2. Collect the email somewhere sane
Don't build a database for this. A form service, a spreadsheet endpoint, or an email provider's hosted form is fine and takes minutes.
Add an email capture to this static page: <paste> - Post to <service, or "recommend one free option and show the setup">. - Validate the address in the browser and let the service validate too. - Show a real success state on the same page — no redirect to a blank "thanks" page. - Handle the failure case: the service being down must not look like a successful signup. - Honeypot field for bots. No captcha. Keep the whole thing under 30 lines of JavaScript.
3. Ask one question
After the email, one optional question: "What are you using for this today?" The answers are worth more than the signups. They tell you what you're actually competing with, in the words your customers use — which then becomes your headline.
4. Then do the unscalable thing
Email the first twenty people personally. Not a broadcast — individual replies asking what they're hoping for. Five of those conversations will change your build order more than any amount of planning.
A waitlist with 40 signups and 10 replies is a better starting position than one with 400 signups and no conversations.