Building a Customer Success Team Is Not a Headcount Exercise
If your answer to increasing churn is "we need more CSMs," you may be solving the wrong problem.
I have seen Customer Success organizations built in very different ways: from a handful of generalist CSMs in a startup to large regional teams managing complex enterprise portfolios.
One thing is consistent: the CS organization that got you to the next stage is rarely the organization you need at the next stage.
Early on, generalists are usually the right answer. You need people who can onboard customers, drive adoption, handle escalations, support renewals, and figure things out along the way. There isn't enough scale, or enough learning, to justify building a complicated organization.
But at some point, that model stops working.
Growth changes the job
As the customer base grows, customers become more diverse. Some need a strategic, high-touch relationship. Others can be successfully managed through digital engagement. Some require deep technical expertise, while others need a highly structured onboarding experience.
This is where segmentation becomes critical.
I don't like segmentation based only on ARR. ARR is important, but it doesn't tell you the whole story. Customer complexity, product adoption, number of stakeholders, geography, implementation requirements, and growth potential all affect the amount of CS capacity required.
A $500K customer with one product and a straightforward deployment may require less effort than a $200K customer with multiple products, integrations, countries, and executive stakeholders.
Capacity should follow complexity and value—not an arbitrary number of accounts per CSM.
From generalists to leverage
As the organization scales, I typically look at introducing specialization where it creates leverage.
That could mean dedicated onboarding, Technical Account Management, Renewal Management, CS Operations, or a scaled/digital CS motion.
The CSM should increasingly spend time on the things that require judgment and customer understanding—not activities that can be standardized, automated, or handled more efficiently elsewhere.
For me, the progression is relatively simple:
- Startup: Generalists who can do everything.
- Growth: Segment customers and introduce different coverage models.
- Scale: Specialize the organization where specialization creates leverage.
The mistake is jumping to specialization too early. The opposite mistake is keeping a generalist model long after the business has outgrown it.
Build the organization, not just the team
There is another part of CS design that often gets overlooked: operating model.
Who owns renewals? Who owns expansion? Where does technical escalation go? How does CS work with Sales, Product and Support? Which decisions belong regionally and which should be global?
These questions become increasingly important as the organization grows across regions.
I've always believed that you should design the operating model before adding significant headcount. Otherwise, you end up hiring people into a system that is already creating friction.
More CSMs can increase capacity. They don't automatically increase effectiveness.
The best CS organizations I've seen are not necessarily the ones with the lowest CSM-to-account ratio. They are the ones where the right customers get the right level of engagement, from the right people, through the right model.
That is what good CS scaling should accomplish.
Not a bigger Customer Success team. A Customer Success organization that can grow faster than its headcount.