Should I validate the idea alone or find a partner first?

Do both, in parallel, rather than treating them as sequential. Solo validation risks tunnel vision, you ask questions that confirm what you already believe. A second person, even one who joins loosely at first just to think it through with you, catches blind spots a solo founder usually misses.

How many customer conversations count as real validation?

10-15 structured conversations with people who actually have the problem is a reasonable floor, fewer than that and you're likely pattern-matching on a handful of anecdotes. The content of the conversations matters more than the count: are you asking about their current behavior and past spending, or asking them to predict whether they'd buy your unbuilt product (which people are notoriously bad at answering honestly)?

What if validation shows the idea doesn't work?

That's validation working correctly, not failing. Most first ideas don't survive real customer conversations intact, and finding that out in week two is far cheaper than finding it out after building for six months with a cofounder. A good validation partner is someone who'll tell you the idea isn't landing, not someone who agrees to keep you comfortable.

Blog Podcast

Validate a startup idea before you commit to a cofounder

Talk to 10-15 people who actually have the problem before you look for a cofounder, not after. Validation and cofounder search are often treated as sequential, but the honest version is that you need a sounding board during validation itself, someone to challenge your assumptions before you've both committed months to the wrong version of the idea. A public profile that says you're validating, not pitching, attracts exactly the kind of person who's useful at this stage.

By Curtis ThomasLast updated 2026-08-05

Why validation and partner search shouldn't be sequential

The common advice is: validate the idea alone, then go find a cofounder once you know it works. In practice this produces founders who spend weeks confirming their own assumptions to themselves, then approach a potential cofounder with a conclusion instead of an open question. A sounding board during validation, someone who'll push back before you're both invested, produces a better-tested idea and a real early signal of whether this specific person is good to build with.

What real validation looks like

Talk to 10-15 people who actually have the problem today, not people who might theoretically have it someday.
Ask about current behavior and past spending, not hypothetical future intent. "What do you use today, and what does it cost you" beats "would you use this if it existed."
Look for people who are already paying for a worse solution, that's a stronger signal than enthusiasm alone.

Finding a validation partner, not just a cofounder

You don't need to offer equity to someone just to get their honest reaction to a rough idea. Framing the ask as "I'm validating an idea in [space] and want a sounding board" is lower-commitment and lower-friction than "I need a cofounder," and it attracts people who are genuinely curious about the problem rather than people evaluating whether to bet a year of their career on you immediately. Some of these relationships turn into real cofounder pairings once the idea has legs; others stay useful, lower-stakes conversations. Both outcomes are fine.

A public profile with a "still validating, want a sounding board" description works well for this, see how to describe what you need if you're not sure how specific to be.

When to move from sounding board to real commitment

Once validation shows real signal, real people, a real problem, real willingness to pay, and your sounding board has been genuinely useful rather than just agreeable, that's the point to have the actual cofounder conversation: equity, vesting, and commitment. Doing this before validation, based on excitement alone, is the most common way founding teams end up misaligned six months in.

Looking for someone to validate with? Browse the public directory.