Why Build a Landing Page Before the Product?
The classic startup mistake: spend 6 months building a product, launch it, and discover that nobody wants to pay for it. A validation landing page tests demand in 2–3 days before you write a line of product code. If the page doesn't generate sign-ups from your target audience, the product won't either.
The validation page isn't about tricking people — it's about testing your hypothesis that people have the problem you think they have and would pay to solve it. Full transparency is both ethical and useful.
The Minimum Validation Page
Your validation page needs: a specific headline describing the problem and solution, a visual (mockup or diagram — not a real screenshot), 3 key benefits or features, a social proof element if you have it, and an email capture or waitlist sign-up.
The page does not need to be polished. Tools like Carrd, Notion, or even a Google Form embedded in a simple HTML page are sufficient. The goal is to test the idea, not to build a finished product page.
Driving Traffic to Your Validation Page
Share in 3–5 communities where your target users congregate. Post on Twitter/X describing the problem and asking if it resonates. Reach out directly to 20–30 people who have publicly mentioned the problem. Run $50–100 in targeted paid ads to see if strangers (not just your network) sign up.
The important distinction: sign-ups from your personal network are warm leads who signed up out of support. Sign-ups from strangers who found your page through a community post or ad are demand signals. Both are useful but different.
Reading the Results
What success looks like: 2–5%+ conversion rate from cold traffic, at least 20–30 sign-ups from people you don't know, and specific feedback from sign-ups about why they want the product. What failure looks like: < 1% conversion from targeted cold traffic and sign-ups who can't articulate why they want it.
If your page isn't converting: first diagnose whether the problem is the traffic (wrong audience) or the page (right audience, unclear message). Test with different communities before assuming the idea is wrong.
After Validation: What to Build
Email everyone who signed up, thank them for their interest, and send them 3 questions: 'What's the most important thing you want this product to do?', 'What are you currently using to solve this problem?', 'What would you pay for this?' The answers define your MVP.