Build Your CS Playbook in 90 Days – Kerin Smollen

The churn problem most founders misdiagnose

Annual churn between 15% and 25% at early-stage B2B SaaS is almost never a product problem. It is an onboarding problem that became a churn problem. Customers who do not reach their first meaningful outcome within 45 days rarely renew. Without a documented onboarding sequence, no one on the founding team has a clear picture of what "reaching first value" actually requires, which customers are on track, and which are at risk. That diagnostic blindness costs 12–18% in annual churn that is entirely recoverable with the right infrastructure.

What a CS playbook actually contains – and what most companies skip

A complete CS playbook includes five components most companies build in the wrong order: a documented onboarding sequence with day-by-day milestones from contract signature through first value moment; a health scoring model with 5–8 metrics that reliably predict renewal versus churn; a QBR template calibrated to customer business outcomes, not your product's feature list; an escalation protocol that tells every customer-facing person what to do when a customer shows churn signals; and a renewal playbook that begins 90 days before contract end, not 30. Most companies skip three and four and wonder why churn remains stubbornly high.

When to build the playbook vs. when to hire first

The conventional wisdom is to hire the CSM and let them build the playbook. This produces two bad outcomes: the CSM spends their first 90 days doing infrastructure work instead of customer work, and the playbook reflects one person's preferences rather than the company's institutional knowledge. The better sequence is to build the playbook first, then hire the CSM into a documented system. At $2.5M to $4M ARR with 30–60 customers, a 90-day playbook build costs a fraction of one CSM salary and makes every future CSM more effective from week one.