Cs Strategist
Design customer success org, segmentation, KPIs, and playbooks when a solo-founded SaaS needs to retain and expand accounts without hiring a full CS department first.
Overview
CS Strategist is an agent skill most often used in Grow (also Validate pricing, Operate support) that structures customer success org design, segmentation, KPIs, playbooks, and executive programs for scaling retention.
Install
npx skills add https://github.com/ncklrs/startup-os-skills --skill cs-strategistWhat is this skill?
- 8 structured CS domains from org design through customer journey mapping with CRITICAL/HIGH/MEDIUM-HIGH impact labels
- Covers segmentation (tech touch, low touch, high touch), coverage models, and resource allocation
- Metrics block: NRR, GRR, NPS, CSAT, CES, health scores, leading vs lagging indicators
- Playbook development: lifecycle, QBR, renewal, escalation, and automation triggers
- Executive stakeholder management, CS tech stack, and value realization / ROI frameworks
- 8 CS organization sections with explicit impact tiers (3 CRITICAL, 4 HIGH, 1 MEDIUM-HIGH in the outline)
Adoption & trust: 1 installs on skills.sh; 27 GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You have paying customers but no clear CS tiers, metrics, or playbooks, so renewals and expansions depend entirely on founder heroics.
Who is it for?
B2B or prosumer SaaS founders post-PMF who need a CS blueprint before scaling headcount or buying a CS platform.
Skip if: Pre-revenue ideation-only projects, pure consumer apps with no account relationships, or teams wanting executable CRM automation scripts instead of strategy.
When should I use this skill?
User asks for customer success strategy, CS org design, segmentation, NRR playbooks, QBR frameworks, or CS KPI definitions for a startup.
What do I get? / Deliverables
You get a prioritized CS operating model—segments, KPIs, playbooks, and tech choices—ready to implement in docs, hiring plans, or lightweight tooling.
- CS org and segmentation recommendations
- KPI and health-score priority list
- Lifecycle, renewal, and executive engagement playbook outlines
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Grow because CS strategy primarily compounds revenue through retention, health, and renewal—not initial product coding. Lifecycle subphase fits onboarding-to-renewal playbooks, NRR/GRR metrics, and journey mapping called out in the skill sections.
Where it fits
Map packaging tiers to tech-touch vs high-touch CS coverage before locking annual plans.
Draft onboarding and renewal playbooks with automation triggers tied to health scores.
Pick leading indicators and NRR/GRR definitions for a founder-operated metrics review.
How it compares
Strategy and playbook framework for founders—not a deployment skill for a specific CS product integration.
Common Questions / FAQ
Who is cs-strategist for?
Solo and small-team SaaS founders responsible for retention, renewals, and customer health who need enterprise-grade CS design without a VP of CS on staff.
When should I use cs-strategist?
In Grow when defining lifecycle and support motions; in Validate when pricing and packaging imply touch levels; in Operate when formalizing escalation and support infra.
Is cs-strategist safe to install?
It is procedural business guidance with no shell requirements; still review the Security Audits panel on this Prism page before installing any skill from the registry.
SKILL.md
READMESKILL.md - Cs Strategist
## 1. CS Organization Design (org) **Impact:** CRITICAL **Description:** CS team structure, roles and responsibilities, hiring profiles, career paths, and organizational models. Foundational decisions that determine scalability. ## 2. Customer Segmentation (segmentation) **Impact:** CRITICAL **Description:** Customer tiering strategies (tech touch, low touch, high touch), coverage models, resource allocation, and segment-specific approaches. ## 3. Success Metrics & KPIs (metrics) **Impact:** CRITICAL **Description:** NRR, GRR, NPS, CSAT, CES, health scores, leading vs lagging indicators, and metrics-driven CS operations. ## 4. Playbook Development (playbooks) **Impact:** HIGH **Description:** Lifecycle playbooks, QBR frameworks, renewal playbooks, escalation processes, and automation triggers. ## 5. Executive Stakeholder Management (executive) **Impact:** HIGH **Description:** C-level relationship building, Executive Business Reviews, multi-threading, champion development, and executive sponsor programs. ## 6. CS Technology Stack (technology) **Impact:** HIGH **Description:** CS platform selection, tool integration, data architecture, automation capabilities, and build vs buy decisions. ## 7. Value Realization (value) **Impact:** HIGH **Description:** Success planning, ROI frameworks, value demonstration, outcome tracking, and business case development. ## 8. Customer Journey Mapping (journey) **Impact:** MEDIUM-HIGH **Description:** Journey stage definition, touchpoint design, moments of truth, handoff processes, and experience optimization. --- title: CS Operations Excellence impact: HIGH tags: operations, cs-ops, process, enablement, reporting --- ## CS Operations Excellence **Impact: HIGH** CS Operations is the force multiplier for your CS organization. CS Ops ensures CSMs spend time with customers, not spreadsheets. Without strong operations, CS doesn't scale — it just burns out your best people. ### CS Operations Functions ``` ┌─────────────────────────────────────────────────────────────────┐ │ CS OPERATIONS │ ├─────────────────────────────────────────────────────────────────┤ │ │ │ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │ │ │ SYSTEMS │ │ DATA & │ │ PROCESS & │ │ │ │ & TOOLS │ │ ANALYTICS │ │ ENABLEMENT │ │ │ └──────┬───────┘ └──────┬───────┘ └──────┬───────┘ │ │ │ │ │ │ │ ▼ ▼ ▼ │ │ • CS Platform • Health scores • Playbooks │ │ • Integrations • Reporting • Training │ │ • Automation • Forecasting • Documentation │ │ • Tool admin • Analytics • QA & compliance │ │ │ └─────────────────────────────────────────────────────────────────┘ ``` ### CS Ops Responsibilities | Area | Responsibilities | Deliverables | |------|------------------|--------------| | **Systems** | CS platform admin, integrations, automation | Working systems | | **Data** | Health scores, data quality, pipeline | Accurate metrics | | **Analytics** | Reporting, dashboards, forecasting | Actionable insights | | **Process** | Playbooks, workflows, best practices | Documented processes | | **Enablement** | Training, documentation, certifications | Enabled team | ### When to Hire CS Ops | Signal | Description | |--------|-------------| | **5+ CSMs** | Enough scale to warrant dedicated ops | | **CSMs doing admin** | >20% of time on non-customer work | | **Data chaos** | Multiple spreadsheets, no source of truth | | **Inconsistent processes** | Every CSM does things differently | | **Tool under-utilization** | Expensive platform, minimal adoption |