TL;DR
Most founders accidentally pitch during customer discovery interviews instead of discovering anything. The fix: ask about current behavior, not hypothetical futures. This guide covers 15 questions that produce useful answers, the questions you should never ask, how to interpret polite responses that mean nothing, and what to do after 10-15 interviews. Validate the market with data first, then use these questions to test pain and willingness to pay.
Customer discovery has a simple goal: figure out whether the problem you want to solve is real, painful, and worth paying to fix.
Most founders skip it. The ones who do it usually do it wrong. They describe their idea, ask "would you use this?", hear "yeah, that sounds great," and count it as validation. It is not.
Rob Fitzpatrick wrote The Mom Test to fix this. The core idea: even your mom will lie to you about your startup idea if you ask the wrong questions. The right questions are about their life, their behavior, and their spending. Not about your product.
This interview style also sits inside Steve Blank's customer development framework: talk to people early, before you confuse your own enthusiasm with evidence.
Below are the questions that work, the questions that waste time, and how to tell the difference between a polite "sounds cool" and a real signal.
What Is Customer Discovery Supposed to Uncover?
Customer discovery is not market research. Market research tells you whether a market exists: competitors, demand signals, market size. Customer discovery tells you whether the pain is strong enough to build for.
After 10-15 interviews, you should know:
- Whether the problem is real: Do people describe it unprompted, or only when you bring it up?
- How they handle it today: Current workarounds, tools, manual processes, or spending
- How painful it is: Mild annoyance vs. costs them hours, money, or lost customers
- Whether they would pay to fix it: Based on current spending patterns, not hypothetical answers
- Who the buyer actually is: Job title, company size, decision-making authority
If you finish 15 interviews and cannot answer these five questions with specifics, your interviews were too soft. Go back and ask harder questions.
The Mistake Founders Make Before the Interview Starts
The biggest customer discovery mistake happens before a single question is asked: the founder pitches.
It looks like this: "I am building an AI tool that helps founders validate their startup ideas. Would you use something like that?" The interviewee says "yeah, totally." The founder writes down "strong interest." Nothing was learned.
The problem is that the question asks for a prediction about hypothetical future behavior. Humans are terrible at predicting their own behavior. They are good at describing their current behavior. That is what you should ask about.
"Talk about their life instead of your idea."
Before your first interview, write down your three riskiest assumptions. What must be true for your idea to work? Those assumptions become your interview guide. Every question should test one of them.
15 Customer Discovery Questions That Actually Work
These questions are organized by what they uncover. You do not need to ask all 15 in every interview. Pick 5-7 based on your riskiest assumptions.
Questions About Current Behavior
These establish what the person does today. Current behavior is the most reliable predictor of future behavior.
1. "How do you currently handle [problem]?"
Opens the door without leading. If they have a detailed answer, the problem is real. If they shrug, it is not painful enough.
2. "Walk me through the last time you dealt with this."
Forces specifics. Generalizations hide the truth. A real story reveals the actual workflow, frustrations, and time spent.
3. "How often does this come up?"
Frequency matters. A painful problem that happens once a year is different from one that happens daily. Daily pain drives purchasing.
4. "What have you tried so far to fix it?"
If they have tried nothing, the pain is not strong enough. If they have tried 3 tools and none worked, you found a gap.
5. "What do you like about your current approach?"
Surprising answers here. People tolerate bad solutions because they are familiar. Your product needs to beat the switching cost, not the current solution's quality.
Questions About Existing Alternatives and Workarounds
These reveal your real competition: not the product you think you compete with, but the behavior you need to replace.
6. "What tools or services do you use for this right now?"
Maps your competitor landscape from the buyer's perspective. Often reveals competitors you missed in desk research.
7. "What do you dislike most about how you handle this today?"
Direct path to unmet needs. The complaints they volunteer are your feature priorities.
8. "Have you looked for a better solution recently?"
If yes, they are an active buyer. If no, they have accepted the status quo. Active buyers convert faster.
9. "Why did you stop using [previous tool]?"
Churn reasons from competitors are gold. They tell you what to avoid and what to guarantee in your positioning.
Questions About Urgency and Willingness to Pay
These separate "nice to have" from "need to have." The hardest and most important questions in customer discovery.
10. "How much time or money do you spend on this per month?"
Quantifies the pain. If they spend $0 and 0 hours, they do not care enough to pay you either. If they spend $500/month on a workaround, your pricing has a ceiling and a floor.
11. "What happens if you do nothing about this?"
Tests urgency. If the answer is "nothing bad, really," the problem is not urgent enough to drive a purchase. If the answer involves lost revenue, wasted time, or missed opportunities, you have urgency.
12. "If a solution existed that did [core value], what would it be worth to you?"
Weaker than observing actual spending, but useful for framing. Compare their answer to what they currently spend. Big gaps mean they are guessing.
13. "Who else in your company would need to approve buying this?"
B2B essential. Reveals the decision-making chain. If the person you are interviewing cannot buy without approval, you need to understand who can.
14. "Can I follow up with you when we have something to show?"
Soft commitment test. A "yes" with their email is a signal. A vague "sure, whenever" is polite deflection.
15. "Do you know anyone else who deals with this problem?"
Referrals are the strongest signal. If they introduce you to a colleague or friend, they consider the problem worth solving. Also a free way to fill your interview pipeline.
Questions Founders Should Never Ask
These questions feel productive but produce useless data. Every one of them invites the interviewee to tell you what you want to hear.
| Bad question | Better question | Why |
|---|---|---|
| "Would you use a tool that does X?" | "How do you handle X today?" | Hypothetical vs. actual behavior |
| "Do you think this is a good idea?" | "What have you tried so far to fix it?" | Opinion vs. evidence of action |
| "How much would you pay for this?" | "How much do you spend on this now?" | Fantasy budget vs. real spending |
| "Wouldn't it be great if...?" | "What is the hardest part of this for you?" | Leading vs. open-ended |
| "Do you have this problem?" | "Tell me about the last time you dealt with..." | Yes/no vs. narrative with details |
The pattern: bad questions ask people to predict or evaluate. Good questions ask people to describe and recall. Predictions are unreliable. Descriptions are data.
How to Interpret Polite Answers That Mean Nothing
The hardest part of customer discovery is not asking the questions. It is interpreting the answers honestly. Most people are polite. Polite answers feel like validation but contain zero information.
| What they say | What it means | Signal strength |
|---|---|---|
| "That sounds really cool" | They are being polite. Nothing was learned. | None |
| "I would definitely use that" | Hypothetical intent. Costs them nothing to say. | Weak |
| "Send me a link when it launches" | Mild interest. No commitment. | Low |
| "Can I sign up for the beta?" | Active interest. They are willing to invest time. | Medium |
| "Can I pay for early access?" | Real commitment. Money on the table. | Strong |
| "Let me introduce you to my colleague who handles this" | Referral = social capital spent on your idea. | Strong |
The signal strength ladder: compliment < opinion < time commitment < money commitment < referral. Only the last three count as validation.
What to Do After 10 to 15 Interviews
After your interviews, score your findings. Here is a simple tagging system:
For each interview, tag the responses:
| Tag | Meaning | Example |
|---|---|---|
| PAIN | Described the problem unprompted or with emotion | "I spend 3 hours every week manually pulling competitor data" |
| WORKAROUND | Has a current solution, even if imperfect | "I use a spreadsheet and check G2 once a month" |
| SPEND | Currently pays money or significant time | "We pay $200/month for SimilarWeb but only use 10% of it" |
| MEH | Acknowledged the problem but showed no urgency | "Yeah, it is annoying but I have bigger priorities" |
| POLITE | Generic positive response with no substance | "That sounds like a great idea" |
Decision framework:
- 8+ PAIN or SPEND tags out of 15: The problem is real and painful. Build.
- 5-7 PAIN/SPEND tags: Promising but unclear. Narrow your target audience and do 5 more interviews with a tighter definition.
- Fewer than 5 PAIN/SPEND tags: The problem is not painful enough for this audience. Pivot the audience, reframe the problem, or move to a different idea.
- Mostly POLITE tags: Your questions were too soft. Go back and ask harder questions about current behavior and spending.
Combine this with your market validation data. Desk research tells you whether the market exists. Interviews tell you whether the pain justifies building. You need both.
Customer Discovery Mistakes That Waste Your Time
1. Interviewing friends and family
They will tell you what you want to hear. Always. Confirmation bias is strongest with people who care about you. Interview strangers who match your target customer profile.
2. Running the interview like a survey
A rigid list of 20 questions read in order produces shallow answers. Start with 2-3 open-ended questions. Follow the thread. The most useful insight usually comes from a follow-up question you did not plan.
3. Pitching instead of listening
If you talk more than 30% of the time, you are pitching. Customer discovery means the customer talks. You listen, probe, and take notes. Save the pitch for after you have validated the problem.
4. Stopping after 3 interviews
Three interviews is anecdotal. Ten is a minimum. Patterns emerge around interview 8-10. If you stop at 3 because the first three were positive, you are confirming your bias, not testing your assumptions. Our startup validation guide covers how to combine interview data with desk research for a complete picture.
5. Skipping desk research before interviews
Walking into interviews without knowing your competitors, the market size, or existing demand signals means you will ask worse questions and miss follow-up opportunities. Run a free Preuve scan first, or follow our step-by-step product idea validation guide. Use the competitor and demand data to inform better interview questions.
Frequently Asked Questions
How many customer discovery interviews should I do?
10 to 15 interviews is the minimum for pattern recognition. After 10 interviews, you should see recurring themes. If every conversation surfaces a different problem, either your target customer definition is too broad or the problem is not painful enough. After 15 interviews with clear patterns, you have enough to make a decision.
What is the difference between customer discovery and customer validation?
Customer discovery is about understanding the problem: who has it, how they deal with it, how painful it is. Customer validation is about testing your solution: does your product solve the problem well enough for people to pay? Discovery comes first. You cannot validate a solution if you have not confirmed the problem.
Should I tell interviewees about my product idea?
Not until the last 5 minutes, if at all. The moment you pitch, the conversation shifts from honest discovery to polite encouragement. Ask about their current behavior, workarounds, and spending first. If you mention your idea, do it at the end and watch for commitment signals (asking for a beta, offering to pay) rather than generic praise.
Where do I find people to interview?
Reddit communities, Slack and Discord groups, LinkedIn outreach, Indie Hackers, Twitter/X, and niche forums. Search for people describing the problem you want to solve. A cold DM that says "I am researching how [target audience] handles [problem], would you do a 15-minute call?" usually works best when it is short, specific, and clearly not a sales pitch.
What if people say they love my idea but will not pay?
That is the most common outcome in customer discovery, and it is the entire point of doing interviews. Enthusiasm without commitment means the problem is not painful enough to pay for, or your positioning is off. Dig deeper: ask what they currently spend on workarounds. If the answer is nothing, the pain is not strong enough.
Can I do customer discovery remotely?
Yes. Most startup customer discovery happens over Zoom or Google Meet. Remote interviews work for B2B and B2C. The only advantage of in-person is reading body language and seeing their environment (useful if the problem is physical or spatial). For software products, remote is fine.
Want to run this process in 60 seconds?
Preuve AI analyzes your startup idea against live market data using the same validation frameworks investors use.
Scan My Idea (Free)Free audit. Takes 60 seconds.
