Customer type: 
What you want to learn: 
Number of interviews: 

Conduct customer development interviews:

1. Before the interview
   Goal: Understand customer context & world
   - Who are they exactly? (role, company, background)
   - What do they do daily?
   - What problem are they trying to solve?
   - Have you met them before? (cold vs warm intro)
   
   This prep makes the interview productive.

2. Interview structure (60 minutes)
   First 5 min: Rapport
   - Small talk, explain why you're there
   - "We're trying to understand how X works"
   - NOT "We want you to validate our idea"
   
   Next 45 min: Their story
   - How do they currently solve the problem?
   - What's broken?
   - What have they tried?
   - Why didn't it work?
   - How much do they spend?
   - Who else is involved?
   - When do they want to solve this?
   
   Last 10 min: Your idea (if they ask)
   - React to THEIR context
   - Don't pitch
   - Let them poke holes

3. The critical questions
   (Steal these, modify for your context)
   - "Walk me through how you currently [solve this problem]"
   - "What's frustrating about that approach?"
   - "Have you looked for solutions? What did you find?"
   - "Why didn't you use [similar solution]?"
   - "What would need to be true for you to try something new?"
   - "How much time/money do you spend on this?"
   - "If this problem disappeared, what would change?"
   - "Who else should I talk to?"

4. Listening tips (the hard part)
   - Don't interrupt
   - Don't defend your idea
   - Don't explain how your product works (unless asked)
   - When they pause, stay silent (they'll keep talking)
   - Follow their emotional cues (when they light up, dig there)
   - Listen for the unsaid (what aren't they saying?)

5. Red flags in their answers
   - "That's interesting but not urgent" = They won't buy
   - "I'd have to think about it" = They're not convinced
   - "We've always done it this way" = Resistant to change
   - "Someone else would have to approve" = Complicated sale
   - "I'm not sure that would work" = Skeptical of solution
   
   Red flags = This might not be a real opportunity

6. Green flags in their answers
   - "I spend X hours/week on this problem" = Real pain
   - "We've tried 5 different solutions" = Urgent enough to buy
   - "I've been asking for this for months" = Pent-up demand
   - "How soon could we get it?" = They want it
   - "I'd definitely pay for that" = Willing to buy
   
   Green flags = This is a real opportunity

7. What to capture
   - Their biggest pain in their own words
   - How they currently solve it (the process)
   - Cost/time spent on current solution
   - Alternatives they've considered
   - Their buying criteria (what matters to them)
   - Decision-making timeline
   - What would convince them
   - Referrals to other customers

8. After the interview
   - Within 24 hours: Write down key insights
   - Look for patterns (with others you've interviewed)
   - DON'T: Try to convince yourself it validates your idea
   - DO: Look for where you were wrong
   - DO: Update your mental model
   
   After 10-20 interviews:
   - What patterns emerge?
   - Are 80% saying same thing?
   - Where are you wrong?
   - What should you pivot?

Examples

Input

{
  "customerType": "CTOs at Series B fintech companies",
  "learningGoal": "Do they care about infrastructure cost savings? How much would they pay?",
  "numberOfInterviews": "15 interviews"
}

Output

Complete interview playbook with pre-interview prep, 60-minute structure, critical questions, listening tips, red/green flag identification, capture framework, and post-interview analysis process.