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

• 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

• ACV thresholds must be calibrated to your specific business — the tiers below are industry medians, not universal rules. [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. [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). [src2]

Tool Selection Decision

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

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, ratio 1:10-25 accounts
Mid-Market (Hybrid):        ACV $25K-$100K
  - Named CSM with higher book, ratio 1:40-75 accounts
SMB / Growth (Tech-Touch):  ACV $5K-$25K
  - Pooled CSM team or digital-only, ratio 1:100-200 accounts
Self-Serve (Digital-Only):  ACV < $5K
  - No CSM, fully automated lifecycle campaigns

Verify: Every active customer is assigned to exactly one tier. Tier distribution roughly follows: 5-15% Enterprise, 20-30% Mid-Market, 50-70% SMB/Growth. · If failed: If more than 40% of ARR concentrates in one tier, consider splitting that tier further.

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: onboarding, adoption, value delivery, renewal, expansion, and escalation. [src3]

Enterprise: CSM-led onboarding (30-60-90), weekly check-ins, quarterly QBR
Mid-Market: CSM-assisted onboarding + email drip, monthly calls, semi-annual review
SMB/Growth: Automated emails + in-app tours, lifecycle campaigns, pooled escalation
Self-Serve: In-app welcome flow, behavioral triggers, community support

Verify: Every lifecycle stage has a defined touchpoint for every tier. No gaps. · If failed: Map missing 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. Calculate: accounts per tier / target ratio = required CSMs. Validate that ARR per CSM stays below $5M. Add 15% buffer for PTO, ramp, and attrition. [src2] [src4]

Capacity formula per tier:
  Required CSMs = (accounts in tier / target ratio) * 1.15 buffer
  Validate: ARR in tier / CSMs < $5M per CSM

Hiring triggers:
  Enterprise: any CSM exceeds 20 accounts
  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 failed: Rebalance tier thresholds 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 lifecycle stage. Each playbook defines trigger, owner, sequence of actions, timeline, and success criteria. [src5] [src6]

Playbook structure per tier:
  Trigger → Owner → Day 0-90 actions → Success criteria → Escalation path

Minimum playbooks needed:
  - Onboarding (all tiers)
  - Adoption risk intervention (all tiers with CSMs)
  - Renewal prep (all tiers)
  - Expansion signal response (Enterprise + Mid-Market)

Verify: At minimum, onboarding + renewal playbooks exist for every tier with assigned CSMs. · If failed: Start with onboarding playbooks only, then expand iteratively.

Step 5: Implement Health Scoring

Duration: 1-2 weeks · Tool: CS platform

Design a multi-dimensional health score combining product usage (35%), engagement (25%), support (20%), and financial signals (20%). Configure score ranges: green (90-100), yellow (70-89), orange (50-69), red (0-49). Set per-tier response thresholds. [src1] [src6]

Health dimensions:
  Product Usage (35%): login frequency, feature adoption, usage trend
  Engagement (25%): meeting attendance, response time, training participation
  Support (20%): ticket count/severity, resolution trend, CSAT
  Financial (20%): payment timeliness, contract trend, renewal proximity

Verify: Run scores against historical churn data — churned accounts should retroactively score below 60. · If failed: Start with a simple 3-factor score and iterate.

Step 6: Set Up Automation Rules

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

Configure automation rules for account routing (by ACV tier), health score alerts (per-tier thresholds), expansion signal detection, renewal prep triggers, and tier migration handoffs. [src3] [src5]

Core automation rules:
  1. New account routing by ACV tier → assign CSM + trigger onboarding
  2. Health score drop alert → tier-appropriate CSM notification
  3. Expansion signal → usage threshold → CSM or in-app prompt
  4. Renewal prep → 120/90/60 day triggers by tier
  5. Tier migration → ACV change → reassign with warm handoff

Verify: Test each rule with 5 sample accounts. Confirm correct routing and alert delivery. · If failed: Disable failing rule, run process manually while debugging.

Output Schema

{
  "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", "required": true},
    {"name": "health_score_spec", "type": "document", "description": "Dimensions, weights, thresholds, response rules", "required": true},
    {"name": "automation_rules", "type": "configuration", "description": "CS platform automation rules", "required": true}
  ]
}

Quality Benchmarks

If below minimum: Revisit tier boundaries — if cost exceeds 12% of ARR, shift the Mid-Market/SMB boundary lower. If health score correlation is below 0.4, increase usage-based dimensions.

Error Handling

Cost Breakdown

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 with high turnover and no measurable impact on retention. [src2]

Correct: Tier-matched engagement intensity

Match engagement depth to customer value. Enterprise accounts get dedicated CSMs with deep relationships. SMB accounts get automated journeys with human escalation only on red health scores.

Wrong: Setting ACV thresholds without data

Copying another company's tier boundaries without analyzing your own ACV distribution creates tiers with wildly uneven account counts. [src1]

Correct: Data-driven tier boundaries

Sort customers by ACV, identify natural clustering, set thresholds where gaps naturally occur, and validate CSM load balance across tiers.

Wrong: Launching all tiers simultaneously

Attempting to implement a full coverage model across all tiers in a single sprint overwhelms the CS team and produces half-finished automation. [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.

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.