“Would you use this?” feels like a sensible customer discovery question.
It is also very easy to answer politely.
A person can imagine using your product, compliment the idea, and return to their current workflow without changing anything. The conversation feels encouraging, but you still do not understand what happens when the problem appears in real life.
Useful customer discovery questions bring you back to behavior. What happened last time? What did the person do? What did it cost? Who else became involved? Why did they keep the current approach?
The goal is not to persuade someone that your idea is good. The goal is to understand their situation well enough to decide what deserves to be built, changed, or tested.
Start the interview without pitching
Set a simple expectation at the beginning:
I am trying to understand how you handle this today. I am not here to sell you anything. I would like to ask about the last time it happened and what you did.
That framing reduces pressure and keeps the conversation focused on the person rather than your presentation.
Choose people who have recently experienced the situation you want to understand. A detailed interview with the wrong participant creates confident notes about the wrong market. Use your ideal customer profile as a hypothesis, then let the interviews improve it.
Questions about the last real event
Begin with a specific memory. These questions help reconstruct it:
- Tell me about the last time you dealt with this problem.
- What were you trying to accomplish?
- What happened immediately before you noticed the problem?
- How did you decide what to do next?
- Who else was involved?
- How long did the process take?
- What was the hardest part?
If the answer stays general, ask for the most recent example. “Usually” describes a summary. “Last Tuesday” can reveal the actual sequence, tools, interruptions, and tradeoffs.
Do not rush to fill silence. The detail you need often arrives after the first neat answer.
Questions about the current solution
Every repeated problem has an alternative, even if the alternative is a spreadsheet, a reminder, extra labor, or doing nothing.
Ask:
- How do you handle this today?
- Which tools, services, or people are part of the process?
- What have you tried before?
- What works well about the current approach?
- What creates the most frustration?
- Why have you kept using it?
- Have you looked for another option? What triggered that search?
Question 11 matters because founders often study only the pain. The current approach survives for a reason. It may be familiar, flexible, inexpensive, approved by a manager, or connected to another system. A new product must respect the value that already exists.
Questions about consequence and urgency
A problem can be real without being important enough to solve now.
Explore the consequence:
- What happens when this goes wrong?
- How often does that happen?
- Who notices the effect?
- Does it cost time, money, trust, or a missed opportunity?
- What other work gets delayed because of it?
- What would cause you to address it this month?
- What happens if nothing changes?
Listen for a visible cost and a trigger. “This is annoying” is different from “I spend every Friday rebuilding the report before my client meeting.” Both are honest, but only one contains a repeated behavior, time cost, and deadline.
Questions about decisions and buying
If you are exploring a business product, the user, buyer, approver, and security reviewer may be different people.
Ask:
- Who would be involved in choosing a new approach?
- Who feels the problem most directly?
- Which requirements would a new solution need to meet?
- What would make changing feel risky?
- Is there a budget connected to this work today?
- How have you purchased a similar tool?
- What would you need to see before testing something new?
These are not closing questions. They reveal how a real decision happens. If you wait until the end of product development to learn that the person you interviewed cannot adopt the product, the discovery process missed an important part of the system.
Questions that create a useful next step
End with questions that preserve honesty:
- What did I fail to ask about this process?
- Who else sees this differently?
- May I show you a rough version when it is ready?
- What would you want to test first?
- Is there someone else you think I should learn from?
Do not treat an agreement to follow up as a sale. It is permission for another conversation.
If the person has an urgent problem and your current product can help, offer a small next step connected to what you heard. The guide to getting your first paying SaaS customers explains how to move from a useful conversation to first value and payment without confusing interest with demand.
Questions to avoid or rewrite
“Do you like the idea?”
Ask: “What do you do when this happens today?”
“Would you pay for this?”
Ask: “What does the current process cost, and who controls that budget?”
“How much would you pay?”
Ask: “How have you evaluated and purchased a similar solution?”
“Is this a big problem?”
Ask: “What happened the last time the problem interrupted your work?”
“Would this feature help?”
Ask: “Show me how you complete that step now.”
The rewritten questions ask for evidence the person can remember. They reduce the pressure to predict a future that may never happen.
Record observations, not just conclusions
Immediately after the interview, separate what you heard into four columns:
| Type | Example |
|---|---|
| Observation | The person exports three reports every Friday |
| Quotation | The exact words used to describe the frustrating step |
| Interpretation | We think speed matters more than customization |
| Open question | We do not know whether the buyer shares that priority |
This keeps your assumption from quietly turning into a fact.
After several interviews, look for repeated situations, behaviors, consequences, and objections. Do not count how many people complimented the idea. Count the patterns that help you make a decision.
Find people to interview
Potential interview participants are already asking questions, comparing approaches, and describing workarounds online. Search communities and professional networks for the problem language, not just the customer title.
When you reach out, explain why their experience is relevant, ask for a small amount of time, and make it clear that the conversation is research. Do not disguise a sales pitch as an interview.
Mangos AI can help founders find relevant public conversations and prioritize people who fit a customer hypothesis. You still need to review the context, ask permission, and conduct the interview with curiosity.
Common questions about customer discovery
How many customer discovery interviews should a startup conduct?
There is no fixed number that creates certainty. Interview enough relevant people to identify repeated situations and meaningful differences. A small set of detailed interviews can guide the next test, then new evidence should continue to update the picture.
Should I show the product during a discovery interview?
Learn about the current situation first. If you show a concept later, separate the reaction to the concept from evidence about the existing problem. A positive reaction is not the same as adoption.
Can customer discovery happen after launch?
Yes. Discovery continues after launch through interviews, onboarding, support, sales, product usage, churn conversations, and public customer discussions. The questions become more specific as the product and market mature.
Leave with a sharper question
A good customer discovery interview does not always leave you feeling more certain. Sometimes it reveals that the problem is weaker, the buyer is different, or the current alternative is better than you assumed.
That is useful. You asked before spending another month building around a polite prediction.
What behavior do you need to understand before making your next product decision?