Why Five Days?
Customer discovery isn't glamorous. It's the work founders avoid. But compression forces rigor. A five-day sprint creates urgency that prevents endless deliberation. You'll conduct 10-12 interviews, spot patterns by Wednesday, and decide by Friday—not after six months of building.
Michael Seibel (YC) advises: "Do customer interviews before you write code." Scott Belsky's "The Messy Middle" confirms that founders who validate before building avoid the sunk-cost trap. You're not building a company this week. You're buying information.
Day 1-2: Recruit Your First 10 Users
Your goal: 10-12 interviews scheduled by end of Day 2.
Start with your warm network. Email everyone in your phone. Be direct:
> "I'm building a [specific product] for [specific problem]. I'm talking to 10 people to validate the idea. Can I buy you coffee/call you for 20 minutes Thursday?"
Specificity matters. "For early-stage founders" beats "for entrepreneurs."
Sourcing channels (rank by quality for Indian startups):
1. LinkedIn (search company/role, message 15 people/day)
2. Reddit (r/India, r/startups—lurk, participate, then DM)
3. WhatsApp groups (relevant communities, ask the admin for intro)
4. YourStory/Product Hunt comments (people publicly interested in startups)
5. Twitter (find micro-influencers in your niche, offer them exclusive access)
Skip paid ads. Paid users optimize for clicks, not honesty. You need people who will tell you harsh truths.
Template to personalize (adjust time to 15 min, offer tea/coffee):
```
Subject: Quick feedback on [specific problem I'm solving]
Hi [Name],
I'm talking to 10 people this week about [specific problem]. You mentioned [specific detail about them] on [LinkedIn/Twitter/etc]. I'd love 15 mins of your time.
Not a sales call—just research.
Free? Thursday 3 PM or Friday 10 AM?
[Your name]
```
Expect 30-40% response rate if you're specific and personal. That's 5-6 confirmations from 15 outreaches. Do this twice.
Day 3-4: Problem Interview Framework
You have eight hours of interview slots. Structure each to extract patterns.
Pre-interview setup:
- Record (with permission). You can't synthesize 10 hours of audio. You'll miss half the insights.
- Use Google Meet or Zoom. Share your calendar link. Reduce friction.
- Brief intro (30 seconds). "I'm exploring [problem]. Not pitching anything."
Interview template (18 minutes):
1. Warm-up (1 min): "What's your role at [company]?"
2. Problem space (5 min): "Walk me through the last time you [experienced the problem I'm solving for]."
3. Current solution (4 min): "How do you solve it today? What tools do you use?"
4. Pain (3 min): "What frustrates you most about that approach?"
5. Budget (2 min): "How much would you pay to fix this?"
6. Closing (3 min): "Who else should I talk to?"
Critical rule: Stop talking. Most founders talk 50% of the interview. Listen for the customer to interrupt you or pause awkwardly. That's where truth lives.
Red flag questions that reveal desperation:
- "Do you think this is a good idea?" (They'll say yes to be nice.)
- "Would you use this?" (Intention ≠ behavior.)
- "Do you have this problem?" (Leading question.)
Instead:
- "Tell me about the last three times you tried to solve this."
- "How much time per week does this waste?"
- "If it went unsolved forever, what would happen?"
India-specific note: Customers often say yes to please you. Watch behavior instead. "Do you currently use a solution?" → ask which one, why that one, what do you pay. Specificity forces truth.
Day 5: Synthesis & Decision
You have 10 hours of recordings. Don't transcribe all of them.
Rapid synthesis process (4 hours):
1. Write a one-paragraph summary of each interview: problem stated, current solution, biggest frustration, budget signal. (60 min)
2. List 20 raw quotes that stuck with you. Copy-paste from notes. (30 min)
3. Find three patterns. Do 8+ customers mention the same problem? Do they all use Tool X? Do they all spend 4+ hours/week on this? (60 min)
4. List three surprising answers. Things that contradicted your hypothesis. (30 min)
Decision framework:
- Pattern strength: 8+ people mention same problem → Double down. Build.
- Pattern strength: 4-7 people mention problem → Pivot. Reshape your angle.
- Pattern strength: <4 people, or contradictions → Abandon or restart with different customer segment.
Write a one-page summary:
```
Thesis: [Your original assumption]
Finding: [What customers actually said]
Action: [Build/Pivot/Abandon]
Next: [Most important follow-up]
```
Share with your co-founder or a mentor. Don't rationalize. Your data is clean this week.
Common Failure Modes
"I got seven interviews, that's enough." No. Seven is one bad day away from statistical noise. Push to 10-12.
"Everyone said yes, so I'm building." Confirmation bias. Reread their frustrations. How many will pay? How many said "maybe"? (Maybe = no.)
"I didn't find a pattern." You found a pattern: no clear consensus. That's valuable. Pivot your customer segment or problem angle.
Actionable Takeaway
This week: Pick a specific customer segment (e.g., "early-stage B2B SaaS founders in Bangalore"). Email 30 people by Wednesday morning. Conduct 10 interviews by Friday EOD. Synthesize Saturday. Decide Monday whether to build.
Don't overthink recruitment. Imperfect data beats perfect planning. Move.