Finding & Winning Customers

Customer Discovery Questions That Actually Reveal Demand

Good customer discovery questions uncover past behavior and real constraints — not opinions about your idea. Follow Mom Test principles: ask about their life, not your solution; ask about specifics, not hypotheticals; and talk less than you listen. Log insights so patterns across interviews drive product and ICP decisions.

Updated August 8, 2026.

Mom Test principles in one minute

Rob Fitzpatrick’s Mom Test frames interviews so even a supportive friend cannot mislead you with polite praise. Talk about their problems and past actions. Avoid pitching until you understand how they work today. Compliments and “I would definitely buy that” are weak signals compared to stories of money spent, tools adopted, or failed workarounds.

Problem and context questions

Start with how they do the job today. You are mapping pain, frequency, and ownership — not validating a feature list.

  • "Walk me through the last time you dealt with [problem]. What happened step by step?"
  • "How often does this come up, and who else gets pulled in?"
  • "What does it cost you when it goes wrong — time, money, risk, or reputation?"
  • "Whose priority is this on the team, and who would have to approve a change?"

Workaround and switching questions

Workarounds reveal willingness to act. People who already duct-tape a process are better early customers than people who only complain.

  • "What have you already tried to fix this? What stuck and what failed?"
  • "What tools or spreadsheets are involved today, and what do you dislike about them?"
  • "If you hired someone tomorrow to own this, what would you ask them to change first?"
  • "What would have to be true for you to switch away from the current approach?"

What not to ask

  • "Would you use a product that does X?" — invites polite yeses.
  • "How much would you pay for this?" before they feel the problem — produces fantasy numbers.
  • Leading questions that describe your solution and ask for approval.
  • Hypothetical futures ("If we built…") before you understand their present.

How to log insights without rewriting history

Capture quotes and facts during or immediately after the call. Separate observation from interpretation so you do not retrofit interviews to support the idea you already love.

  • Record: role, company context, problem story, current workaround, quantified impact, next step.
  • Tag: ICP fit / anti-ICP, urgency high-medium-low, budget signal present or absent.
  • Review weekly: which problem statements repeat unprompted across independent conversations?
  • Only after patterns emerge: share a short pitch and watch for concrete next actions.

Put this into practice on Bowora

Use discovery to clarify ICP and offer, then list on Bowora when you have a clear problem statement and early proof buyers recognize.

Common questions

What are the best customer discovery questions?
Questions about the last time the problem happened, what they tried, what it cost, and who owns the decision. Specific past behavior beats opinions about your idea.
How many discovery interviews should I do?
Keep going until the same problem stories and constraints repeat across independent conversations in your target segment. Early teams often aim for a focused batch (commonly on the order of a dozen serious interviews) before locking a direction — quality and pattern recognition matter more than a fixed count.
Should I mention my product in a discovery call?
Not at the start. Learn their process first. If you pitch early, answers bias toward politeness. Share a brief concept only after you have mapped the problem, then watch for concrete next steps rather than compliments.
How is customer discovery different from a sales call?
Discovery prioritizes learning about their world. A sales call qualifies and advances a deal. Early on the conversations overlap, but if you are still testing the problem, resist closing pressure until you know what to sell.

Sources

Facts, frameworks, and program details were checked against these first-party references. Last content review: August 8, 2026.