Skip to content
Skills Library
Sales & customer service · Planning

keep-segment

/keep-segment

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".

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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".

Triggers from the description

segment our customersdefine our CS tiershow should we allocate CS resourcesbuild a customer segmentation modelwho gets high-touch vs. digital
Original author description

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".

How it works

  1. Steps
  2. Delivery
Original SKILL.md headings · 146 lines, 916 words
SKILL.md preview
---
name: keep-segment
description: 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".
allowed-tools: Read, Bash, Glob, Grep, AskUserQuestion
version: 0.1.0
author: tonone-ai <hello@tonone.ai>
license: MIT
---

# 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     | $[Z]-$[Y] | Low-Medium          | ~30-40%       | ~10-20%  |
| 4    | Long Tail | <$[Z]     | Low                 | ~30-40%       | ~5-10%   |

Calibrate thresholds to actual ARR distribution. A company with $2M ARR has different thresholds than one at $20M.

### Step 2: Health Score Components

If no formal health score exists, define one:

| Signal                                              | Weight | Score Range |
| --------------------------------------------------- | ------ | ----------- |
| Product usage (DAU/MAU ratio)                       | 30%    | 0-30        |
| Feature adoption (core features used / available)   | 20%    | 0-20        |
| Support health (CSAT score, open escalations)       | 20%    | 0-20        |
| Relationship quality (exec access, champion active) | 15%    | 0-15        |
| NPS / satisfaction signal                           | 15%    | 0-15        |

**Total: 0-100**

| Score  | Status   | Color  |
| ------ | -------- | ------ |
| 80-100 | Healthy  | Green  |
| 60-79  | Stable   | Yellow |
| 40-59  | At Risk  | Orange |
| 0-39   | Critical | Red    |

### Step 3: Expansion Potential Score

Add an expansion lens (separate from health):

| Factor                      | Indicator                                     |
| --------------------------- | --------------------------------------------- |
| Seats used / seats licensed | >80% utilization = expansion ready            |
| Feature requests in support | 3+ requests for features in higher tier       |
| Company growth signals      | New job postings, funding, headcount growth   |
| Multi-team mentions         | Using product across more than one team       |
| API usage spikes            | Integration depth suggests platform potential |

Score: HIGH / MEDIUM / LOW per account.

### Step 4: Define CS Motion Per Tier

Map each tier to the appropriate CS motion and resource level:

```
## Tier 1 — Strategic (High-Touch)

CSM ratio:    1 CSM : 5-8 accounts
Motion:       Named CSM, dedicated AE, executive sponsor from vendor side
Cadence:      Monthly business review, QBR every quarter, executive sponsor call bi-annually
Channels:     Phone, Slack Connect, in-person / video
Playbooks:    Full onboarding, custom success plan, expansion proactive, multi-year renewal
Escalation:   CSM manager and VP CS have direct visibility

## Tier 2 — Growth (Mid-Touch)

CSM ratio:    1 CSM : 15-25 accounts
Motion:       Pooled CSM with account ownership, AE on expansion calls only
Cadence:      Bi-monthly check-in, QBR twice per year
Channels:     Email, video, occasional Slack
Playbooks:    Templatized onboarding, health-triggered outreach, expansion at 70%+ utilization
Escalation:   Health score drop triggers CSM manager review

## Tier 3 — Scale (Digital / Light Touch)

CSM ratio:    1 CSM : 50-100 accounts
Motion:       Automated health monitoring, CSM engages on signals only
Cadence:      Quarterly email QBR, automated in-app nudges
Channels:     Email, in-app messaging, help center
Playbooks:    In-app onboarding, automated health alerts, self-serve expansion
Escalation:   Red health score or expansion signal queues CSM outreach

## Tier 4 — Long Tail (Self-Serve)

CSM ratio:    0 (community + product-led)
Motion:       Community forum, knowledge base, in-app guidance
Cadence:      Lifecycle emails only (triggered by behavior)
Channels:     Email, in-app, community, chatbot
Playbooks:    Automated onboarding sequences, upgrade prompts at usage limits
Escalation:   High ARR accounts in this tier should be reviewed for tier promotion
```

### Step 5: Resource Allocation Model

```
## CS Resource Map

Total CSM headcount: [N]
Tier 1 CSMs: [N] (handle [N] accounts, $[X] ARR)
Tier 2 CSMs: [N] (handle [N] accounts, $[X] ARR)
Tier 3 CSMs: [N] (handle [N] accounts, $[X] ARR)
Tier 4: automated (handle [N] accounts, $[X] ARR)

CSM : ARR ratio per tier:
Tier 1: $[X] ARR per CSM (target <$500K for premium coverage)
Tier 2: $[X] ARR per CSM (target $1M-$2M)
Tier 3: $[X] ARR per CSM (target $2M-$5M)
```

### Step 6: Tier Promotion / Demotion Rules

Define when an account moves between tiers:

- Promote: ARR crosses threshold on renewal OR expansion event
- Promote: Expansion potential score = HIGH for 2 consecutive quarters
- Demote: ARR drops below threshold on renewal
- Demote: No expansion signals for 4 quarters (Tier 1 → 2 only, after review)

## Delivery

Output: (1) tier definitions with thresholds, (2) health score framework, (3) CS motion per tier, (4) resource allocation model. If output exceeds 40 lines, delegate to /atlas-report.

Versions

The database has no other skills named keep-segment.

Identical content appears in 3 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 5a5c71cf41f9 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90customer-segments
    Creates customer and user segment documents. Use when the user wants to 'segment customers,' 'customer segments,' 'user segments,' 'lifecycle segments,' or 'audience segmentation.
  • 100icp-builder
    Define ideal customer profiles and buyer personas with structured frameworks. Use when the user asks about ideal customer profile, ICP, buyer persona, target audience definition, customer segmentation, customer research, user interviews, or persona creation. Trigger phrases…
  • 90customer-success-manager
    Reduces churn and grows retention: onboarding, health scores, at-risk playbooks and expansion. Use when churn is high, for onboarding design, customer health tracking, or 'why are customers leaving'.
  • 100sales-account-segmentation
    Designs the account segmentation model between ICP and tier structure - which firmographic, technographic, intent and jobs-to-be-done signal layers define account fit, the weighted fit score calibrated from 12 months of closed-won deals, fit and readiness as separate axes,…
  • 100gtm-customers
    Build or update your customers bank for the GTM context in your repo: who already buys from you, which ICP segment each belongs to, which ones are your best customers, and which logos you have permission to show publicly. Reads customers from wherever they live (CRM, Notion or…
  • 100gtm-customers
    Build or update the Customers database in your Notion GTM Hub: who already buys from you, which ICP segment each belongs to, which ones you would clone, and which logos you have permission to show publicly. Takes a pasted list, a CSV, a CRM, or a description. Use for \"add my…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.