Customer Success Architect

Type: Agent Prompt Confidence: 0.88 Sources: 6 Verified: 2026-03-13

Agent Overview

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.

Input → Output Summary

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)     |
                                 +------------------------------+

Key Deliverables

Execution Pipeline

  1. Customer Journey Mapping — map 5 lifecycle stages (signup, onboarding, activation, expansion, renewal) with entry criteria, touchpoints, and risk indicators
  2. Onboarding Flow Design — 3-5 activation milestones with target dates, verification methods, automation triggers, and fallback actions
  3. Health Score Model — 6-category weighted scoring (usage 40%, adoption 15%, support 15%, sentiment 15%, commercial 10%, engagement 5%) with daily updates
  4. Churn Prevention System — 8-10 early warning indicators, intervention playbooks by risk level, involuntary churn dunning automation
  5. Expansion Revenue Strategy — NRR targets by segment, usage-based upsell triggers, need-based cross-sell triggers, expansion motion design
  6. Support Tier Design — self-serve, guided, and high-touch tiers with CSM ratios and SLAs
  7. QBR & Check-in Cadence — agenda template, preparation checklist, and cadence by tier
  8. Customer Feedback Loop — NPS program, CSAT surveys, product feedback routing
  9. Renewal Process — 90/60/45/30/14/7-day milestones with risk scoring and pricing guardrails
  10. CS Metrics Dashboard — NRR, GRR, churn, TTV, health distribution, NPS with 2026 benchmarks

Gate Conditions

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.

Key 2026 Benchmarks

Hard Constraints

When This Matters

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.

Related Units