customer-segmentation
Autonomous customer segmentation using multiple dimensions (demographic, psychographic, behavioral, needs-based, value-based, firmographic). Produces segment profiles, MASDA validation, targeting/positioning recommendations, and Mermaid diagrams with optional PNG export.
What this skill does
# Customer Segmentation You perform autonomous customer segmentation analysis. You research market and customer data yourself — do not ask the user for data they would need to look up. Only ask the user for decisions and confirmations. ## Input handling Follow shared foundation §7 — interview mode. When input is missing or insufficient, interview to gather at minimum: | Dimension | Required | Default | |---|---|---| | **Subject** (product, company, or market) | Yes | — | | **Industry/market** | Yes | — | | **B2B or B2C** | Yes | Inferred from subject | | **Geographic scope** | No | Global | | **Segmentation focus** (behavioral, needs-based, etc.) | No | Multi-dimensional | | **Known customer data or segments** | No | Will be researched | **Exit interview when**: Subject, industry, and B2B/B2C context are clear. ## Phase 1 — Setup ### 1. Collect input Accept one of: - A product, company, or market name/description - A file path to a business case document - Pasted business case content - No input or vague input → enter interview mode (§7) ### 2. Detect scope From the input (or interview results), identify: - **Subject**: The product, company, or market to segment - **Industry/market**: Sector and segment - **B2B or B2C**: Business model context (determines dimension selection) - **Geographic scope**: Region or global (default: global) - **Segmentation focus**: Specific dimensions to prioritize (default: multi-dimensional) ### 3. Confirm scope Present detected scope: ``` **Subject**: [name] **Industry**: [industry/segment] **Context**: [B2B / B2C / Both] **Geographic scope**: [scope] **Segmentation approach**: [multi-dimensional / focused on X] ``` Ask the user to confirm or adjust. Ask diagram render mode and output path per the `diagram-rendering` and `autonomous-research` mixins. ## Phase 2 — Research Use WebSearch and WebFetch per the `autonomous-research` mixin. ### 2a. Market and demographic data Research: - Target market demographics (age, income, education, occupation — B2C) or firmographics (industry, company size, revenue, tech stack — B2B) - Market size and customer population data - Industry reports on customer behavior and preferences - Census and government statistics ### 2b. Behavioral and needs data Research: - Customer purchase patterns and usage behaviors in the industry - Customer needs, pain points, and jobs-to-be-done - Product review analysis and customer sentiment - Customer journey touchpoints ### 2c. Competitive positioning data Research: - How competitors segment their market - Competitor positioning and value propositions - Underserved or unserved segments - Market gaps and whitespace ### 2d. Value data Research: - Pricing tiers and willingness-to-pay patterns in the industry - Customer lifetime value benchmarks - Cost-to-serve patterns by segment type - Revenue concentration patterns (e.g., 80/20 distribution) ## Phase 3 — Dimension Selection Select the most relevant combination of segmentation dimensions based on context: ### B2C default dimensions | Dimension | What it captures | Data sources | |---|---|---| | **Demographic** | Age, gender, income, education, family | Census, industry reports | | **Geographic** | Region, urban/rural, climate | Census, market data | | **Psychographic** | Lifestyle, values, attitudes, personality | Industry research, VALS-style frameworks | | **Behavioral** | Purchase frequency, usage, loyalty, occasion | Industry reports, reviews | | **Needs-based** | Jobs-to-be-done, problems, desired outcomes | Reviews, forums, research | | **Value-based** | Spending tier, CLV potential, price sensitivity | Pricing data, industry benchmarks | ### B2B default dimensions | Dimension | What it captures | Data sources | |---|---|---| | **Firmographic** | Industry, company size, revenue, geography | Industry databases, reports | | **Technographic** | Technology stack, digital maturity | Tech reports, industry analysis | | **Behavioral** | Purchase cycle, decision-making, engagement | Industry research | | **Needs-based** | Business problems, desired outcomes, JTBD | Industry reports, case studies | | **Value-based** | Contract size, CLV potential, cost-to-serve | Pricing data, benchmarks | Select 3-4 dimensions that provide the most differentiation for the specific subject. Document why each was chosen. ## Phase 4 — Segment Identification Identify 4-7 distinct customer segments. For each segment: 1. **Name**: Memorable, descriptive label (e.g., "Budget-Conscious Professionals", "Enterprise Early Adopters") 2. **Size**: Estimated percentage of total market and absolute numbers where available 3. **Key differentiator**: What makes this segment distinct from others 4. **Primary dimension**: Which segmentation dimension most defines this segment ### Segment identification rules - 4-7 segments — fewer than 4 is too broad, more than 7 is unmanageable - Each segment must be meaningfully different from the others - No "catch-all" or "other" segments — every segment has a clear identity - Segments must collectively cover the addressable market (no major gaps) ## Phase 5 — Segment Profiling For each segment, create a rich multi-dimensional profile: ```markdown ### Segment [N]: [Memorable Name] **Description**: [2-3 sentence overview] **Demographics / Firmographics**: - [key characteristics] **Psychographics**: - Values: [what they care about] - Lifestyle: [relevant patterns] - Attitudes: [toward the product/category] **Behaviors**: - Purchase pattern: [frequency, channel, trigger] - Usage: [heavy/medium/light, how they use] - Loyalty: [switching behavior, brand affinity] **Needs (JTBD)**: - Primary job: [main problem to solve] - Secondary jobs: [supporting needs] - Pain points: [current frustrations] **Value Profile**: - Estimated size: [% of market, absolute numbers] - Revenue potential: [spending tier, CLV estimate] - Price sensitivity: [high/medium/low] - Cost-to-serve: [high/medium/low] **MASDA Validation**: | Criterion | Assessment | |---|---| | Measurable | [can size and characteristics be quantified?] | | Accessible | [can this segment be reached through available channels?] | | Substantial | [is it large/profitable enough to serve?] | | Differentiable | [does it respond differently to different offerings?] | | Actionable | [can programs be designed to attract and serve it?] | ``` ## Phase 6 — Segment Sizing Estimate market size per segment: | Segment | % of market | Est. customer count | Est. revenue potential | CLV tier | |---|---|---|---|---| | [Name 1] | [%] | [count] | [$X] | High/Medium/Low | | [Name 2] | [%] | [count] | [$X] | High/Medium/Low | Where data is insufficient, label as `[Estimated]` with rationale. ## Phase 7 — Targeting Assessment Evaluate each segment on two axes: ### Segment attractiveness (1-5) - Market size and growth rate - Revenue potential and profitability - Competitive intensity (less competition = more attractive) - Strategic fit with the subject's strengths ### Competitive strength (1-5) - Subject's ability to serve this segment - Existing brand recognition or trust - Product-market fit - Channel access and distribution capability | Segment | Attractiveness (1-5) | Competitive strength (1-5) | Recommendation | |---|---|---|---| | [Name 1] | [score] | [score] | Primary / Secondary / Monitor / Avoid | ### Targeting recommendations For each recommended target segment, explain: - Why this segment should be prioritized - What it would take to win - Key risks ## Phase 8 — Positioning Recommendations For each target segment, propose: | Segment | Value proposition | Key differentiator | Messaging theme | |---|---|---|---| | [Name 1] | [what to offer] | [why choose us] | [core message] | Select the two most strategically relevant dimensions to define positioning axes. ## Phase 9 — Activation Roadmap For each target segment, outline how to operationalize: | Segment | Marketing | Product | Pricing | Channels | |---|---|---|---|---
Related in Sales & CRM
process-mapper
IncludedUse when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean / Six Sigma / Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work — this is tactical process documentation for internal operations.
payment-integration
IncludedIntegrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.