Engagement snapshot
- Mandate
- Give CSMs one coherent operating system for customer health and renewal execution.
- Timeline
- 10 weeks from stack audit to target-state rollout plan.
- Team shape
- VP Customer Success, RevOps lead, 2 solution architects, and 4 frontline CSMs.
The problem
CSMs built renewal and risk views manually because health signals were spread across several tools with inconsistent definitions.
What we built
Redesigned the CS stack, standardized account health logic, and wired together support, usage, CRM, and renewal workflows.
Operating context
The company had invested in customer-success tooling but still relied heavily on manual prep. Health scores and renewal views were inconsistent because no one had fully aligned the underlying systems and definitions.
Key constraints
- The target state had to fit existing sales and support workflows.
- Account health logic needed to be explainable to CSMs and leadership.
- The redesign needed to reduce prep work without creating a brittle over-automated stack.
What we built
Health signal model
Standardized the account signals and definitions used across CS, support, and revenue workflows.
Workflow integration design
Connected usage, ticketing, CRM, and renewal actions into cleaner handoff paths.
Governance and reporting
Assigned ownership for health logic, field changes, and reporting maintenance.
Delivery path
Current-state audit
Mapped how CSMs currently prepared renewals, escalations, and QBRs across the live stack.
Target-state design
Defined a simpler account health model and the system roles needed to support it.
Rollout planning
Sequenced integration, reporting, and enablement work so the client could implement safely.
Why it mattered
The unification effort helped because it reduced disagreement about customer state. CSMs spent less time building their own version of the truth and more time acting on a shared one.
Implementation notes
- Health scores only help when the underlying definitions are stable and explainable.
- Customer-success tooling should reduce prep work, not just display more dashboards.
- Renewal workflows improve once support, usage, and CRM events use cleaner contracts.