How to Do Customer Interviews to Validate a Business Idea

Quick answer: To validate a business idea through customer interviews: talk to 10–15 real potential customers before building anything; ask about their current behaviour and real problems, not opinions on your idea; listen for specific stories, not polite agreement; and stop when you keep hearing the same problems and can predict what the next person will say. Validation is not "people like it" — it's "people have this problem badly enough to pay to solve it."

Why customer interviews beat surveys and guesswork

Most founders validate the wrong way. They tell people their idea, get "sounds great!" in response, and take that as a green light. Six months later, no one buys.

The problem is the question. When you ask "would you use this?" you get social kindness. People don't want to disappoint you. They say yes to mean maybe. They mean "I'd try it for free."

Customer interviews done right don't ask about your idea at all. They ask about the person's life, their current behaviour, the problem as they already experience it. If the problem is real and painful, the evidence is in how they describe it — the time they waste, the workarounds they've built, the money they're already spending on imperfect solutions.

This approach — popularised by Rob Fitzpatrick's book The Mom Test — is the fastest way to know, before you build anything, whether you have a real problem worth solving.

Step 1: Define what you're trying to learn

Before you talk to anyone, write down the one or two biggest assumptions your business depends on. These are the things that must be true for your idea to work.

For example:

"Small kirana owners in Tier 2 cities struggle to track credit given to customers and lose money because they can't remember who owes what."
"HR managers at companies with 50–200 employees spend hours every month manually reconciling attendance with payroll."

Your interview's job is to find out whether that assumption is real — not to pitch the solution.

Step 2: Find the right people to talk to

Talk to potential customers, not friends and family. This sounds obvious but is the most common mistake. Friends want you to succeed. Family won't tell you the truth. You need the people who would actually pay for the solution, and you need their honest reaction, not their support.

Where to find them:

LinkedIn (direct message, keep it short and curious, not salesy)
WhatsApp groups and communities in your target industry
Local business associations, markets, trade events
Customers of a complementary product (ask the product owner for an introduction)
Cold walk-ins at the type of business you're targeting

Offer nothing in return except a short, respectful conversation. If you can only get people to talk by offering payment, that is itself a signal worth noting.

How many interviews? Start with 10. By the time you've spoken to 10 people in the same customer segment, you'll notice patterns. If you're still hearing entirely different problems and experiences, keep going — you may be talking to the wrong segment or the problem isn't consistent enough to build around. Stop when you can predict what the next person will say before they say it.

Step 3: Write your interview guide (not a script)

A guide, not a script. You want a conversation, not a questionnaire. Prepare five to eight open questions and let the answers lead you.

Opening questions — establish context:

"Can you walk me through how you currently handle [the area your idea targets]?"
"What does a typical week look like for you when it comes to [problem area]?"
"How long have you been doing it this way?"

Problem-depth questions — find the pain:

"What's the most frustrating part of that process right now?"
"Has this ever caused you a serious problem — lost money, lost a customer, missed something important?"
"What do you do when [the problem situation] happens? Walk me through what you actually do."

Evidence questions — look for commitment signals:

"Have you tried to solve this before? What did you try?"
"How much time or money does this problem cost you, roughly?"
"If this were fixed tomorrow, what would change for you?"

Questions to avoid:

"Would you use an app that does X?" — asks for a hypothetical, gets polite yes.
"Do you think this is a good idea?" — explicitly asks for their opinion of your idea.
"On a scale of 1–10, how important is this problem?" — numbers without context are meaningless.
Leading questions: "Isn't it frustrating when X happens?" — you've already told them the answer.

Step 4: Conduct the interview

Keep it to 20–30 minutes. Longer and people lose energy; shorter and you rarely get to the real problem.

Talk less, listen more. Your goal is to speak less than 20% of the time. Ask, then stay quiet. Let silence do the work — people fill silence with the truth.

Take notes or ask to record. Don't rely on memory. If you record, ask permission first. Transcripts reveal patterns you miss in the moment.

Follow the story. If someone says "there was this one time where it went really wrong" — stop everything and ask them to tell you the full story. Real incidents are gold. They reveal exactly how the problem plays out, how much it hurt, and what the person did about it.

Never pitch. The moment you describe your solution, the interview is over. The person shifts from sharing problems to evaluating your idea — and back to being politely supportive.

Step 5: Debrief and find the pattern

After each interview, write a short debrief while the conversation is fresh. Note:

The single biggest problem they mentioned (in their own words)
Any specific incident they described
What they're currently doing about the problem
Any signals of real cost: money spent, time lost, customers affected
Anything that surprised you

After 10 interviews, look for patterns across your notes:

Green signal: Multiple people describe the same problem in similar terms, unprompted. Some have tried to solve it themselves (built a workaround, tried an existing tool). Some have already spent money on the problem.
Yellow signal: People describe different versions of the problem. You're either talking to the wrong segment or the problem is too scattered to build one solution for.
Red signal: Everyone is polite and says the problem exists, but no one has spent time or money on it. They live with it. That usually means it's not painful enough.

What to do with what you learn

Customer interviews don't tell you what to build — that's design work. They tell you whether there is a real problem worth building for.

If the signal is green:

Write a one-paragraph "problem statement" in the customers' own language.
Define the customer segment precisely (not "small businesses" — "kirana owners in Tier 2 cities with 3–8 staff who give customer credit").
Make your first "solution" the simplest possible thing — a prototype, a manual service, a single screen — and test it with the same people.

If the signal is yellow or red: go back and interview more people, or reconsider the assumption. A bad signal at this stage is not failure — it is the cheapest possible lesson.

How Thola helps: from validated idea to execution

Customer interviews are the first step of the founder journey, not the last. Once you know the problem is real, the next challenge is turning that insight into a plan — a business model, financial projections, a structured execution path.

Thola (by ScalingWolf) includes a guided idea-to-execution journey specifically for founders at this stage. It walks you from raw idea through validation, planning and early execution — with a decision gate that pressure-tests your assumptions against real numbers before you commit major resources.

Thola is a coach and a guardrail, not an autopilot: it guides the process, but every decision stays with you. As your business grows, the same app adds a live health score, cash-flow monitoring, CRM, HR and 12-month forecasts — so the tool grows with the business it helped you build.

6,000+ founders already use Thola. Free to start; paid plans from ₹199/month.

Take your validated idea into a guided plan — free on Thola → (opens in a new tab)

Frequently asked questions

How many customer interviews do I need to validate a business idea? Start with 10 interviews in the same customer segment. By then, you'll notice either a strong pattern (same problems described in similar terms) or a lot of noise (very different experiences). If you can predict what the 11th person will say before they say it, you have enough. If everything still feels inconsistent, do more interviews or reconsider which segment you're targeting.

What questions should I ask in a customer interview? Ask about their current behaviour and real past experiences, not opinions on your idea: "Walk me through how you currently handle this"; "What's the most frustrating part?"; "Has this ever caused you a serious problem?"; "What did you do when that happened?" Avoid hypotheticals ("would you use this?") and leading questions ("isn't it frustrating when X?").

What is the Mom Test in customer interviews? The Mom Test (from Rob Fitzpatrick's book) is a rule of thumb: ask questions your mum would answer honestly even if she loved you and wanted your idea to succeed. That means asking about real behaviour and specific past events — not "do you think this is a good idea?" The test forces you away from opinion questions toward evidence questions.

How do I know if my business idea is validated? Your idea is validated when: (1) multiple interviewees describe the same problem unprompted and in similar terms; (2) some have already tried to solve it (built workarounds, spent money, or switched tools); (3) the problem has a real cost in time or money they can describe specifically. "People think it's a good idea" is not validation. Evidence of existing pain is.

What should I do after customer interviews? Write a precise problem statement in the customers' own words, define your customer segment tightly, and build the smallest possible test of a solution — a prototype, a manual service, or a single-function tool. Test it with the same people you interviewed. Then use a structured planning tool to turn a validated problem into a business model, financial plan and execution path.