mcpField
C
customer-segment-slicing

customer-segment-slicing

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

About customer-segment-slicing

A customer discovery skill for founders and teams whose target audience is too broad to yield consistent feedback. It helps define specific who-and-where segments, assess their suitability, and select one for the next discovery or traction test.

Key features

  1. 01Split broad audiences into slices
  2. 02Identify each slice’s problem and motivation
  3. 03Map places to find each group
  4. 04Score reachability, value, and fit
  5. 05Select a starting segment

Use cases

  1. 01Narrowing an audience before customer interviews
  2. 02Choosing a segment for sales outreach
  3. 03Planning a focused traction test

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/lvtd-llc/skills --skill customer-segment-slicing

After installing, type/customer-segment-slicingin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlworkflows/slice-customer-segment.md

Details

From the project README

Customer Segment Slicing

Use this skill before customer conversations, traction tests, sales outreach, or persona work when the target customer is too broad to produce consistent evidence. A useful segment is a who-where pair: who has the problem and where the team can find them.

Source Traceability

Primary source: The Mom Test by Rob Fitzpatrick, especially chapters 6-7. Guidance is paraphrased for this MIT repo; authoring notes used converted EPUB lines 2791-3610.

Slicing Workflow

  1. Start with the broad audience or market.
  2. Split by demographics, role, use case, behavior, buying context, urgency, or current workaround.
  3. For each slice, state the motivation or problem that makes them care.
  4. Keep slicing any group that still produces mixed goals or feature requests.
  5. Add where to find each group: communities, events, tools, platforms, job titles, search queries, partners, directories, or physical locations.
  6. Score the slices by reachability, expected value, urgency, consistency, and team fit.
  7. Pick one starting segment for the next discovery or traction pass.

Useful Segment Tests

Ask:

  • Would most people in this slice share the same problem or goal?
  • Can we find at least five of them this week?
  • Do they already spend time, money, attention, or reputation on this problem?
  • Would their feedback point toward one product direction rather than many?
  • Are there hidden stakeholders, buyers, users, or partners?
  • Is this slice narrow enough to learn from but valuable enough to matter?

Output Format

# Customer Segment Slicing

## Broad Segment
[Starting audience.]

## Candidate Slices
| Segment | Problem or Goal | Where To Find Them | Current Behavior | Reachability | Value | Urgency | Consistency | Fit |
|---------|-----------------|--------------------|------------------|--------------|-------|---------|-------------|-----|

## Recommended Starting Segment
[One who-where pair.]

## Why This Segment
- Strong shared motivation:
- Easy access path:
- Evidence to gather:
- Risks:

## Next Conversations
1. [Person/source]
2. [Person/source]
3. [Person/source]

Workflow

Use workflows/slice-customer-segment.md for a full segmentation pass.

Quality Bar

  • Do not accept categories like "students", "businesses", or "creators" without further slicing.
  • Do not optimize positioning or features from mixed-segment feedback.
  • Do not choose a segment that cannot be found.
  • Do not talk only to impressive people if they are not representative users, buyers, or stakeholders.

Comments

Markdown supported