In 2016, I spent four months building a digital product nobody wanted. The idea had seemed brilliant in my head. The problem was real. The solution was elegant. And exactly 23 people bought it, which was about 977 fewer than the break-even number.
The post-mortem was embarrassing in its simplicity: I hadn’t talked to enough potential customers before building. I’d talked to two friends who said “that sounds cool” — which is what friends say about everything — and then went straight to building. Four months and several thousand euros later, the market delivered the feedback I should have gotten in week one.
That experience is why I developed the 5-Conversation Sprint: a structured one-week process for validating any business idea through five conversations with potential customers. Not five hundred conversations. Not a market research study. Five targeted, well-structured conversations that tell you whether to proceed, pivot, or abandon — before you invest significant time or money.
Why Five Conversations (Not Fifty)
You don’t need statistical significance to validate a business idea. You need pattern recognition. And patterns emerge with surprisingly small sample sizes when the conversations are structured well.
Here’s the math: if you talk to five potential customers and all five describe the same problem in similar language, that’s a strong signal. If four out of five express genuine interest in a solution, that’s directionally valid. If three out of five say “I’d pay for that” without being prompted, you have something worth building.
Conversely, if you talk to five people and get five different problems, five different reactions, and no consistent pattern, you either have the wrong idea, the wrong audience, or the wrong framing. Five conversations won’t tell you which, but they’ll tell you something is off before you invest months finding out.
The power of five isn’t in the number — it’s in the constraint. Five conversations force you to be selective about who you talk to, structured in your questions, and honest about what you hear. Fifty conversations let you hide in volume, cherry-pick supportive data, and delay the uncomfortable conclusions.
I’ve run over thirty 5-Conversation Sprints for my own ideas and with founders in our accelerator program. The framework has prevented at least a dozen expensive mistakes and confirmed about eight ideas that went on to generate real revenue. The ROI of five hours of conversation versus four months of wasted building is incalculable.
Day 1-2: Finding the Right Five People
The conversations are only as valuable as the people you have them with. The wrong five people will validate a bad idea or invalidate a good one.
Who to talk to:
Your five people should be as close as possible to your actual target customer. Not friends (they’ll be nice). Not fellow founders (they’ll project their own experiences). Not people who are vaguely interested in your space. Actual potential buyers.
The criteria:
- They have the problem you’re trying to solve (or you believe they do)
- They have the authority and budget to buy a solution
- They’re reachable within two days (speed matters — momentum dies quickly)
- They represent at least two different sub-segments of your target market (diversity prevents tunnel vision)
How to find them:
- LinkedIn search for job titles and industries that match your target
- Industry forums, communities, and groups where your target hangs out
- Referrals from your existing network (“Do you know anyone who deals with [problem]?”)
- Past contacts who fit the profile
- Event attendee lists from relevant conferences or meetups
The ask:
Don’t ask for a “sales call” or a “demo.” Ask for a conversation about their experience with the problem. Here’s the exact message template I use:
“Hi [name], I’m researching how [specific role/industry] handles [specific problem]. I’m not selling anything — I’m trying to understand the problem better before I build anything. Would you be open to a 20-minute conversation about your experience? I’m happy to share what I learn from the research as a thank-you.”
This message works because it’s honest (you genuinely want to learn), bounded (20 minutes), and reciprocal (you’ll share findings). My response rate with this template is about 40%, which means contacting 12-15 people typically yields five conversations.
Day 3-5: The Five Conversations
Each conversation follows a specific structure designed to extract honest information rather than polite validation. The entire conversation should take 20-30 minutes.
Part 1: Context (5 minutes)
Start with their world, not your idea. Ask:
- “Tell me about your role. What does a typical week look like?”
- “What are the biggest challenges you’re dealing with right now?”
Listen for whether the problem you’re trying to solve comes up naturally. If it does, that’s a strong signal. If it doesn’t, note that — it means the problem may not be top-of-mind, which matters for willingness to pay.
Part 2: Problem Exploration (10 minutes)
Now focus on the specific problem area. Ask:
- “How do you currently handle [problem area]?”
- “What’s the most frustrating part of that?”
- “How much time/money does this problem cost you in a typical month?”
- “Have you tried to solve this before? What happened?”
- “If this problem disappeared tomorrow, what would change?”
These questions reveal: problem severity (is it painful enough to pay for?), current solutions (what are you competing with?), willingness to invest (have they spent money trying to fix it?), and impact (does solving it matter enough?).
The critical question is the “have you tried to solve this?” question. If someone has a problem but has never tried to solve it, the problem might not be severe enough to generate buying behavior. If they’ve tried multiple solutions and none worked, you’ve found a hungry market.
Part 3: Solution Reaction (10 minutes)
Only after understanding their problem, describe your proposed solution. Keep it to two sentences. Then ask:
- “What’s your initial reaction?”
- “What would make this useful versus not useful for you?”
- “What concerns would you have?”
- “If this existed today, would you use it? Would you pay for it?”
- “What would you expect to pay?”
Listen for enthusiasm versus politeness. Enthusiasm sounds like: “When can I get this?” “Can I sign up now?” “My colleague needs this too.” Politeness sounds like: “That’s interesting.” “I could see that being useful.” “Sure, maybe.”
The difference is night and day once you learn to hear it. Enthusiasm is a buy signal. Politeness is a non-signal that founders frequently mistake for validation.
Part 4: Close (2 minutes)
Thank them. Ask if they’d be willing to be a beta tester if you build this. Ask if they know others who face the same problem. Both of these are additional data points: willingness to be a beta tester indicates genuine interest, and referrals indicate perceived value.
Day 5-6: Pattern Analysis
After five conversations, analyze the patterns. Use this matrix:
| Pattern | Strong Signal | Weak Signal | Red Flag |
|---|---|---|---|
| Problem recognition | 4-5/5 mention the problem unprompted | 2-3/5 mention it only when asked | 0-1/5 recognize it |
| Current spending | 3+/5 have tried paid solutions | 1-2/5 have tried free solutions | Nobody’s tried to solve it |
| Solution reaction | 3+/5 show enthusiasm | 2-3/5 show polite interest | Confusion or indifference |
| Willingness to pay | 3+/5 name a specific price | 1-2/5 say “maybe" | "I wouldn’t pay for that” |
| Beta interest | 4+/5 say yes | 2-3/5 say yes | 0-1/5 interested |
If you see mostly strong signals: Proceed to building. You have validation. Don’t over-research — ship it ugly and iterate with real customers.
If you see mostly weak signals: Adjust your idea. The problem might be real but your solution might be wrong, your audience might be wrong, or your framing might be wrong. Run another sprint with adjusted parameters.
If you see red flags: Abandon or fundamentally rethink. The market is telling you something important. Listen to it. The cost of five conversations is nothing compared to the cost of building something nobody wants.
Common Mistakes in Validation Conversations
I’ve coached dozens of founders through their first 5-Conversation Sprints, and the same mistakes show up consistently:
Pitching instead of asking. The conversation is supposed to be 80% listening. If you’re talking more than 20% of the time, you’re pitching, not validating. Bite your tongue. Ask the next question. Listen.
Leading questions. “Don’t you think it would be great if there was a tool that did X?” is not a validation question. It’s a leading question that invites agreement. Ask open-ended questions that let the person describe their reality without being guided toward your preferred answer.
Ignoring negative signals. When someone says “I’m not sure I’d pay for that,” many founders hear “I need to explain the value better.” Sometimes that’s true. More often, the person is giving you honest feedback that you don’t want to hear. If three people say they wouldn’t pay, that’s a signal, not a communication problem.
Asking friends and family. Your mother will say your idea is wonderful. So will your best friend. These conversations provide zero validation because the social dynamics override honesty. Talk to strangers who have no incentive to make you feel good.
Skipping the “have you tried to solve this?” question. This is the most important question in the entire framework. Past behavior predicts future behavior. If someone has never tried to solve the problem you’re addressing, the probability that they’ll pay you to solve it is low — regardless of what they say in the conversation.
After the Sprint: What Comes Next
The 5-Conversation Sprint is a filter, not a guarantee. A positive result means “this idea is worth investing more in.” It doesn’t mean “this will definitely succeed.”
If the sprint validates your idea, the next steps are:
- Build the minimum version. Not the full vision — the smallest thing that delivers the core value. The Ship Trigger framework helps define what “minimum” actually means.
- Go back to your five people. Offer them early access, a beta test, or a pilot engagement. Their willingness to participate with real time or real money is stronger validation than their words in the conversation.
- Set your next validation milestone. “Five paying customers in sixty days” or “ten beta users with weekly usage” or similar concrete target. This keeps you from sliding back into building without validation.
If the sprint invalidates your idea, resist the urge to immediately pivot. Sit with the data for a few days. Discuss it with someone you trust. The conversations may have revealed a different problem worth solving, or a different audience worth serving. Sometimes the best ideas emerge from the wreckage of invalidated ones.
The 5-Conversation Sprint cost me five hours. My failed product cost me four months. The math is simple. Validate before you build. Every time.
Key takeaways:
- Find five actual potential buyers (not friends, not fellow founders) within two days using the research-framing message template.
- Structure each 20-30 minute conversation in four parts: context, problem exploration, solution reaction, and close — spend 80% listening.
- Ask “have you tried to solve this before?” in every conversation — past buying behavior is the strongest predictor of future buying behavior.
- Listen for enthusiasm versus politeness — “when can I get this?” is validation; “that sounds interesting” is not.
- Use the pattern matrix to make a clear proceed/adjust/abandon decision — if three or more strong signals across five conversations, build; if red flags, stop.
