Customer Discovery Guide: How to Find Problems Worth Solving
A complete customer discovery guide for founders who want to find real problems worth solving before committing to a build.
Validate your customer discovery findings
Check public demand signals to confirm the problems you discover are real and widespread.
Check Demand SignalsCustomer discovery is the practice of getting out of the building and talking to real potential customers to understand their problems, workflows, and needs. It is the most important research activity an early-stage founder can do. No amount of desktop research, competitive analysis, or AI-powered signal scanning can replace direct conversations with the people you hope to serve.
This guide covers the customer discovery process from start to finish: how to find the right people to talk to, what questions to ask, how to listen for signal, and how to synthesize your findings into actionable insights.
Why Customer Discovery Comes First
Customer discovery exists to answer one question before you build anything: is the problem you want to solve real, painful, and worth paying to fix? Founders who skip discovery and start building from their own assumptions are making the single most common and most expensive mistake in early-stage product development.
The cost of customer discovery is time. The cost of building the wrong product is time plus money plus momentum plus morale. Discovery is the cheapest insurance you can buy against building something nobody wants.
Finding People to Interview
Your customer discovery interviews are only as good as the people you talk to. Talking to friends, family, or fellow founders in unrelated fields produces polite, supportive feedback that tells you nothing about whether a real market exists for your idea.
The best interview subjects are strangers who match your target customer profile and have no reason to spare your feelings. Find them in relevant communities — subreddits, LinkedIn groups, industry forums, Slack communities. Reach out with a simple, honest request: I am researching a problem in your space and would love to ask you a few questions about your experience.
- Target people who currently experience the problem you want to solve
- Look for people who have tried existing solutions and found them wanting
- Interview people who represent your ideal customer profile, not your broadest possible audience
- Aim for 10 to 20 interviews before drawing conclusions
- Each interview should focus on understanding the problem, not pitching your solution
What to Ask in a Customer Discovery Interview
The Mom Test framework provides the most reliable interview approach. The core principle is simple: ask questions that would reveal whether the problem is real, without leading the person toward a positive answer by describing your solution.
Good questions explore the person's current behavior and experience. Bad questions ask for opinions about your idea. Ask about the last time they experienced the problem, what they did about it, how much time or money it cost them, and what they wish existed instead.
How DemandProofHQ Complements Customer Discovery
DemandProofHQ helps you prepare for customer discovery by scanning public demand signals first. The report you get back tells you what signals already exist for the problem you are researching, which communities to look in for interview subjects, and what language potential customers use to describe the problem. This makes your discovery conversations more targeted and productive. Start at /idea-check.
DemandProofHQ helps review public demand signals, but it does not guarantee product-market fit or replace direct customer conversations.
Prepare for better customer discovery
Check public demand signals before your interviews to focus on the most promising problems.
Start ResearchRecommended next steps