How to Prepare Customer Interviews That Produce Useful Evidence
Live report
Customer Interview Kit
Interview scripts, a recruiting plan, and a synthesis template to test your riskiest assumptions with real users. Your inputs and existing venture evidence are carried into a decision-ready report. Claims remain labelled as facts, assumptions, inferences, or items needing validation.
A customer interview can sound productive while producing very little evidence.
People are polite. They respond to hypothetical ideas. Founders explain too much. A positive conversation ends with the sentence, "I would definitely use this."
The problem appears later when nobody changes behaviour, shares data, joins a pilot or pays. A Customer Interview Kit helps the interviewer learn from past and present behaviour instead of collecting encouragement.
How the phase starts
First, create your private venture context
The free verdict turns your description into the starting context for your workspace. From there, choose Customer Interview Kit and answer its focused, phase-specific questions before the report runs.
Already have a venture in IdeaClarify? Sign in and continue from your workspace.
TL;DR — Read this first
What it is
A Customer Interview Kit is a structured plan for recruiting, conducting, recording and analysing conversations with relevant customers or users.
Why it matters
It reduces leading questions and makes evidence easier to compare across interviews.
Use it when
Use it after the main customer, problem and risky assumptions are clear enough to investigate with real people.
What you receive
Participant criteria, outreach copy, interview guide, probes, note template, consent prompts, evidence rules and synthesis structure.
Important limit
Interviews reveal language, context and reported behaviour. They do not prove demand or predict what people will do in a real buying situation.
What is a Customer Interview Kit?
A Customer Interview Kit is a reusable set of materials for learning from people who experience, influence or buy around a particular problem.
It normally includes participant criteria, recruitment messages, an interview sequence, neutral questions, follow-up probes, consent guidance, note-taking fields and a way to compare evidence across conversations.
The kit is not a rigid script. It creates enough consistency to compare interviews while leaving room to follow meaningful details.
Interviews are for learning, not pitching
The interviewer should understand the person's situation before describing a proposed solution. Once a concept is presented, the conversation changes. The participant may start evaluating the pitch instead of recalling how the problem actually occurs.
A later part of the conversation may test a concept, but the evidence from that section should be labelled separately.
The IdeaClarify HEARD Framework
The framework keeps the interview grounded in reality. It also helps distinguish a frustrating story from a problem that creates enough cost or urgency to change behaviour.
- H: History Ask about a specific recent event rather than a general opinion.
- E: Existing behaviour Understand what the person does today, including workarounds and the option of doing nothing.
- A: Actors and authority Identify users, buyers, approvers, blockers and people affected by the decision.
- R: Reality of cost Explore time, money, delay, risk, emotion and consequences without suggesting an answer.
- D: Decision and commitment Understand what would cause action and look for credible next steps such as an introduction, data share, pilot or purchase process.
Choose participants by relevance, not convenience
Friends and colleagues may be easy to recruit, but they are often too close to the founder or too far from the buying situation.
Participant criteria should include the situation, role, frequency of the problem and decision involvement. Exclusion criteria are equally useful. A person who has never handled the process should not be treated as evidence about it.
Ask about a real event
"Would you use a tool that saves time?" invites a positive answer. "Tell me about the last time this process delayed your work" creates a concrete story that can be examined.
Useful probes include: What happened next? Who else was involved? What did you try? How long did it take? What did it cost? Why did you choose that option? What prevented a different response?
Separate problem discovery from concept testing
Problem discovery explores the person's world without requiring the proposed solution. Concept testing examines how someone interprets a specific idea, prototype or offer.
Both can be useful, but combining them carelessly allows enthusiasm for the concept to rewrite the earlier problem evidence. The kit should mark where the conversation changes.
Plan how evidence will be compared
Interview notes become difficult to use when every conversation is recorded differently. A standard note structure can capture the event, current process, frequency, cost, actors, quotes, workarounds, buying conditions, contradictions and follow-up actions.
Synthesis should identify patterns and differences. It should not count repeated phrases as statistical proof.
What information should go into IdeaClarify?
The strongest kits begin with a narrow learning objective.
- Idea or product description.
- Initial customer or user group.
- Problem and situation being investigated.
- Assumptions from the Idea Clarifier or Market Research.
- Known users, buyers and decision-makers.
- Interview purpose and decisions it should inform.
- Participant criteria and available recruitment channels.
- Concept, prototype or offer to test, if any.
- Sensitive topics or consent requirements.
- Language, geography and interview format.
- Number of interviews planned and note-taking method.
Worked example: interviews for a school meal-planning service
A team is considering a planning service that helps primary schools reduce food waste. The first interview plan targets headteachers and asks whether they would buy an AI forecasting tool.
The kit reframes the research. Kitchen managers handle meal counts, administrators manage budgets, teachers communicate absences and local authorities may control contracts. The participant set must cover more than one role.
The guide begins with the last week in which prepared meals were left over. It asks how quantities were estimated, when attendance changes became known, who could adjust the order, what happened to unused food and how the cost was recorded.
Only after the current process is understood does the interviewer show a simple concept. A useful commitment may be access to anonymised weekly counts for a pilot design, not verbal enthusiasm.
What a Customer Interview Kit report should produce
A useful kit should help another interviewer conduct the research consistently without pretending the conversation can be fully scripted.
- Research objective and decisions to inform.
- Participant and exclusion criteria.
- Recruitment message and screening questions.
- Opening and consent language.
- Core interview sequence.
- Neutral questions and follow-up probes.
- Separate concept-testing section where relevant.
- Note-taking and evidence-capture template.
- Commitment and follow-up options.
- Synthesis categories and contradiction log.
- Interviewer guidance and common bias warnings.
- Open questions and recommended sample mix.
What customer interviews cannot tell you
Interviews describe what people remember and choose to share. Memory is incomplete, social pressure changes answers and stated preference may not match future behaviour.
A small set of interviews cannot establish market size or statistical prevalence. It can improve the language, context and hypotheses used in later validation.
Sensitive, regulated or vulnerable participant research may require specialist ethics, consent or legal review.
What founders usually get wrong
Asking whether the idea is good
The participant is placed in the role of encouraging or advising the founder instead of describing behaviour.
Leading with the solution
The proposed product shapes the rest of the conversation.
Interviewing anyone available
Relevance is replaced by convenience.
Accepting vague answers
Words such as often, difficult and expensive need a specific example or scale.
Talking more than the participant
The interviewer explains the idea instead of learning how the situation works.
Treating repeated opinions as validation
Several positive comments do not equal commitment or demand.
Ignoring contradictory interviews
Differences may reveal segments, roles or conditions that the original idea missed.
How this phase connects with other IdeaClarify phases
Market Research and Competitor Teardown define the context. Strategy and Customer Simulation help identify assumptions and possible reactions. The Customer Interview Kit turns the highest-risk questions into a real research plan.
Validation Experiments then test behaviour or commitment. Personas should be updated using evidence from interviews rather than remaining fictional profiles. Pricing, PRD and UX Flow may change when the buying process or workflow is better understood.
The next phase is Validation Experiments when the interviews have clarified which assumption requires behavioural evidence.
Creating a customer interview guide in a chat window vs IdeaClarify
A chat tool can generate a list of interview questions in seconds. Without context, it may include leading, hypothetical or repetitive questions and may not define who should be interviewed.
IdeaClarify should connect each question to an assumption and decision. It should separate discovery from concept testing, include participant criteria and create a consistent evidence structure for later analysis.
Frequently asked questions
How many customer interviews should I conduct?
There is no universal number. Begin with enough relevant conversations to identify patterns and contradictions, then continue until additional interviews are no longer changing the important decisions. The sample should cover meaningful roles and segments.
Should I record customer interviews?
Recording can improve accuracy, but obtain appropriate consent and handle the data responsibly. Requirements differ by country and context.
Can I interview friends or colleagues?
They may help test the guide, but they should not be treated as market evidence unless they genuinely meet the participant criteria.
When should I show the product idea?
Usually after exploring the current situation. Keep concept reactions separate from problem evidence.
Are interviews enough to validate an idea?
No. They improve understanding and identify stronger hypotheses. Behavioural experiments, pilots or payment evidence are still needed.
Can students use the kit for academic research?
Yes, but they must follow their institution's research, ethics, consent and citation requirements.
Turn assumptions into conversations that can change the plan. Start with the decision you need to make. Recruit people who know the situation and ask about what happened, not what sounds attractive.
Suggested supporting articles
- Customer Discovery Questions That Avoid Leading the Participant
- Problem Interviews vs Concept Testing
- How to Recruit Relevant Customer Interview Participants
- How to Analyse Customer Interviews Without Overclaiming
Reviewed 2026-07-12
Previous phase
Startup Strategy: How to Choose What Your Idea Will Focus On
Next phase
How to Design Validation Experiments Before Building the Full Product
Related phases
How to Analyse Competitors Without Copying Them
Compare direct competitors, substitutes, positioning, pricing, customer experience and gaps. Learn what a competitor teardown should change about your business idea.
AI Customer Simulation: What It Can Tell You Before Real Research
Use structured AI customer simulation to explore objections, questions and segment differences before real interviews. See its value, method and limits.
Market Research for a Business Idea: What to Study Before You Build
Learn how to research demand, customers, competitors, market size, trends and risks before building a product. Turn your idea into a structured market research report.