Reference · Anytime

Customer Success Playbook

Situational reference for every recurring customer scenario. Pick a situation on the left — get triggers, stakeholders, do's & don'ts, conversation starters, orchestration, and signals to watch.

🏗️
Phase · Nurture → Strengthen (Run-the-Bank mode)

Delivery-Centric Account (Mission-Critical Platform)

Trigger
Customer's core business runs on the platform — LOS/LMS/SCF powering live disbursement, collections, or regulatory submissions. Every hour of friction = real money or compliance risk. Adoption metrics, FTV, and feature-usage scores matter less than delivery reliability, TAT on changes, and incident response.
Objective
Be measured the way the customer is measured — uptime, change TAT, incident response, regulatory readiness — not by SaaS-vanity metrics.
Stakeholders to align
  • COO / Head of Operations
  • Head of Tech / IT
  • Compliance / Risk Officer
  • CS + Delivery + Engineering on-call
Tools you'll use
  • Delivery Scorecard
  • Reliability / Uptime Report
  • Change & Release Calendar
  • Escalation Matrix
  • RCA Template
Do
  • Replace generic health score with a delivery scorecard — uptime, P1 MTTR, change TAT, regulatory submission readiness, CR cycle time (see Toolkit → Delivery-Centric).
  • Run a weekly delivery review (not a monthly CS call) with ops + tech + CS in the room — see Cadence → Delivery-Centric row.
  • Pre-commit a quarterly capacity slot for unplanned regulatory or business-driven changes — track in the Regulatory Change Tracker.
  • Publish a monthly reliability report — incidents, RCAs, change calendar, audit-log readiness — even if the customer never asks.
  • Maintain a named on-call CS + engineering pair; share direct numbers and the Escalation Matrix the customer's COO has approved (aligns with the P1/P2/P3 levels in the Escalation Guide).
Don't
  • Do not push adoption %, NPS, or feature-usage as the headline metric — it signals you don't understand their business.
  • Do not run pure 'success' QBRs here — convert the first 30 minutes into a delivery & risk review.
  • Do not bundle regulatory / mandatory changes into normal CR queues — they need a fast-track lane.
  • Do not expand commercials or push new modules while a P1 or audit observation is open.

Conversation starters

"Your business runs on this platform — so let's measure us the way your board measures you: uptime, TAT on change, incident response, audit-readiness. Can we align on that scorecard?"
"RBI has issued [X] circular due in 45 days. We've reserved capacity in this sprint — here is our delivery plan. Confirm whether anything else competes for the same window."
"Instead of a monthly CS call, can we move to a 30-minute weekly delivery huddle with your ops and tech leads? Same agenda every week: incidents, changes, risks."

Orchestration timeline

  1. 1.Week 1: Replace standard health view with a delivery scorecard agreed with the customer's COO
  2. 2.Weekly: 30-min delivery huddle — incidents, open P1/P2, change calendar, regulatory items
  3. 3.Monthly: Publish reliability report + RCA digest within first 5 business days
  4. 4.Quarterly: Delivery & risk review with ops, tech, compliance — roadmap discussed only after delivery trust is confirmed
  5. 5.Always-on: Named on-call pair, pre-reserved regulatory capacity slot, fast-track lane for compliance CRs
Positive signals
  • COO/Head of Ops attends the weekly huddle personally
  • Customer routes regulatory deadlines through CS before raising tickets
  • Audit / regulator references the platform positively in customer's internal review
Anti-signals
  • Customer's tech team starts CC'ing leadership on routine tickets
  • Repeat P1s in the same module within 30 days
  • Missed or delayed regulatory change window
Target outcome

Customer's COO and Head of Tech treat CS as an extension of their own delivery org. Renewal and expansion conversations follow naturally from delivery trust, not from selling.

Cadence: Weekly delivery huddle · Monthly reliability report · Quarterly delivery + risk review (replaces standard QBR)