keep-segment

Featured

Customer segmentation model builder — tiers customers by ARR, health, and expansion potential; defines CS motion per tier; maps resource allocation. Use when asked to "segment our customers", "define our CS tiers", "how should we allocate CS resources", "build a customer segmentation model", or "who gets high-touch vs. digital".

AI & Automation 2,716 stars 395 forks Updated today MIT

Install

View on GitHub

Quality Score: 99/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Customer Segmentation Model You are Keep — the customer success engineer on the Product Team. Build a segmentation framework that matches CS resource intensity to account value and potential. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 0: Gather Customer Base Data Scan for account and revenue data: ```bash find . -name "*.md" -o -name "*.csv" -o -name "*.json" 2>/dev/null | xargs grep -l "ARR\|MRR\|customer\|account\|tier\|segment\|health\|NPS\|churn" 2>/dev/null | head -15 find . -name "*.md" 2>/dev/null | xargs grep -l "CSM\|customer.success\|expansion\|upsell\|NRR\|GRR" 2>/dev/null | head -10 ``` Ask for missing inputs: - How many customers total? - ARR distribution: what does the top 20% look like vs. the bottom 20%? - How many CSMs are available? - What is the current motion (all high-touch, all automated, or mixed)? - What is the target NRR? (Net Revenue Retention — drives how aggressive expansion needs to be) ### Step 1: Define Tier Thresholds Set tier boundaries based on ARR and the company's stage: | Tier | Name | ARR Range | Expansion Potential | % of Accounts | % of ARR | | ---- | --------- | --------- | ------------------- | ------------- | -------- | | 1 | Strategic | >$[X] | High | ~5-10% | ~50-60% | | 2 | Growth | $[Y]-$[X] | Medium | ~20-30% | ~30-40% | | 3 | Scale ...

Details

Author
jeremylongshore
Repository
jeremylongshore/claude-code-plugins-plus-skills
Created
11 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

customer-segmentation

Builds lifecycle segments with RFM scoring calibrated against your own customer distribution rather than absolute cutoffs, plus behavioural signals, explicit filter logic per segment, and the staleness rule that says when a segment must be recomputed. Use for audience segmentation and targeting, or when existing segments have stopped matching reality. Boundary: defines who is in each segment. `email-campaign` and `customer-journey` then decide what those segments receive. For churn risk on one named account use `opportunity-scoring`.

1 Updated today
sidchaudhary
AI & Automation Listed

coverage-model

Designs who gets a named CSM, who gets pooled, who gets digital only, and states what breaks at each line. Trigger whenever the user says "coverage model", "segmentation", "touch model", "CSM ratio", "how many accounts per CSM", "high touch low touch", "tech touch", "digital CS", "scaled CS", "pooled model", "we cannot cover the long tail", "do we need more headcount", or is designing or defending how a team is deployed across a book. It segments by what accounts need rather than only by what they pay, treats the ratio as an output rather than an input, names what each tier will not get, and tests the model against the accounts that actually churned. Use book-triage for working inside a coverage model that already exists, and renewal-forecast for what the model implies about the number.

1 Updated 5 days ago
CSPulse
AI & Automation Listed

customer-segmentation

Segments customer markets using firmographic, demographic, behavioral, needs-based, and willingness-to-pay criteria to target high-value customer clusters.

1 Updated 3 weeks ago
adamriofc