Cs Strategist

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

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

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

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

Key Metrics Reference

Coverage Model Decision Framework

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

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.

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

When to Hire CS Ops

CS Ops Hiring Profile

Good CS Operations

✓ Single source of truth
  → CS platform is authoritative
  → No competing spreadsheets

✓ Automated data flow
  → Product usage syncs automatically
  → Health scores update daily

✓ Documented playbooks
  → Searchable, up-to-date
  → New CSM productive in 30 days

✓ Self-service reporting
  → CSMs can pull their own data
  → Don't need ops for every question

✓ Proactive insights
  → Ops surfaces trends before asked
  → "Here's what the data shows"

✓ Change management
  → New processes rolled out with training
  → Feedback incorporated

Bad CS Operations

✗ Tool administrator only
  → Updates fields, doesn't drive strategy
  → Reactive button pusher

✗ Data silos
  → 5 different spreadsheets
  → No one knows what's true

✗ Manual everything
  → Health scores calculated in Excel
  → Stale by the time it's done

✗ Undocumented processes
  → "Ask Sarah, she knows"
  → Knowledge locked in heads

✗ Report factory
  → Endless requests, no insights
  → Reports created, not used

✗ No feedback loop
  → Processes created without input
  → Team doesn't follow them

CS Ops Metrics

Reporting Framework

Executive Dashboard (Weekly/Monthly)

EXECUTIVE CS DASHBOARD
──────────────────────

RETENTION (Trailing 12 months)
┌─────────────────────────────────────────┐
│ GRR: 92% ▲     NRR: 108% ▲    NPS: 38  │
└─────────────────────────────────────────┘

PORTFOLIO HEALTH
┌─────────────────────────────────────────┐
│ Healthy: 65% │ Stable: 20% │ At-Risk: 15%│
└─────────────────────────────────────────┘

THIS QUARTER
┌─────────────────────────────────────────┐
│ Renewals Due: $2.1M                      │
│ Forecast: $1.95M (93%)                   │
│ At-Risk: $180k (4 accounts)              │
└─────────────────────────────────────────┘

CSM Dashboard (Daily)

MY PORTFOLIO
────────────

TODAY'S PRIORITIES
□ At-risk call: Acme Corp (health: 35)
□ QBR prep: BigCo (Thursday)
□ Renewal due: SmallCo (14 days)

PORTFOLIO SUMMARY
┌─────────────────────────────────────────┐
│ Accounts: 25  │ ARR: $1.2M              │
│ Healthy: 18   │ At-risk: 3              │
│ Renewals (90d): 5 ($340k)               │
└─────────────────────────────────────────┘

TASKS OVERDUE
□ Follow up: Client X (2 days)
□ Success plan: Client Y (5 days)

Automation Opportunities

Enablement Program

New CSM Onboarding (8 weeks)

Ongoing Enablement

Process Documentation Standards

PLAYBOOK DOCUMENTATION TEMPLATE
───────────────────────────────

OVERVIEW
• Purpose: [Why this playbook exists]
• Owner: [Who maintains it]
• Last updated: [Date]

TRIGGER
• What initiates this playbook?

STEPS
1. Step name (Timeline)
   • Action details
   • Channel
   • Templates

2. Step name (Timeline)
   ...

EXIT CRITERIA
• How do we know it's complete?

METRICS
• How do we measure success?

ESCALATION
• When to escalate
• Who to escalate to

Quality Assurance

CS Ops Tech Stack

Building CS Ops Function

PHASE 1: Foundation (Month 1-2)
□ Audit current processes
□ Document as-is state
□ Identify quick wins
□ Establish data governance

PHASE 2: Systems (Month 2-4)
□ CS platform implementation
□ Key integrations
□ Health score v1
□ Basic automation

PHASE 3: Enablement (Month 4-6)
□ Playbook documentation
□ Training program
□ Reporting suite
□ QA processes

PHASE 4: Optimization (Month 6+)
□ Advanced automation
□ Predictive analytics
□ Continuous improvement
□ Scale programs

Anti-Patterns

• Ops as admin only — Should drive strategy, not just update fields
• Manual data work — If it can be automated, automate it
• Undocumented processes — Tribal knowledge doesn't scale
• Report factory — Creating reports no one uses
• No CSM input — Building processes without user feedback
• Tool as solution — Tools enable, but don't create good CS
• Perfection paralysis — Ship 80%, iterate on the rest
• Siloed ops — Must connect to sales ops, marketing ops

Executive Stakeholder Management

Impact: HIGH

Deals are won and lost at the executive level. The same is true for renewals and expansions. If your only relationship is with an end user, you're one champion departure away from churn. Executive relationships are insurance, expansion fuel, and competitive moats.

The Multi-Threading Imperative

SINGLE-THREADED (RISKY)
┌─────────────────────────────────────┐
│  Your Company                       │
│       │                             │
│      CSM                            │
│       │                             │
│       ▼                             │
│   Champion ────────────────┐        │
│                            │        │
│  Customer Company          │        │
└────────────────────────────┼────────┘
                             │
                   Champion leaves = Churn risk

MULTI-THREADED (RESILIENT)
┌─────────────────────────────────────┐
│  Your Company                       │
│    │     │      │                   │
│   CSM   AE     Exec Sponsor         │
│    │     │      │                   │
│    ▼     ▼      ▼                   │
│  User  Manager  VP/C-level          │
│                            │        │
│  Customer Company          │        │
└────────────────────────────┼────────┘
                             │
              Any single loss = Continuity

Stakeholder Mapping

Stakeholder Map Template

┌─────────────────────────────────────────────────────────────────┐
│                    STAKEHOLDER MAP                               │
│                    Account: [Name]                               │
├─────────────────────────────────────────────────────────────────┤
│                                                                  │
│  EXECUTIVE LEVEL                                                 │
│  ┌──────────────────────────────────────────────────────────┐   │
│  │ CEO: [Name]                  CFO: [Name]                 │   │
│  │ Relationship: ○○○○●          Relationship: ○○●○○         │   │
│  │ Engagement: Annual           Engagement: EBR             │   │
│  └──────────────────────────────────────────────────────────┘   │
│                                                                  │
│  VP / DIRECTOR LEVEL                                             │
│  ┌──────────────────────────────────────────────────────────┐   │
│  │ VP Ops: [Name] ★ CHAMPION    Director IT: [Name]         │   │
│  │ Relationship: ●●●●●          Relationship: ○○○●●         │   │
│  │ Engagement: Weekly           Engagement: Monthly         │   │
│  └──────────────────────────────────────────────────────────┘   │
│                                                                  │
│  MANAGER / USER LEVEL                                            │
│  ┌──────────────────────────────────────────────────────────┐   │
│  │ Manager: [Name]              Power User: [Name]          │   │
│  │ Relationship: ●●●○○          Relationship: ●●●●○         │   │
│  │ Engagement: Weekly           Engagement: Bi-weekly       │   │
│  └──────────────────────────────────────────────────────────┘   │
│                                                                  │
│  Legend: ★ Champion  ⚠ Risk  ✓ Engaged  ○ Low  ● High          │
└─────────────────────────────────────────────────────────────────┘

Executive Business Review (EBR)

Purpose: Strategic alignment with C-level, demonstrate value, secure commitment

Frequency: Semi-annual for strategic accounts, annual for enterprise

Attendees:

• Your side: CSM, CS Leader, Executive Sponsor, AE (optional)
• Their side: C-level/VP, Champion, Key stakeholders

EBR Agenda (60-90 minutes)

1. EXECUTIVE ALIGNMENT (15 min)
   → Their strategic priorities this year
   → Market/competitive landscape changes
   → Our understanding of their goals

2. PARTNERSHIP SUMMARY (10 min)
   → Journey together
   → Key milestones achieved
   → Team engagement highlights

3. VALUE DELIVERED (20 min)
   → Business outcomes achieved
   → ROI metrics
   → Success stories
   → Comparison to original business case

4. ADOPTION & USAGE INSIGHTS (10 min)
   → Usage trends
   → Benchmark vs peers
   → Optimization opportunities

5. STRATEGIC ROADMAP (15 min)
   → Our product direction
   → Alignment with their needs
   → Co-innovation opportunities

6. FORWARD PLAN (15 min)
   → Partnership goals next 6-12 months
   → Expansion opportunities
   → Success milestones
   → Commitment discussions

7. NEXT STEPS (5 min)
   → Action items
   → Next EBR scheduling

EBR vs QBR

Champion Development

Identifying Potential Champions

Champion Enablement

INTERNAL CHAMPION ENABLEMENT:
→ Arm with success metrics they can share
→ Provide executive-ready materials
→ Help them build internal business cases
→ Give them "insider" roadmap access
→ Make them look good to their leadership

EXTERNAL CHAMPION ENABLEMENT:
→ Reference customer opportunities
→ Speaking engagements
→ Case study participation
→ Advisory board membership
→ Exclusive events access

Executive Sponsor Program

Executive Sponsor Responsibilities:

□ Attend EBRs for assigned accounts
□ Available for escalations within 24 hours
□ Quarterly check-in with CS on account health
□ Strategic relationship building at conferences
□ Executive-to-executive references

Good Stakeholder Management

✓ Multi-threaded from day one
  → Identify 3+ contacts at onboarding
  → Don't wait until champion leaves

✓ Regular executive touchpoints
  → At least annual for enterprise
  → Not just when renewing

✓ Value articulation at their level
  → Executives care about business outcomes
  → Not feature adoption metrics

✓ Champion protection
  → Make champions successful internally
  → Their success = your success

✓ Blocker conversion
  → Understand their concerns
  → Address directly, don't avoid

✓ Documented relationships
  → Stakeholder map in CRM
  → Updated regularly

Bad Stakeholder Management

✗ Single-threaded for years
  → "We have a great relationship with Sarah"
  → Sarah leaves, account at risk

✗ Only engage at renewal
  → Radio silence for 11 months
  → Transactional, not strategic

✗ Feature-focused with executives
  → "We released 12 new features!"
  → They don't care

✗ Champion taken for granted
  → No investment in their success
  → They become detractors

✗ Avoiding blockers
  → Hope they go away
  → They don't, they get louder

✗ No executive-to-executive
  → CSM is only relationship
  → Limited escalation paths

Champion Departure Playbook

Trigger: Champion announces departure or leaves

Knowledge to capture before departure:

□ Open initiatives/projects
□ Key success metrics
□ Political landscape
□ Upcoming decisions
□ Potential replacement
□ Their assessment of relationship
□ Introduction to other stakeholders
□ Permission to stay in touch (reference potential)

Stakeholder Engagement Cadence

Relationship Strength Scoring

Anti-Patterns

• Single-threading — One relationship is not a strategy
• Renewal-only engagement — Transactional relationship
• Feature pitching to executives — Wrong level of conversation
• Ignoring blockers — They don't disappear
• Champion as crutch — Over-reliance on one person
• No executive sponsor program — Missed strategic leverage
• Stakeholder map as one-time exercise — Must be living document
• Assuming champion loyalty — They're loyal to their career, not you

Customer Journey Mapping

Impact: MEDIUM-HIGH

The customer journey is every interaction a customer has with your company — from first awareness to loyal advocacy. Mapping this journey reveals friction points, gaps, and opportunities to create differentiated experiences.

The Customer Journey Framework

┌─────────────────────────────────────────────────────────────────┐
│                    CUSTOMER JOURNEY                              │
├─────────────────────────────────────────────────────────────────┤
│                                                                  │
│  PRE-SALES    SALES      ONBOARD    ADOPT    RENEW    ADVOCATE  │
│      │          │           │         │        │         │      │
│      ▼          ▼           ▼         ▼        ▼         ▼      │
│   Aware     Evaluate     Welcome   Engage   Commit   Champion   │
│   →→→→→→→→→→→→→→→→→→→→→→→→→→→→→→→→→→→→→→→→→→→→→→→→→→→→→→→→→   │
│                                                                  │
│   Marketing   Sales       CS        CS       CS       CS/Mktg   │
│                                                                  │
└─────────────────────────────────────────────────────────────────┘

Journey Stages Detailed

Journey Map Template

┌─────────────────────────────────────────────────────────────────┐
│                      JOURNEY MAP                                 │
│                  Stage: [ONBOARDING]                            │
├─────────────────────────────────────────────────────────────────┤
│                                                                  │
│ CUSTOMER GOALS                                                   │
│ ──────────────                                                  │
│ • Get set up quickly                                            │
│ • Understand how to use key features                            │
│ • See initial value                                             │
│                                                                  │
│ TOUCHPOINTS                                                      │
│ ───────────                                                     │
│ Day 1: Welcome email → Kickoff call → Access provisioning       │
│ Day 3: Training session → In-app guidance                       │
│ Day 7: Check-in call → First value milestone                    │
│ Day 14: QBR prep → Adoption review                              │
│ Day 30: Onboarding complete → Transition to BAU                 │
│                                                                  │
│ EMOTIONS                                                         │
│ ────────                                                        │
│ 😰 → 😐 → 🙂 → 😊 → 😄                                            │
│ Anxious  Neutral  Confident  Satisfied  Excited                 │
│                                                                  │
│ FRICTION POINTS                                                  │
│ ───────────────                                                 │
│ • Day 1: Waiting for access (2+ hour delay)                     │
│ • Day 3: Training too generic, not role-specific                │
│ • Day 7: Unclear what "success" looks like                      │
│                                                                  │
│ OPPORTUNITIES                                                    │
│ ─────────────                                                   │
│ • Automate access provisioning                                  │
│ • Role-based training paths                                     │
│ • Clear success milestones in-app                               │
│                                                                  │
│ METRICS                                                          │
│ ───────                                                         │
│ • Time to first login: 24h → Target: 4h                         │
│ • Training completion: 60% → Target: 85%                        │
│ • Day 7 activation: 45% → Target: 70%                           │
│                                                                  │
└─────────────────────────────────────────────────────────────────┘

Moments of Truth

Moments of Truth are critical interactions that disproportionately impact customer perception and loyalty.

Handoff Management

Sales-to-CS Handoff

PRE-CLOSE HANDOFF (Best Practice)
┌─────────────────────────────────────────────────────────────────┐
│                                                                  │
│   SALES                              CS                          │
│     │                                 │                          │
│     │ ← Internal intro (T-14 days)    │                          │
│     │ ← CSM joins late-stage calls    │                          │
│     ├───────────────────────────────→ │ CSM attends close call   │
│     │                                 │                          │
│   Close                               │                          │
│     │                                 │                          │
│     └─────────────────────────────────┤                          │
│              Handoff meeting          │                          │
│              (within 48 hours)        │                          │
│                                       │                          │
│                                       ▼                          │
│                                    Customer kickoff              │
│                                                                  │
└─────────────────────────────────────────────────────────────────┘

POST-CLOSE HANDOFF (Common but worse)
┌─────────────────────────────────────────────────────────────────┐
│                                                                  │
│   SALES                              CS                          │
│     │                                 │                          │
│   Close                               │                          │
│     │                                 │                          │
│     └─────────────────────────────────┤                          │
│              Handoff (1-2 weeks later)│                          │
│              "Here's the customer"    │                          │
│                                       │                          │
│              ← Customer frustrated    │                          │
│              (repeated questions)     │                          │
│                                       │                          │
└─────────────────────────────────────────────────────────────────┘

Handoff Checklist

SALES → CS HANDOFF DOCUMENT
──────────────────────────

DEAL CONTEXT
□ Why did they buy? [Business pain]
□ Why now? [Trigger event]
□ Why us? [Competitive differentiation]
□ Decision criteria [What mattered most]

STAKEHOLDERS
□ Executive sponsor: [Name, role, contact]
□ Champion: [Name, role, contact]
□ Technical owner: [Name, role, contact]
□ End users: [Number, roles]

SUCCESS CRITERIA
□ Primary objective: [Outcome]
□ How they'll measure success: [Metric]
□ Timeline expectations: [Dates]

RISKS & CONCERNS
□ Known risks: [Issues surfaced in sales]
□ Competitor mentions: [Who else considered]
□ Objections raised: [Concerns addressed]

COMMERCIAL
□ Contract value: $X ARR
□ Contract terms: [Length, special terms]
□ Expansion potential: [Opportunities mentioned]
□ Renewal date: [Date]

Journey Friction Analysis

Good Journey Design

✓ Proactive communication
  → Customer knows what's next
  → No surprises

✓ Seamless handoffs
  → No repeated questions
  → Context transfers with customer

✓ Right channel, right time
  → Email for async, call for complex
  → In-app for contextual

✓ Consistent experience
  → Every CSM follows same playbook
  → Customer tier drives experience

✓ Feedback loops
  → Capture experience at each stage
  → Act on insights

✓ Continuous improvement
  → Journey map reviewed quarterly
  → Friction points addressed

Bad Journey Design

✗ Reactive touchpoints
  → Only contact when customer reaches out
  → No proactive value

✗ Broken handoffs
  → "Who's your CSM?" at month 3
  → Customer has to re-explain everything

✗ One-size-fits-all
  → Enterprise gets same journey as SMB
  → Inappropriate for complexity

✗ Channel mismatch
  → Complex issues over email
  → Simple questions require calls

✗ No journey ownership
  → "That's sales' job" / "That's support's job"
  → Customer falls through cracks

✗ Static journey
  → Designed once, never updated
  → Doesn't reflect reality

Journey Metrics

Cross-Functional Journey Ownership

Journey Mapping Workshop

Participants: CS, Sales, Marketing, Product, Support Duration: Half-day Output: Journey map with prioritized improvements

AGENDA:

1. CURRENT STATE (90 min)
   → Walk through each stage
   → Document touchpoints
   → Identify emotions
   → Note friction points

2. BREAK (15 min)

3. PRIORITIZATION (60 min)
   → Impact vs effort matrix
   → Quick wins identified
   → Long-term improvements

4. ACTION PLANNING (45 min)
   → Assign owners
   → Set timelines
   → Define success metrics

5. NEXT STEPS (15 min)
   → Review cadence
   → Communication plan

Anti-Patterns

• Siloed stages — No one owns the full journey
• No customer input — Journey designed without customer feedback
• One-time exercise — Journey map created and forgotten
• Over-engineering — 50 touchpoints per stage, impossible to execute
• No metrics — Can't measure if journey is working
• Ignoring digital journey — Only mapping human touchpoints
• Same journey for all — Not segment-appropriate
• Handoff amnesia — Context lost at every transition

Success Metrics & KPIs

Impact: CRITICAL

You can't manage what you don't measure. But measuring the wrong things — or too many things — is worse than measuring nothing. CS metrics should drive action, not just dashboards.

The Metrics Hierarchy

┌─────────────────────────────────────────────────────────────────┐
│                    BUSINESS OUTCOMES                             │
│  ════════════════════════════════════════════════════════════   │
│  NRR, GRR, Logo Retention, Revenue Churn                        │
│  → Lagging indicators, board-level, owned by CS leadership      │
├─────────────────────────────────────────────────────────────────┤
│                   LEADING INDICATORS                             │
│  ════════════════════════════════════════════════════════════   │
│  Health Score, Adoption Rate, NPS, Time-to-Value                │
│  → Predictive, operational, owned by CS ops                     │
├─────────────────────────────────────────────────────────────────┤
│                    ACTIVITY METRICS                              │
│  ════════════════════════════════════════════════════════════   │
│  Touchpoints, QBRs completed, Success plans created             │
│  → Input metrics, individual, owned by CSMs                     │
└─────────────────────────────────────────────────────────────────┘

Core CS Metrics

Net Revenue Retention (NRR)

         Starting MRR + Expansion - Contraction - Churn
NRR = ──────────────────────────────────────────────────── × 100
                        Starting MRR

Example:
  Starting MRR: $1,000,000
  Expansion: $150,000
  Contraction: $30,000
  Churn: $50,000

  NRR = ($1,000,000 + $150,000 - $30,000 - $50,000) / $1,000,000
  NRR = $1,070,000 / $1,000,000 = 107%

Gross Revenue Retention (GRR)

         Starting MRR - Contraction - Churn
GRR = ────────────────────────────────────── × 100
                 Starting MRR

Example:
  Starting MRR: $1,000,000
  Contraction: $30,000
  Churn: $50,000

  GRR = ($1,000,000 - $30,000 - $50,000) / $1,000,000
  GRR = $920,000 / $1,000,000 = 92%

Customer Health Score

Health Score = Σ (Component × Weight)

Typical components:
┌─────────────────────────────────────────────────────────┐
│ Component          │ Weight │ Inputs                    │
├────────────────────┼────────┼───────────────────────────┤
│ Product Usage      │ 30%    │ DAU/MAU, feature adoption │
│ Engagement         │ 25%    │ Logins, sessions, depth   │
│ Relationship       │ 20%    │ NPS, CSM sentiment        │
│ Support            │ 15%    │ Tickets, resolution, CSAT │
│ Growth Signals     │ 10%    │ User adds, usage growth   │
└─────────────────────────────────────────────────────────┘

Satisfaction Metrics

Net Promoter Score (NPS)

"How likely are you to recommend [product] to a colleague?"
Scale: 0-10

Promoters (9-10) - Detractors (0-6) = NPS
                    Total Responses

Example:
  100 responses: 50 promoters, 30 passives, 20 detractors
  NPS = (50 - 20) / 100 = 30

Customer Satisfaction Score (CSAT)

"How satisfied are you with [interaction/product]?"
Scale: 1-5 or 1-7

CSAT = (Satisfied responses / Total responses) × 100
"Satisfied" typically = 4-5 on 5-point scale

Customer Effort Score (CES)

"How easy was it to [complete task/resolve issue]?"
Scale: 1-7 (1 = very easy, 7 = very difficult)

Lower is better.

Good Metrics Practice

✓ Focus on outcomes, not activities
  → NRR matters, calls logged doesn't
  → Health score matters, touchpoints don't (directly)

✓ Lead with leading indicators
  → Health score predicts churn
  → Don't wait for churn to measure retention

✓ Segment metrics
  → Enterprise NRR vs SMB NRR
  → Different benchmarks, different targets

✓ Tie to compensation
  → What gets measured gets managed
  → What gets compensated gets prioritized

✓ Automate collection
  → Manual metrics don't get updated
  → Integrate product, CRM, CS platform

✓ Review regularly
  → Weekly: health scores, at-risk accounts
  → Monthly: retention forecasts, segment performance
  → Quarterly: NRR/GRR trends, NPS analysis

Bad Metrics Practice

✗ Activity metrics as primary
  → "CSMs logged 500 calls this month"
  → Means nothing about customer outcomes

✗ Vanity metrics
  → "95% of customers attended onboarding"
  → But only 40% activated

✗ Too many metrics
  → 50 KPIs means nothing is a priority
  → Focus on 5-7 that matter

✗ Manual data
  → Spreadsheet health scores
  → Always stale, inconsistent

✗ No segmentation
  → "Our NRR is 95%"
  → But SMB is 80% and Enterprise is 115%

✗ Lagging-only
  → Only know churn after it happens
  → No early warning system

Metrics by Role

Metrics Dashboard Template

┌─────────────────────────────────────────────────────────────────┐
│                    CS EXECUTIVE DASHBOARD                        │
├─────────────────────────────────────────────────────────────────┤
│ BUSINESS OUTCOMES (Trailing 12 months)                          │
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐│
│ │ NRR: 112%   │ │ GRR: 93%    │ │ Logo: 89%   │ │ NPS: 42     ││
│ │ ▲ +3% QoQ   │ │ ▲ +1% QoQ   │ │ ═ flat      │ │ ▲ +5 QoQ    ││
│ └─────────────┘ └─────────────┘ └─────────────┘ └─────────────┘│
├─────────────────────────────────────────────────────────────────┤
│ LEADING INDICATORS                                               │
│ Health Distribution:    │ At-Risk Accounts:                      │
│ ████████████ Healthy 65% │ 12 accounts ($450k ARR)               │
│ ██████ Stable 20%       │ ▼ -3 from last month                   │
│ ███ At-risk 10%         │                                        │
│ █ Critical 5%           │                                        │
├─────────────────────────────────────────────────────────────────┤
│ THIS QUARTER                                                     │
│ Renewals due: $2.1M     │ Forecast: $1.95M (93%)                │
│ Expansion pipeline: $400k │ Expected close: $280k                │
└─────────────────────────────────────────────────────────────────┘

Metric Calculation Frequencies

Building a Health Score

Step 1: Define Components

Product Usage (30%)
├── Login frequency (10%)
├── Feature breadth (10%)
└── Usage depth (10%)

Engagement (25%)
├── Sessions per user (10%)
├── Time in product (10%)
└── Active users % (5%)

Relationship (20%)
├── NPS score (10%)
├── CSM sentiment (5%)
└── Executive engagement (5%)

Support (15%)
├── Ticket volume trend (5%)
├── Ticket sentiment (5%)
└── Resolution satisfaction (5%)

Growth (10%)
├── User growth (5%)
└── Usage growth (5%)

Step 2: Define Scoring

For each component, score 0-100:

Login frequency example:
  0-1 logins/month: 20
  2-4 logins/month: 40
  5-10 logins/month: 60
  11-20 logins/month: 80
  20+ logins/month: 100

Step 3: Validate Correlation

Test health score against actual churn:
  → Churned customers should have had low scores
  → Retained customers should have had high scores
  → Adjust weights if correlation is weak

Forecasting Renewals

Renewal Forecast = Σ (Renewal ARR × Probability)

Probability by health:
  Health 80-100: 95% probability
  Health 60-79: 85% probability
  Health 40-59: 60% probability
  Health 20-39: 30% probability
  Health 0-19: 10% probability

Example:
  Customer A: $100k ARR, Health 85 → $95k expected
  Customer B: $50k ARR, Health 45 → $30k expected
  Customer C: $75k ARR, Health 25 → $22.5k expected

  Total due: $225k
  Forecast: $147.5k (65.5%)

Anti-Patterns

• Measuring activities, not outcomes — Calls logged ≠ value delivered
• Ignoring leading indicators — Churn is lagging, health is leading
• One metric to rule them all — NRR alone misses important signals
• No segmentation — Aggregate metrics hide segment problems
• Manual data collection — Ensures stale, unreliable metrics
• Vanity metrics in board decks — "Logos retained" when revenue churning
• No action thresholds — Health score exists but no one acts on red
• Inconsistent definitions — Every team calculates NRR differently

CS Organization Design & Team Structure

Impact: CRITICAL

Your CS org structure determines your ceiling for scale. The wrong structure creates bottlenecks, burnout, and missed revenue. The right structure enables predictable growth.

CS Org Evolution Stages

STAGE 1: Founding (0-20 customers)
├── Founder/CEO owns relationships
├── No dedicated CS
└── "Everyone does CS"

STAGE 2: First Hire (20-100 customers)
├── First CSM (generalist)
├── Handles everything
└── Reactive, learning mode

STAGE 3: Specialization (100-500 customers)
├── CSMs by segment/vertical
├── CS Ops/Enablement
└── Onboarding specialist

STAGE 4: Scale (500+ customers)
├── CS Leadership (VP/Director)
├── Segmented teams (Enterprise/MM/SMB)
├── CS Operations team
├── Dedicated Renewals
└── Customer Marketing

Core CS Roles

Team Structures

By Segment (Most Common)

VP Customer Success
├── Director, Enterprise CS
│   └── Enterprise CSMs (1:15 ratio)
├── Director, Mid-Market CS
│   └── Mid-Market CSMs (1:50 ratio)
├── Manager, Digital CS
│   └── Digital CSMs (1:300+ ratio)
└── CS Operations

By Function

VP Customer Success
├── Onboarding Team
│   └── Implementation Specialists
├── Adoption Team
│   └── CSMs (all segments)
├── Renewals Team
│   └── Renewal Managers
└── CS Operations

By Industry/Vertical

VP Customer Success
├── Healthcare CS Team
├── Financial Services CS Team
├── Technology CS Team
└── CS Operations

CSM-to-Account Ratios

Good Org Design

✓ Segment-appropriate coverage
  → Enterprise gets dedicated CSMs
  → SMB gets efficient tech touch
  → Not the same playbook scaled

✓ Clear ownership and accountability
  → Every account has an owner
  → Every metric has an owner
  → No orphan accounts

✓ Career progression paths
  → CSM → Senior → Lead → Manager
  → Specialization paths (Enterprise, Ops, Enablement)
  → Prevents turnover

✓ Right span of control
  → Managers: 5-8 direct reports
  → Directors: 2-4 managers
  → Allows coaching time

✓ Integrated with GTM
  → Clear sales-to-CS handoff
  → CS input to product
  → Renewal/expansion coordination

Bad Org Design

✗ One team for all segments
  → Enterprise CSMs managing 200 SMB accounts
  → Impossible to prioritize
  → Burns out your best people

✗ No CS Operations
  → CSMs doing admin, reporting, tool management
  → Expensive resources on low-value work

✗ CSM does everything
  → Sales, implementation, support, renewals
  → Jack of all trades, master of none
  → Impossible to scale

✗ Flat hierarchy
  → 20 CSMs reporting to one VP
  → No coaching, no development
  → High turnover

✗ Siloed from sales
  → No handoff process
  → Competing for customer attention
  → Duplicate conversations

CSM Hiring Profile

CSM Interview Questions

Strategic Thinking:
→ "How would you prioritize 50 accounts with limited time?"
→ "Walk me through building a success plan for a new enterprise customer"

Customer Management:
→ "Tell me about a time you saved an at-risk account"
→ "How do you handle a customer asking for something we can't deliver?"

Business Acumen:
→ "How do you tie product usage to customer business outcomes?"
→ "Describe how you'd run an Executive Business Review"

Technical:
→ "Explain [your product] to a non-technical executive"
→ "How do you identify adoption gaps from usage data?"

Onboarding New CSMs

Compensation Structure

Scaling Checklist

□ Define customer segments clearly
  → ARR thresholds, complexity, strategic value

□ Set target CSM ratios per segment
  → Based on touch model requirements

□ Build CS Ops function
  → Before you have 5+ CSMs

□ Create career ladder
  → IC and management tracks

□ Document playbooks
  → Before hiring next CSM

□ Implement CS platform
  → At ~50 customers or 3+ CSMs

□ Establish cross-functional processes
  → Sales handoff, product feedback, support escalation

Org Structure Mistakes

Anti-Patterns

• Hiring ahead of need — Build playbooks and processes first
• Copying competitor structure — Your segment mix is different
• Promoting best CSM to manager — Management requires different skills
• CSM as catch-all — Clear role boundaries enable specialization
• Ignoring tenure — New CSMs need different ratios than experienced
• Segment by logo not ARR — A $5k and $500k account aren't the same
• No ramp time — Full book on day one guarantees failure

CS Playbook Development

Impact: HIGH

Playbooks are the operating system of your CS organization. Without them, every CSM reinvents the wheel. With them, you scale best practices across the team and ensure consistent customer experiences.

Playbook Categories

LIFECYCLE PLAYBOOKS (Proactive)
├── Onboarding Playbook
├── Adoption Playbook
├── Expansion Playbook
├── Renewal Playbook
└── Advocacy Playbook

INTERVENTION PLAYBOOKS (Reactive)
├── At-Risk Playbook
├── Escalation Playbook
├── Champion Change Playbook
└── Executive Sponsor Loss Playbook

OPERATIONAL PLAYBOOKS (Recurring)
├── QBR Playbook
├── EBR Playbook
├── Success Plan Playbook
└── Handoff Playbook

Playbook Anatomy

┌─────────────────────────────────────────────────────────────────┐
│                       PLAYBOOK TEMPLATE                          │
├─────────────────────────────────────────────────────────────────┤
│ TRIGGER: What initiates this playbook?                          │
│ OWNER: Who is responsible?                                       │
│ TIMELINE: How long does this take?                              │
│ EXIT CRITERIA: How do we know it's complete?                    │
├─────────────────────────────────────────────────────────────────┤
│ STEPS:                                                           │
│ 1. Step name (Day X) - Channel - Owner                          │
│    • Action details                                             │
│    • Templates/resources                                        │
│    • Success criteria                                           │
│ 2. Step name (Day Y) - Channel - Owner                          │
│    ...                                                          │
├─────────────────────────────────────────────────────────────────┤
│ METRICS: How do we measure success?                             │
│ AUTOMATION: What can be automated?                              │
│ ESCALATION: When/how to escalate?                               │
└─────────────────────────────────────────────────────────────────┘

Onboarding Playbook (High Touch)

Exit Criteria:

• [ ] Success plan documented and agreed
• [ ] Key stakeholders identified
• [ ] First value milestone achieved
• [ ] Product adoption >60%
• [ ] Health score >70

Onboarding Playbook (Tech Touch)

Automation triggers:

• No login Day 3 → Re-engagement email
• Low usage Day 7 → Help offer email
• High usage Day 7 → Power user tips
• Completed onboarding → Celebration + next steps

QBR Playbook

Pre-QBR (2 weeks before)

QBR Agenda (45-60 minutes)

1. BUSINESS ALIGNMENT (10 min)
   → Customer's current priorities
   → Changes since last QBR
   → Success criteria reminder

2. VALUE DELIVERED (15 min)
   → Key metrics and outcomes
   → ROI demonstration
   → Success stories from their team

3. ADOPTION & USAGE (10 min)
   → Product usage highlights
   → Feature adoption
   → Recommendations for improvement

4. ROADMAP PREVIEW (10 min)
   → Upcoming features relevant to them
   → Beta opportunities
   → Feedback on priorities

5. SUCCESS PLAN UPDATE (10 min)
   → Progress against goals
   → Adjustments needed
   → Next quarter objectives

6. NEXT STEPS (5 min)
   → Action items (both sides)
   → Next QBR scheduling

Post-QBR (within 48 hours)

Renewal Playbook

T-90 Days: Preparation Phase

T-60 Days: Engagement Phase

T-30 Days: Execution Phase

At-Risk Playbook

Trigger: Health score drops below 40 OR cancel signals detected

Escalation triggers:

• No response in 3 days → Manager involvement
• Health drops below 20 → Executive involvement
• Cancel request received → Save team engaged
• Multiple stakeholder churn → Account review

Good Playbook Design

✓ Clear triggers
  → "When health drops below 40" not "when customer seems unhappy"
  → Objective, measurable

✓ Specific actions
  → "Send renewal summary email using template X"
  → Not "reach out to customer"

✓ Defined ownership
  → Every step has an owner
  → No ambiguity

✓ Realistic timelines
  → Based on actual execution data
  → Buffer for delays

✓ Exit criteria
  → How do we know we're done?
  → What does success look like?

✓ Built-in automation
  → Emails that can be templatized
  → Triggers that can be automated

Bad Playbook Design

✗ Vague triggers
  → "When customer is at risk"
  → No objective criteria

✗ Generic steps
  → "Check in with customer"
  → No specific action

✗ No ownership
  → "Team should review"
  → No individual accountability

✗ Unrealistic timelines
  → 15 steps in first week
  → Guaranteed non-compliance

✗ No metrics
  → No way to know if playbook works
  → No improvement possible

✗ Static
  → Written once, never updated
  → Doesn't reflect reality

Playbook Automation

Playbook Compliance Tracking

Playbook Review Cadence

Anti-Patterns

• Shelf-ware playbooks — Created but not used
• Too many playbooks — 50 playbooks, none followed
• No automation — All manual, doesn't scale
• No compliance tracking — Don't know if followed
• Never updated — Created 2 years ago, still in use
• Copy-paste from blog — Not customized for your business
• Missing escalation paths — No guidance when stuck
• No templates — CSMs create everything from scratch

Renewal & Expansion Strategy

Impact: CRITICAL

Renewals are the foundation of SaaS economics. Expansion is the growth engine. World-class CS organizations don't just retain customers — they grow them. NRR above 100% means you can grow even without new customer acquisition.

The Renewal-Expansion Relationship

                    NET REVENUE RETENTION
┌─────────────────────────────────────────────────────────────────┐
│                                                                  │
│   Starting MRR + EXPANSION - Contraction - Churn                │
│   ────────────────────────────────────────────────              │
│                    Starting MRR                                  │
│                                                                  │
│   ┌─────────────────────────────────────────────────────────┐   │
│   │                                                         │   │
│   │  RENEWALS protect the base (GRR)                       │   │
│   │  EXPANSION grows the base (NRR - GRR)                  │   │
│   │                                                         │   │
│   │  Example:                                               │   │
│   │  GRR: 92% (retained $920k of $1M)                      │   │
│   │  Expansion: $150k                                       │   │
│   │  NRR: 107% ($920k + $150k = $1.07M)                    │   │
│   │                                                         │   │
│   └─────────────────────────────────────────────────────────┘   │
│                                                                  │
└─────────────────────────────────────────────────────────────────┘

Expansion Revenue Types

Renewal Process

Timeline

T-120: PLANNING PHASE
└── Review health, usage, satisfaction
└── Identify risks and opportunities
└── Forecast renewal likelihood

T-90: ENGAGEMENT PHASE
└── Renewal kickoff conversation
└── Value demonstration
└── Address concerns proactively

T-60: NEGOTIATION PHASE
└── Present renewal proposal
└── Discuss expansion opportunities
└── Negotiate terms

T-30: EXECUTION PHASE
└── Contract finalized
└── Signatures collected
└── Payment processed

T-0: RENEWAL COMPLETE
└── Thank customer
└── Celebrate internally
└── Begin next cycle planning

Renewal Playbook

Expansion Signals

Expansion Conversation Framework

DISCOVERY
─────────
"What new initiatives are you working on?"
"Where are you seeing the most value today?"
"What challenges is your team facing now?"

CONNECT
───────
"Based on your goal to [X], our [feature/product] can help by..."
"Customers in similar situations have seen [outcome]..."

PROPOSE
───────
"Here's what I'd recommend..."
"The investment would be [X] for [outcome]..."

CONFIRM
───────
"Does this align with your priorities?"
"What would you need to see to move forward?"

Good Renewal Practices

✓ No surprises
  → Customer knows renewal is coming
  → Value demonstrated throughout year

✓ Early engagement
  → Start at T-90, not T-30
  → Time to address concerns

✓ Value-led conversation
  → "Here's the ROI you've achieved"
  → Not "Here's your invoice"

✓ Multi-threaded
  → Executive sponsor engaged
  → Not just champion

✓ Expansion integrated
  → Natural part of renewal conversation
  → Not separate sales pitch

✓ Risk-aware forecasting
  → Health score informs probability
  → Not wishful thinking

Bad Renewal Practices

✗ Last-minute scramble
  → T-7: "Your renewal is due"
  → Customer surprised, annoyed

✗ Contract focus
  → "Just need you to sign"
  → No value discussion

✗ Single-threaded
  → Champion is only contact
  → Risky if champion changes

✗ Discount-first
  → "What discount do you need?"
  → Trains customers to negotiate

✗ Expansion as separate event
  → "Now let me transfer you to sales"
  → Disjointed experience

✗ Hope-based forecasting
  → "They've always renewed"
  → Ignoring warning signs

Renewal Forecasting

FORECAST = Σ (Renewal ARR × Probability)

PROBABILITY BY HEALTH:
┌─────────────────────────────────────────────────────────────────┐
│ Health Score │ Probability │ Rationale                          │
├──────────────┼─────────────┼─────────────────────────────────────┤
│ 80-100       │ 95%         │ Healthy, engaged, getting value    │
│ 60-79        │ 85%         │ Stable, some concerns              │
│ 40-59        │ 60%         │ At-risk, needs intervention        │
│ 20-39        │ 30%         │ Critical, save attempt needed      │
│ 0-19         │ 10%         │ Likely churning                    │
└─────────────────────────────────────────────────────────────────┘

EXAMPLE:
Customer A: $100k ARR, Health 85 → $95k expected
Customer B: $50k ARR, Health 45 → $30k expected
Customer C: $75k ARR, Health 25 → $22.5k expected

Total due: $225k
Forecast: $147.5k (65.5%)

Expansion Forecasting

CS vs Sales Ownership

Handling Downgrades

WHEN CUSTOMER WANTS TO DOWNGRADE:

1. UNDERSTAND
   → "Can you help me understand what's driving this?"
   → Get to root cause

2. OPTIONS
   → Address root cause if possible
   → Offer alternatives (pause, different tier)
   → Calculate ROI at current level

3. ACCEPT GRACEFULLY
   → If downgrade is right answer, accept it
   → Preserve relationship for future
   → "We want you to be in the right plan"

4. DOCUMENT
   → Capture reason for downgrades
   → Feed back to product/CS

NEVER:
✗ Make downgrading difficult
✗ Guilt trip the customer
✗ Ignore the request

At-Risk Renewal Escalation

Renewal Incentive Structure

Multi-Year Deals

When to offer:

✓ High health score (80+)
✓ Strong relationship
✓ Customer values predictability
✓ Strategic account

OFFER STRUCTURE:
1-year: Standard pricing
2-year: 5-10% discount
3-year: 10-15% discount

Benefits:

• Reduced churn risk
• Cash flow predictability
• Deeper partnership

Risks:

• Locked into lower price if product improves
• Customer may be unhappy but stuck

Metrics

Anti-Patterns

• Reactive renewals — Starting at T-30 is too late
• Contract-focused — "Sign here" without value conversation
• Discount-led saves — Trains customers to threaten churn
• Ignoring at-risk — Hope is not a strategy
• Expansion as separate process — Should be integrated with CS
• Single-threaded renewals — Champion leaves, renewal at risk
• No expansion motion — Leaving money on the table
• Poor handoff CS/Sales — Customer gets pinballed between teams

Customer Segmentation & Coverage Models

Impact: CRITICAL

The #1 mistake in Customer Success is treating all customers the same. Segmentation is not optional — it's the foundation of scalable CS. Your coverage model determines unit economics, customer experience, and team sanity.

The Three-Tier Model

┌─────────────────────────────────────────────────────────────────┐
│                        HIGH TOUCH                                │
│  ════════════════════════════════════════════════════════════   │
│  • $100k+ ARR (or strategic accounts)                           │
│  • Dedicated CSM (1:10-25 ratio)                                │
│  • Weekly/bi-weekly touchpoints                                 │
│  • Custom success plans                                         │
│  • Executive Business Reviews (quarterly)                       │
│  • Cost to serve: 15-25% of ARR                                │
├─────────────────────────────────────────────────────────────────┤
│                        LOW TOUCH                                 │
│  ════════════════════════════════════════════════════════════   │
│  • $15k-$100k ARR                                               │
│  • Pooled CSM model (1:50-100 ratio)                           │
│  • Monthly touchpoints + triggered outreach                     │
│  • Templated success plans                                      │
│  • Group QBRs / Office hours                                    │
│  • Cost to serve: 5-10% of ARR                                 │
├─────────────────────────────────────────────────────────────────┤
│                        TECH TOUCH                                │
│  ════════════════════════════════════════════════════════════   │
│  • <$15k ARR                                                    │
│  • No dedicated CSM (1:500+ or 1:∞)                            │
│  • Automated journeys + self-service                            │
│  • In-app guidance, email sequences                             │
│  • Community, knowledge base, webinars                          │
│  • Cost to serve: <3% of ARR                                   │
└─────────────────────────────────────────────────────────────────┘

Segmentation Criteria

Beyond ARR: Multi-Dimensional Segmentation

Simple ARR-only segmentation:
  $100k+ = High Touch
  $15k-100k = Low Touch
  <$15k = Tech Touch

Better multi-factor segmentation:
  Score = (ARR weight × ARR tier)
        + (Complexity weight × complexity score)
        + (Growth weight × expansion potential)
        + (Strategic weight × strategic fit)

Example weights:
  ARR: 40%
  Complexity: 25%
  Growth potential: 20%
  Strategic value: 15%

Segmentation Matrix

Good Segmentation

✓ Data-driven thresholds
  → Based on analysis of cost-to-serve and outcomes
  → Not arbitrary round numbers

✓ Multi-dimensional
  → ARR + complexity + potential + fit
  → Not just contract size

✓ Dynamic reassignment
  → Accounts move between segments
  → Expansion triggers high-touch upgrade

✓ Clear criteria
  → Anyone can determine segment from data
  → No subjective judgment

✓ Tied to economics
  → Cost-to-serve sustainable at each tier
  → Profitable at scale

✓ Different playbooks
  → Distinct approaches, not just different ratios
  → Tech touch ≠ low touch with fewer calls

Bad Segmentation

✗ ARR-only
  → $99k account treated completely differently than $101k
  → Ignores complexity, potential, strategic value

✗ Static assignment
  → "They signed as SMB, they're always SMB"
  → Even after 5x expansion

✗ Too many segments
  → 10 segments with 10 different playbooks
  → Impossible to execute consistently

✗ Gut feel
  → "This customer feels important"
  → No objective criteria

✗ Same playbook, different frequency
  → Low touch = high touch with fewer meetings
  → Misses the point entirely

✗ Ignoring cost economics
  → High-touch treatment for $5k accounts
  → Unprofitable and unsustainable

Coverage Model Economics

Example calculation:

Enterprise account: $200k ARR
CSM fully-loaded cost: $150k/year
CSM ratio: 1:15 accounts
Cost per account: $150k / 15 = $10k
Cost-to-serve: $10k / $200k = 5% ✓

SMB account: $10k ARR
If same CSM ratio (1:15): $10k cost = 100% of ARR ✗
Need 1:150 ratio: $1k cost = 10% of ARR
Or tech touch: <$300 cost = 3% of ARR ✓

High Touch Playbook Elements

Low Touch Playbook Elements

Tech Touch Playbook Elements

Segment Transition Triggers

Pooled Model Operations

The Low Touch "Pooled" Model:

Option A: Geographic pools
  → West Coast CSM, East Coast CSM, etc.
  → Timezone alignment

Option B: Industry pools
  → Healthcare CSM, Finance CSM, etc.
  → Domain expertise

Option C: Round-robin
  → Next available CSM
  → Load balancing

Pooled model rules:
  → Customer always knows their "team" even if no dedicated CSM
  → CRM shows account owner for routing
  → Shared context in CS platform
  → Warm handoffs between pool members

Hybrid Model: Digital + Human

Best-in-class low touch combines:

DIGITAL LAYER (always on):
  → Automated health monitoring
  → Triggered email campaigns
  → In-app guidance
  → Self-service resources

HUMAN LAYER (triggered):
  → Health score drops → CSM outreach
  → Expansion signals → CSM call
  → Support escalation → CSM follow-up
  → Renewal approaching → CSM check-in

Measuring Segment Performance

Segment-Specific Health Scores

Anti-Patterns

• One playbook for all — Tech touch cannot be high touch without calls
• Segment by logo count — 10 small accounts ≠ 1 enterprise account
• Over-investing in SMB — Unprofitable, unsustainable, unfair to enterprise
• Under-investing in tech touch — 80% of customers, deserves real strategy
• Static forever — Segments should shift as customers grow/shrink
• Arbitrary thresholds — $99k vs $101k shouldn't be a cliff
• Ignoring complexity — Simple $150k account may need less than complex $80k
• Treating expansion same as new — Existing high-touch customer expanding SMB product line

CS Technology Stack Strategy

Impact: HIGH

Technology enables scale. Without the right tools, CSMs spend 40%+ of their time on data gathering and admin instead of customer engagement. But technology alone doesn't fix bad processes — it just automates them faster.

The CS Tech Stack Layers

┌─────────────────────────────────────────────────────────────────┐
│                    INTELLIGENCE LAYER                            │
│  Churn prediction, next best action, AI insights                │
│  Planhat, Catalyst, Gainsight (PX), custom ML                   │
├─────────────────────────────────────────────────────────────────┤
│                    ENGAGEMENT LAYER                              │
│  In-app messaging, email automation, digital CS                 │
│  Intercom, Pendo, Appcues, Customer.io, Braze                   │
├─────────────────────────────────────────────────────────────────┤
│                    FEEDBACK LAYER                                │
│  NPS, CSAT, surveys, sentiment                                  │
│  Delighted, Wootric, Satismeter, Qualtrics                      │
├─────────────────────────────────────────────────────────────────┤
│                    ANALYTICS LAYER                               │
│  Product usage, feature adoption, behavioral data               │
│  Amplitude, Mixpanel, Pendo, Heap, Segment                      │
├─────────────────────────────────────────────────────────────────┤
│                    CS PLATFORM (CORE)                            │
│  Customer 360, health scores, playbooks, workflows              │
│  Gainsight, ChurnZero, Totango, Vitally, Planhat                │
├─────────────────────────────────────────────────────────────────┤
│                    CRM FOUNDATION                                │
│  Account data, contacts, opportunities, contracts               │
│  Salesforce, HubSpot, Dynamics                                  │
└─────────────────────────────────────────────────────────────────┘

CS Platform Comparison

Core CS Platform Capabilities

Build vs Buy Decision

Build when:

□ You have truly unique requirements
□ You have engineering capacity
□ Time to value isn't critical
□ Data security requires on-premise
□ You want full control

Buy when:

□ You need standard CS capabilities
□ You need fast time to value
□ You don't have engineering capacity
□ You want vendor to handle innovation
□ You want proven best practices

Data Integration Architecture

┌─────────────────────────────────────────────────────────────────┐
│                     DATA SOURCES                                 │
├──────────────┬──────────────┬──────────────┬───────────────────┤
│ CRM          │ Product      │ Support      │ Billing           │
│ (Salesforce) │ (Amplitude)  │ (Zendesk)    │ (Stripe)          │
└──────┬───────┴──────┬───────┴──────┬───────┴───────┬───────────┘
       │              │              │               │
       ▼              ▼              ▼               ▼
┌─────────────────────────────────────────────────────────────────┐
│                   DATA WAREHOUSE / CDP                           │
│              (Snowflake, BigQuery, Segment)                      │
└───────────────────────────┬─────────────────────────────────────┘
                            │
                            ▼
┌─────────────────────────────────────────────────────────────────┐
│                     CS PLATFORM                                  │
│                   (Gainsight, etc.)                              │
│  ┌───────────┐ ┌───────────┐ ┌───────────┐ ┌───────────┐       │
│  │ Customer  │ │ Health    │ │ Playbooks │ │ Reporting │       │
│  │ 360       │ │ Scores    │ │           │ │           │       │
│  └───────────┘ └───────────┘ └───────────┘ └───────────┘       │
└─────────────────────────────────────────────────────────────────┘

Key Integrations

Good Technology Strategy

✓ Start with process, then automate
  → Define playbooks before implementing
  → Technology accelerates, doesn't create

✓ Single source of truth
  → CS platform is the system of record for health
  → CRM is system of record for account data
  → Clear ownership

✓ Data quality first
  → Garbage in, garbage out
  → Clean data before implementing health scores

✓ Phased implementation
  → Core first (360, health, playbooks)
  → Add layers (automation, AI) over time

✓ Adoption > Features
  → 80% adoption of 20% features
  → Better than 20% adoption of 80% features

✓ Integrate, don't duplicate
  → Don't rebuild what exists in other tools
  → Connect systems, don't recreate

Bad Technology Strategy

✗ Tool before process
  → "We bought Gainsight, now what?"
  → Technology won't fix bad processes

✗ Too many tools
  → 15 tools, no integration
  → CSMs live in spreadsheets anyway

✗ No data governance
  → Multiple sources of truth
  → Conflicting numbers in meetings

✗ Shelfware
  → Expensive platform, minimal usage
  → Overpaid for features not used

✗ Custom everything
  → Every field, every workflow custom
  → Nightmare to maintain

✗ No owner
  → Who maintains the CS platform?
  → Becomes stale without steward

Implementation Checklist

PHASE 1: Foundation (Weeks 1-4)
□ CRM integration configured
□ Account hierarchy established
□ Contact sync working
□ Basic customer 360 live
□ CSM assignments configured

PHASE 2: Health Scoring (Weeks 5-8)
□ Product usage integration
□ Health score components defined
□ Health score weights calibrated
□ Health score dashboards created
□ Alert rules configured

PHASE 3: Playbooks (Weeks 9-12)
□ Onboarding playbook implemented
□ At-risk playbook implemented
□ QBR playbook implemented
□ Renewal playbook implemented
□ Task automation configured

PHASE 4: Optimization (Weeks 13-16)
□ Reporting suite finalized
□ Email integration complete
□ Team fully trained
□ Process compliance tracking
□ Health score validation complete

CS Platform Adoption Metrics

Technology Budget Allocation

Common Platform Mistakes

Vendor Evaluation Criteria

Anti-Patterns

• Tool without process — Technology amplifies, doesn't create
• Data hoarding — Every metric tracked, none acted upon
• Integration debt — Manual CSV uploads, stale data
• Feature bloat — Buying features CSMs will never use
• No steward — Platform becomes abandoned shelfware
• Siloed tools — Every team has their own tool, no integration
• Over-automation — Customers get 15 automated emails per week
• Analysis paralysis — Evaluating tools for 6 months instead of implementing