If you want the fastest useful path, start with "Write your idea as a specific problem statement, not a product description" and then move straight into "Find and interview ten people who have the problem you are solving". That usually gives you enough structure to keep the rest of the guide practical.
Know your actual use case
This guide is written for a pre-build validation framework that helps founders test demand with real market evidence before committing engineering resources., so define the real problem before you try every step blindly.
Keep the scope narrow
Focus on lean and mvp first instead of changing everything at once.
Use the guide as a sequence
Use the overview first, then jump to the section that matches your current decision or curiosity.
Write your idea as a specific problem statement, not a product description
Step 1Reframe from 'I want to build an app that does X' to 'People who are [audience] struggle with [problem] and currently solve it by [workaround].' If you cannot fill in [workaround], you may be solving a problem that does not actually bother anyone enough to pay for a solution.
Find and interview ten people who have the problem you are solving
Step 2Talk to real potential users — not friends or family. Ask them about the last time they experienced the problem, how they currently handle it, and how much time or money they spend on workarounds. Do not pitch your idea. Listen for pain intensity and existing spending.
Build a simple landing page describing the solution and collect signups
Step 3Create a one-page site with a clear headline, three key benefits, and an email signup form. Drive 200-500 visits through targeted Reddit posts, relevant communities, or $50-100 of Google Ads. A conversion rate above 5% suggests real interest — below 2% suggests weak demand.
Test willingness to pay, not just willingness to express interest
Step 4Add a pricing page or pre-order option to your landing page. Signups measure curiosity. Credit card entries or pre-orders measure real demand. The gap between people who say they would pay and people who actually enter payment info is typically 10:1.
Set a kill criteria before you start building
Step 5Define in advance what evidence would make you proceed and what would make you pivot. Example: 'If I get 50 email signups and 5 pre-orders in 30 days, I build. If not, I test a different idea.' This prevents emotional attachment from overriding weak data.
What if someone steals my idea during validation?
Ideas are worth almost nothing — execution is everything. The risk of someone stealing and successfully executing your idea from a landing page is near zero. The risk of building in secret for six months and discovering nobody cares is very high. Validate openly.
Can I validate without spending money?
Yes. Free landing page tools like Carrd or Notion, organic posts in relevant online communities, and in-person conversations cost nothing. Paid ads accelerate the data collection but are not required. Budget validation is slower but equally valid.
How many customer interviews are enough?
Ten interviews usually reveal clear patterns if they exist. If after ten conversations you hear the same problem described consistently with similar workarounds and frustration levels, you have signal. If every conversation reveals different problems, your target audience is too broad.
What counts as a validated idea?
Validation is not binary — it is evidence strength. A strongly validated idea has: 10+ interviews confirming the problem exists, a landing page with 5%+ conversion rate, and at least some people willing to pay before the product exists. Weak validation is friends saying they like the concept.
