How to validate a startup idea without wasting months building the wrong thing

Executive overview

Builders default to coding first and skip talking to customers — then launch to silence. The 2-20-200 framework structures validation into three escalating time investments before you commit to a full build.

Two hours of research, twenty hours of conversations or landing page testing, then two hundred hours of MVP work. Each gate filters bad ideas before the cost compounds.

Build only after the market pulls you forward, not after you've already built.

The 2-hour pre-validation (5PM framework + SEO research)

• 5PM framework covers six dimensions: problem, purchaser, pricing model, market, product-founder fit, pain to validate
• Full 5PM walkthrough available in episode 628 of Startups for the Rest of Us
• SEO research identifies where potential customers talk: Reddit, Twitter, Facebook groups
• Check whether people are actively searching for a solution — if not, expect heavy outreach work
• Run all five ideas through this step first; only advance the strongest one or two

The 20-hour validation (conversations and landing pages)

• Start with warm outreach — your network, people who already know you
• Treat audience-based validation with caution: followers encourage rather than commit (the "curse of the audience")
• For cold outreach, go where the pain lives: LinkedIn, Reddit, niche Facebook groups
• Offering to pay for an expert's time removes friction; most will talk for free anyway
• Target 11–40 genuine "yes, I'd use this" responses before proceeding — 3 is too few, 100 adds little signal past 40
• A landing page works as an alternative or complement: clear value proposition, email capture, then follow up directly with sign-ups

The 200-hour MVP build

• Only start building after clearing the 2 and 20 steps
• MVP doesn't have to be code — no-code or human-in-the-loop automation can work
• Goal is getting something into customers' hands to begin the iteration cycle

When you can skip validation

• If an MVP takes fewer than 20–40 hours to ship, building it may be faster than validating
• Developers often use "fast build" as an excuse to avoid customer conversations — be honest about realistic build time

Recommended next reading

• Start Small, Stay Small by Rob Walling — market-first mindset for developers
• Deploy Empathy by Michelle Hansen — how to run effective customer conversations at any stage