How to Validate Startup Ideas (Before Writing Any Code)

The Validation Trap#

Here's a pattern we've seen hundreds of times: A founder has an idea. It feels exciting. They spend 6 months building a product. They launch to... crickets. Turns out nobody actually wanted what they built.

This isn't a failure of execution. It's a failure of validation.

"If I build it, they will come" is one of the most persistent myths in startups. According to CB Insights, 42% of startups fail because there's no market need—not because of bad execution, running out of money, or getting outcompeted. They simply built something nobody wanted.

The solution is counterintuitive: validate BEFORE you build. Test demand with zero code. If people won't sign up for a landing page, they probably won't pay for a product either.

The goal of validation isn't to prove your idea is good. It's to discover if it's bad—as quickly and cheaply as possible.

Step 1: Find Real Pain Points#

The foundation of any good startup idea is a real pain point. Not "wouldn't it be cool if..." but "people are actively suffering from this problem right now."

Where to find pain points:

• Reddit: Subreddits like r/SaaS, r/startups, r/smallbusiness, and niche industry communities
• Twitter/X: Search for complaints in your target market
• Hacker News: "Ask HN" threads, Show HN feedback
• Support tickets: If you work in an industry, look at what customers complain about
• Industry forums: Specialized communities where professionals vent

What to look for:

• "I hate when..."
• "Why doesn't anyone build..."
• "I'd pay for..."
• "Just spent hours doing X manually"
• Workarounds and hacks that shouldn't need to exist

The key is to find pain, not solutions. Your job is to understand the problem deeply—solutions come later.

Pro tip: StartupWorkshop's Scout does this automatically. It scans communities weekly and matches pain points to your profile, so you can skip the manual scrolling.

Step 2: Talk to Potential Users#

Once you've identified a pain point, validate that it's real and significant by talking to actual people who experience it.

The classic mistake is asking "Would you use this?" or "Do you think this is a good idea?" These questions invite polite lies. Nobody wants to crush your dreams.

Instead, use The Mom Test approach (from Rob Fitzpatrick's excellent book):

Questions to ask:

1. "Tell me about the last time you dealt with [problem]"
2. "How are you solving this today?"
3. "What have you tried that didn't work?"
4. "How much time/money does this cost you?"
5. "What would change if this problem went away?"

You want specific stories about the past, not hypothetical opinions about the future. If someone says "Yeah, that's annoying" but can't remember the last time it actually affected them, it's probably not a big pain point.

How many conversations? Start with 5-10. You'll often see clear patterns emerge quickly. If 8 out of 10 people describe the exact same frustration, you're onto something.

Step 3: Create a Landing Page#

You don't need a product to test demand. You need a landing page.

A validation landing page has three elements:

1. Problem statement: Articulate the pain in their words
2. Solution preview: What you're building to solve it
3. Email capture: The call to action

Here's a minimal HTML structure for reference:

<section class="hero">
  <h1>Tired of [specific pain point]?</h1>
  <p>[Product name] helps you [key benefit] without [current hassle]</p>
  <form>
    <input type="email" placeholder="Enter your email" />
    <button type="submit">Get Early Access</button>
  </form>
</section>

Tools to build this:

• Carrd: $19/year, dead simple
• Framer: More customization, free tier available
• StartupWorkshop: We generate landing pages from your idea description (coming soon)

The page doesn't need to be beautiful. It needs to be clear. Can someone understand what you're building and why they'd want it within 5 seconds?

Step 4: Drive Traffic#

A landing page without traffic is just a tree falling in an empty forest. Here's how to get eyes on it:

Organic approaches:

• Post where your users already hang out (Reddit, Twitter, communities)
• Share your story: "I'm building X because I was frustrated by Y"
• Answer questions related to your problem space, link to your page naturally
• Product Hunt Ship (for "coming soon" pages)

Paid approaches:

• Google Ads: Target keywords people search when experiencing the problem
• Reddit Ads: Very targeted community placements
• Twitter/X Ads: Good for B2B and tech audiences

You don't need a big budget. $50-100 in paid ads can give you meaningful signal within a few days.

The number that matters: Conversion rate. If 1000 people visit and 5 sign up, that's 0.5%. If 100 people visit and 10 sign up, that's 10%. The percentage tells you more than the absolute number.

Step 5: Analyze and Decide#

After running traffic, you'll have data. Here's how to interpret it:

Green light (proceed):

• Conversion rate > 5%
• Multiple people asking when they can pay
• High engagement (replies, shares, questions)
• Strong alignment with interview feedback

Yellow light (dig deeper):

• Conversion rate 2-5%
• Interest but hesitation ("looks interesting, but...")
• Inconsistent feedback between interviews and landing page
• Action: Run more interviews, test different positioning

Red light (pivot or kill):

• Conversion rate < 2%
• Little engagement despite decent traffic
• Feedback contradicts interview learnings
• Action: Kill this specific angle, potentially explore adjacent problems

Remember: Killing a bad idea early is a WIN, not a failure. You just saved months of work on something that wouldn't succeed.

Putting It All Together#

The validation loop looks like this:

Find pain point -> Talk to users -> Build landing page -> Drive traffic -> Analyze -> Decide
      ^                                                                              |
      +------------------------------------------------------------------------------+
                                     (if pivot needed)

Each iteration takes 1-2 weeks, not months. You can test multiple ideas in parallel. The goal is to find the intersection of:

1. Real pain: People actually have this problem
2. Willingness to pay: They'd pay to solve it
3. Your fit: You can build it, and you'd enjoy working on it

The StartupWorkshop Way#

We built StartupWorkshop to make this entire process faster and less painful:

• Scout finds pain points for you, matched to your skills and interests
• Deep Dive does competitor research and market analysis (coming soon)
• Validation generates landing pages and tracks conversions (coming soon)

One tool, complete validation loop. No more manual scanning. No more building before validating.

The best time to validate was before you started building. The second best time is now.

Ready to validate smarter? Try StartupWorkshop.