A first customer interview should help a founder understand a real task. It is easy to leave a friendly conversation with encouragement and little evidence. A more useful discussion explores something the customer has recently done and the difficulties encountered along the way.
Y Combinator’s early-stage guidance stresses talking directly to customers while learning what to build. The following interview plan is Gulfprenuer’s practical adaptation for a founder testing a business idea; it is not a record of completed research.
Recruit for the situation you want to understand
Choose people who actually perform the task your product would improve. If the idea concerns stock management, interview someone who handles stock rather than someone who only likes the concept of a business app. Write down why each participant fits the proposed customer group.
Friends can be useful introductions, but a convenient group should not automatically represent the market. Seek varied relevant experiences and note which important customer types are still missing.
Ask about the last time
Begin with a concrete event: when did you last do this task, and what happened? Invite the person to describe the sequence in their own words. Ask which tools they used, how long it took and where help was needed.
Follow the details that reveal consequences. Did the task cause a delay? Was information entered twice? Was a workaround necessary? Ask to see a non-sensitive example if the person is comfortable sharing one. Avoid collecting private records that are not needed for your research.
Learn about the current alternative
Customers already have a way of coping, even when it is inconvenient. Ask what they have tried, what they pay for and what they would lose by changing. A manual process may be familiar and dependable; a new product needs a reason to displace it.
Delay your sales pitch until you understand the problem. Once a proposed solution appears, the conversation can shift toward politeness or feature suggestions. Neither is the same as evidence of a pressing need.
End with a specific, optional next step
If the problem and customer fit are plausible, invite the participant to review a small prototype or join a defined pilot. Explain what participation involves and how feedback will be used. Let people decline without pressure.
Record whether the person follows through. A scheduled review that actually happens provides more information than a general promise to stay in touch. A pilot should have a clear scope and a way to assess its result.
Turn notes into a decision
After each interview, separate observations from interpretation. What did the participant do or say? What does the founder think it means? Which assumption needs another test? Keep contradictions rather than smoothing them into a favourable story.
Look for repeated patterns within a specific customer group. Decide whether to test a solution, narrow the audience or investigate a different problem. The purpose is to improve the next decision, not to collect enough positive remarks to justify an idea already chosen.
Gulfprenuer editorial analysis. Featured image: AI-generated editorial illustration; it does not depict the named people or an actual event.
