What Should You Ask in a Customer Interview Before an MVP?

The difference between an interview that reveals real problems and one that produces vague, polite reassurance almost always comes down to the questions asked. Here’s a practical set of questions worth including in a customer discovery interview before you build an MVP, and why each one works.

Start With Their Current Reality

“Walk me through how you currently handle [the relevant situation].” This opens the conversation on their terms, without steering toward your idea, and often surfaces detail you wouldn’t have thought to ask about directly.

“How often does this come up?” Frequency shapes how urgent and how valuable a solution would be. A daily annoyance and a once-a-year inconvenience call for very different responses.

Dig Into Cost and Consequence

“What does this actually cost you — time, money, or something else?” Vague frustration is common and not very predictive. A specific, quantifiable cost is a much stronger signal that the problem is worth solving.

“Tell me about the last time this went particularly badly.” Specific stories reveal detail a general question rarely does, and often surface the sharpest version of the problem.

Understand What They’ve Already Tried

“What have you tried to fix this?” This surfaces existing competitors, workarounds, and internal tools, and tells you what you’re actually up against — often a spreadsheet or manual process rather than another polished product.

“What did you like and dislike about what you tried?” Understanding what’s working (even imperfectly) about a current solution tells you what a new product needs to preserve, and what it needs to fix.

Test Priority, Not Just Interest

“Where does this rank compared to other problems you’re dealing with right now?” A real but low-priority problem is unlikely to drive adoption of something new, even if the person genuinely experiences it.

“Have you actively looked for a solution before?” Active searching is a stronger urgency signal than passive frustration — see how to validate demand without asking “would you use this?” for more on why behavior beats opinion here.

A Sample Question Flow

Stage	Sample Question	Purpose
Opening	“Walk me through how you currently handle this.”	Understand current process
Detail	“Tell me about the last time this went badly.”	Get specific, vivid detail
Cost	“What does this cost you in time or money?”	Quantify the problem’s significance
Alternatives	“What have you already tried?”	Map the competitive/workaround landscape
Priority	“Where does this rank against your other problems?”	Test urgency, not just existence
(Optional, late)	“Here’s an idea I’m exploring — what’s your reaction?”	Weakest signal, use cautiously

What to Leave Out

Avoid questions that ask people to predict their own future behavior or react to a hypothetical product — “would you use this,” “would you pay for this,” “does this sound good” — since these tend to produce agreeable, low-information answers. For a deeper breakdown of why these specific phrasings fail, see customer discovery interview questions that reveal real problems.

Following Up in the Moment

The questions above are starting points, not a rigid script. When an answer is vague — “it’s kind of annoying” — follow up immediately: “Can you give me a specific example?” or “How much time would you say that costs you in a typical week?” The follow-up is often where the most useful detail actually surfaces.

Turning Answers Into a Build Decision

After a round of interviews using questions like these, look across your notes for repetition — the same cost, the same workaround, the same frustration, described independently by multiple people. That pattern, not any single interview, is what should inform your decision about whether and what to build.

Frequently Asked Questions

What's the single most important question to ask in a customer interview?

A question that asks about a specific, real past experience — like "tell me about the last time you dealt with this" — tends to reveal more useful information than any single other question, because it's grounded in something that actually happened.

Should I ask about my specific product idea in the interview?

Only near the end, if at all, and treat the response as a weaker signal than everything the person said before you mentioned it. Introducing your idea early skews the rest of the conversation toward politeness.

How many questions should a customer interview include?

A handful of core questions, five to eight, with room to follow up on interesting or unclear answers, tends to work better than a long, rigid script that limits natural conversation.

Should I ask the same questions to every interviewee?

A consistent core set of questions makes it easier to compare answers across interviews and spot patterns, while still leaving room to follow up on details specific to each conversation.

What should I do if someone gives a vague answer?

Follow up with a more specific prompt — ask for a recent example, a number, or a specific consequence — rather than accepting a general statement like "it's annoying" at face value.