Customer Interview Scripts: What to Ask and What to Ignore

Everyone says “talk to your customers.” Almost nobody explains what that actually means. Here is a complete script — opening line to closing question — so you know exactly what to say when you get someone on a call.

A customer interview is not a pitch or a feedback session. It is an evidence-gathering exercise. You are trying to answer specific questions: Does this problem actually exist? How often does it occur? What have people already tried? When done correctly, a 30-minute interview gives you more actionable information than a hundred survey responses. You can hear what the person emphasizes, notice when their language becomes specific and animated, and ask follow-up questions that a form cannot ask.

The goal is not to validate your idea. The goal is to understand the problem so well that you either confirm the idea is worth building — because real people have a real problem with real urgency — or discover that the problem is not what you assumed, and save yourself months of work on the wrong solution.

Most solopreneurs interview two or three people and call it validation. That is too few. Aim for 10 to 15 interviews before drawing conclusions. Patterns that appear in three or more conversations are worth taking seriously. Observations from a single interview are interesting but not actionable.

Why Most Interview Questions Produce Useless Answers

The most common customer interview questions are some version of: “Would you use this?” or “What do you think of this idea?” Both are broken. They ask people to predict their future behavior, and humans are reliably bad at this. When someone tells you they would use your product, they are being kind. They are not telling you what they will actually do when faced with a real decision and a real price.

Rob Fitzpatrick’s The Mom Test identifies this as the core mistake in customer discovery: asking questions that feel validating but produce data you cannot act on. Your mom will tell you the idea is great. Your potential customers will too, if you ask them whether they like it.

Good customer interview questions ask about past behavior, real problems, and current workarounds. They never ask people to evaluate your idea. They ask people to describe their own experience. This distinction sounds small. It produces completely different information.

How to Find People to Interview

The two most common excuses for skipping customer interviews are “I do not know what to ask” and “I do not know who to talk to.” Five channels work reliably for solo founders with no existing audience.

Your warm network. Start here. Think of three to five people who fit your target profile. Do not ask them to evaluate your idea. Ask for a 20-minute conversation about how they currently handle a specific situation. The framing matters: “I am doing research on how freelancers manage invoicing” gets far more yeses than “I have an idea for an app, can I get your feedback?”

Reddit communities. Find the subreddits where your target customer talks about their problems. Search for threads where people describe the exact situation you are trying to solve. Reply to posts, offer a gift card for 15 minutes of their time, or post in subreddits that allow research requests. r/Entrepreneur, r/SaaS, r/solopreneur, and r/freelance are all communities where founders have successfully recruited interview subjects.

LinkedIn. Send connection requests to people with job titles matching your customer profile. A short, honest message explaining that you are researching a problem (not pitching a product) converts better than you expect. Keep it under 50 words.

Existing audience. If you have an email list or a small following, use it. Ask who would be willing to talk for 20 minutes about a specific challenge. Offer a free resource, early access, or a $15 coffee gift card in return.

Referrals from your first interviews. After every conversation, ask one question: “Is there anyone else you know who deals with this problem regularly? I would love to talk to them.” Warm referrals close at a much higher rate than cold outreach.

Ten interviews is your minimum. Fifteen is better. If you are hearing the same patterns by interview seven or eight, you are on track.

The Opening Script

How you open the interview shapes everything that follows. The goal is to signal that you are there to listen, not to pitch.

Use this opening word-for-word or adapt it to your voice:

“Thanks for making time. I want to be clear about what this is — I am not going to pitch you anything today. I am in research mode, trying to understand how people in your situation actually handle [specific situation]. There are no right or wrong answers. The most useful thing you can do is be completely honest, even if what you say is not what I want to hear. Can you start by telling me a bit about your current role and how [the situation] shows up for you day to day?”

This opening removes the social pressure to be polite about an idea (because no idea is mentioned). It gives explicit permission to be critical. It invites them to talk about their own experience, not your solution.

Do not show mockups, name your product, or describe what you are building during the interview. The moment you reveal your idea, the conversation shifts from honest exploration to polite evaluation. Save the product reveal for after you have 10 interviews done.

Want a step-by-step plan that takes you from idea to evidence in one week? Download the free 7-Day Idea Test guide. It covers the full sequence: picking the right problem, running the interviews, and running a demand confirmation test that tells you whether people will actually pay. Get the free 7-Day Idea Test

The Core Question Bank

These questions are organized into four phases. Work through them in order, but do not treat this as a rigid script. Follow the energy. When someone gives a specific, animated answer, dig in with follow-up questions before moving on.

Phase 1: Their Experience (establish context)

• “Walk me through the last time you had to deal with [the problem area]. What happened?”
• “How often does this come up for you — daily, weekly, monthly?”
• “When it comes up, what is the first thing you do?”

These questions anchor the conversation in specific memory rather than hypothetical generalization. “The last time” is a powerful phrase. It forces specificity.

Phase 2: The Problem (understand the pain)

• “What is the hardest part of dealing with that?”
• “What does it cost you when this does not work well — in time, money, or stress?”
• “If you had to guess — how much time per week do you spend on this?”
• “What have you tried in the past to make this easier?”

The follow-up on time and money is important. When someone says “it is really frustrating,” that tells you something. When they say “it takes me two hours every week and I bill at $150 an hour,” that tells you something you can build a business case on.

Phase 3: Current Solutions (find the gap)

• “What tools or methods do you use right now to handle this?”
• “What do you like about how you currently handle it?”
• “What drives you crazy about your current approach?”
• “Have you ever paid for something to solve this — a tool, a service, a course?”
• “If so, what made you try it, and did it actually solve the problem?”

This phase is where you find the competitive landscape from the customer’s perspective. Whether they have paid for anything similar tells you about willingness to pay — which is the most important signal in idea validation. See also: The Mom Test: a deeper look at this specific technique.

Phase 4: Urgency and Stakes

• “On a scale of one to ten, how big a problem is this for you right now?”
• “What would change for you if this problem were completely solved?”
• “Is this something you are actively trying to fix, or something you have learned to live with?”

The last question is critical. There is a meaningful difference between a problem people are actively seeking to solve and one they have quietly accepted. You want to build solutions for the first category.

What to Listen For and How to Interpret It

Running the interview is the easy part. Interpreting what you hear is where most founders go wrong. Y Combinator’s customer discovery guidance — used in every batch since 2005 — consistently emphasizes the same lesson: founders hear what they want to hear unless they have a specific framework for what to listen for. Here is that framework.

Listen for emotion, not politeness. The most useful moments in a customer interview are when someone’s language shifts from composed to frustrated. Emotional intensity signals real pain. Polite agreement signals social courtesy.

Specificity is signal. When someone describes a problem in vague terms (“it is just kind of annoying”), that is a weak signal. When they describe it in precise detail (“every Friday afternoon I spend 45 minutes copying invoice data from one spreadsheet into another format for my accountant, and I have been doing it for two years”), that is a strong signal.

Note what they have already tried. If someone has already attempted to solve this problem multiple times and keeps failing, that is a strong signal of urgency. If they have never tried to solve it, dig into why. Sometimes that reveals a real constraint. Sometimes it reveals the problem is not urgent enough to motivate action.

Unprompted mentions matter most. When a customer brings up a pain point you did not ask about — especially if it connects to your idea — that is a strong validation signal. They volunteered it, which means it is top of mind.

Be skeptical of enthusiasm without evidence. “This is such a great idea” tells you nothing. “I paid $47 last month for a half-solution to this same problem and it still did not work” tells you a great deal. Weight enthusiasm accordingly.

After 10 interviews, look for patterns: which problems came up in more than half the conversations, which solutions did people mention independently, which phrases did multiple people use to describe the same pain. Recurring language is exactly what you should use in your marketing copy.

After the Interview: Turning Notes into Evidence

The interview is not finished when the call ends. What you do in the next 30 minutes determines whether the evidence is useful.

Write up your notes immediately while the conversation is fresh. Do not rely on a transcript alone — transcripts capture words, not emphasis. Your notes should capture: the three most specific things they said, any moment where their language became particularly animated, what they said they have already tried, and whether they are actively seeking a solution or have accepted the problem.

If the interviews confirm real demand, the next step is not to build the product — it is to run a demand confirmation test: a pre-sale, a landing page, or a simple offer. The interviews give you direction; the demand test gives you evidence of willingness to pay.

Run your findings through a structured idea evaluation to make a go/wait/kill decision. See How to Evaluate a Business Idea for the full scoring framework, and MVP for Solopreneurs for how to connect interview evidence to a minimum testable version.

Frequently Asked Questions

What are the best customer interview questions for idea validation?

The best customer interview questions for validation focus on past behavior, not hypothetical preferences. Ask “Walk me through the last time you dealt with this problem” rather than “Would you use this?” Questions about what someone has already tried and what they have paid for are the most predictive of whether real demand exists for your idea.

How many interviews do you need before drawing conclusions?

Aim for 10 to 15 interviews minimum. Patterns that appear in 3 or more conversations are worth taking seriously. Most founders stop at 2 or 3 — too few to distinguish a genuine pattern from a coincidence. By interview 8 or 9, if you are hearing the same problems in the same words, you have enough signal to act on.

Should I reveal my product idea during the interview?

Not during the interview itself. Once you reveal the idea, the conversation shifts from honest exploration to polite evaluation. After completing your full set of interviews, briefly describe what you are thinking of building and ask whether it sounds relevant. Use that as a light signal — but never let it override the behavioral evidence you gathered.

What if everyone is enthusiastic but nobody has the problem badly enough?

Enthusiasm without urgency is the most common trap in customer discovery. If no one has paid for a partial solution, tried to solve the problem, or described it in specific costly terms — pause before building. Return to Phase 4 questions and push harder on what would need to change for someone to actively seek a solution today.

How is a customer interview different from a survey?

An interview reveals how people actually behave: what they try, what they pay for, what they complain about unprompted. A survey captures what people say they think — faster but shallower. Use surveys to follow up on patterns found in interviews, not replace them. For context on what happens when founders skip this step, see failed product launch patterns.

Keep Reading

• The Mom Test: What It Is and How to Use It
• The Lean Canvas for Solopreneurs
• How to Evaluate a Business Idea: A Structured Guide