Enterprise Customer Success Playbook

Executive engagement in enterprise accounts is the highest-leverage CS activity — a strong relationship with the executive sponsor protects ARR during organizational changes and enables expansion conversations at the right level. Executive engagement framework: Executive Business Review (EBR): distinct from the standard QBR, the EBR is a 30–45 minute meeting with the executive sponsor (VP or C-level) and the vendor's VP of CS or executive sponsor. Frequency: biannual or annual. Format: strategic, business-outcome focused. The executive does not want to see product roadmap slides — they want to understand the business value their investment has delivered (ROI), where the relationship is going at a strategic level, and assurance that their team is being served well. Executive sponsor newsletters: for executives who are difficult to get face time with, a quarterly "Executive Update" email (3–4 bullet points maximum: business outcomes achieved, upcoming product direction relevant to their business, any operational updates) keeps the relationship warm without requiring a meeting. Escalation access: enterprise executives want confidence that they have a "phone a friend" relationship with senior vendor leadership if something goes very wrong. The VP of CS's contact information shared directly with the executive, with the explicit invitation to reach out for significant concerns, is a relationship investment that is rarely activated but extremely valuable for retention.

Enterprise onboarding is a multi-stakeholder, multi-phase process with a timeline measured in months, not days. Key differences from SMB: Stakeholder breadth: enterprise onboarding involves executive sponsors (who need ROI confirmation), department managers (who need workflow integration), IT and security (who need configuration and compliance documentation), project managers (who run the implementation timeline), and end users (who need training). A structured kickoff meeting with all identified stakeholders (not just the champion) in the first week prevents stakeholder-gap surprises. Formal project plan: enterprise onboarding requires a written project plan with milestones, owner assignments, and a target go-live date — shared with the customer at kickoff and updated bi-weekly. Integration work: enterprise accounts typically require integrations with existing systems (SSO, CRM, BI tools) that add configuration time and require IT involvement. The CSM must identify these integration dependencies in the discovery call before onboarding starts and factor them into the project timeline. Success criteria agreement: in the kickoff, the CSM facilitates a conversation to define what "successful onboarding" and "value realization" look like in measurable terms for this specific customer. These agreed success criteria become the framework for QBR reporting. Training: enterprise accounts receive structured training programs — live training sessions for admins, department leads, and end users — rather than self-serve learning resources alone. Record all training sessions for replay by users who miss the live session.

Enterprise account risk management is the discipline of identifying accounts at elevated churn or contraction risk early enough to intervene effectively — before the customer has already made a mental decision to leave. Risk identification signals: health score deterioration: any account whose health score declines by > 15 points month-over-month without an identified explanation is flagged for immediate CSM review. Product usage decline: key feature adoption declining > 20% over 30 days in an account with no known planned usage pause. Executive sponsor departure: the champion or economic buyer leaves the company — a documented "sponsor departed" event triggers an automatic CTA for the CSM to map new stakeholders within 2 weeks. No QBR in > 150 days for an Enterprise tier account. Unresolved escalation > 30 days. Risk classification: when a risk signal is triggered, the CSM classifies the account as: Yellow (monitored risk — CSM takes proactive action to address, no management involvement required) or Red (critical risk — CSM escalates to CS Manager for joint account strategy, executive engagement initiated). Risk mitigation playbook: each risk classification has a specific playbook. Red accounts: immediate executive outreach from VP of CS; full account health diagnostic; accelerated QBR with roadmap visibility; SLA credit or service recovery gesture if a specific grievance exists. Response timeline: Red classification → first risk response action within 24 hours.