Role: Designs the complete customer success function — customer journey mapping, onboarding flows, health scoring models, churn prevention systems, expansion revenue triggers, support tier design, QBR cadence, and CS metrics dashboards — producing a ready-to-execute CS playbook.
Type: document_producer
Phase: 5.5 (Customer Success) — runs after Sales Process (5B) is complete
Trigger: Sales Process complete with defined handoff process. Skip if pre-revenue with no beta users; queue for after first 5 customers.
INPUTS: OUTPUTS:
+-----------------------+ +------------------------------+
| Startup Brief |---+ | Customer Success Playbook |---> Operations Builder
| (product, pricing) | | | (journey, onboarding, health |---> Dashboard
+-----------------------+ | | scoring, churn prevention, |
| Buyer Personas |---+--> | expansion, support, QBR, |
| (segments, needs) | | | renewal, metrics) |
+-----------------------+ | +------------------------------+
| Sales Process |---+ | Health Score Model Spec |---> KPI Architect
| (handoff criteria) | | (signals, weights, thresholds|---> Dashboard
+-----------------------+ | data sources, calculation) |
| Pricing Model |---* +------------------------------+
| (optional) | | Onboarding Flow Diagram |---> Operations Builder
+-----------------------+ | (milestones, automation) |
+------------------------------+
Before: Sales Process (5B) complete so the sales-to-CS handoff process is defined. Without a clear handoff, onboarding starts with information gaps.
After: CS playbook reviewed by user; can be queued for execution after first 5 customers if pre-revenue.
Skip if: Pre-revenue and no beta users yet. Queue for execution after first 5 customers.
Invoke in Phase 5.5 after the Sales Process (5B) is complete. The CS Playbook feeds the Operations Builder (who integrates CS workflows into team structure and tooling) and the KPI Architect (who builds the company-wide metrics dashboard). A structured CS function is the single highest-leverage investment for NRR — companies with formal CS programs see 10-20 percentage points higher retention. Can be skipped for pre-revenue startups with no users; queue for execution after first 5 customers.