本文へ移動
cccskills
無料GitHub で公開

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.

インストール方法を見る

含まれるファイル(12)

  • SKILL.md7.0 KB
  • rules/_sections.md1.6 KB
  • rules/cs-operations.md10.7 KB
  • rules/executive-stakeholder-management.md12.3 KB
  • rules/journey-mapping.md14.9 KB
  • rules/metrics-kpis.md13.2 KB
  • rules/org-team-structure.md7.7 KB
  • rules/playbooks-lifecycle.md10.7 KB
  • rules/renewal-expansion.md11.2 KB
  • rules/segmentation-coverage-models.md11.2 KB
  • rules/technology-stack.md12.6 KB
  • rules/value-realization.md18.0 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Expert full-cycle enterprise sales strategist for B2B SaaS. Use when planning sales strategy, pipeline management, deal progression, account planning, competitive displacement, or territory optimization. Covers multi-threading, executive engagement, champion development, buying committee navigation, and complex deal orchestration. Use for enterprise selling, account expansion, land-and-expand, and quota attainment.

日本語の概要は準備中です。原文の説明を表示しています。

ncklrs/startup-os-skills522026年2月27日 更新

adr

無料

Expert Architecture Decision Record (ADR) creation and lifecycle management based on Olaf Zimmermann's methodology. Use when creating ADRs, reviewing architectural decisions, evaluating decision readiness, writing MADR templates, assessing decision quality, or managing ADR logs. Covers the full lifecycle from readiness (START criteria) through creation, MADR formatting, completion (ECADR criteria), and ongoing maintenance.

日本語の概要は準備中です。原文の説明を表示しています。

ncklrs/startup-os-skills522026年2月27日 更新

Hand off code review to OpenAI Codex CLI. Use when asked to "review code with codex", "codex review", "get a second opinion on code", "review my changes", "review this PR", or when you want AI-powered code review from a different model perspective.

日本語の概要は準備中です。原文の説明を表示しています。

ncklrs/startup-os-skills522026年2月27日 更新

Expert community-led growth and community management guidance. Use when building developer communities, Discord/Slack communities, online communities, managing community platforms, designing member onboarding, creating engagement programs, running ambassador programs, measuring community health, setting up moderation systems, or implementing DevRel strategies. Use for community-led growth, member activation, user-generated content programs, and community governance.

日本語の概要は準備中です。原文の説明を表示しています。

ncklrs/startup-os-skills522026年2月27日 更新

Expert competitive intelligence and strategy guidance for B2B/SaaS companies. Use when conducting competitive research, creating battlecards, analyzing win/loss data, building market landscape maps, positioning against alternatives, handling competitive objections, writing comparison pages, or developing sales enablement for competitive situations. Use for competitive monitoring, feature comparisons, and market intelligence gathering.

日本語の概要は準備中です。原文の説明を表示しています。

ncklrs/startup-os-skills522026年2月27日 更新

Master orchestrator that chains all Remotion video creation skills together in a single automated pipeline. Takes a creative brief and produces a complete, production-ready Remotion video project. Use when starting a new video from scratch, when asked to "create a video", "make a video", "build a complete video", or "video from idea to code".

日本語の概要は準備中です。原文の説明を表示しています。

ncklrs/startup-os-skills522026年2月27日 更新

ncklrs のスキルをすべて見る

このスキルの問題を報告する