Customer Interview Questions That Don't Lead the Buyer

Good customer interview questions ask about specific past events, not opinions about the future: "Tell me about the last time this happened", "What did you do about it?", "What did that cost?" and "Who else was involved?" Avoid questions that describe your idea and ask for approval, because people answer those kindly rather than truthfully.

The approach follows Rob Fitzpatrick's The Mom Test, whose three rules, as summarised by Sachin Rekhi, are: talk about their life instead of your idea, ask about specifics in the past instead of opinions about the future, and validate by asking for commitments.

Key takeaways

Ask about the last time, not what they would do.
Never pitch in a discovery interview. It turns research into politeness.
Follow the money and the people: what it costs and who decides.
End with a commitment ask, such as a follow-up, an introduction or a pilot.
Write it up the same day, in the same format every time.

What makes a customer interview question good?

It asks about something that actually happened, it does not reveal what answer you hope for, and the answer would change what you do next.

Leading versus non-leading questions
Leading (avoid)	Non-leading (use)
"Would you use an app that does X?"	"Tell me about the last time you had to do X."
"Is X a big problem for you?"	"What is the hardest part of X?"
"How much would you pay for this?"	"What do you spend on X today, in time or money?"
"Don't you hate it when...?"	"What happened the last time it went wrong?"
"Would this save you time?"	"How long did it take last week?"

What are the best customer interview questions?

Twenty questions grouped by what they uncover: the problem, the current solution, the cost, the decision, and the next step. You will rarely need all of them in one call.

The problem

Tell me about the last time [the situation] happened.
What were you trying to get done?
What made it difficult?
How often does this come up?

The current solution

What do you do about it today?
What tools, people or services are involved?
What have you tried before that did not work? Why?
If you could change one thing about how it works now, what would it be?

The cost

How long did it take the last time?
What happens when it goes wrong?
What does it cost, in money, time or risk?
Is anyone already paying to fix this?

The decision

Who else is affected when this goes wrong?
Who would decide whether to change how it is done?
How did you choose the tool or process you use now?
What would need to be true for you to switch?

The next step

Is there anyone else I should talk to about this?
Could I follow up once I have something to show you?
Would you be open to trying a small paid version?
What would make that worth it for you?

Which interview questions should you avoid?

Hypothetical questions about the future, questions about your idea, and anything that asks for approval. They all produce answers that sound like evidence but are not.

"Would you buy...?" People are poor predictors of their own purchases, and kind to founders.
"What do you think of my idea?" Invites compliments, not information.
"What features would you want?" Buyers describe solutions; you want their problems.
Leading lists. Offering options narrows the answer to what you already thought.

The same summary quotes Fitzpatrick on why commitments matter: "it's not a real sales lead until you've given them such a concrete chance to reject you."

How should you run a customer interview?

Keep it short, let them talk most of the time, follow the most specific story, and end with a clear ask. Take notes on facts and quotes, not impressions.

Set it up as research. "I'm trying to understand how teams handle X" rather than "I'd like to show you something".
Follow specifics. When they mention a real event, ask for more detail about it.
Stay quiet. Silence after a question often produces the most useful answer.
End with an ask from the last group of questions.
Log it the same day using a consistent template; see customer discovery for technical founders for one.

What should you ask the budget owner?

Questions about how they decide: what they spend on today, how they evaluate changes, what risks worry them, and who else must approve.

How do you decide on spending like this?
What would make you say no, even if the team wanted it?
Who else needs to approve it (finance, IT, legal)?
How would you measure whether it worked?

Our buyer persona guide covers the difference between the user, the champion and the budget owner.

Frequently asked questions

What are the best questions to ask in a customer interview?

Questions about specific past events: the last time the problem happened, what they did, what it cost and who was involved. They reveal real behaviour instead of polite opinions.

What questions should you not ask customers?

Avoid hypothetical questions like would you buy this, questions asking for opinions on your idea, and leading questions that suggest the answer you want.

How long should a customer interview be?

Long enough to hear one or two specific stories in detail and ask for a next step. Many founders aim for a short call and follow up if needed.

Should I show my product in a customer interview?

Not in a discovery interview. Showing a product turns the conversation into feedback on your idea. Save demos for later, once you understand the problem.

How do you end a customer interview?

With a concrete ask: an introduction to someone else, a follow-up once you have something to show, or an offer to try a small paid version.

Start where you are

Better questions come from knowing where the idea is weakest.

Sources

The question list is a starting point. Adapt the wording to your buyer and your market.