mcpField
C
cs-strategist

cs-strategist

github.com/ncklrsMarketing & growth53143 installsUpdated 35w ago
Repository

About cs-strategist

A strategy skill for building and scaling customer success organizations. It covers team structure, customer segmentation, metrics, playbooks, and technology, emphasizing tailored coverage and measuring value delivery and revenue retention.

Key features

  1. 01Team structure and role design
  2. 02Customer segmentation and coverage models
  3. 03Metrics, health scores, and forecasting
  4. 04Lifecycle playbooks
  5. 05Technology stack and value realization

Use cases

  1. 01Plan a customer success team and responsibilities
  2. 02Allocate service by customer size and complexity
  3. 03Establish health metrics and retention forecasts
  4. 04Create customer journeys and value plans

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/ncklrs/startup-os-skills --skill cs-strategist

After installing, type/cs-strategistin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

rules/
_sections.md
cs-operations.md
executive-stakeholder-management.md
journey-mapping.md
metrics-kpis.md
org-team-structure.md
playbooks-lifecycle.md
renewal-expansion.md
segmentation-coverage-models.md
technology-stack.md
value-realization.md

Details

From the project README

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
StageCharacteristicsFocus
ReactiveSupport-driven, firefightingBasic retention
ProactiveHealth monitoring, early interventionChurn prevention
StrategicOutcome-focused, expansion-drivenNRR growth
TransformationalCustomer value embedded in productMarket 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
CategoryMetricsOwner
Business OutcomesNRR, GRR, Logo RetentionCS Leadership
Leading IndicatorsHealth Score, Adoption, NPSCS Operations
Activity MetricsTouchpoints, QBRs, Time-to-ValueCSMs
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
LayerFunctionExample Tools
Core PlatformCustomer 360, health scoresGainsight, ChurnZero, Totango
Data LayerProduct analytics, usageAmplitude, Pendo, Mixpanel
EngagementIn-app, email automationIntercom, Customer.io, Appcues
FeedbackSurveys, NPSDelighted, Wootric, Satismeter
IntelligenceChurn prediction, next best actionPlanhat, 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
PhaseDefinitionDeliverable
DefineAgree on success criteriaSuccess Plan
DeliverExecute implementation & onboardingGo-Live
DemonstrateProve value with metricsValue Report
DevelopExpand usage and outcomesGrowth Plan

Key Metrics Reference

MetricDefinitionGoodGreat
NRRNet Revenue Retention105%+120%+
GRRGross Revenue Retention90%+95%+
Logo RetentionCustomers retained85%+92%+
NPSNet Promoter Score30+50+
CSATCustomer Satisfaction4.0/54.5/5
CESCustomer Effort Score<3<2
Time to ValueDays to first outcome<30<14
Health ScoreComposite customer health70+ avg80+ avg

Coverage Model Decision Framework

FactorHigh TouchLow TouchTech Touch
ARR$100k+$15k-100k<$15k
ComplexityHighMediumLow
Strategic ValueHigh potentialStandardTransactional
Touch FrequencyWeekly-MonthlyMonthly-QuarterlyAutomated
CSM Ratio1:10-251:50-1001:500+
Cost to Serve15-25% of ARR5-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

Comments

Markdown supported