Most customer interviews are a waste of time. Not because talking to customers is wrong, but because founders ask the wrong questions.
"Would you use a product that does X?" is the classic trap. The answer is almost always yes. People are polite. They want to be supportive. And hypothetical questions produce hypothetical answers. You walk out of the interview feeling validated, but you haven't learned a single thing about whether someone would actually pay for what you're building.
The fix isn't more interviews. It's better questions. Here are five that consistently surface real signal.
Question 1: "Walk me through the last time you dealt with [problem]."
This is the most important question you can ask, and it has nothing to do with your product. You're asking about their current behavior, not their future intentions. What matters is what they actually did, not what they say they would do.
Listen for specifics. When did it happen? How long did it take? Who else was involved? What tools did they use? The more detail they provide, the more real the problem is. If they struggle to recall a specific instance, the problem might not be as painful as you assumed.
The best predictor of future behavior is past behavior. If someone hasn't tried to solve a problem before, they probably won't pay you to solve it either.
Question 2: "What's the hardest part about that?"
This follow-up does the heavy lifting. You've gotten them to describe their current process. Now you're finding out where it breaks down. Their answer tells you exactly where your product needs to create value.
Pay attention to emotional language. "It's annoying" is different from "it costs us deals" which is different from "I've lost sleep over it." The intensity of the language maps directly to willingness to pay. If the hardest part is merely inconvenient, you have a vitamin. If it's genuinely painful, you might have a painkiller.
What to avoid
Don't lead the witness. Don't say "Is the hardest part X?" because they'll agree with you to be agreeable. Let them tell you. Silence is your friend here. Ask the question and wait. The pause feels awkward, but it's where the real answers live.
Question 3: "How are you solving this today?"
Every problem has a current solution, even if that solution is "we just deal with it" or "I use a spreadsheet." Understanding the existing alternative is critical because that's what you're actually competing against. You're not competing against other startups. You're competing against the status quo.
If someone has cobbled together a workflow using three different tools, duct tape, and willpower, that's a strong signal. They care enough about the problem to invest effort in solving it. Your product just needs to be better than their duct-tape solution.
If their answer is "nothing, we just ignore it," that's a warning sign. Either the problem isn't painful enough to solve, or you're talking to the wrong customer segment.
Pro tip: Ask what they've already tried and abandoned. Failed solutions tell you what doesn't work and what tradeoffs people aren't willing to make. This saves you from building something that already failed for someone else.
Question 4: "What would it mean for you if this problem just... disappeared?"
This question reveals the outcome they actually care about. And the answer is often surprising. You might think you're solving a productivity problem, but the customer might describe a reduction in stress, better team morale, or the ability to go home on time.
The answer to this question becomes your marketing copy. It's the transformation your customer is buying. Not the feature set, not the technology, not the AI. The outcome on the other side.
Listen for the second-order effects. The direct benefit ("save 4 hours a week") matters less than what they'd do with those 4 hours. That's the real value proposition.
Question 5: "If I built something that solved this, what would make you NOT use it?"
This is the objection question, and most founders never ask it. They're too busy pitching to ask what would stop someone from buying. But this is where you find the landmines.
Common answers include:
- "If it required me to change my existing workflow"
- "If I had to get my team to adopt it"
- "If it was more than $X per month"
- "If it didn't integrate with [tool they already use]"
Each of these is a product requirement disguised as an objection. Pricing sensitivity, integration needs, adoption friction: these are the constraints your product has to work within. Better to learn them in an interview than after you've built the wrong thing.
The Meta-Rule: Shut Up and Listen
The biggest mistake in customer interviews isn't asking the wrong question. It's talking too much. Your job in an interview is to listen, not to pitch. The ratio should be 80% them, 20% you. If you catch yourself explaining your product, stop. You're there to learn about their problem, not to sell your solution.
Record the interview (with permission). Take notes on exact phrases they use, not your interpretation. "I spend hours every week reconciling data across three tools" is gold. "User experiences data management challenges" is your brain filtering out the useful stuff.
These five questions won't give you product-market fit. Nothing that simple exists. But they will give you real data to update your hypotheses, reshape your canvas, and make decisions based on evidence instead of gut feeling. And that's how the best founders find fit: one honest conversation at a time.