Customer interviews examples: lessons and useful context

The hard part of an interview is not asking. It is the four seconds after an answer, when you decide whether what you just heard was information.

Below are answers you will hear repeatedly, given as they usually arrive, with what each tends to mean and the follow-up that turns it into something usable. None of them are lies. Most are accurate summaries of a situation the speaker has never had to describe out loud before.

What to take away

• Almost every common answer is ambiguous, and one follow-up resolves it.
• A good follow-up asks for a past event, a name, or a number. Never for an opinion about the answer just given.
• The answer you least want to hear usually carries the most information.

"We have always done it that way"

What it usually means. Nobody currently owns the question. The method predates everyone in the room and has never been compared with an alternative.

The follow-up. "Do you know how it started?" Then: "Has anyone tried to change it?" If somebody tried and failed, find out what stopped them, because that obstacle will stop you too. If nobody has ever tried, you are looking at low pain rather than high inertia, and those need different offers.

"That is interesting, send me something"

What it usually means. A polite exit. It costs nothing, it ends the conversation kindly, and it lets both of you leave feeling positive.

The follow-up. Offer something with a small cost attached instead. Fifteen minutes next week to look at their actual data, or an introduction to whoever would have to approve it. Whether they accept is the real answer, and it arrives immediately.

"We tried that and it did not work"

What it usually means. Something adjacent failed, for a reason that may or may not apply to you. This is one of the most valuable answers available and it is usually heard as a rejection.

The follow-up. "What exactly did you try, and when?" Then find out whether it failed on the product, the rollout, the price, or the politics. A failure of adoption inside their organization tells you the problem was real enough to attempt, which is stronger evidence than most enthusiasm.

"I would have to check with someone"

What it usually means. You are talking to a user or an influencer, not the buyer. That is fine at this stage, as long as you know it.

The follow-up. "Who, and what would they need to see?" Then: "What was the last thing they approved like this?" Those two map the purchase path in under a minute, and the second gives you a real precedent instead of a hypothetical process. Problem discovery sets out why the roles separate.

"We built our own"

What it usually means. The problem was worth real money, since somebody funded internal work on it. It also means the buyer already made a decision they would have to reverse in public to buy from you.

The follow-up. "Who maintains it, and what happens when they are away?" Internal tools are expensive in a way that never appears on an invoice, and the person paying that cost is often not the person who commissioned it. Find the maintainer and the situation looks different.

"It is not really my area"

What it usually means. Either you have the wrong person, or you have the right person describing an area with no owner. Those are opposite situations.

The follow-up. "Whose area is it?" A name gives you a referral, which is the cheapest recruiting there is. A vague answer tells you the problem falls between roles, which explains why it persists and warns you that your buyer will be hard to identify.

"How much is it?"

What it usually means. Genuine interest, or an attempt to end the conversation with a number they can reject. You cannot tell which from the question.

The follow-up. Give a real number and say nothing. The silence is the instrument. What comes next, a flinch, a comparison with something else they pay for, or a question about terms, tells you more than any answer to what would you expect to pay. Pricing validation is where that gets systematic.

"Everyone in this industry has this problem"

What it usually means. They are describing their own situation and generalizing, which is what everyone does.

The follow-up. "Who specifically? Could you name two?" Names give you referrals and a second data point. No names means you have one person's account, which is what it always was. Whether the generalization holds is a counting question rather than a conversational one, and the SBA's outline of market research and competitive analysis is where that job starts.

What to do with the answers

Log each one with the follow-up and what it produced, not just the sentiment. A round that produced eight referrals, three named buyers and two documented past attempts is a useful round even if nobody was enthusiastic.

Then look at which follow-ups you did not ask. There is usually a pattern, and it is usually the ones that risk an awkward moment: the price, the name of the approver, the request for something small and real. Those are the questions carrying the information, which is exactly why they are uncomfortable, and skipping them is the failure described in the interview mistakes.

Common questions

What if the follow-up gets a vague answer too?

Ask once more with a narrower frame, then stop. "When was the last time" and "who was involved" are usually enough. Pressing a third time changes the relationship and rarely improves the data.

Should I use these as a script?

No. They are responses to answers, so they only make sense in order. A script produces an interview that sounds like a form, and people fill in forms differently from how they tell stories: how much the phrasing and order of a written question move the answer is set out at length in the guidance on writing survey questions. The shape of a good conversation is set out in customer interviews.

Which answer should worry me most?

Uniform mild interest with no workarounds behind it. Everyone is pleasant, nobody has done anything about the problem, and there is nothing to follow up. That is a topic people find agreeable rather than a problem they pay to remove.

Do these work for consumer conversations?

Most of them. The buyer questions collapse into one, since the person deciding is usually the person paying, and the substitute for an approval chain is a household conversation, which is worth asking about directly. What changes more is the offer you eventually test: see offer testing.