Customer Discovery Interview Questions That Reveal Pain

Most customer discovery interviews fail for a boring reason: the founder asks people to imagine the future, and people are happy to imagine anything.

You ask “would you use this?” and you get a friendly yes. You ask “how much would you pay?” and you get a number that means nothing. Six interviews later you feel validated and you have learned almost nothing.

The fix is not a better questionnaire. It is asking about the past.

The one rule that makes discovery work

Ask about things that already happened. The past is fixed, so people report it roughly accurately. The future is a hypothesis, so people guess, and their guesses are shaped by being polite to you.

Every good discovery question has the same shape: “Walk me through the last time you had to do X.” You are a detective reconstructing a real event, not a salesperson testing a pitch.

Questions that surface the past

These questions consistently produce usable detail:

• “When did you last run into this problem?” Anchors the conversation in a specific event.
• “Walk me through what you did, step by step.” Reveals the workaround you are competing with.
• “What did that cost you — time, money, or both?” Turns pain into a number.
• “What else have you tried?” Surfaces the competitors and the abandoned attempts.
• “What made you start looking for a fix?” Finds the trigger event that creates urgency.
• “Who else is affected when this goes wrong?” Exposes the real buying committee in B2B.

Notice that none of these mention your product. If you can get through an interview without pitching, you will learn more than from ten that turn into demos.

Questions that look clever but lie

Avoid anything that invites imagination:

• “Would you use a tool that…?” — hypothetical, and flattering to you.
• “How much would you pay for…?” — a guess about a product that does not exist.
• “Do you think this is a good idea?” — people dislike saying no to your face.
• “How often do you think you’d need it?” — you want the real frequency you already found in their past.

If you must talk about the future, ask about commitment instead of opinion: “When this happens again next month, can I show you an early version?” A yes to that is worth more than any number.

Follow-ups that do the real work

The first answer is rarely the useful one. The value is in the follow-up:

• “Why?” — repeated two or three times, gently, until you reach the real reason.
• “What happened next?” — keeps the story moving and exposes consequences.
• “You mentioned X — tell me more about that.” — pulls on the thread the person almost skipped.
• “What would have had to be true for you to keep using the last tool?” — reveals why the last attempt failed.

Silence is also a tool. Ask, then wait. The gap usually fills with the most honest sentence of the conversation.

How to analyze what you heard

After five to ten calls, stop and read the notes side by side. You are looking for themes, not votes. A problem mentioned casually by twelve people may matter less than one that caused visible frustration in six. Count frequency and intensity separately, and attach the exact quote to each theme. That quote discipline is the same reason quotes matter more than summaries.

Then write one sentence: “When [situation], [buyer] wants to [outcome], so they can [result].” If you cannot fill it in from what people actually said, you need more interviews, not more code.

FAQ

How many interviews before I can trust the result?

Ten is a common floor, but ten is not a magic number. You stop when new interviews stop telling you anything new. If the fifth, sixth and seventh call repeat the same theme, you are close.

Do I need to record the calls?

Recording helps, with permission. If you cannot, take notes on quotes verbatim and mark the moments where emotion rose. Do not summarize into your own words right away; that is where bias enters.

What if someone asks me what I am building?

Answer briefly and honestly, then return to their past: “I am exploring that, but I would rather understand how you handle it now.” You can always pitch after the interview.

Where do I find people to interview?

Go where the problem lives: niche communities, your competitor’s reviewers, and people who posted about the pain in public. You can also start from public complaints that already describe the workaround, then invite a few of those people to a short call. If you want the problem list first, run a research report for 2.99 EUR and interview around validated signals instead of guesses. Then use the interview template to keep every call consistent.