cs-strategist
Strategic Customer Success leadership guidance for CS org design, customer segmentation and tiering (tech touch, low touch, high touch), success metrics and KPIs (NRR, GRR, NPS, CSAT, CES), playbook development, executive stakeholder management, CS technology stack strategy, value realization frameworks, and customer journey mapping. Use when building CS teams, defining customer segments, designing playbooks, measuring success outcomes, or implementing CS platforms.
What this skill does
# CS Strategist
Strategic Customer Success expertise for building and scaling world-class CS organizations — from team structure and segmentation to playbooks, metrics, and technology.
## Philosophy
Customer Success is not support with a different name. It's a strategic function that drives **predictable revenue growth** through proactive customer value delivery.
The best CS organizations:
1. **Segment ruthlessly** — One-size-fits-all is no-size-fits-any
2. **Measure outcomes, not activities** — Calls made ≠ value delivered
3. **Scale before you hire** — Technology enables, humans differentiate
4. **Own the number** — CS owns Net Revenue Retention, full stop
## How This Skill Works
When invoked, apply the guidelines in `rules/` organized by:
- `org-*` — CS org design, team structure, roles, hiring
- `segmentation-*` — Customer tiering, coverage models, resource allocation
- `metrics-*` — KPIs, health scores, forecasting, reporting
- `playbooks-*` — Lifecycle playbooks, automation, QBRs
- `executive-*` — Stakeholder management, EBRs, C-level relationships
- `technology-*` — CS platforms, tool stack, integration
- `value-*` — Value realization, ROI frameworks, success plans
- `journey-*` — Customer journey mapping, touchpoints, moments of truth
## Core Frameworks
### The CS Maturity Model
| Stage | Characteristics | Focus |
|-------|-----------------|-------|
| **Reactive** | Support-driven, firefighting | Basic retention |
| **Proactive** | Health monitoring, early intervention | Churn prevention |
| **Strategic** | Outcome-focused, expansion-driven | NRR growth |
| **Transformational** | Customer value embedded in product | Market leadership |
### Customer Segmentation Tiers
```
┌─────────────────────────────────────────────────────────┐
│ HIGH TOUCH │
│ Enterprise / Strategic accounts ($100k+ ARR) │
│ Dedicated CSM, EBRs, custom success plans │
│ Ratio: 1:10-25 accounts │
├─────────────────────────────────────────────────────────┤
│ LOW TOUCH │
│ Mid-market accounts ($15k-$100k ARR) │
│ Pooled CSMs, scaled programs, office hours │
│ Ratio: 1:50-100 accounts │
├─────────────────────────────────────────────────────────┤
│ TECH TOUCH │
│ SMB / Self-serve accounts (<$15k ARR) │
│ Automated journeys, community, self-service │
│ Ratio: 1:500+ accounts (or no dedicated CSM) │
└─────────────────────────────────────────────────────────┘
```
### The CS Metrics Hierarchy
| Category | Metrics | Owner |
|----------|---------|-------|
| **Business Outcomes** | NRR, GRR, Logo Retention | CS Leadership |
| **Leading Indicators** | Health Score, Adoption, NPS | CS Operations |
| **Activity Metrics** | Touchpoints, QBRs, Time-to-Value | CSMs |
### Net Revenue Retention Formula
```
Starting MRR + Expansion - Contraction - Churn
NRR = ─────────────────────────────────────────────────── × 100
Starting MRR
Target NRR by segment:
- Enterprise: 115-130%+
- Mid-market: 105-115%
- SMB: 95-105%
```
### The CS Tech Stack
| Layer | Function | Example Tools |
|-------|----------|---------------|
| **Core Platform** | Customer 360, health scores | Gainsight, ChurnZero, Totango |
| **Data Layer** | Product analytics, usage | Amplitude, Pendo, Mixpanel |
| **Engagement** | In-app, email automation | Intercom, Customer.io, Appcues |
| **Feedback** | Surveys, NPS | Delighted, Wootric, Satismeter |
| **Intelligence** | Churn prediction, next best action | Planhat, Catalyst |
### Customer Journey Stages
```
PRE-SALES → ONBOARDING → ADOPTION → VALUE → EXPANSION → ADVOCACY
↓ ↓ ↓ ↓ ↓ ↓
Handoff Time-to- Feature Outcome Expansion Reference
Quality Value Adoption Achieved Opportunity Customer
```
### The Value Realization Framework
| Phase | Definition | Deliverable |
|-------|------------|-------------|
| **Define** | Agree on success criteria | Success Plan |
| **Deliver** | Execute implementation & onboarding | Go-Live |
| **Demonstrate** | Prove value with metrics | Value Report |
| **Develop** | Expand usage and outcomes | Growth Plan |
## Key Metrics Reference
| Metric | Definition | Good | Great |
|--------|------------|------|-------|
| **NRR** | Net Revenue Retention | 105%+ | 120%+ |
| **GRR** | Gross Revenue Retention | 90%+ | 95%+ |
| **Logo Retention** | Customers retained | 85%+ | 92%+ |
| **NPS** | Net Promoter Score | 30+ | 50+ |
| **CSAT** | Customer Satisfaction | 4.0/5 | 4.5/5 |
| **CES** | Customer Effort Score | <3 | <2 |
| **Time to Value** | Days to first outcome | <30 | <14 |
| **Health Score** | Composite customer health | 70+ avg | 80+ avg |
## Coverage Model Decision Framework
| Factor | High Touch | Low Touch | Tech Touch |
|--------|------------|-----------|------------|
| **ARR** | $100k+ | $15k-100k | <$15k |
| **Complexity** | High | Medium | Low |
| **Strategic Value** | High potential | Standard | Transactional |
| **Touch Frequency** | Weekly-Monthly | Monthly-Quarterly | Automated |
| **CSM Ratio** | 1:10-25 | 1:50-100 | 1:500+ |
| **Cost to Serve** | 15-25% of ARR | 5-10% of ARR | <3% of ARR |
## Anti-Patterns
- **Measuring activities over outcomes** — Calls logged ≠ customers retained
- **One playbook for all segments** — Tech touch playbooks for enterprise fail
- **CS as support escalation** — Reactive mode kills proactive capacity
- **Health scores without action** — Red accounts need intervention, not dashboards
- **Siloed CS data** — CS platform not integrated with CRM/Product
- **CSM as single thread** — Champion leaves, relationship collapses
- **QBRs as PowerPoint theater** — Value delivery, not presentation
- **Ignoring tech touch** — 80% of customers, 20% of attention
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.