A founder spent four months building a productivity app for teachers. She had interviewed nobody. She had tested nothing. She was sure teachers needed this because she used to be a teacher and she had needed it.
When she finally showed it to five teachers, three of them said the same thing: “This is nice, but we already use Google Classroom for this.”
Four months. Gone. Not because the idea was bad in principle, but because she never had the five conversations that would have redirected her before she built the wrong thing.
The 5-Conversation Sprint is the antidote to building in a vacuum. Five structured conversations in five days. Clear questions. Honest answers. By Friday, you know whether your idea has a market or a problem — and you know it before you have invested months of building time.
Why Five Conversations Is Enough
Five is not a statistically significant sample. I know that. But five conversations with the right people, asking the right questions, will reveal patterns that no amount of desk research can provide.
Here is what I have observed across 40+ startups at Startup Burgenland: if three out of five people describe the same problem in the same language, the problem is real. If three out of five say they have tried to solve this problem and failed, the market is real. If three out of five say they would pay for a solution, the business is real.
You are not looking for statistical proof. You are looking for patterns. And patterns emerge in five conversations if you ask the right questions.
More importantly, five is achievable. Twenty conversations sounds like a research project. Five sounds like a week. The frameworks that get used are the ones that feel doable.
Before the Sprint: Choose Your Five
Not all conversations are equal. You need five people who match your hypothesized ideal customer profile. Not friends who will be polite. Not family who will be encouraging. People who represent your actual market.
Where to find them:
- Professional networks (LinkedIn, industry groups)
- Online communities where your target customer hangs out
- Existing contacts who match the profile
- Cold outreach (more on this below)
When reaching out, be direct: “I am building something for [specific audience] and I would value 20 minutes of your honest perspective. No sales pitch. Just questions.”
Most people say yes. The hit rate for honest, specific requests from someone who is clearly not selling is surprisingly high — I have seen 40-60% response rates on cold outreach when the message is genuine and respectful.
The Five Questions
Each conversation follows the same structure. Five questions. Twenty minutes. Do not deviate.
Question 1: “Tell me about the last time you dealt with [the problem].”
Not “do you have this problem?” — that is a yes/no question that invites polite agreement. Instead, ask for a specific recent experience. The story reveals whether the problem is real, how painful it is, and how it actually shows up in their life.
Listen for:
- Emotional language. If they get frustrated or animated describing the problem, it is real and painful.
- Specificity. If they can describe a specific recent incident in detail, the problem is active — not theoretical.
- Frequency. Is this a daily annoyance or a once-a-year inconvenience? Frequency determines willingness to pay.
Question 2: “What have you tried to solve this?”
This is the competitive landscape question — but from the customer’s perspective, not yours. You are not asking about products. You are asking about behavior.
Listen for:
- Active solutions. If they are currently using something (a competitor, a workaround, a spreadsheet), the problem is important enough that they have already invested effort. Good signal.
- Failed attempts. If they have tried things and stopped, find out why. The reason they stopped is your product design brief.
- Nothing. If they have tried nothing, either the problem is not painful enough to solve, or they do not believe a solution exists. Both are important signals.
Question 3: “What is the worst part about the current solution (or lack of one)?”
This question identifies the gap between what exists and what your customer actually needs. The gap is your opportunity.
Listen for:
- Specific frustrations. “It takes too long” is vague. “I spend three hours every Friday manually entering data that should be automatic” is specific and buildable.
- The emotional cost. “It makes me feel disorganized” or “I dread doing it” reveals the emotional dimension of the problem. Products that relieve emotional pain command higher prices than products that save time.
Question 4: “If you could wave a magic wand, what would the ideal solution look like?”
Let them describe the outcome, not the product. You are not looking for feature requests. You are looking for the desired end state — the picture of success in their mind.
This question reveals what “solved” looks like from the customer’s perspective. It is often different from what the founder imagines. The teacher might not want a new app. She might want “to spend zero time on attendance and all my time on teaching.” That is a design constraint, not a feature request.
Question 5: “If something existed that [delivered the outcome from Q4], what would it be worth to you?”
This is the pricing signal. Not “would you pay for this” — which always gets a polite “probably.” Instead, anchor to the outcome and ask for a value.
Listen for:
- A specific number. If they name a number without hesitating, they have already done the mental math. Strong buying signal.
- A comparison. “About what I pay for [existing tool]” gives you market pricing context.
- Hesitation. If they struggle to name a price, the problem may not be painful enough to justify a purchase. Or they need to see the solution before they can value it — which means you need to build a prototype.
Running the Sprint: Day by Day
Monday: Conversations 1 and 2. Schedule them back to back if possible. Immediately after each conversation, write down the key findings while they are fresh. Do not summarize — write the actual phrases the person used.
Tuesday: Conversation 3. By now, you should start seeing patterns. Are the same problems coming up? The same language? The same frustrations?
Wednesday: Conversation 4. Pay attention to where this conversation diverges from the first three. Divergence is as informative as convergence — it tells you where your market segments.
Thursday: Conversation 5. Complete the final conversation.
Friday: Analysis. Lay out all five sets of notes. Look for:
- Problem consensus: Did 3+ people describe the same problem?
- Solution gap: Did 3+ people describe inadequate current solutions?
- Willingness to pay: Did 3+ people indicate they would pay for a better solution?
- Language patterns: What words did they use to describe the problem? These become your marketing copy.
What the Results Tell You
Strong signal (4-5 consensus): The problem is real, the market exists, and people will pay. Move to building a minimum viable version. Ship it ugly.
Mixed signal (3 consensus): The problem exists but may be narrower than you thought, or your audience may be slightly different from your hypothesis. Revise your ICP and run another sprint with a more specific segment.
Weak signal (0-2 consensus): The problem is not as painful as you assumed, or you are talking to the wrong people. Either pivot your idea or pivot your audience. Do not build.
Surprise signal: Sometimes the conversations reveal a different problem than the one you were testing. A founder testing a project management tool for freelancers discovered that the real pain was not managing projects — it was sending invoices. She pivoted to invoicing software and found immediate traction.
After the Sprint: Next Steps
The sprint is not the end. It is the beginning of a cycle.
If you got a strong signal, build the minimum viable experience and get it in front of those same five people. Their feedback on a real (ugly) product is infinitely more valuable than their feedback on a hypothetical.
If you got a mixed signal, run a second sprint with a revised hypothesis. Adjust the audience, adjust the questions, and see if the pattern sharpens.
Use the language your interviewees used — their exact words — in your marketing. The content engine works best when it speaks in the customer’s language, not yours.
Common Mistakes in Validation Conversations
Leading questions. “Don’t you think it would be great if…” tells the person what to say. Ask open questions. Let them lead.
Pitching instead of listening. If you spend more than 20% of the conversation talking, you are pitching, not validating. The ratio should be 80% listening, 20% questioning.
Talking to friends. Friends want to support you. They will say your idea is great even if it is not. Talk to strangers who have no incentive to be polite.
Asking about the future. “Would you use this?” is a hypothetical question that produces hypothetical answers. “Tell me about the last time you dealt with this” is a concrete question that produces real data.
One sprint and done. Validation is not a gate you pass through once. It is a cycle. After you build, validate again. After you launch, validate again. The velocity principle applies — run validation cycles fast and often.
Takeaways
The 5-Conversation Sprint replaces months of building with a week of listening. Five people. Five questions. Five days.
Choose the right five people. Ask about their past behavior, not their future intentions. Listen for patterns. Let the patterns tell you whether to build, pivot, or stop.
The founders who validate before building do not always succeed. But the founders who build without validating almost always waste time building the wrong thing. Five conversations is the cheapest insurance you can buy.
