Customer discovery is a short, structured period of talking to likely buyers before you build anything. Its job is to answer one question with evidence: is there a frequent, painful problem that a group you can reach is already spending time or money on? We run it as a two-to-four-week sprint that ends with a written problem statement you can test everything else against.
Who this is for
Discovery is for founders whose main evidence is their own experience or the enthusiasm of people who know them.
That describes most first-time founders, and there's nothing wrong with it. Personal experience is how many good ventures start. The risk is that you are one data point, and friends are kind. Discovery is right for you if any of these are true:
- No one outside your circle has asked when they can buy it.
- You can describe the product in detail but not the last time a buyer hit the problem.
- You've been planning for months and haven't spoken to ten strangers in the target market.
- You have two or three possible buyer groups and can't decide which one to serve first.
If you have already built something and few people are buying, discovery still applies. It's often the fastest way to find out why.
What's included
The sprint covers planning, the conversations themselves and the write-up.
- Buyer hypothesis. We write down who you think the buyer is, in specific terms: role, company size or household type, region, and the trigger that makes the problem urgent.
- Interview script. A short script built around past behaviour ("Tell me about the last time…") rather than opinions about your idea.
- Recruiting plan. Where to find about twenty qualified people and how to ask them for twenty minutes, with message templates you adapt.
- Conversations. You run most of them; we run or join the first few. Every one is logged in the same notes template.
- Pattern review. Halfway through we review notes together and adjust the script or the buyer group.
- Write-up. A one-page problem statement, a ranked list of buyer types, the exact words buyers used to describe the pain, and a list of what's still unknown.
Our guide to customer interviews shows the script structure in full, so you can see how the conversations work before you commit.
Timeline
Most sprints run two to four weeks, and recruiting is the part that sets the pace.
| Week | Main work |
|---|---|
| 1 | Hypothesis, script, recruiting list and first outreach |
| 2 | First 8 to 10 conversations; mid-point review |
| 3 | Remaining conversations, often with a sharper buyer group |
| 4 | Pattern analysis and written problem statement |
Business-to-business buyers usually take longer to book than consumers. If your buyers are busy in a particular season, such as accountants in spring or farm suppliers at harvest, we plan around it.
How results are measured
Discovery is measured by the quality of the evidence, not by whether it confirms the idea.
We look for a few signals in the notes. How many of the twenty described the problem before you mentioned it? How many have already tried to fix it, with a spreadsheet, a hire or a competing product? How many could tell you what it costs them? And how many asked to be told when you have something? As a working rule, if fewer than a quarter of qualified people show strong signs of pain, the problem is probably not urgent enough for that group. That's a reason to change the group, not necessarily the idea.
Mistakes to avoid
Most discovery goes wrong in the same few ways.
- Pitching instead of listening. The moment you describe your solution, people start being polite. Save the idea for the last two minutes, if at all.
- Asking about the future. "Would you use this?" produces yes. "What did you do last time?" produces facts.
- Interviewing only friendly people. Twenty conversations with former colleagues measure loyalty, not demand.
- Stopping at five. The patterns that matter usually show up between conversations ten and twenty.
- Not writing it down the same way. Without a common template you'll remember the conversations that agreed with you.
What happens next
The problem statement becomes the input to MVP scoping. If discovery shows the venture needs a formal feasibility study first, for example because the start-up costs are large, we'll say so. Discovery is billed as a defined project; see pricing for the ranges, or call, text or email to describe your idea and get a scope.
Frequently asked questions
Can't I just send a survey instead?
A survey tells you what people say about a problem you described to them. A conversation tells you what they actually did last time it happened. Surveys are useful later, to size something interviews have already found.
Who do I interview if I don't know anyone in the market?
Strangers are better than friends anyway. We help you find them through industry associations, online groups, LinkedIn searches, suppliers who serve the same customers, and polite cold messages. Expect to contact three to five people for every conversation you get.
Will you run the interviews or will I?
Either, but we usually recommend you run most of them with our script and notes template. The founder needs to hear the pain directly. We can join or run the first few to model the approach.
What if discovery says the idea doesn't work?
Then it has done its job at the lowest possible cost. In practice, discovery rarely produces a flat no; more often it moves the venture to a different buyer or a neighbouring problem that hurts more.