mcpField
C
customer-conversation-access

customer-conversation-access

github.com/lvtd-llcMarketing & growth160 installsUpdated 7w ago
Repository

About customer-conversation-access

A skill for planning ways to reach relevant customers and invite them into useful conversations. It helps teams choose credible access paths and frame specific, low-pressure meeting requests.

Key features

  1. 01Select access paths by customer segment
  2. 02Use warm introductions and communities
  3. 03Frame concise, specific conversation requests
  4. 04Avoid disguised sales pitches

Use cases

  1. 01Find customer contacts through existing communities
  2. 02Draft a warm introduction or meeting request

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/lvtd-llc/skills --skill customer-conversation-access

After installing, type/customer-conversation-accessin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlworkflows/frame-warm-intro.md

Details

From the project README

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

PathUse WhenWatch For
Warm introsSomeone credible can introduce the teamMake the ask easy and specific
Existing communitiesCustomers gather in events, forums, meetups, Slack, Discord, or associationsParticipate before extracting value
Casual chatsThe context naturally touches the problemKeep the idea out until needed
Teaching or office hoursThe team has a useful point of viewDo not disguise a sales pitch as education
Landing-page repliesPeople opted into the topicFollow up personally, not only with metrics
AdvisorsIndustry structure is unclearAdvisors should create learning, not just status

Meeting Framing

When a formal ask is required, include:

  1. Vision: the broad problem or better world.
  2. Stage: where the team is now.
  3. Weakness: what the team does not understand yet.
  4. Pedestal: why this person can help.
  5. 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.

Comments

Markdown supported