Skip to content
fnd.r-segmenting-customers logo

fnd.r-segmenting-customers

Generates strategic customer segment definitions with observable filters, segment sizing, and pain intensity scores. Use when defining target customers, building Canvas section 04, translating market research to segments, or when user mentions "segments", "ICP", "target market", or "who to sell to".

SKILL.md

Full skill instructions

Customer Segmenting

Generate strategic customer segment definitions for strategy/​canvas/​04.segments.md.

Prerequisites

Before proceeding, verify:

  • strategy/​canvas/​03.opportunity.md exists (TAM/​SAM/​SOM data required)

If missing, inform user:

Canvas 03.opportunity.md required before defining segments.
Use fnd-researcher agent to establish market sizing first.

Optional context (read if exists):

  • strategy/​canvas/​01.context.md — KBOS framework
  • strategy/​canvas/​05.problem.md — Problem severity data

Core Principle

Segments must be observable and strategic:

CriterionTest
ObservableCan identify via searchable database query
SizeableMarket size estimable from public data
AccessibleReachable through known channels
DifferentiableDistinct needs from other segments

Process

1. Load Context

Read available canvas files:

strategy/​canvas/​03.opportunity.md  # Required: TAM/​SAM/​SOM
strategy/​canvas/​01.context.md      # Optional: strategic context
strategy/​canvas/​05.problem.md      # Optional: pain data

Extract: market size, trends, existing customer hypotheses.

2. List Segment Hypotheses

From market research, identify 3-5 potential customer groups.

For each, capture:

  • Who they are (role, company type)
  • Why they might buy (problem fit)
  • How big the group is (rough estimate)

3. Define Observable Filters

For each segment, identify 2-4 searchable criteria.

Valid filters (can query in databases):

  • Company size: "50-200 employees"
  • Industry: "E-commerce, NAICS 454110"
  • Technology: "Uses Shopify Plus"
  • Geography: "US-based, tier-1 cities"
  • Behavior: "Monthly GMV >$100K"

Invalid filters (not searchable):

  • "Innovative companies"
  • "Growth-minded founders"
  • "Customer-centric organizations"

See references/​filters.md for comprehensive examples.

4. Score Pain Intensity

Rate each segment's pain 1-5:

ScoreSignal
5Hair-on-fire, actively buying solutions
4Significant pain, budget exists
3Recognized problem, no urgency
2Mild inconvenience
1Unaware of problem

Require evidence for each score — job postings, market reports, interview quotes.

See references/​scoring.md for detailed rubric.

5. Estimate Segment Size

For each segment, calculate:

  • Total matching filters (from industry data)
  • Portion within SAM (addressable)
  • Derivation source (cite report or calculation)

Use 03.opportunity.md TAM/​SAM as ceiling.

6. Prioritize Segments

Rank by: Pain Intensity × Willingness to Pay × Accessibility

Select:

  • 1 Primary (P0) — Immediate focus, highest score
  • 1-2 Secondary (P1) — Expansion path

Document rationale for prioritization.

7. Write Output

Format per references/​template.md.

Write to: strategy/​canvas/​04.segments.md

Quality Checklist

Before writing output, verify:

  • Each segment has 2+ observable, searchable filters
  • No psychographic traits in filters
  • Segment sizes quantified with sources
  • Pain scores have evidence justification
  • 1-3 segments total (not 5+)
  • Clear prioritization rationale
  • Cross-references 05.problem.md if exists

Common Mistakes

MistakeExampleFix
Too many segments5+ with blurry boundariesConsolidate to 1-3 focused segments
Vague sizing"Large market""~12,000 US companies matching filters"
Missing pain evidence"Pain: 4""Pain: 4 — 340 job postings for this role"
Psychographic filters"Forward-thinking retailers""Retailers >$1M GMV on modern platforms"
No prioritization logic"Both equally important""Primary: highest pain (5) + proven WTP"

Output Location

strategy/​canvas/​04.segments.md

Boundaries

  • Does NOT validate segment existence (requires outreach)
  • Does NOT guarantee segment accessibility
  • Does NOT interview customers (provides framework)
  • Segment sizes are estimates from available data
  • Pain scores require evidence — flag when assumed
  • Does NOT handle persona creation (behavior, not demographics)
  • Observable filters must be searchable in databases
  • Psychographic traits are NOT valid filters

Resources

More skills from majiayu000

xiaohongshu logo
majiayu000/claude-arsenal

xiaohongshu

xiaohongshu

286 148
View
agent-task-conductor logo
majiayu000/claude-skill-registry

agent-task-conductor

Conduct multi-agent task orchestration and workflow coordination.

663 1
View
conductor-setup logo
majiayu000/claude-skill-registry

conductor-setup

Initialize project with Conductor artifacts (product definition,

663 1
View
animation-designer logo
majiayu000/claude-skill-registry

animation-designer

Expert in web animations, transitions, and motion design using Framer Motion and CSS

663 1
View
diagramming logo
majiayu000/claude-skill-registry

diagramming

Creates Mermaid and ASCII diagrams for flowcharts, architecture, ERDs, state machines, mindmaps, and more. Use when user mentions diagram, flowchart, mermaid, ASCII diagram, text diagram, terminal diagram, visualize, C4, mindmap, architecture diagram, sequence diagram, ERD, or needs visual docume...

663 1
View
h3-pg logo
majiayu000/claude-skill-registry-data

h3-pg

PostgreSQL bindings for H3 hexagonal grid system. Use when working with H3 cells in Postgres, including spatial indexing, geometry/geography integration, and raster analysis.

23 1
View
conductor-development logo
majiayu000/claude-skill-registry

conductor-development

Context-Driven Development skill for projects using Conductor. Use this skill when you detect a `conductor/` directory in the project, when working on tasks defined in a `plan.md` file, or when the user asks about tracks, specs, or plans. Automatically applies TDD workflow, tracks task completion...

663 1
View
conductor-status logo
majiayu000/claude-skill-registry

conductor-status

Display project status, active tracks, and next actions

663 1
View
dockerization logo
majiayu000/claude-skill-registry

dockerization

Official Stakpak application containerization standard operating procedure, a step-by-step guidline to properly dockerize applications. This is a rule book curated by the Stakpak Team.

663 1
View

Popular AI tools

Kaiber logo
Video

Kaiber

Generate, edit, and beat-sync AI video with leading models in one workspace.

Paid
View
Vimcal logo
Productivity

Vimcal

The world's fastest calendar for remote work

Free
View

Transform Your Design with AI Designer by ImgCreator.ai

Freemium
View
Akool AI logo
Content & writing

Akool AI

Revolutionizing Video Production with AI-Powered Creativity

Paid
View

Extend an image past the frame and let AI fill the new aspect ratio.

Freemium
View
StarByFace logo
Security

StarByFace

Discover your celebrity doppelgänger with StarByFace!

Free
View
C

ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.

Freemium
View
Opus Clip logo
Coding & apps

Opus Clip

Opus.ai: Revolutionize Your Web Experience

Free
View