Customer Interviews for Founders: How to Get Honest Answers Instead of Polite Lies

Every founder is told to talk to customers. Far fewer are told how. The result is that thousands of founders run interviews every year, come away encouraged, build what they heard, and then discover that nobody buys. The interviews happened. The data was wrong.

The problem is not that customers lie on purpose. It is that people are polite, optimistic about their future behavior, and eager to be helpful to someone who is clearly excited about an idea. Ask them whether they would use your product and most will say yes. That answer costs them nothing, makes you happy, and tells you almost nothing about what they will actually do.

Good customer interviews are designed around this reality. They focus on past behavior instead of future intentions, on the customer's life instead of your idea, and on specifics instead of opinions.

Why Most Customer Interviews Produce Bad Data

There are three common failure modes, and most founders hit all three in their first round of interviews.

Pitching instead of listening. The founder spends the first ten minutes explaining the idea, then asks what the person thinks. At that point the interview is no longer about the customer's problem; it is about the founder's solution, and the customer responds to the pitch rather than describing their reality.

Asking hypothetical questions. "Would you use a tool that does X?" and "How much would you pay for Y?" invite speculation. People are poor predictors of their own future behavior, and they systematically overestimate how much they would use and pay for things.

Seeking validation. Founders unconsciously steer conversations toward confirming answers. They nod enthusiastically at agreement, move quickly past disagreement, and leave the call remembering the compliments.

Each of these produces confident, encouraging, and misleading conclusions.

Talk About Their Life, Not Your Idea

The most useful reframe comes from Rob Fitzpatrick's book The Mom Test: ask questions that even your mother could not lie to you about. The way to do that is to stop talking about your idea entirely and ask about the customer's life, work, and past behavior.

Instead of "Would you use an app that helps freelancers track invoices?" ask "How do you keep track of who owes you money right now?" Instead of "Is invoicing a pain for you?" ask "Tell me about the last time a client paid late. What happened?"

Questions about the past are anchored in reality. A customer cannot easily exaggerate what they did last Tuesday. Questions about the future invite optimism. Questions about your idea invite politeness. Keep the conversation in the customer's world and in the past tense for as long as possible.

Questions That Uncover Real Problems

A small set of questions does most of the work in a discovery interview:

• "Walk me through the last time you dealt with [problem area]."
• "What was the hardest part about that?"
• "Why was that hard?"
• "What have you tried to solve it? What did you like or dislike about those solutions?"
• "How much time or money does this cost you today?"
• "What happens if you just don't solve it?"

That last question is important. If the honest answer is "nothing much," the problem may be real but not painful enough to pay to fix. Real opportunities show up as problems people are already spending time or money trying to solve, often with clumsy workarounds like spreadsheets, manual processes, or patched-together tools.

Follow-up questions matter more than the initial ones. When someone mentions a frustration, ask "why?" and "can you give me an example?" The first answer is usually surface level; the useful detail is two or three questions deeper.

Finding the Right People to Interview

Who you interview matters as much as what you ask. Friends and family are the easiest to reach and the least useful, because their desire to support you contaminates every answer.

Aim for people who match your target customer but have no personal stake in your success. Good sources include online communities where your audience gathers, LinkedIn outreach to people with relevant job titles, introductions from early contacts, and people who have publicly complained about the problem you are exploring.

Keep the ask small and honest: "I'm researching how [role] handles [problem area]. Would you be open to a 20-minute call? I'm not selling anything." Most people are surprisingly willing to help when the request is specific, short, and clearly not a sales call.

Five to ten interviews within a well-defined segment is usually enough to start seeing patterns. If every conversation sounds completely different, your segment is probably too broad.

Testing Willingness to Pay Without Asking

Asking "How much would you pay?" produces fiction. Better signals come from what people already spend and what they are willing to commit to now.

Ask what they currently pay for related tools or services, and how they made that purchase decision. Ask who in their organization approves spending on tools like this. These answers reveal budget, process, and priority far more reliably than hypothetical pricing questions.

The strongest signal is commitment. Near the end of a promising interview, ask for something that costs the customer a little: an introduction to a colleague with the same problem, time for a follow-up session to test a prototype, or a pre-order or deposit. People who say the problem is urgent but decline every small commitment are telling you, politely, that it is not urgent.

Running the Interview Itself

Keep interviews to 20 to 30 minutes. Start with a brief explanation of what you are researching, then move quickly into open-ended questions about their experience.

Let silence work for you. When a customer finishes an answer, pause for a few seconds before asking the next question. People often fill silence with the most honest and useful details.

Take notes, or record with permission and transcribe later. Capture exact phrases, especially emotional ones. The words customers use to describe their problems become the language of your landing page later, and they are far more persuasive than anything you would write yourself.

Resist the urge to pitch at the end unless the customer asks. If they ask what you are building, describe it briefly and watch their reaction — genuine interest sounds different from polite interest, and follow-up questions are the tell.

Turning Interviews Into Decisions

After each interview, write a short summary within the hour: the person's context, the problems they described, how painful those problems seemed, what they currently do about them, and any commitments they made.

After five to ten interviews, look for patterns across the summaries. Which problems came up repeatedly? Which ones did people spend money or time trying to solve? Which ones generated emotion? A problem that appears in most interviews, causes visible frustration, and has existing spending attached is a strong candidate. A problem that came up once, or that people described calmly as "a bit annoying," probably is not.

Be honest about what you find. The purpose of interviewing is not to confirm the idea you already had. It is to find the problem worth solving — and sometimes that means discovering, early and cheaply, that the original idea should change.