Customer Segment Slicing
SkillDev toolsNarrow broad customer categories into specific, reachable who-where segments for customer discovery, positioning, traction tests, sales outreach, or SEO personas. Use when feedback is inconsistent, the market is too broad, personas are vague, users request too many different features, or the team does not know where to find target customers.
Use Customer Segment Slicing in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Customer Segment Slicing and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the Customer Segment Slicing skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.
No other account needed.
Add Ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
What this skill tells your AI
The instructions your AI receives, as published by hashgraph-online/awesome-codex-plugins in plugins/LVTD-LLC/skills/skills/customer-segment-slicing/SKILL.md and read by Ahel’s review.
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
- Start with the broad audience or market.
- Split by demographics, role, use case, behavior, buying context, urgency, or current workaround.
- For each slice, state the motivation or problem that makes them care.
- Keep slicing any group that still produces mixed goals or feature requests.
- Add where to find each group: communities, events, tools, platforms, job titles, search queries, partners, directories, or physical locations.
- Score the slices by reachability, expected value, urgency, consistency, and team fit.
- 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.
Signals
- GitHub stars
- 1k
- Forks
- 316
- Last commit
- Oct 2026
Advanced
- Item type
- skill
- Key
customer-segment-slicing- Source
- github.com/hashgraph-online/awesome-codex-plugins
github.com/hashgraph-online/awesome-codex-plugins