Customer discovery: a practical guide for solo founders

Customer discovery is a way to test your assumptions about customers before treating them as facts. Start with one audience, investigate a concrete problem and use the answers to choose an experiment. The outcome may be a smaller product, a different audience or a decision not to build.

1. Write an assumption you can disprove

Describe who encounters the problem, when it happens and what they currently do. Separate what you observed from what you believe. An assumption such as 'freelance designers struggle to collect overdue invoices' is more useful than 'people need an invoice app', because you can investigate the workflow without pitching a solution.

This is an illustrative hypothesis, not customer evidence. Before recruiting, write what would change your mind: perhaps invoices are already collected automatically, or the people you selected rarely encounter late payments.

2. Recruit around behavior, not enthusiasm

Look for people who recently completed the relevant task. Ask a screening question about that experience instead of whether they like your idea. Include people with different workarounds and people who found the task easy. Friends can help you practice, but agreement from your network should not stand in for evidence from the intended audience.

3. Investigate a recent episode

Ask: 'Tell me about the last time this happened.' Follow with what triggered it, what they did next, what they tried and what the consequences were. Ask permission before collecting documents or contact details. Do not reveal private examples when sharing your findings.

Keep the pitch separate. Once you describe your proposed app, the conversation changes from understanding their behavior to reacting to your solution. That can be useful later, but it answers a different question.

4. Keep evidence and interpretation separate

For each conversation, record the context, behavior, workaround and consequence. Add your interpretation in a separate column. Count recurring experiences within the relevant segment, and preserve contradictions. A frequent problem with little consequence can be less compelling than a narrow problem people already spend money to solve.

There is no universal interview count that proves demand. A sample recruited from one community may share biases. Be explicit about whom you have not reached and whether the people describing the pain can actually buy a solution.

5. Choose one next commitment

If the problem is unclear, ask a more targeted question. If the problem is clear but the solution is uncertain, test one workflow through a prototype or manual service. If willingness to pay is uncertain, test a real, clearly described offer rather than asking a hypothetical pricing question.

Before running the experiment, define what result would make you continue, narrow the scope or stop. Intairview can help run the interviews and organize responses; it does not turn interview opinions into proof of purchases or product-market fit.