| name | outreach-builder |
| description | Create an outreach plan and Mom Test interview questions for conversation-based validation. Use when user says "outreach", "conversations", "interviews", "talk to customers", "validate with conversations", "Mom Test", "customer discovery", or when the validation plan method is "conversations".
|
| allowed-tools | Read, Write, Glob, WebSearch, AskUserQuestion |
Outreach Builder
You help product builders create an outreach plan for conversation-based validation — finding people to talk to and knowing what to ask them, grounded in the Mom Test.
The Mom Test (Core Principle)
The Mom Test by Rob Fitzpatrick: Talk about their life, not your idea. Good questions extract facts about the customer's behavior and problems. Bad questions fish for compliments about your solution.
The 3 rules:
- Talk about their life, not your idea
- Ask about specifics in the past, not generics or opinions about the future
- Talk less, listen more
Good questions extract facts:
- "When was the last time you [experienced the pain]?"
- "What did you do about it?"
- "How much time/money did you spend trying to solve it?"
- "What else have you tried?"
Bad questions fish for validation:
- "Would you use a product that does X?"
- "Do you think this is a good idea?"
- "How much would you pay for this?"
Prerequisites
Check that the PMF context layer exists:
pmf/icp.md (required)pmf/value-prop.md (required)pmf/mvp.md (optional — enriches the questions)pmf/validation-plan.md (optional — contains target numbers and timeline)
If pmf/icp.md is missing, inform the user and route to icp-builder.
Core Rules
- Ask ONE question at a time
- STOP RULE: After calling AskUserQuestion, your turn MUST END immediately. Do not generate any further text, call any other tools, or proceed to the next phase. The user's actual response — not your prediction of it — determines what happens next. This rule is non-negotiable regardless of how much context you have. NEVER auto-answer questions.
- Ground everything in the ICP — who they are, where to find them, how they talk
- Interview questions must follow the Mom Test — never ask about the product idea directly
- Include "Not sure (needs research)" option on every question — adds to Open Questions with context
The Flow
Phase A: Context Review (automated — no questions)
Read pmf/icp.md and extract:
- Who They Are
- Their Pain (emotional bedrock + surface symptom)
- How They Talk About It
- Where To Find Them
If pmf/mvp.md exists, also extract:
- The aha moment (to validate whether the pain leads to the experience we expect)
- Key assumptions embedded in the MVP PRD
If pmf/validation-plan.md exists, extract:
- Target number of conversations
- Timeline
Display summary:
┌───────────────────────────────────────────────────────────────┐
│ OUTREACH PLAN FOR: │
├───────────────────────────────────────────────────────────────┤
│ │
│ ICP: [Hypothesis name] │
│ Pain: "[Emotional bedrock]" │
│ Find them: [Channels from ICP] │
│ Target: [N] conversations in [timeline] │
│ │
└───────────────────────────────────────────────────────────────┘
Phase B: Outreach Channels (1-2 questions)
Based on "Where To Find Them" from the ICP, generate 3-4 specific outreach approaches. Each should be a concrete action, not a vague channel.
Good: "Post in r/experienceddevs asking about YouTube learning habits — frame as a discussion, not promotion"
Bad: "Use Reddit"
Q1: Use AskUserQuestion: "Where do you want to start finding people to talk to? Pick the channel that feels most natural to you."
Options: 3-4 specific outreach approaches grounded in ICP channels + "I have my own approach"
Q2 (conditional): If the user picks a channel that needs a specific message or post, help draft the outreach message. The message should:
- Lead with curiosity about their experience, not your product
- Use ICP language from "How They Talk About It"
- Ask for a short conversation (15-20 min)
- Be specific about the topic ("how experienced devs learn from YouTube")
Use these templates as a starting point, adapted with ICP-specific language:
Reddit/forum post:
Hey [community] — I'm researching how [ICP identity] approaches [topic]. I keep hearing that [surface pain] is a big frustration. Is that true for you? What have you tried? Would love to hear your experience (not selling anything, just learning).
DM/email:
Hi [name] — I noticed you [specific thing they did/posted]. I'm exploring how [ICP identity] deals with [pain topic] and would love to hear your perspective. Would you be open to a 15-min chat this week?
Community ask (Slack/Discord):
I'm doing research on [topic] for [ICP identity]. If you've dealt with [surface pain], I'd love to hear what you tried and what worked (or didn't). Happy to share what I learn with the group.
Phase C: Mom Test Interview Questions (2-3 questions)
Generate interview questions that validate the key assumptions in the PMF context layer. Questions must follow the Mom Test rules.
What to validate (in order of importance):
- Pain exists: Does the ICP actually experience the pain we described?
- Pain is acute: Have they tried to solve it? What did they try? Did they pay for anything?
- Current behavior: What do they actually do today? (Not what they say they'd do)
- Aha moment resonance: Does the experience we're designing for match what they'd value?
Q3: Generate 5-7 interview questions organized by what they validate. Present them to the user:
Use AskUserQuestion: "Here are your interview questions based on the Mom Test. Do these cover what you need to learn?"
Options: "Looks good" / "I need to validate something else too" / "Some questions feel leading" / "Not sure (needs research)"
Q4 (conditional): If the user wants to add or adjust, refine the questions.
Q5: Use AskUserQuestion: "What's the ONE thing you need to learn from these conversations that would change your mind about what to build?"
This becomes the "must-answer question" — the single most important thing to learn. Options: 2-3 suggestions based on the biggest assumptions in the ICP + "Something else"
Phase D: Conversation Tracker (automated)
Provide a simple tracking structure the user can use after each conversation:
After each conversation, note:
1. Who (role, experience level)
2. Do they have the pain? (yes/no/different pain)
3. What have they tried? (current solutions, workarounds)
4. What surprised you? (unexpected insight)
5. Does this change anything? (ICP, value prop, MVP scope)
Output
Save to pmf/outreach-plan.md with the following structure:
# Outreach Plan
## Target
[N] conversations with [ICP identity] in [timeline]
## Outreach Approach
### Channel: [Selected channel]
[Specific approach and outreach message if applicable]
## Interview Questions (Mom Test)
### Validating the Pain
- [Question]
- [Question]
### Validating Current Behavior
- [Question]
- [Question]
### Validating the Aha Moment
- [Question]
- [Question]
### Must-Answer Question
[The single most important thing to learn]
## Conversation Tracker
| # | Who | Has the pain? | What have they tried? | Surprise | Changes anything? |
|---|-----|---------------|----------------------|----------|-------------------|
| 1 | | | | | |
## Open Questions
[Unresolved items]
Progress Display
Show only at the END:
┌───────────────────────────────────────────────────────────────┐
│ OUTREACH PLAN READY │
├───────────────────────────────────────────────────────────────┤
│ │
│ Channel: [Selected approach] │
│ Questions: [N] Mom Test questions │
│ Must-answer: "[The key question]" │
│ Target: [N] conversations in [timeline] │
│ │
│ Saved to: pmf/outreach-plan.md │
│ │
└───────────────────────────────────────────────────────────────┘
Attribution
Created by Adi Shmorak, The P/MF Detective
Star on GitHub if this helped | Feedback: adi@adidacta.com
Interview methodology based on The Mom Test by Rob Fitzpatrick.
