Start with a question you need to answer
A customer interview is a conversation about someone’s work, needs, and decisions. For freelancers and small teams, it can help clarify where a service fits, what makes a task difficult, or why a prospective customer chooses one approach over another. Its purpose is not to persuade the person to buy. If you treat the interview as a sales call, you may hear polite encouragement instead of a useful account of what happens in practice.
Before inviting anyone, write down what you hope to learn. “Understand how small teams handle urgent website updates” is more useful than “find out whether people like our website service.” The first gives you a situation to explore; the second invites a verdict on your idea. Choose people who have encountered the situation you are studying, including some who have not used your service. Explain what the conversation is for, how long you expect it to take, and whether you would like to take notes or record it. Ask permission before recording.
Ask about past behavior before future intentions
People can usually describe a recent experience more concretely than they can predict what they might do later. Start with an open invitation such as, “Tell me about the last time you needed to update your website quickly.” Then ask what prompted the work, who was involved, what steps they took, and where they got stuck. These questions give the person room to identify what mattered to them.
Avoid packing an assumption into the question. “How frustrating was your old process?” presumes frustration; “What was that process like?” does not. “Would you pay for a faster option?” can encourage a hypothetical yes that may have little connection to a real decision. Instead, ask what options they considered, what they chose, and what influenced that choice. If they mention cost, timing, or quality without prompting, you can explore it: “How did timing affect your decision?”
Use follow-ups that clarify rather than steer
An interview guide can keep you focused, but it should not be a script you rush through. Listen for specific moments and ask the person to walk you through them. “What happened next?”, “Can you give me an example?”, and “What made that difficult?” are simple follow-ups that often reveal more than a new question on a different topic. If someone says a supplier was “unreliable,” ask what they observed rather than deciding what unreliable means for them.
Be especially careful when discussing your own proposed service. If you explain its benefits first, the person may respond to your description rather than their needs. When you do show an idea, separate their initial reaction from your interpretation. Ask, “What would you expect this to do?” or “Where, if anywhere, would this fit into your current process?” Give them time to disagree. Silence can feel awkward, but filling it with examples or suggested answers can steer the conversation.
Make it easy to give an honest answer
A neutral question can still feel leading if your tone suggests there is a right answer. Thank people for concrete examples, corrections, and criticism—not just positive reactions. Avoid debating their choices or explaining why your service would have solved a problem. You can clarify what they mean without trying to change their mind.
Keep the conversation respectful of the person’s time and boundaries. Ask only for details relevant to your learning goal, and let them skip anything they do not want to discuss. If you are speaking with an existing customer, make clear that candid feedback will not affect how you support them. Close by asking whether there is something important you did not cover. That final question may surface a concern your interview guide missed.
Turn conversations into findings without overclaiming
Soon after each interview, review your notes while the context is fresh. Separate what the person said or did from your interpretation. For example, “They emailed three suppliers and chose the one who could start this week” is an observation; “Everyone values speed above price” is a much broader claim. Note surprises and contradictions as well as repeated themes.
Compare interviews for patterns, but do not treat a small set of conversations as a vote representing every potential customer. Look for specific situations: which tasks repeatedly cause difficulty, what alternatives people already use, and what conditions shape their decisions. You can then make a modest change—such as rewriting a service description or testing a simpler intake process—and continue learning. A good interview does not have to validate your original idea. It helps you understand the customer’s situation well enough to make a better-informed next step.
