Building Customer Success From Scratch – Kerin Smollen

The practical threshold is 50–75 active accounts or $2M–$3M ARR, whichever comes first. Below that, a founder or account manager can maintain sufficient customer relationships personally. Above that threshold, relationship quality degrades – customers start feeling like accounts rather than partners, onboarding becomes inconsistent, and churn begins to climb. Companies that wait until churn is already elevated typically find that they have lost the customers who would have been their strongest references and expansion revenue sources. Building CS earlier – before the churn signal – is almost always cheaper than recovering from it after.

Account management is relationship maintenance – the goal is to preserve the relationship and handle renewals. Customer success is outcome management – the goal is to ensure the customer achieves the specific outcomes they purchased the product to achieve. CS is proactive: it monitors usage data, tracks adoption milestones, identifies health signals before they become churn signals, and intervenes before problems surface. Account management is typically reactive. Most early-stage B2B SaaS companies have account management and call it customer success. The distinction matters because the playbooks, skills, and metrics for each are different.

A customer health score is a composite signal – typically combining product usage data, support ticket volume and sentiment, QBR attendance, and stakeholder engagement. The inputs vary by product and customer profile, but the output is always the same: a categorization of each account into red, yellow, or green health tiers. Building one from scratch starts with a customer audit – identifying which customers churned in the past 12 months and what their leading signals looked like before they left. Those signals become the components of the health score. A usable health score does not require sophisticated data infrastructure – even a manual weekly review against five variables is more valuable than no tracking at all.

At $5M ARR with 100–150 accounts, a single experienced CS associate carrying 50–75 accounts with a strong playbook is typically sufficient as a starting point. The ratio of CS staff to accounts depends heavily on the complexity of the product and the effort required per account: high-touch enterprise products with complex implementations may require a 1:30 ratio, while self-serve or low-touch products can run 1:150. The more important variable than headcount is whether the CS person has a documented playbook to execute – a great hire without a playbook produces inconsistent outcomes, while a solid hire with a clear playbook produces predictable outcomes at scale.

The fastest churn reduction intervention is onboarding redesign. Research consistently shows that customers who do not fully complete onboarding churn at two to three times the rate of customers who do. Auditing your current customer base for onboarding completion and redesigning onboarding as a structured activation program – with defined milestones, human check-ins, and completion gates – typically produces measurable churn reduction within one to two quarters. The second fastest intervention is an at-risk account recovery motion: identifying the red-tier accounts through a health audit and running a structured save effort. Both are achievable before a full CS function is operational.