Customer Conversation Access
Use this skill to help teams get into useful customer conversations without
turning every interaction into a formal interview or sales pitch. The best
access path depends on where the target segment already spends time and who can
credibly introduce the team.
Source Traceability
Primary source: The Mom Test by Rob Fitzpatrick, especially chapters 4, 6, and
7. Guidance is paraphrased for this MIT repo; authoring notes used converted
EPUB lines 2176-2362 and 2791-3610.
Access Paths
| Path |
Use When |
Watch For |
| Warm intros |
Someone credible can introduce the team |
Make the ask easy and specific |
| Existing communities |
Customers gather in events, forums, meetups, Slack, Discord, or associations |
Participate before extracting value |
| Casual chats |
The context naturally touches the problem |
Keep the idea out until needed |
| Teaching or office hours |
The team has a useful point of view |
Do not disguise a sales pitch as education |
| Landing-page replies |
People opted into the topic |
Follow up personally, not only with metrics |
| Advisors |
Industry structure is unclear |
Advisors should create learning, not just status |
Meeting Framing
When a formal ask is required, include:
- Vision: the broad problem or better world.
- Stage: where the team is now.
- Weakness: what the team does not understand yet.
- Pedestal: why this person can help.
- Ask: the specific, easy-to-forward conversation request.
Keep the framing short. Do not ask for opinions on the idea. Ask for help
understanding a domain, problem, workflow, or decision process. Prefer a short,
specific conversation over a broad "pick your brain" request.
Output Format
# Customer Conversation Access Plan
## Segment
[Who we need to talk to.]
## Best Access Paths
| Path | Why It Fits | First Action | Risk |
|------|-------------|--------------|------|
## Warm Intro Or Meeting Ask
- Vision:
- Stage:
- Weakness:
- Why them:
- Ask:
## Follow-Up
- Target number of conversations:
- Next source if this fails:
- What to track:
Workflow
Use workflows/frame-warm-intro.md when drafting an intro request, meeting
request, or conversation opener.
Quality Bar
- Do not default to cold outreach if a warmer path is plausible.
- Do not hide a sales pitch inside a request for advice.
- Do not ask for a formal meeting when a casual conversation would learn enough.
- Do not measure access only by response rate. The goal is useful
conversations with the right people.
1---2name: customer-conversation-access3description: Find and frame customer conversations through warm intros, communities, casual chats, events, advisors, landing-page replies, and meeting requests. Use when a team needs people to interview, cold outreach is failing, a meeting ask sounds needy or pitchy, or customer discovery needs a credible reason to talk.4license: MIT5compatibility: Codex, Claude Code, and other Agent Skills-compatible clients.6metadata:7 version: "0.1.3"8 displayName: Customer Conversation Access9 category: Marketing10 tags: customer-discovery,outreach,startups,interviews,research11---1213# Customer Conversation Access1415Use this skill to help teams get into useful customer conversations without16turning every interaction into a formal interview or sales pitch. The best17access path depends on where the target segment already spends time and who can18credibly introduce the team.1920## Source Traceability2122Primary source: The Mom Test by Rob Fitzpatrick, especially chapters 4, 6, and237. Guidance is paraphrased for this MIT repo; authoring notes used converted24EPUB lines 2176-2362 and 2791-3610.2526## Access Paths2728| Path | Use When | Watch For |29|------|----------|-----------|30| Warm intros | Someone credible can introduce the team | Make the ask easy and specific |31| Existing communities | Customers gather in events, forums, meetups, Slack, Discord, or associations | Participate before extracting value |32| Casual chats | The context naturally touches the problem | Keep the idea out until needed |33| Teaching or office hours | The team has a useful point of view | Do not disguise a sales pitch as education |34| Landing-page replies | People opted into the topic | Follow up personally, not only with metrics |35| Advisors | Industry structure is unclear | Advisors should create learning, not just status |3637## Meeting Framing3839When a formal ask is required, include:40411. Vision: the broad problem or better world.422. Stage: where the team is now.433. Weakness: what the team does not understand yet.444. Pedestal: why this person can help.455. Ask: the specific, easy-to-forward conversation request.4647Keep the framing short. Do not ask for opinions on the idea. Ask for help48understanding a domain, problem, workflow, or decision process. Prefer a short,49specific conversation over a broad "pick your brain" request.5051## Output Format5253```markdown54# Customer Conversation Access Plan5556## Segment57[Who we need to talk to.]5859## Best Access Paths60| Path | Why It Fits | First Action | Risk |61|------|-------------|--------------|------|6263## Warm Intro Or Meeting Ask64- Vision:65- Stage:66- Weakness:67- Why them:68- Ask:6970## Follow-Up71- Target number of conversations:72- Next source if this fails:73- What to track:74```7576## Workflow7778Use `workflows/frame-warm-intro.md` when drafting an intro request, meeting79request, or conversation opener.8081## Quality Bar8283- Do not default to cold outreach if a warmer path is plausible.84- Do not hide a sales pitch inside a request for advice.85- Do not ask for a formal meeting when a casual conversation would learn enough.86- Do not measure access only by response rate. The goal is useful87 conversations with the right people.
ConcertoNotes