Customer Discovery Process for Validating SaaS Idea

Customer discovery is the practice of talking to at least 20 people who fit your target profile, before your product exists, to learn whether the problem is real, repeated, and expensive. It's the stage nearly everyone skips because it's uncomfortable, slow, and it might tell you something you don't want to hear. It's also where you find out whether you're about to spend six months building something people will actually pay for. This article covers the full process: why it comes first, how many interviews you need, where to find the people, and how to know when you're done.

What is customer discovery and why does it come before building?

Customer discovery is structured learning from your target customers about their problem, run before you build so the findings can still change what you build. It comes first because the information that would save you from building the wrong thing exists before you write any code, and the only way to get it is to ask.

The reason discovery beats building-first is a matter of cost and reversibility:

Interviews are cheap and reversible. A round of 20 conversations costs you time and maybe a few hundred dollars. If they reveal the idea is wrong, you pivot for free. Building is expensive and sticky. Once you've built, sunk cost sets in. You defend the thing you made instead of testing whether anyone wants it. The findings arrive in time to matter. Discovery done before building can redirect the whole product. The same lessons learned after launch cost months and are far harder to act on.

There's a concrete version of this trade. A study of 20 interviews can cost around $500 and kill a feature before you spend $10,000 engineering it. That asymmetry is the entire argument for doing discovery first, and it's why experienced founders treat it as non-negotiable rather than optional.

Why do most founders skip customer discovery?

Most founders skip discovery because it's slow, socially uncomfortable, and it risks surfacing the one thing they don't want to hear: that the idea isn't as good as they think. Building feels like progress. Talking to strangers feels like delay. So the instinct is to retreat into the work that's comfortable and looks productive.

The skip is expensive in a specific, well-documented way:

"Build it and they will come" is a myth that drains founders. The belief that a good product markets itself leads people to pour months into building before confirming anyone wants it. Premature scaling is the top killer. Roughly 85% of SaaS ventures fail within 18 months, primarily from scaling without demand signals, exactly the signal discovery is designed to produce. Skipping feels safe and isn't. Avoiding hard feedback protects your enthusiasm in the short term and destroys your runway in the long term.

The founders who don't skip it aren't braver or smarter. They've just internalized that a few uncomfortable weeks of conversations are cheaper than a few wasted quarters of building. The discomfort is the price of finding out early.

How many customer interviews do I actually need?

Aim for at least 20 interviews with people who fit your target, because that's roughly where a focused segment reaches pattern repetition, the point where you can predict what the next person will say before they say it. For a single, narrowly defined customer segment, themes often start repeating between interviews 5 and 8, but 20 gives you the confidence that the pattern is real and not a small-sample fluke.

There's a useful way to think about what each block of interviews does:

Interviews 1 to 5: map the white space. You think you understand your customer. These first conversations show you what you actually don't know yet about their world and their real problem. Interviews 6 to 10: confirm the patterns. The themes from the first five either repeat or fall apart. This is where a hunch becomes a finding. Interviews 11 to 20: refine and sharpen. You incorporate the critical feedback, tighten your understanding of the pain, and start being able to predict answers. Push to 30 if you can. By then you understand the customer deeply, and some of these people can start converting into your first real users.

If you're researching more than one distinct segment, plan for 10 to 15 interviews per segment, not 20 total, because each segment has its own patterns. The number to trust isn't a fixed count, it's the moment new interviews stop teaching you anything new.

How do I know when I've talked to enough people?

You've talked to enough people when you hit research saturation, the point where each new interview reinforces existing themes instead of uncovering new ones. Experienced researchers don't interview until they hit a number; they interview until they hit saturation, and then they stop. The number follows the learning, not the other way around.

The signs you've saturated:

You can predict the answers. Before the person responds, you already know roughly what they'll say. That predictive confidence is the clearest marker. No new themes appear. The last several interviews have added detail to existing patterns but haven't surfaced a genuinely new problem, workaround, or trigger. You're confirming, not discovering. Your mental state shifts from "what will I learn?" to "yes, that matches what the others said." The workarounds and costs repeat. The same spreadsheets, the same manual processes, the same rough time-and-money costs keep coming up across independent people.

One critical adjustment: count evidence, not interviews. Ten conversations packed with real workarounds and real spend are worth more than thirty full of polite "sounds useful" responses. If you've done 20 interviews and heard 20 nice reactions but found no workarounds, no spend, and no commitments, you haven't validated anything, you've collected encouragement. Weigh the facts (existing workarounds, real spend, offered commitments), not the tally.

Where do I find people to interview if I have no audience?

You find them in the specific communities and platforms where your target customer already spends time, which you identified when you narrowed your ICP. Having no audience is not a blocker for discovery, because discovery is outbound: you go to them, they don't come to you.

The channels that reliably work for early discovery:

LinkedIn, plus Sales Navigator for B2B. The highest-precision channel for reaching people by role, industry, company size, and seniority. Sales Navigator lets you filter to your exact ICP and message decision-makers directly. Niche subreddits. Not r/SaaS alone, but the specific subreddit where your customer talks shop, r/shopify for e-commerce sellers, a trade-specific subreddit for a vertical tool. People there are already discussing their problems in public. Slack and Discord communities. Industry and role-based communities where your ICP gathers to ask each other questions. High-trust, high-context, and full of people living your problem daily. Indie Hackers. Strong for founder- and operator-facing tools, where people openly discuss what they're building and struggling with. Industry newsletters and niche forums. Older, quieter, but often dense with exactly the specialist audience you need.

The pattern across all of these: go where the conversation about your problem is already happening, and join it honestly. You're not there to pitch. You're there to learn from people who have the pain.

How many people do I need to message, and how do I book the calls?

Expect to message 100 to 200 people to book 10 to 20 calls, because most people ignore a first message and only a fraction of those who reply will actually schedule. The conversion from message to booked call is low, and that's normal, not a sign you're doing it wrong.

The mechanics that work:

Reach out honestly, not with a pitch. Tell people plainly what you're exploring and that you'd value 20 to 30 minutes of their input. No fancy templates, no fake flattery. You're asking for help, not selling. Lead with their expertise, not your idea. "You clearly deal with X all the time, I'd love to understand how" beats "I'm building a tool for X." People like being asked about what they know. Follow up relentlessly. Message again, and again. Most replies come after the second or third touch, not the first, because most non-replies are habit, not rejection. Make booking frictionless. Send a Calendly link so people can grab a slot without a back-and-forth. Aim for 20 to 30 minute calls. Ask for two or three intros at the end of every single call. Every person you talk to knows others with the same problem, but they won't offer introductions unless you ask. This is how a cold list of 20 snowballs into a warm pipeline, and referred conversations are warmer, easier to book, and better-targeted than cold outreach.

The math is simple and unglamorous: if you need 10 calls, expect to message 100-plus people. Too many founders spend their energy perfecting a deck or waiting for the perfect warm introduction instead of just sending the messages.

Why is talking to the wrong people worse than talking to no one?

Talking to the wrong people is worse than talking to no one because it fills your notebook with confident, irrelevant data that points you in the wrong direction. Ten conversations with people who aren't your ICP are worth less than one conversation with someone who is, and they're actively dangerous because they feel like progress.

The specific harms of off-target interviews:

False patterns. Non-ICP people have different problems, so their repeated themes can look like a signal while pointing you at the wrong product entirely. Wasted saturation. You might hit "pattern repetition" across the wrong audience and conclude you've validated something you haven't. Misleading enthusiasm. People outside your target might love the idea for reasons that will never translate into your actual market paying for it.

The fix is to screen for fit before you invest a full call: do they actually have the problem, in the context and at the scale your ICP describes? A related trap is mistaking lukewarm feedback for a soft yes. "That's sort of interesting, but I wouldn't pay for it" implicitly tells you the idea is a waste of time while sounding gentle enough to ignore. A flat no is cleaner data, it lets you pivot early. When you filter outreach and referrals for genuine fit, a stream of no's is the screen doing its job. You're hunting for the people who feel the pain acutely enough to make time for a stranger, and everyone else is noise you're better off without.