Prism

CS Operating Model

Prism Customer Success Handbook — Section 1.2

Mission

Prism's CS function exists to make sure customers reach and keep crossing the adoption milestones that make white-label reporting stick with their clients (see PRODUCT_ONE_PAGER.md). Revenue follows adoption, not the other way around: an account that gets its clients onto the Portal renews and expands; an account that builds dashboards nobody outside the company sees churns regardless of how "engaged" it looks internally.

Single CSM (Matt) covering the full book. No pods, no segment specialists, no manager layer — every process below is designed for one person to run consistently across the whole book, not for a team to divide up.

Segmentation & coverage model

The book skews heavily SMB by count, with a small Mid-Market tier and a handful of Enterprise accounts — roughly an 80/16/4 split. (Exact counts live on the Executive Dashboard, computed live from the database; this page describes proportions and logic, not a headline number that goes stale the moment the book changes.) Segmentation is by ARR band with a support-and-motion overlay, not ARR alone — ARR-only segmentation is a known CS anti-pattern because it ignores implementation complexity and stakeholder count, which is what actually drives CSM effort.

Segment Share of book Coverage motion Why
SMB Large majority Tech-touch: dashboard-driven, exception-based outreach, quarterly light-touch check-in Low deal complexity, single buyer/user overlap, high volume — 1:1 coverage would be unsustainable for a solo CSM. Health monitoring does the watching; the CSM's time goes to accounts the dashboard flags.
Mid-Market Small minority Low-touch: monthly cadence call, EBR-lite twice a year Enough ARR concentration and stakeholder count to justify scheduled time, not enough to warrant Enterprise-level investment.
Enterprise A handful High-touch: full EBR cadence, named relationship, IT/security stakeholder engaged at onboarding Highest ARR concentration, multi-stakeholder buying and usage (practice lead + IT, per PRODUCT_ONE_PAGER.md), highest revenue-at-risk per account. Small enough in number that a solo CSM can genuinely go deep on each one.

Why not equal coverage across the book: unlimited customization or uniform high-touch doesn't scale to one person, and it wastes attention on accounts that don't need it. Segment-differentiated coverage is what makes solo coverage of a large book defensible instead of a fiction.

Rejected alternative: industry-based segmentation (e.g., "legal accounts get one motion, logistics another"). Rejected because Prism's product motion (Connect → Studio → Portal → Scheduler → Insights) is identical regardless of the customer's industry — what differs is deal size and stakeholder complexity, which ARR band already captures. Industry affects the content of conversations (referenced in the Playbook Library's discovery questions), not the coverage motion.

Metrics the CSM owns

  • Composite health score and its four sub-scores (Product Adoption, Support Issues, Stakeholder Engagement, Success Plan Progress) — segment-differentiated weighting, documented in 1.6 Health Scoring Methodology
  • Risk Level — the second signal layered on health, catching compounding risk that a single composite number hides
  • Renewal forecast category (Commit / Likely / At Risk / Unknown) — a judgment call, not a derived number; see the Renewal Motion playbook (3.7 Renewal Motion) for why that's a deliberate design choice, not a gap
  • At-risk ARR and upcoming renewal volume — reported at the book level via the Executive Dashboard

Explicitly not owned by the CSM in v1: NRR/GRR (requires expansion/contraction history not in the data model — rejected as a fabricated-looking metric rather than approximated, see decision log), billing/invoicing, VoC/NPS.

The CSM role at Prism

One person runs discovery, onboarding, adoption tracking, health monitoring, risk mitigation, renewal forecasting, expansion identification, and escalation handling across all three segments. The role is deliberately generalist, not specialized by function (no separate onboarding specialist, no renewals manager) — at this company size, splitting those functions would create handoffs with no one to hand off to.

This is also the honest interview framing: Prism's CSM role is what a CSM role at a 50–200 person B2B SaaS company genuinely looks like — broad scope, judgment-heavy, systems-building as part of the job rather than a separate function.