samuelcastro/startup-skills / idea-validation
idea-validation
VerifiedGuide founders through validating startup ideas before building. Use when a founder says "I have an idea", "help me validate", "is this a good idea", "should I build this", "customer discovery", or asks about product-market fit, market sizing, or customer interviews. Covers problem discovery, customer interviews, market validation, and go/no-go decisions.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.3 KB |
| references/case-studies.md | markdown | 10.6 KB |
| references/frameworks.md | markdown | 4.9 KB |
| references/interview-guide.md | markdown | 5.7 KB |
| references/traps.md | markdown | 6.4 KB |
references/interview-guide.md
View on GitHub# Customer Interview Guide
How to conduct validation interviews that reveal truth, not politeness.
## The Mom Test
Core principle from Rob Fitzpatrick's book: **Talk about their life, not your idea.**
### Rules
1. Talk about their life, not your idea
2. Ask about specifics in the past, not hypotheticals about the future
3. Talk less, listen more
### Bad Questions → Good Questions
| ❌ Bad (Hypothetical) | ✅ Good (Behavioral) |
|----------------------|---------------------|
| "Would you use this?" | "How do you solve this today?" |
| "Would you pay for this?" | "How much are you paying now?" |
| "Do you have this problem?" | "Tell me about the last time this happened" |
| "What would you pay?" | "What have you tried? How much did it cost?" |
| "Is this a good idea?" | "What's the hardest part about [doing X]?" |
## Interview Structure
### Opening (2 min)
- Thank them for time
- Explain you're exploring a problem space (not selling)
- Ask permission to take notes
### Context Questions (5 min)
- "Tell me about your role/situation"
- "Walk me through a typical day/week when you deal with [X]"
- "How long have you been dealing with this?"
### Problem Exploration (15 min)
- "What's the hardest part about [doing X]?"
- "Tell me about the last time that happened"
- "Why was that hard?"
- "What did you do about it?"
- "What else have you tried?"
- "How did that work out?"
### Solution Exploration (10 min)
- "What solutions have you tried?"
- "What do you like about your current solution?"
- "What's frustrating about it?"
- "If you could wave a magic wand, what would be different?"
- "What would it mean if this problem went away?"
### Closing (3 min)
- "What questions should I have asked that I didn't?"
- "Who else should I talk to about this?"
- "Can I follow up if I have more questions?"
## Signal Detection
### Strong Positive Signals ✅
| Signal | Example |
|--------|---------|
| **Emotional response** | Sighing, frustrated tone, visible relief when discussing problem |
| **Time/money spent** | "I've tried 5 different tools" / "We spend $X/month on this" |
| **Active searching** | "I've been looking for something like this" |
| **Specific stories** | Detailed recounting of painful incidents |
| **Asking for solution** | "Wait, are you building something? Can I try it?" |
| **Referrals unprompted** | "You should talk to my colleague, she has this worse" |
| **Leaning forward** | Physical engagement, interrupting with questions |
### Weak/Negative Signals ❌
| Signal | Example |
|--------|---------|
| **Vague agreement** | "Yeah, that's kind of annoying I guess" |
| **No current solution** | "I've never really tried to fix it" |
| **Hypothetical interest** | "I could see how that might be useful" |
| **Compliments** | "That's a cool idea!" (without asking to use it) |
| **Deflection** | "You should talk to someone else about that" |
| **No time investment** | Hasn't searched for solutions, hasn't complained to anyone |
### The "Hair on Fire" Test
Ask yourself: Is this a "nice to have" or "need to have"?
| Vitamin (Nice to Have) | Painkiller (Need to Have) |
|------------------------|---------------------------|
| "Sure, I'd check it out" | "When can I get this?" |
| General interest | Specific urgency |
| No current workaround | Elaborate workarounds |
| Casual tone | Emotional tone |
## Questions by Idea Type
### B2B SaaS
- "How does this problem impact your team's productivity?"
- "What does this cost you in time/money?"
- "Who else is affected by this?"
- "What would you need to see to bring this to your boss?"
- "What's your budget for solving this?"
### Consumer
- "How often do you encounter this?"
- "What do you do when it happens?"
- "Have you told anyone else about this frustration?"
- "What apps/services do you use for this now?"
- "Would you tell a friend about a solution?"
### Marketplace (Two-Sided)
**Supply side:**
- "How do you get customers today?"
- "What's your biggest challenge with [current platform]?"
- "What would make you switch?"
**Demand side:**
- "How do you find [suppliers] today?"
- "What's frustrating about that process?"
- "What would make you trust a new platform?"
### Dev Tools
- "How do you solve this currently?"
- "What's your workaround?"
- "How much time does this take?"
- "Would you build vs. buy?"
- "What would make you trust a startup's tool?"
## Interview Logistics
### Finding People
- Personal network (but beware bias)
- LinkedIn outreach
- Craigslist ads (Cocoon, Cover examples)
- Reddit/forums
- Compensate for time ($20-50 gift card reduces friend-bias)
### How Many?
| Type | Minimum |
|------|---------|
| B2C uniform behavior | 20 interviews |
| B2B varied buying patterns | 50+ interviews |
| Marketplace (each side) | 20+ per side |
**Rule**: Keep going until clear patterns emerge. If interview 15 sounds like interview 5, you're getting signal.
### Recording & Notes
- Ask permission to record
- Take notes on exact words (quote them back later)
- Note emotional reactions, not just content
- Debrief immediately after
## Red Flags in Your Own Behavior
Watch for these in yourself:
- Pitching instead of listening
- Fishing for compliments
- Asking leading questions
- Getting defensive about objections
- Talking more than 30% of the time
- Only talking to people who'll be nice to you
## Post-Interview Analysis
After each interview, rate:
1. **Problem severity** (1-5): How painful is this?
2. **Current spend** ($/time): What are they investing now?
3. **Active searching** (Y/N): Are they looking for solutions?
4. **Decision maker** (Y/N): Can they buy?
5. **Pull strength** (1-5): How eager were they?
After 10+ interviews, look for:
- Consistent problem descriptions
- Similar workarounds
- Common objections
- Clear buyer persona emerging
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |