---
# === IDENTITY ===
id: business/customer-success/customer-success-model-selection/2026
canonical_question: "How do I choose a CS model — high-touch vs tech-touch vs hybrid, decision framework by ACV tier?"
aliases:
  - "Customer success model selection framework"
  - "High-touch vs tech-touch CS decision guide"
  - "CS coverage model by ACV tier"
entity_type: execution_recipe
domain: business > customer-success > customer-success-model-selection
region: global
jurisdiction: global
temporal_scope: 2025-2026

# === VERIFICATION ===
last_verified: 2026-03-12
confidence: 0.88
version: 1.0
first_published: 2026-03-12

# === TEMPORAL VALIDITY ===
temporal_validity:
  status: evolving
  last_breaking_change: "AI-assisted CSM tooling (Gainsight Horizon AI, ChurnZero AI agents) shifted digital-touch capacity upward by 30-50% in late 2025"
  next_review: 2026-09-08
  change_sensitivity: high

# === CONSTRAINTS ===
constraints:
  - "ACV tier boundaries are guidelines, not absolutes — adjust based on product complexity, customer technical sophistication, and expansion potential"
  - "CSM-to-account ratios assume full ramp (90+ days tenure); new CSMs need 50% lighter books during onboarding"
  - "Health scoring requires minimum 90 days of product usage data before scores are statistically meaningful"
  - "Digital-touch automation requires minimum 200+ accounts in a segment to justify build cost"
  - "Budget at 5-10% of ARR for total CS function cost including tooling, headcount, and enablement"

# === SKIP CONDITIONS ===
skip_this_unit_if:
  - condition: "User needs a strategic overview of customer success, not execution"
    use_instead: "Search knowledgelib.io for customer success strategy overview — no dedicated unit yet"
  - condition: "User already has a model and needs to optimize health scoring only"
    use_instead: "business/customer-success/churn-prevention-system-design/2026"
  - condition: "User is pre-revenue or has fewer than 20 customers"
    use_instead: "Search knowledgelib.io for early-stage customer success — no dedicated unit yet"

# === AGENT HINTS ===
inputs_needed:
  - key: current_acv_distribution
    question: "What is the ACV distribution across your customer base?"
    type: choice
    options: ["mostly <$10K ACV", "mix of <$10K and $10K-$100K", "mostly $10K-$100K", "mix including >$100K enterprise", "no preference — provide general framework"]
  - key: cs_team_size
    question: "How large is the current CS team?"
    type: choice
    options: ["0-2 CSMs (startup)", "3-10 CSMs (scaling)", "10-25 CSMs (growth)", "25+ CSMs (enterprise)"]
  - key: cs_platform
    question: "Which CS platform is in use or preferred?"
    type: choice
    options: ["Gainsight", "Vitally", "ChurnZero", "Totango", "none yet — recommend one", "other"]
  - key: primary_goal
    question: "What is the primary CS goal?"
    type: choice
    options: ["reduce churn", "drive expansion/NRR", "scale coverage without adding headcount", "all of the above"]

# === EXECUTION METADATA ===
execution:
  required_inputs:
    - name: "Customer list with ACV and segment data"
      source: "CRM (Salesforce, HubSpot) or billing system"
      format: "spreadsheet or CRM export"
    - name: "Current churn and expansion data by segment"
      source: "finance/billing system"
      format: "spreadsheet"

  outputs:
    - name: "CS coverage model document"
      format: "document"
      description: "Tier definitions, touch model per tier, CSM-to-account ratios, and capacity plan"
    - name: "CSM capacity model spreadsheet"
      format: "spreadsheet"
      description: "Headcount plan by tier with ARR coverage, account loads, and hiring triggers"
    - name: "Playbook library outline"
      format: "document"
      description: "Per-tier playbook definitions for onboarding, adoption, renewal, and expansion"

  tools_required:
    - name: "CS platform (Gainsight, Vitally, ChurnZero, or Totango)"
      purpose: "Health scoring, automation, playbook execution, and reporting"
      tier: "paid"
      cost: "$500-$5,000/mo depending on customer count"
      alternatives: ["spreadsheet-based manual tracking (0-100 customers only)"]
    - name: "CRM system"
      purpose: "Source of customer data, ACV, segment, and lifecycle stage"
      tier: "paid"
      cost: "varies"
      alternatives: ["HubSpot free CRM for early stage"]

  credentials_needed:
    - service: "CS platform"
      type: "username+password or SSO"
      where_to_get: "Platform vendor sales team"
      free_tier_limits: "Vitally offers startup plan; others require paid license"

  estimated_duration: "2-4 weeks for full model design and initial implementation"
  estimated_cost: "$0 (spreadsheet-based) to $5,000/mo (enterprise CS platform)"

# === DISTRIBUTION ===
canonical_source: "https://knowledgelib.io/business/customer-success/customer-success-model-selection/2026"
suggested_citation: "Source: knowledgelib.io — AI Knowledge Library (verified 2026-03-12)"

# === RELATED UNITS ===
related_kos:
  feeds_into:
    - id: "business/customer-success/churn-prevention-system-design/2026"
      label: "Churn prevention system design — Step 2 builds the composite 0-100 customer health score model (four weighted dimensions, segment normalization, health zones, trigger rules)"
  related_to:
    - id: "finance/saas-benchmarks/saas-net-revenue-retention-benchmarks/2026"
      label: "SaaS Net Revenue Retention (NRR) benchmarks by segment and vertical"

# === SOURCES ===
sources:
  - id: src1
    title: "Customer Success Team Planning & Cost Benchmarks"
    author: Gainsight
    url: https://www.gainsight.com/blog/customer-success-team-planning-cost-benchmarks/
    type: industry_report
    published: 2025-01-15
    reliability: authoritative
  - id: src2
    title: "The $2 Million Dollar Man/Woman: How to Think About Scaling Your Customer Success Team"
    author: Jason Lemkin / SaaStr
    url: https://www.saastr.com/the-2-million-dollar-man-woman-how-to-think-about-scaling-your-customer-success-team/
    type: expert_commentary
    published: 2024-06-10
    reliability: authoritative
  - id: src3
    title: "What Is Tech-Touch Customer Success"
    author: Vitally
    url: https://www.vitally.io/post/what-is-tech-touch-customer-success
    type: vendor_documentation
    published: 2025-03-01
    reliability: authoritative
  - id: src4
    title: "The Golden Ratio of Customer Success Managers to Customers"
    author: Vitally
    url: https://www.vitally.io/post/what-is-the-golden-ratio-of-customer-success-managers-to-customers
    type: vendor_documentation
    published: 2025-02-15
    reliability: authoritative
  - id: src5
    title: "Customer Success Manager Coverage Ratio & ARR"
    author: ChurnZero
    url: https://churnzero.com/blog/customer-success-manager-coverage-ratio-arr/
    type: industry_report
    published: 2025-04-01
    reliability: authoritative
  - id: src6
    title: "What Customer Success Teams Are Prioritizing In 2026"
    author: Gainsight
    url: https://www.gainsight.com/blog/what-customer-success-teams-are-prioritizing-in-2026-and-what-the-data-shows-is-working/
    type: industry_report
    published: 2026-01-10
    reliability: authoritative
---

# Customer Success Model Selection — High-Touch vs Tech-Touch vs Hybrid by ACV Tier

## Purpose

This recipe produces a complete CS coverage model document defining tier boundaries, touch-model assignments, CSM-to-account ratios, a capacity plan with hiring triggers, and per-tier playbook outlines — ready for implementation in a CS platform (Gainsight, Vitally, ChurnZero, or Totango). The output enables a CS leader to move from ad-hoc account assignments to a structured, scalable coverage model that matches engagement intensity to customer value and complexity. [src1]

## Prerequisites
<!-- Agents: verify ALL prerequisites before executing. Missing prerequisites = failed execution. -->

- [ ] **Customer list with ACV data** available from CRM or billing system — export with fields: account name, ACV/ARR, segment, industry, contract start date, renewal date, product tier
- [ ] **Churn and expansion data** for the past 12 months — gross churn rate and expansion rate by segment
- [ ] **Current CS headcount and account assignments** — who owns what today
- [ ] **Product usage data access** — login frequency, feature adoption, or engagement metrics (needed for health scoring in Step 5)
- [ ] **CS platform account** — Gainsight, Vitally, ChurnZero, Totango, or a spreadsheet for early stage

## Constraints
<!-- Hard rules. Agents: enforce throughout execution. Violating these = broken output or legal risk. -->

- ACV thresholds must be calibrated to your specific business — the tiers below are industry medians, not universal rules. A company selling $500K+ enterprise deals has different thresholds than a PLG company with $5K average ACV. [src2]
- Never assign more than $5M ARR to a single CSM regardless of account count — cognitive overload degrades service quality above this threshold. [src1]
- Digital-touch programs require a minimum of 200 accounts in the segment to amortize the automation build cost. Below that threshold, use a pooled CSM model instead. [src3]
- CSM ramp time is 90 days to full book of business. New hires should carry 50% load in months 1-3. [src1]
- Budget 5-10% of ARR for total CS function (headcount + tooling + enablement). Below 5% signals underinvestment; above 10% signals inefficiency at scale. [src2]

## Tool Selection Decision

<!-- Agent selects the right tool path based on user inputs. -->

```
Which path?
├── Customer count < 100 AND no CS platform
│   └── PATH A: Spreadsheet-Based — Google Sheets + manual tracking
├── Customer count 100-500 AND budget for tooling
│   └── PATH B: Mid-Market CS Platform — Vitally or ChurnZero
├── Customer count 500-5,000 AND enterprise needs
│   └── PATH C: Enterprise CS Platform — Gainsight or Totango
└── Customer count 5,000+ AND PLG motion
    └── PATH D: Digital-First Platform — Gainsight + product analytics
```

| Path | Tools | Cost | Speed | Output Quality |
|------|-------|------|-------|---------------|
| A: Spreadsheet | Google Sheets, CRM | $0 | 1 week | Functional but manual, breaks above 100 accounts |
| B: Mid-Market | Vitally or ChurnZero | $500-$2,000/mo | 2-3 weeks | Automated playbooks, health scoring, scales to 500 |
| C: Enterprise | Gainsight or Totango | $2,000-$5,000/mo | 3-4 weeks | Full automation, AI insights, multi-tier orchestration |
| D: Digital-First | Gainsight + analytics | $5,000+/mo | 4-6 weeks | Product-led signals, digital journeys at massive scale |

## Execution Flow

### Step 1: Assess Customer Segments by ACV

**Duration**: 2-4 hours
**Tool**: Spreadsheet + CRM export

Export your full customer list with ACV, contract dates, industry, and product tier. Sort by ACV descending and identify natural clustering. Use the following tier framework as a starting baseline, then adjust boundaries based on where natural breaks occur in your data. [src1]

```
Tier framework (adjust thresholds to your ACV distribution):

Enterprise (High-Touch):    ACV > $100K
  - Dedicated named CSM
  - Quarterly business reviews (QBRs)
  - Custom success plans
  - Executive sponsor alignment
  - CSM ratio: 1:10-25 accounts

Mid-Market (Hybrid):        ACV $25K-$100K
  - Named CSM with higher book
  - Semi-annual business reviews
  - Templated success plans with customization
  - Proactive outreach on health score drops
  - CSM ratio: 1:40-75 accounts

SMB / Growth (Tech-Touch):  ACV $5K-$25K
  - Pooled CSM team or digital-only
  - Automated onboarding sequences
  - In-app guidance and lifecycle emails
  - Human intervention on red health scores only
  - CSM ratio: 1:100-200 accounts (pooled)

Self-Serve (Digital-Only):  ACV < $5K
  - No dedicated or pooled CSM
  - Fully automated lifecycle campaigns
  - Community-driven support
  - In-app product tours and knowledge base
  - CSM ratio: 0 (automation only)
```

**Verify**: Every active customer is assigned to exactly one tier. No account is untiered. Tier distribution roughly follows: 5-15% Enterprise, 20-30% Mid-Market, 50-70% SMB/Growth, remainder Self-Serve.
**If failed**: If more than 40% of ARR concentrates in one tier, consider splitting that tier further (e.g., Enterprise into Strategic and Enterprise).

### Step 2: Map Touch Model Per Tier

**Duration**: 3-5 hours
**Tool**: Document editor + CS platform

For each tier, define the engagement model — the specific touchpoints, cadence, and delivery method (human vs automated) across the customer lifecycle. [src3]

```
Touch model definition per tier:

ENTERPRISE (High-Touch):
  Onboarding:      Dedicated CSM-led, 30-60-90 day plan, kickoff call
  Adoption:        Weekly check-ins (first 90 days), then biweekly
  Value delivery:  Quarterly QBR with ROI metrics, exec alignment
  Renewal:         CSM-led renewal prep starting 120 days before
  Expansion:       CSM identifies upsell signals, warm handoff to AE
  Escalation:      Direct CSM + manager escalation path
  Health check:    CSM reviews health score weekly

MID-MARKET (Hybrid):
  Onboarding:      CSM-assisted, guided setup + automated email drip
  Adoption:        Monthly check-in calls, in-app guidance
  Value delivery:  Semi-annual business review (virtual)
  Renewal:         Automated renewal reminders + CSM outreach at 90 days
  Expansion:       Usage-based triggers → CSM outreach for upgrade
  Escalation:      CSM triages via health score; pooled for low-severity
  Health check:    Automated weekly, CSM review on score drops

SMB / GROWTH (Tech-Touch):
  Onboarding:      Automated email sequence + in-app product tours
  Adoption:        Lifecycle email campaigns triggered by usage milestones
  Value delivery:  Automated usage reports, webinars, community
  Renewal:         Automated renewal flow, human only for at-risk
  Expansion:       In-app upgrade prompts based on usage thresholds
  Escalation:      Pooled CSM queue for escalated tickets
  Health check:    Fully automated, alerts to pooled team on red scores

SELF-SERVE (Digital-Only):
  Onboarding:      In-app welcome flow + knowledge base links
  Adoption:        Behavioral email triggers only
  Value delivery:  Community, help center, monthly product updates
  Renewal:         Auto-renewal with self-service cancellation flow
  Expansion:       In-app upgrade prompts only
  Escalation:      Support ticket queue (not CS-routed)
  Health check:    Churn prediction model triggers win-back campaigns
```

**Verify**: Every lifecycle stage (onboarding, adoption, value delivery, renewal, expansion) has a defined touchpoint for every tier. No gaps.
**If failed**: Map missing lifecycle stages to the most similar adjacent tier's approach, then customize.

### Step 3: Design CSM Capacity Model

**Duration**: 3-5 hours
**Tool**: Spreadsheet

Build the capacity model that determines headcount requirements per tier. Use industry benchmarks as starting points, then adjust for your product complexity and customer expectations. [src2] [src4]

```
Capacity model calculation:

For each tier:
  1. Count accounts in tier
  2. Sum ARR in tier
  3. Set target CSM-to-account ratio (from Step 1)
  4. Calculate required CSMs: accounts / ratio
  5. Validate ARR per CSM does not exceed $5M
  6. Add 15% buffer for PTO, ramp, and attrition

Example calculation:
  Enterprise tier:  60 accounts, $12M ARR, ratio 1:15
    CSMs needed = 60 / 15 = 4.0
    ARR/CSM = $12M / 4 = $3M ✓ (under $5M cap)
    With buffer = 4.0 * 1.15 = 4.6 → 5 CSMs

  Mid-Market tier:  250 accounts, $10M ARR, ratio 1:50
    CSMs needed = 250 / 50 = 5.0
    ARR/CSM = $10M / 5 = $2M ✓
    With buffer = 5.0 * 1.15 = 5.75 → 6 CSMs

  SMB tier (pooled): 800 accounts, $6M ARR, ratio 1:150
    CSMs needed = 800 / 150 = 5.3
    ARR/CSM = $6M / 5.3 = $1.1M ✓
    With buffer = 5.3 * 1.15 = 6.1 → 6 pooled CSMs

Hiring triggers (add 1 CSM when):
  - Enterprise: new accounts push any CSM above 20
  - Mid-Market: any CSM exceeds 65 accounts or $3M ARR
  - SMB pooled: queue response time exceeds 4 hours
```

**Verify**: Total CSM headcount cost (fully loaded) is 5-10% of total ARR. If above 10%, reduce ratios in lower tiers; if below 5%, consider adding coverage.
**If failed**: Rebalance tier thresholds — move the boundary between Mid-Market and SMB to shift accounts to the more cost-effective tier.

### Step 4: Build Playbooks Per Tier

**Duration**: 1-2 weeks
**Tool**: CS platform + document templates

Create lifecycle playbooks for each tier and each lifecycle stage. Each playbook defines trigger, owner, sequence of actions, timeline, and success criteria. [src5] [src6]

```
Playbook structure (repeat for each tier x lifecycle stage):

Playbook: [Tier] — [Lifecycle Stage]
  Trigger:          What initiates this playbook
  Owner:            CSM (named) | CSM (pooled) | automation
  Actions:
    Day 0:          [action]
    Day 7:          [action]
    Day 14:         [action]
    Day 30:         [action]
  Success criteria:  Measurable outcome that marks completion
  Escalation:       What happens if success criteria not met

Example — Enterprise Onboarding Playbook:
  Trigger:          Contract signed (Closed-Won in CRM)
  Owner:            Named Enterprise CSM
  Actions:
    Day 0:          Internal handoff from AE → CSM (notes, goals, stakeholders)
    Day 1:          Welcome email + kickoff scheduling
    Day 3-5:        Kickoff call (goals, timeline, success metrics, stakeholder map)
    Day 7:          Technical setup / integration configuration
    Day 14:         First value milestone check-in
    Day 30:         30-day health check + adoption review
    Day 60:         60-day success plan review with executive sponsor
    Day 90:         First QBR — ROI presentation + next quarter plan
  Success criteria:  3+ active users, core feature adopted, success plan documented
  Escalation:       If <2 users by Day 30, CSM manager intervention

Example — SMB Automated Onboarding Playbook:
  Trigger:          Account provisioned
  Owner:            Automation (CS platform)
  Actions:
    Day 0:          Welcome email with setup guide link
    Day 1:          In-app product tour launched on first login
    Day 3:          Email: "Complete your setup" (if setup incomplete)
    Day 7:          Email: "Here's what others do first" (best practices)
    Day 14:         Email: usage report + tips for adoption
    Day 30:         NPS survey + adoption milestone email
  Success criteria:  Product setup complete, 3+ logins in first 30 days
  Escalation:       If zero logins by Day 7, trigger pooled CSM outreach
```

**Verify**: At minimum, create playbooks for: onboarding, adoption risk, renewal prep, and expansion signal — across all tiers with assigned CSMs.
**If failed**: Start with onboarding playbooks only (highest impact), then add remaining lifecycle stages iteratively.

### Step 5: Implement Health Scoring

**Duration**: 1-2 weeks
**Tool**: CS platform

Design a multi-dimensional health score that combines product usage, support sentiment, engagement, and financial signals. Configure the score in your CS platform to drive automated actions. [src1] [src6]

```
Health score dimensions (weight to total 100):

  Product Usage (35%):
    - Login frequency vs expected baseline
    - Feature adoption breadth (% of contracted features used)
    - Usage trend (increasing / stable / declining)

  Engagement (25%):
    - CSM meeting attendance rate
    - Response time to CSM outreach
    - Training/webinar participation
    - Community activity

  Support (20%):
    - Open ticket count and severity
    - Time to resolution trend
    - Escalation frequency
    - CSAT scores on resolved tickets

  Financial (20%):
    - Payment timeliness
    - Contract size trend (expansion vs contraction)
    - Renewal date proximity
    - Multi-year vs annual contract

Score ranges:
  90-100: Healthy (green)  → Expansion opportunity, advocate candidate
  70-89:  Neutral (yellow) → Monitor, proactive engagement
  50-69:  At-risk (orange) → CSM intervention required within 48 hours
  0-49:   Critical (red)   → Immediate escalation to CS manager + exec sponsor

Per-tier response thresholds:
  Enterprise: yellow triggers CSM review; orange triggers same-day call
  Mid-Market: orange triggers CSM outreach within 48 hours
  SMB/Growth: red triggers pooled CSM outreach; orange triggers automated email
```

**Verify**: Run health scores against historical churn data — accounts that churned in the past 12 months should score below 60 retroactively. If not, adjust weights.
**If failed**: Start with a simple 3-factor score (usage + support + engagement) and iterate. Perfect is the enemy of shipped.

### Step 6: Set Up Automation Rules

**Duration**: 1-2 weeks
**Tool**: CS platform automation engine

Configure the automation rules that operationalize the coverage model — routing accounts, triggering playbooks, alerting CSMs, and running digital-touch campaigns. [src3] [src5]

```
Core automation rules:

Rule 1: New Account Routing
  Trigger:   New account created in CRM
  Logic:     If ACV >= $100K → assign to Enterprise CSM (round-robin by book size)
             If ACV $25K-$99K → assign to Mid-Market CSM (round-robin)
             If ACV $5K-$24K → assign to SMB pool
             If ACV < $5K → digital-only (no CSM assignment)
  Action:    Assign CSM, trigger onboarding playbook for tier

Rule 2: Health Score Alert
  Trigger:   Health score drops below tier threshold
  Logic:     Enterprise yellow → Slack alert to named CSM
             Mid-Market orange → Email + task created for CSM
             SMB red → Escalate to pooled queue priority
  Action:    Create task, send alert, log event

Rule 3: Expansion Signal
  Trigger:   Usage exceeds 80% of plan limits OR new department detected
  Logic:     Enterprise → Notify CSM + AE for expansion conversation
             Mid-Market → CSM outreach with upgrade positioning
             SMB → In-app upgrade prompt + automated email
  Action:    Create expansion opportunity in CRM

Rule 4: Renewal Prep
  Trigger:   Renewal date in 120 days (Enterprise) / 90 days (Mid-Market) / 60 days (SMB)
  Logic:     Run health check, generate renewal risk assessment
             If health < 70 → escalate to CSM manager
             If health >= 70 → standard renewal playbook
  Action:    Launch renewal playbook, create renewal opportunity

Rule 5: Tier Migration
  Trigger:   ACV changes (upgrade or downgrade at renewal)
  Logic:     If new ACV crosses tier boundary → reassign to appropriate tier
             Warm handoff between outgoing and incoming CSM
  Action:    Update tier, reassign CSM, notify both CSMs
```

**Verify**: Test each automation rule with 5 sample accounts. Confirm correct routing, correct playbook trigger, and correct alert delivery.
**If failed**: Disable the failing rule, run that process manually while debugging, and re-enable after fix.

## Output Schema

<!-- Exact format of the deliverable. -->

```json
{
  "output_type": "cs_coverage_model",
  "format": "document + spreadsheet",
  "components": [
    {"name": "tier_definitions", "type": "table", "description": "ACV boundaries, touch model, ratio per tier", "required": true},
    {"name": "capacity_model", "type": "spreadsheet", "description": "CSM headcount plan with ARR coverage and hiring triggers", "required": true},
    {"name": "playbook_library", "type": "document", "description": "Lifecycle playbooks per tier (onboarding, adoption, renewal, expansion)", "required": true},
    {"name": "health_score_spec", "type": "document", "description": "Dimensions, weights, thresholds, and response rules", "required": true},
    {"name": "automation_rules", "type": "configuration", "description": "CS platform automation rules for routing, alerts, and campaigns", "required": true}
  ],
  "expected_deliverables": "5 components",
  "sort_order": "execution sequence"
}
```

## Quality Benchmarks

| Quality Metric | Minimum Acceptable | Good | Excellent |
|---------------|-------------------|------|-----------|
| Tier coverage (% of accounts assigned) | > 95% | 100% | 100% with edge cases documented |
| CSM cost as % of ARR | 5-12% | 6-9% | 7-8% |
| Playbook coverage (lifecycle stages) | Onboarding + renewal | + adoption + expansion | All stages + escalation paths |
| Health score churn correlation | > 0.4 correlation | > 0.6 | > 0.75 |
| Automation rule test pass rate | > 80% | > 95% | 100% with edge case handling |

**If below minimum**: Revisit tier boundaries — if cost exceeds 12% of ARR, shift the Mid-Market/SMB boundary lower to move more accounts into tech-touch. If health score correlation is below 0.4, add more usage-based dimensions and reduce reliance on engagement signals.

## Error Handling

| Error | Likely Cause | Recovery Action |
|-------|-------------|----------------|
| ACV data missing for >10% of accounts | CRM data hygiene issues | Run CRM cleanup sprint; use product tier as proxy for ACV |
| Health scores cluster at 70-80 (no differentiation) | Weights too balanced, not enough signal variance | Increase usage weight to 45%, decrease engagement to 15%; add sharper thresholds |
| CSM burnout / account neglect in largest books | Ratio too aggressive for product complexity | Reduce ratio by 20%, add pooled backup support for administrative tasks |
| Playbook adoption <50% by CSM team | Playbooks too complex or not integrated into workflow | Simplify to 3-step playbooks, embed in CS platform task flow (not external docs) |
| Digital-touch emails have <10% open rate | Generic content, wrong cadence, or poor segmentation | A/B test subject lines, segment by usage pattern, reduce frequency |
| Tier migration causes customer confusion | No warm handoff process between CSMs | Implement 2-week overlap period where both old and new CSM engage |

## Cost Breakdown

| Component | Free Tier | Paid Tier | At Scale |
|-----------|-----------|-----------|----------|
| CS platform | Spreadsheet ($0) | Vitally/ChurnZero ($500-$2K/mo) | Gainsight ($3K-$10K/mo) |
| CSM headcount (fully loaded) | Founder-led ($0 incremental) | $80K-$120K/CSM/year | $100K-$150K/CSM/year (enterprise) |
| Email/in-app automation | Intercom free tier | Customer.io ($150/mo) | Integrated in CS platform |
| Analytics/BI | Google Sheets | Looker/Tableau ($500/mo) | Integrated dashboards |
| **Total for 500-account base** | **$0 (manual)** | **$15K-$25K/mo** | **$40K-$80K/mo** |

## Anti-Patterns

### Wrong: One-size-fits-all CSM assignment
Assigning every customer a dedicated CSM regardless of ACV creates unsustainable unit economics. A CSM managing 200 accounts at $3K ACV each cannot deliver meaningful engagement — they become a reactive ticket router, not a strategic partner. The result is high CSM turnover and no measurable impact on retention. [src2]

### Correct: Tier-matched engagement intensity
Match engagement depth to customer value and complexity. Enterprise accounts get dedicated CSMs with deep relationships. SMB accounts get automated journeys with human escalation only on red health scores. This preserves CSM capacity for accounts where human touch demonstrably impacts retention and expansion.

### Wrong: Setting ACV thresholds without data
Copying another company's tier boundaries (e.g., "$100K = enterprise") without analyzing your own ACV distribution creates tiers with wildly uneven account counts — one CSM with 5 accounts while another drowns with 150. [src1]

### Correct: Data-driven tier boundaries
Sort customers by ACV, identify natural clustering, and set thresholds where gaps naturally occur. Then validate by checking CSM load balance across tiers. Adjust boundaries until no tier creates a CSM ratio more than 2x different from the target.

### Wrong: Launching all tiers and playbooks simultaneously
Attempting to implement a full coverage model across all tiers, all lifecycle stages, and all automation rules in a single sprint overwhelms the CS team and produces half-finished automation that nobody trusts. [src5]

### Correct: Phase the rollout
Start with the highest-value tier (Enterprise) and onboarding playbook only. Stabilize for 30 days. Then expand to Mid-Market, then SMB digital-touch. Add lifecycle stages incrementally: onboarding first, then renewal, then adoption, then expansion.

## When This Matters

Use this recipe when a CS leader needs to design or restructure the coverage model — either for a team scaling past 3 CSMs, a company shifting from founder-led CS to a structured function, or an organization merging high-touch and digital programs. Requires customer list with ACV data and at least 12 months of churn history as inputs.

## Related Units

- [NRR Benchmarks for CS Model Validation](/finance/saas-benchmarks/net-revenue-retention-benchmarks/2026)
- [Health Score Design Recipe](/business/customer-success/health-score-design/2026)
- [CSM Playbook Library](/business/customer-success/csm-playbook-library/2026)
- [SaaS Churn Analysis Benchmarks](/finance/saas-benchmarks/saas-churn-benchmarks/2026)
- [Customer Success Strategy Overview](/business/customer-success/customer-success-strategy-overview/2026)