20 Customer Discovery Questions That Actually Tell You Something

Most founders walk into customer discovery interviews asking the wrong questions. They pitch instead of listen, ask about hypothetical futures instead of lived-in pasts, and walk away with polite encouragement instead of usable signal. This list fixes that — 20 questions you can copy, paste, and bring to your next interview.

---

Category 1: Understanding the Problem

These questions anchor the conversation in real, specific experience. You're not asking what someone thinks they want — you're asking what actually happened.

1. "Tell me about the last time you experienced [problem]."

What it reveals: Whether this problem is recent and recurring, or something they vaguely remember from years ago. Frequency and recency are your first indicators of pain severity.

2. "What did you do about it?"

What it reveals: Whether the person takes active steps when the problem hits — which signals urgency — or just lives with it, which signals low priority. Passive acceptance is a yellow flag.

3. "What was the hardest part?"

What it reveals: The specific friction point that matters most to them, which is often not the friction point you assumed. This single answer should inform your product's core value proposition.

4. "Why was that hard?"

What it reveals: The root cause underneath the surface complaint. One level deeper is where the real product insight lives. Most founders stop at "what," but "why" is where you learn whether this is a tools problem, a process problem, or a people problem.

5. "What would happen if you never solved this?"

What it reveals: The true cost of inaction — financial, operational, emotional. If their answer is a shrug, the problem isn't urgent enough to build a business around. If it's "I'd lose customers" or "my team would burn out," you've found something worth solving.

---

Category 2: Current Solutions

Your competition isn't just other software products. It's spreadsheets, workarounds, agencies, and doing nothing. These questions map the real competitive landscape from the customer's perspective.

6. "How are you solving this today?"

What it reveals: Your actual competition — which is often a combination of tools, manual effort, and institutional workarounds rather than a single named competitor.

7. "What do you like about your current approach?"

What it reveals: The features and behaviors your product must match or beat before someone will switch. If they love that their current solution is "flexible," rigidity will kill your adoption.

8. "What's frustrating about it?"

What it reveals: The opening your product needs to exploit. The frustrations people volunteer about existing solutions are the most honest buying signals you'll collect — these are the gaps they're already aware of and already feeling.

9. "What have you tried that didn't work?"

What it reveals: Prior failed solutions tell you two critical things: what they've already ruled out (so you don't rebuild it), and how much effort they've already invested in solving this problem. High prior effort = high motivation to find something that works.

---

Category 3: Decision-Making and Buying Behavior

Understanding how a person buys is as important as understanding what they need. These questions tell you who to target, what objections you'll face, and how long your sales cycle will actually be.

10. "How did you find [current solution]?"

What it reveals: Which discovery channels work for your audience — word of mouth, Google searches, communities, newsletters. Your go-to-market strategy should start here.

11. "Who else was involved in choosing it?"

What it reveals: Whether this is a solo purchase decision or a committee decision with multiple stakeholders. If there's a procurement team, a manager, or a budget owner involved, your sales motion needs to account for them.

12. "What would make you switch?"

What it reveals: The specific threshold — price, capability, reliability, or something else — that would prompt action. This is the bar you need to clear. Anything short of it is a nice-to-have, not a must-have.

13. "What's the cost of doing nothing?"

What it reveals: How the person frames inaction — as acceptable, as a slow bleed, or as a genuine crisis. The more vivid and specific their answer, the higher the urgency. Vague answers ("it'd be annoying") signal low buying motivation.

---

Category 4: Willingness to Pay and Urgency

Polite enthusiasm is worthless. These questions separate people who will pay from people who will ghost your launch email.

14. "Have you actively looked for a better solution?"

What it reveals: Whether the pain is strong enough to prompt real-world action. Someone who has spent time searching, reading reviews, or trialing competitors is warm. Someone who hasn't thought about it beyond this conversation is not your early adopter.

15. "What would you pay to make this problem go away?"

What it reveals: A rough ceiling for your pricing — but more importantly, it reveals how the person mentally categorizes the problem. Is this a "$10/month annoyance" or a "I'd pay whatever it takes to fix this" crisis? The framing tells you as much as the number.

16. "How much time or money does this cost you today?"

What it reveals: The quantifiable cost of the status quo, which becomes the foundation of your value proposition and pricing justification. If someone says "probably three hours a week," you now have something concrete to sell against.

17. "If I could solve this tomorrow, what would change for your business?"

What it reveals: How the person envisions success — and whether the outcome they describe is specific and meaningful ("we'd close deals 30% faster") or generic and forgettable ("things would be easier"). Specificity signals real pain.

---

Category 5: Red Flags and Validation

These three questions close the loop. They're how you check your blind spots, expand your interview pipeline, and test whether you've earned enough trust to follow up.

18. "Is there anything I should have asked that I didn't?"

What it reveals: The topics the person was waiting to talk about but you never opened the door to. This question frequently surfaces the most important insight of the entire conversation.

19. "Who else should I talk to about this?"

What it reveals: Whether this person is genuinely engaged with the problem space (and has opinions about who else lives in it) or was just being polite. A referral is a meaningful signal. An "I'm not sure" is a soft no.

20. "Can I follow up with you in two weeks?"

What it reveals: Their real level of interest. People who say yes to a follow-up are warm — they're willing to invest more time in a problem that hasn't been solved yet. People who deflect are telling you something important about how urgently they actually want this.

---

What NOT to Ask in Customer Discovery

A few question patterns will poison your data. Avoid these:

Leading questions. "Don't you find it frustrating when...?" You're not gathering information — you're fishing for validation. People will agree with you to be polite, and you'll mistake their politeness for signal.

Hypothetical questions. "Would you use a tool that did X?" People are notoriously bad at predicting their own future behavior. Ask what they've done, not what they would do.

The classic trap: "Would you use this?" This is the single most useless question in a customer discovery interview. It feels informative. It isn't. You want to know what someone has paid for and actively searched for — not what they say they'd do in an imaginary future.

Solution-pitching disguised as questions. "What if we built it so that...?" The moment you start describing your product, you've left discovery and entered sales. Keep the conversation on their world, not yours.

---

One More Thing: What Interviews Can't Tell You

Customer interviews give you direct access to lived experience. They're irreplaceable for understanding pain, behavior, and language. But they have a ceiling — they tell you what the people in the room think, not what the broader market looks like.

To build a real business, you need both sides: what people say in interviews, and what the market data actually shows. How big is the addressable market? Who are the real competitors and how are they positioned? Where is demand growing or shrinking?

That's what DimeADozen.AI is built for. You bring your idea; we give you the market side — competitive landscape, market sizing, demand signals — so you can triangulate what you're hearing in interviews against what the data shows. Both together give you a picture you can actually build on.

Your next customer interview will be more useful if you know the market context before you walk in.