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 source: https://skillmd.com/skills/hashgraph-online/customer-conversation-access8 version: "0.1.3"9 displayName: Customer Conversation Access10 category: Marketing11 tags: customer-discovery,outreach,startups,interviews,research12---1314# Customer Conversation Access1516Use this skill to help teams get into useful customer conversations without17turning every interaction into a formal interview or sales pitch. The best18access path depends on where the target segment already spends time and who can19credibly introduce the team.2021## Source Traceability2223Primary source: The Mom Test by Rob Fitzpatrick, especially chapters 4, 6, and247. Guidance is paraphrased for this MIT repo; authoring notes used converted25EPUB lines 2176-2362 and 2791-3610.2627## Access Paths2829| Path | Use When | Watch For |30|------|----------|-----------|31| Warm intros | Someone credible can introduce the team | Make the ask easy and specific |32| Existing communities | Customers gather in events, forums, meetups, Slack, Discord, or associations | Participate before extracting value |33| Casual chats | The context naturally touches the problem | Keep the idea out until needed |34| Teaching or office hours | The team has a useful point of view | Do not disguise a sales pitch as education |35| Landing-page replies | People opted into the topic | Follow up personally, not only with metrics |36| Advisors | Industry structure is unclear | Advisors should create learning, not just status |3738## Meeting Framing3940When a formal ask is required, include:41421. Vision: the broad problem or better world.432. Stage: where the team is now.443. Weakness: what the team does not understand yet.454. Pedestal: why this person can help.465. Ask: the specific, easy-to-forward conversation request.4748Keep the framing short. Do not ask for opinions on the idea. Ask for help49understanding a domain, problem, workflow, or decision process. Prefer a short,50specific conversation over a broad "pick your brain" request.5152## Output Format5354```markdown55# Customer Conversation Access Plan5657## Segment58[Who we need to talk to.]5960## Best Access Paths61| Path | Why It Fits | First Action | Risk |62|------|-------------|--------------|------|6364## Warm Intro Or Meeting Ask65- Vision:66- Stage:67- Weakness:68- Why them:69- Ask:7071## Follow-Up72- Target number of conversations:73- Next source if this fails:74- What to track:75```7677## Workflow7879Use `workflows/frame-warm-intro.md` when drafting an intro request, meeting80request, or conversation opener.8182## Quality Bar8384- Do not default to cold outreach if a warmer path is plausible.85- Do not hide a sales pitch inside a request for advice.86- Do not ask for a formal meeting when a casual conversation would learn enough.87- Do not measure access only by response rate. The goal is useful88 conversations with the right people.