Role Playbook
SaaS
200-500 employees
VP Customer Success · Renewal & NRR Owner
You inherit the relationship the day after Sales walks away. That's the VP Customer Success OKR trap at 200-500 SaaS.
Health scores look fine until they don'tGreen-yellow-red dashboards stay green for months, then flip red 30 days before renewal — too late to recover.
Sales handoff is verbal, not contractualThe CSM inherits an account with one notes doc and a Slack thread. Implicit promises become explicit churn risk.
Expansion is a side hustle, not a motionRenewal-only CSMs leave 30%+ NRR upside on the table. Expansion needs a system, not a quarterly nudge.
Product roadmap is the silent riskThe customer asked for X, Sales said yes, Product said maybe, and you're the one explaining at renewal.
Sales mis-qualifies a deal
→
You absorb the churn 6 months later
Product slips a customer-promised feature
→
You defend the renewal
Support escalates a recurring issue
→
You renegotiate to save the account
The job isn't running QBRs. It's making upstream commitments auditable before the renewal call.
THE SCORECARD
Three VP Customer Success OKRs that defend the seat at 200-500 SaaS.
You don't run the renewals desk. You don't run the support team. You don't run onboarding. You own the three bets that turn the seat from QBR-time discovery into a tracked operating system — early risk surfacing, separated motions, handoff SLAs. Three objectives below.
| Objective | Key Result | Benchmark / Threshold | Target |
|---|
| Every at-risk account is identified ≥90 days before renewal — when there's still time to fix it O1 · Outcome state. The seat is defined by how early risk surfaces, not by how heroic the save plan is. |
100% of accounts reviewed weekly by named CSM — usage, exec engagement, support volume, NPSWeekly because monthly misses 3 weeks of leading-indicator decay; named because shared accountability is no accountability |
Quarterly QBR typical Threshold | 100% weekly |
| Renewal-risk forecast accuracy within ±5% at 90 days out — not ±15% at 30 days90 days is the recovery window; 30-day forecasts are too late to save anything |
±15-25% at 30d typical Threshold | ±5% at 90d |
| Gross retention ≥ 92% — independent of expansion mathGross retention isolates the churn problem from expansion success; 92% means logo and dollar churn are both in control |
88-90% typical Threshold | ≥ 92% |
| Renewal and expansion run as separate tracked motions — not one CSM conversation hoping for both O2 · Outcome state. Same CSM may run both, but the motions, the metrics, and the comp tied to each are kept separate. |
100% of CSMs have separate scorecards for renewal vs expansion — comp tied to both, but tracked independentlySeparation because when expansion depends on a successful renewal conversation, CSMs avoid the upsell to protect the renewal — and revenue leaks |
Combined typical Threshold | 100% |
| Expansion ARR ≥ 18% of starting ARR per year18% because top-quartile SaaS runs 20-25% expansion; below 12% means expansion isn't a motion, it's an accident |
8-12% typical Threshold | ≥ 18% |
| Net revenue retention ≥ 110% across the customer base for 4 consecutive quarters110% because below 105% the board models churn against bookings; 4 quarters because single-quarter NRR is volatile |
Median 106% (2024)1 Threshold | ≥ 110% |
| Sales-to-CS handoff completes within 7 days of close — every account, no exceptions O3 · Outcome state. Handoff quality determines whether the CSM learns the account in week 1 or at QBR-time. Late or thin handoffs are the structural cause of late-quarter churn surprises. |
≥ 95% of new accounts have completed handoff within 7 days — 5 required fields signed off by AE and CSM7 days because the customer's onboarding momentum is built or lost in week 1; 5 fields because more is theatre and less is verbal |
Verbal/post-mortem typical Threshold | ≥ 95% in 7d |
| AE scorecards reflect handoff quality — handoff completeness counts toward AE quota retire creditWithout consequence at the AE layer, handoffs stay verbal; AE comp is the only lever that makes handoff a Sales priority, not a CS request |
Not tracked typical Threshold | Yes |
1 ICONIQ Growth 2024 SaaS Benchmarks — median NRR 106%, top-quartile 120%+, top-decile 130%+. Gross retention benchmarks per Bridge Group 2024 SaaS AE Metrics + KeyBanc Capital Markets 2024 SaaS Survey.
How to start in week 1 of the quarter
Don't migrate Gainsight. Don't redesign QBRs. Do these five things:
→ Pull last 4 quarters of churn events. For each, identify the earliest leading indicator that bent (usage drop, exec change, support spike, NPS dip). Build the baseline: how many weeks of warning did the data show — even if nobody acted on it?
→ Define 4 leading indicators that get reviewed weekly per account: usage trend, exec engagement, support ticket volume, recent NPS. Anything else is monthly. Communicate the list to all CSMs.
→ Audit CSM-to-account ratios by tier. Where is ratio drift happening? Surface it as a quarterly conversation with CFO + CRO — ratio is a hiring decision, not a CS-team complaint.
→ Separate renewal and expansion motions in the CSM scorecard. Same CSM may run both, but the metrics are tracked separately so expansion isn't dependent on a successful renewal conversation.
→ Document Sales-to-CS handoff: 5 fields required (commitments made, expansion potential, key stakeholder, success criteria, risk flags). Anything else optional. Enforce at the Sales VP layer, not the CSM layer.
Why O2 is the seat-defining objective
O1 is what the board watches. O3 is what your CSMs feel. O2 is what makes either possible. When risk surfaces at week 1 instead of month 6, O1 becomes predictable and O3 becomes structural rather than heroic.
STRATEGIC BETS
The three bets inside every VP Customer Success OKR stack — and the dozen your team runs without you.
Your renewals manager runs the actual contract negotiation. Your support lead runs ticket triage. Your operations analyst runs the health-score formula. You don't. Your job is the three bets that turn renewal from recovery into confirmation, separate expansion from upsell, and align CSM workload with account complexity.
Strategy 1 — Replace lagging health scores with leading-indicator KRs
→ O2
1.1
Define 4 leading indicators per account: product usage trend, exec engagement frequency, support volume + sentiment, recent NPS — refreshed weekly
CSM team + Data team
1.2
Trend-bending alerts: any leading indicator dropping 2 weeks in a row fires to CSM owner, regardless of overall health-score color
Internal
1.3
Quarterly health-score recalibration — backtest against last quarter's churn events; if churns weren't visible 90+ days out, the indicators are wrong
Data team
1.4
Renewal-risk forecasts run at 90 / 60 / 30 day intervals, not just at quarter-end — accuracy tracked weekly
Internal
Strategy 2 — Replace upsell-when-lucky with a separated expansion motion
→ O1
2.1
Separate renewal and expansion in the CSM scorecard — different KRs, different cadences, different reviews
All CSMs
2.2
Expansion-trigger playbook: 6 trigger events (usage hits a threshold, headcount growth at customer, new exec sponsor, etc.) each have a defined CSM motion
All CSMs + RevOps
2.3
High-touch tier gets a dedicated expansion conversation quarterly — separate from QBR, separate from renewal
High-touch CSMs
2.4
Expansion attribution clean — credit shared with Sales when AE materially involved, but expansion KR sits with CS
CRO + CFO
Strategy 3 — Replace verbal Sales-CS handoff with a tracked dependency
→ O3
3.1
Required handoff fields: commitments made, expansion potential, key stakeholder, success criteria, risk flags — enforced at AE scorecard level
CRO + Sales VPs
3.2
Week-1 onboarding plan templated and run by CSM with explicit success criteria — customer signs off on the criteria within 7 days of contract
All CSMs
3.3
Handoff-quality KR tracked at the AE level — CSMs flag bad handoffs, AE scorecards reflect it
CRO
3.4
Sales commits to product features captured at deal-close, fed into Product roadmap as tracked dependencies — Product owns the response
CRO + CTO
ENFORCEMENT LAYER
Enforcement for VP Customer Success OKRs — the cadence layer above your CS tools.
Gainsight tracks health scores. Catalyst tracks customer journeys. Your CRM holds renewal dates. Each runs in one lane. None enforces whether the leading indicators were reviewed weekly, whether handoff dependencies cleared, or whether expansion triggers fired. That's the cadence layer above your stack.
How this works in practice
→ Your CS team enters KR values weekly — usage trend, exec engagement, handoff status
→ Each becomes a tracked KR with an owner
→ ShiftFocus runs the cadence and fires triggers when KRs bend
We don't pull from Gainsight or your CRM. We make the retention KRs your team already maintains catch churn at week 1, not month 6.
Two triggers define daily pain: Trigger 3 (Momentum Decay) when health-score leading indicators bend, and Trigger 6 (Dependency SLA Breach) when an upstream dependency from Sales, Product, or Support breaks the retention KR.
The two that fire hardest at the VP CS layer
Trigger 3 · Momentum Decay — when leading indicators bend before the renewal lands
⚡ Fires whenAny leading-indicator KR for an account — usage trend, exec engagement frequency, support volume, NPS — trends wrong for 2 consecutive weeks. Threshold
▎ Why this matters
Churn shows up at renewal. The behavior shift that causes it shows up 5 months earlier. Trigger 3 fires the moment the trend bends — when there's still time for a CSM-led save conversation, not after the customer has decided.
▎ Why ShiftFocus catches it
Gainsight tracks health score (lagging composite). Pendo tracks usage (single dimension). Each lives in its own dashboard. ShiftFocus runs all the leading-indicator KRs through one weekly cadence — when two bend in the same account same week, you see it before either becomes a churn signal.
▎ Example scenario
Week 6: account's "Weekly active users" KR drops 22% over 3 weeks. Same week, support-ticket-volume KR ticks up. Trigger fires. CSM gets the alert with both KRs called out — not "health score dropped to yellow" with no explanation.
Trigger 6 · Dependency SLA Breach — when upstream commitments to retention skip
⚡ Fires whenAn upstream dependency tracked as a KR — Product roadmap commit promised in a deal, Engineering bug-fix SLA on a critical-account issue, Sales handoff documentation overdue — misses its SLA by >48h. Threshold
▎ Why this matters
Every retention KR depends on upstream commitments holding. When Product slips a roadmap item or Sales skips handoff fields, your renewal conversation gets harder months later. ShiftFocus tracks those upstream commits as KR-level dependencies. When breached, the cost attributes upstream — not to CS for "the customer is unhappy."
▎ Why ShiftFocus catches it
Jira tracks engineering tasks but doesn't link them to retention KRs. Salesforce holds the deal but doesn't track the post-deal commitments. ShiftFocus runs the cadence layer where every commitment to a customer is a tracked dependency — and missing it fires a trigger that attributes to the function, not to CS.
▎ Example scenario
Q2 deal: Sales committed feature X to enterprise customer for Q3. Logged as a Product dependency. Q3 week 6: Product slips X to Q4. Trigger fires to CTO + CRO + VP CS. Tuesday's exec meeting opens with "feature X is breached on 4 enterprise accounts; renewal exposure ~$1.2M; here's the recovery plan" — not VP CS in DMs trying to reschedule the renewal.
The other 4 that also fire on your KRs
Trigger 1 · Missed Cadence
⚡ WhenCSM skips weekly health-review on an at-risk account, or QBR cadence skipped 2 quarters in a row.
▎ Example scenario
Mid-Market CSM skipped 2 weekly reviews on a yellow account. Trigger fires to CSM's manager — not VP CS in DMs.
Trigger 2 · Velocity Drop
⚡ WhenRenewal-process velocity slows — discovery-to-close cycle stretches past 60 days, or expansion conversations stall in pipeline.
▎ Example scenario
Q3 renewal pipeline: avg cycle 75 days vs. plan 50. Trigger fires — process review with renewal manager.
Trigger 4 · KPI Drift
⚡ WhenNRR drops below 105%, OR gross retention drops below 90%, OR expansion ARR drops below 12%.
▎ Example scenario
Mid-quarter NRR projection: 103%. Threshold breached. Trigger fires — root-cause review with Sales + Product + CS.
Trigger 5 · Owner Absence
⚡ WhenAccount has no named CSM (default-assigned to "team"), or owner-of-record stale >90 days after tier change.
▎ Example scenario
Audit: 8 accounts in Mid-Market tier with no named CSM. Trigger fires — assignment review.
Why this works alongside your existing CS stack
Gainsight holds health scores. Catalyst maps journeys. Pendo tracks usage. Salesforce holds renewals. Each does its job. ShiftFocus is the cadence layer above them — every Sales/Product commitment becomes a tracked SLA, trend-bending fires before the renewal is contested, and retention KRs run on one weekly review.
ESCALATION DESIGN
The VP Customer Success escalation chain — 5 levels, all on a 48-hour clock.
Every trigger feeds into this ladder. The ladder climbs on time, not on judgment. Below is a single Product-roadmap dependency breach (committed feature slipping past commitment date for an enterprise account) threaded through all five rungs.
L1
Auto-Nudge — to Product owner
Friday 4pm: feature X commitment dependency overdue. Trigger 6 fires. Product PM + Eng lead get Slack + email: dependency overdue, 48h SLA window, status update required. Initiative flags yellow.
Immediate
L2
Peer Flag — CTO + CRO + VP CS see it
Monday morning: still unresolved. Tracked dependency surfaces in CTO, CRO, and VP CS dashboards. Peer pressure resolves it without VP CS becoming the chaser.
+48h
L3
CTO Review — direct conversation with PM
Tuesday: still stuck. CTO directly asks the PM for status and re-commit. The conversation is between CTO and PM — VP CS stays out of it, owning the customer impact, not the feature debate.
+48h
L4
Pattern Brief — recurring breaches surface
Q3 audit: 4 Sales-committed features have slipped this quarter. Pattern goes to CTO + CRO + VP CS — not the individual instances. "Sales-Product commit reliability" becomes a quarterly operating concern, not a CS chase.
Week 7
L5
Intervention — operating-cadence review
3 weeks before quarter close. Renewal exposure projecting $2M+ from Sales-committed features slipping. Full GTM + Product exec team in the room. Decision: tighten Sales-Product commitment process, or accept the structural NRR risk and re-baseline retention forecast.
T-3 weeks
What this kills
The failure mode where you spend Q3 explaining feature slips to 4 enterprise customers, present a clean QBR Monday that's already missing 2 commits, and absorb renewal-risk damage at QBR for decisions that didn't have SLAs in the first place. Trigger 6 fires the moment a feature commit dependency breaches — at the function, not your desk.
EXECUTION INTELLIGENCE
How the 5 ShiftFocus metrics read on your VP CS KRs.
ShiftFocus runs five health metrics on every KR — same five whether the KR is "NRR ≥ 110%" or "Health-score leading indicators reviewed weekly" or "CSM ratio matches ACV tier." You don't need to compute them. The point is reading them. Here's what each tells you on a VP CS KR.
What this looks like at week 6 of Q3
$40M ARR SaaS, 320 employees. VP CS has three OKRs running. Here's how the metrics read across them, mid-quarter:
What the retention gap actually costs
The primary case is operating quality. Dollar leakage varies by ARR — but three costs reliably stack the same year:
→ Surprise churn at renewal week — recovery rate <25% at 30d vs >70% at 5 months
→ Expansion missed because the motion isn't separated — CSMs avoid the upsell to protect the renewal
→ Onboarding rework from thin handoffs — implementation team rebuilds context the AE already had
Each costs more than the cadence investment that prevents it.
The case to make to your CEO
Convert "why is NRR dropping?" into "of 11 churns this quarter, 4 trace to mis-qualified deals 3 quarters back, 3 to roadmap slips, 2 to support escalations; here's the recovery plan." The seat-defining moment is when your CEO stops asking about retention — because the function explains itself.
▶ Pilot-verifiable
See where your retention KRs actually break — and which upstream function caused it.
Connect your CS, CRM, and Product systems. We'll audit the last 4 quarters for churn-trace patterns, leading-indicator drift, and Sales-Product-Support handoff breaches — and show you which functions' missed commits caused which renewal risks, account by account, week by week.