ideacheck
← ideacheck

September 2026 · 7 min read

Customer Discovery Questions That Get Honest Answers

Customer interviews are useful only when they reveal what people already do. The moment a conversation turns into a product pitch, people become encouraging rather than honest. This script keeps the discussion anchored in recent behaviour.

Choose people with recent experience

Do not interview anyone who merely fits a demographic. Interview people who dealt with the problem in the last month. A recent example gives you facts: what happened, what tools they used, and whether the problem was important enough to interrupt their work.

The best participants are strangers or loose connections. Friends want to be supportive, and supportive feedback is one of the fastest ways to build confidence without evidence.

Open with the past, not your solution

Start with: “Tell me about the last time you had to do [job].” Follow the story. Ask what happened before, during, and after. You are trying to understand the workflow, not win agreement for your idea.

Then ask: “What was the hardest part?” and “What did you try?” The second question matters because a workaround signals that the pain has real consequences.

  • How often does this situation happen?
  • Who else is involved when it happens?
  • What does a bad outcome cost in time, money, risk, or missed revenue?
  • What tools, spreadsheets, people, or habits do you rely on today?
  • Have you ever paid to solve it? Why or why not?

Avoid hypothetical questions

“Would you use an app that…” and “Would you pay for…” produce weak evidence. People cannot reliably predict future behaviour, especially when saying yes costs them nothing. A polite yes is not a buying signal.

Instead, ask for evidence from the past. If they say the problem is important, ask when they last tried to fix it, what they spent, and what stopped them. Specifics beat enthusiasm.

End with a concrete commitment

Once you understand the problem, it is reasonable to briefly describe what you are exploring. Then ask for a small but real next step: permission to watch the workflow, an introduction to another affected person, or a paid pilot when a manual version is ready.

A commitment is not a guarantee of future revenue. It is simply stronger evidence than praise. Record what they agreed to, then compare commitments across interviews.

Synthesize after every five calls

Do not wait until the tenth call to examine your notes. After five conversations, write down the repeated trigger, desired outcome, workaround, buyer, and objections. If no pattern appears, change your target segment rather than forcing a conclusion.

A good interview process should sharpen your problem statement. By the end, you should be able to say who has the problem, when it occurs, and what they lose by doing nothing.