Start with a specific customer and situation
Before describing what your service does, decide whose work you want to understand. “Small businesses” is too broad to guide useful research. “Owners of local service businesses who handle their own appointment requests” gives you a clearer starting point. You can ask about a specific activity, learn how people currently manage it, and judge whether your service could help.
Write down what you think the problem might be, but treat it as a question rather than a fact. For example: “Do owners lose track of requests that arrive through several channels?” Also note what would change your mind. If people already have a reliable process and see little reason to adjust it, that matters just as much as finding someone who struggles. Research should help you decide whether to pursue an idea, not merely supply words for a pitch.
Find people who encounter the work firsthand
Speak with people who do the task, manage it, or deal with its consequences. A business owner may describe a scheduling issue differently from the employee answering messages each day. Both views can be useful, provided you keep track of which role each person has. Existing customers, former clients, professional contacts, and people in relevant communities may all be possible starting points.
When requesting a conversation, explain the subject and the time you hope to spend. Make clear that you are trying to understand their process, not asking them to sit through a sales presentation. If a conversation is not practical, you can still learn from a customer’s own description of a request or from questions that come up repeatedly in your normal work. Handle private details carefully, and ask permission before recording or sharing anything identifiable.
Ask about recent actions, not hypothetical purchases
Begin with a concrete prompt: “Can you walk me through the last time you handled an appointment request?” Follow the sequence. Where did the request arrive? Who responded? What information was missing? What happened when plans changed? Questions about a recent example tend to reveal steps and constraints that a broad question such as “What are your biggest challenges?” might miss.
Avoid leading with your proposed solution. “Would an automated booking system solve this?” invites a quick opinion about your idea, not an account of the customer’s problem. Instead, ask what they have tried, what works well enough, and what they would prefer not to change. Listen for the cost of the problem in their own terms: extra follow-up, confusion between team members, delayed decisions, or time spent checking work. You do not need to turn those observations into a precise financial estimate to take them seriously.
Separate patterns from memorable stories
After each conversation, record the customer’s role, the situation discussed, the steps they took, and the words they used to describe the difficulty. Keep your observations separate from your interpretation. “Three messages needed follow-up” is an observation; “they need a new customer management system” is a possible interpretation. This distinction makes it easier to revisit your assumptions later.
Compare accounts for recurring situations, but do not force every comment into the same pattern. One person’s urgent problem may be rare; a frequent annoyance may not be important enough to justify a new service. Look for signs that people already spend effort addressing the issue, such as creating workarounds or asking for help. Also note differences: a process that troubles a solo operator may work smoothly for a team with a dedicated coordinator. Those differences can help you narrow your intended customer.
Test your understanding before making the pitch
Summarize what you heard in plain language: who faces the situation, what they are trying to accomplish, where the process becomes difficult, and how they handle it today. Share that summary with a few relevant people and ask what you have misunderstood or left out. Corrections are useful. They may show that you have mistaken a symptom for the underlying problem or overlooked a constraint your service must respect.
Then shape a modest pitch around the verified problem rather than a long list of features. Explain the specific part of the work you could take on, what the customer would still need to do, and what a first engagement might look like. If the conversations do not reveal a clear need, keep researching or adjust the audience instead of stretching the evidence. A good research process does not guarantee a sale; it gives you a sounder basis for deciding what to offer and how to discuss it.
