How to Get Strangers to Talk to You About Their Problem
The ask that works is short, specific, and about them, not you. Most people are willing to spend twenty minutes talking about a problem they have experienced. Most people are not willing to be a sounding board for someone's business idea.
Here is the version that works:
"I am doing some research on [the problem area]. I would love to spend twenty minutes hearing about your experience with it, not to pitch you anything, just to understand how people are navigating this. Would you be open to a quick call?"
That is it. No mention of what you are building. No teaser about an exciting new solution. Just a genuine request to hear about their experience.
If someone asks what you are working on, you can be honest: "I am exploring whether there is an opportunity here, but I am at the very early stage and mostly just trying to understand the problem better." That framing tends to make people more willing to talk, not less.
The Three Questions That Reveal Whether a Problem Is Real
Once you are in the conversation, you are not there to share anything. You are there to understand their reality before your solution exists in the room. These three questions, asked in roughly this order, will get you there.
1. Tell me about your current experience with this problem.
Open-ended. No assumptions built in. Let them define the problem in their own words, not yours. The specific language they use matters. If they describe it the way you would, that is interesting. If they describe it completely differently, that is more interesting. Either way, do not correct them or redirect them toward your frames.
2. What have you already tried?
This is where you learn about the competitive landscape without ever asking about competitors. What people have tried before tells you how serious the problem is. Someone who has paid for three different solutions and still has the problem is in a different situation than someone who has vaguely thought about looking into it someday. Prior attempts reveal urgency. No prior attempts often reveal that the problem, while real, does not hurt enough to move people to action.
3. Have you ever paid for a solution?
This is the most important question and the one most founders are afraid to ask directly. Payment history is the single most honest signal you will get. People will tell you they would pay for something while having no intention of doing so. But what they have already paid for is a record of what mattered to them enough to take action.
If the answer is no, follow up with: "What stopped you from looking for something?" The answer to that question is often worth the whole conversation.
What Not to Do During a Customer Discovery Conversation
Do not pitch. Not even a small version. Not even a hint.
The moment you describe your solution, the conversation changes. The other person shifts from honestly describing their experience to being polite about your idea. They start filtering what they say through the question of whether it will hurt your feelings. You lose access to the honest version of their thinking.
Do not ask hypothetical questions. "Would you use something that..." or "Would you pay for a product that..." are almost useless. Hypotheticals get hypothetical answers. People imagine the best version of themselves, the version that would absolutely use the organized app, the version that would definitely pay for the service, and they answer from that imaginary place. Stay in their past and present, not your imagined future.
Do not lead. If you have a theory about the problem, do not let it show in how you ask the questions. "I imagine this must be really frustrating" is a leading statement. "What has that experience been like for you?" is not. The difference sounds small and changes everything.
How to Hear What Customers Are Not Saying Out Loud
The most valuable part of these conversations is often not what people tell you directly.
Vague answers are a signal. When someone says "yeah, it can be kind of annoying sometimes," that is not a painful problem. That is a mild inconvenience. People who have a real, urgent problem do not struggle to describe it. They have specific stories. They remember specific moments. They use specific numbers, the hours they lost, the money they spent, the times they nearly quit because of it.
When someone pauses before answering, that pause often means they are thinking rather than retrieving a pre-formed answer. The responses that follow pauses are frequently more honest than the quick ones.
Enthusiasm early in a conversation is not necessarily a good sign. Polite people get excited about ideas. What you are looking for is the moment when someone shifts from being encouraging to being specific, when they stop saying "this sounds great" and start saying "this would have been so useful when I had to deal with X last year." That shift is the real signal. I have watched founders miss it completely because they were so relieved to hear enthusiasm that they stopped paying attention to what came after.
What to Do After You Finish All 10 Customer Conversations
Take notes during each conversation, or record them if the person agrees. Do not try to process in real time. Just capture what you hear.
After all ten, look for the patterns. What problem descriptions kept coming up? What had people already tried? Who had paid, and what had they paid for? Where were the differences between people who seemed to have the problem badly versus those who mentioned it only in passing?
Three things typically emerge from ten honest conversations.
Confirmation. The problem is real and painful, people have already spent money trying to solve it, and the gap you identified is genuinely there. This tells you to keep going.
Recalibration. The problem exists but is milder than you thought, or it affects a narrower group than you expected. This does not mean stop. It means your idea needs more definition.
Redirection. What you heard does not match the problem you thought you were solving. This is the most valuable outcome, even though it does not feel that way. Finding out before you build is worth more than finding out after.
Whatever you find, the conversations are not the end of the process. They are the beginning of honest thinking. Take what you heard and hold it up against your assumptions. Where they match, you have something. Where they do not, you have work to do.
Most founders skip this step because they are afraid of what they might hear. The answer you get from ten real conversations is always more useful than the answer you get from staying in your own head.
Knowing whether you are dealing with a real problem or a mild annoyance will sharpen every question you ask and what you listen for.
[READ: The Difference Between a Real Problem and a Mild Annoyance — LINK: /tell-real-problem-from-mild-annoyance]
The full validation framework these conversations fit into lives in the Evaluate Your Idea.
