In this article
Illustrative photo by Yosuke Ota / Unsplash.
Customer interviews are more useful when they uncover what someone actually does than when they collect opinions about your proposed product. Ask about a recent situation, the steps taken and the consequences. Treat what you hear as qualitative evidence to investigate, not as a representative market forecast.
The questions below are a practical interview framework for an early-stage service business. They are not a validated research instrument or a guarantee that an idea will sell.
Choose a narrow problem to investigate
“Small businesses need help” is too broad. “Independent consultants lose track of client follow-ups” is specific enough to explore. Recruit people who encounter the situation, including some who appear to handle it well.
Explain the purpose of the conversation and how you will use notes. Ask permission before recording. Avoid collecting details you do not need, and anonymize examples before sharing them beyond the research context.
Ask for the last real example
Start with: “Tell me about the last time you followed up with a potential client.” Then ask what triggered the task, where the information lived and what happened next. A recent account gives you a sequence to examine.
Follow with neutral questions: “What made that difficult?” and “How did you handle it?” Avoid embedding your preferred answer, such as “Was your spreadsheet frustrating?” The person may have been perfectly happy with it and struggling with something else.
Explore the current workaround
- What do you use today?
- Who else is involved?
- What happens when the task is delayed or missed?
- Have you tried to change the process? What happened?
- Which parts work well enough that you would keep them?
Ask for concrete examples where possible. “It takes too long” is a starting point; the next question is what part of the task takes the effort. Do not force a precise number when the person does not know.
Keep the pitch separate
If you describe your solution at the beginning, later answers may become feedback on your pitch. First understand the person’s situation. If you show a concept afterward, label that part of the conversation separately in your notes.
Compliments and hypothetical willingness to pay should be recorded as what they are. They are not equivalent to a purchase, a trial or another observed commitment. Use them to form a next question rather than to declare demand proven.
Synthesize without overstating the evidence
Create a note for each interview with context, problem, workaround, consequence and open questions. Separate an exact quote from your interpretation. Then look across interviews for recurring situations and meaningful differences.
If three people mention the same issue, you have a pattern worth exploring among those interviews. You have not established its prevalence in the whole market. Include counterexamples: someone who solved the issue may teach you more than another person agreeing it exists.
Decide the next observable step
Choose a small follow-up based on what you learned: examine the existing workflow, show a clearer concept or offer a narrowly defined pilot. Write down what would challenge your assumption as well as what would support it.
The value of the interview is a better decision. If it helps you narrow the audience or abandon an unimportant problem, it has served its purpose even when it does not confirm your first idea.
