More Customers. Better Outcomes. Smarter Scaling.

Why scaling Customer Success requires a smarter operating model, not just a bigger team.

It's a familiar conversation in growing SaaS companies. The business is doing well. New customers are coming on board, existing customers are expanding, and the Customer Success team is starting to feel the pressure. CSMs are managing larger portfolios, struggling to find time for proactive engagement, and increasingly finding themselves responding to immediate customer needs rather than getting ahead of them.

Eventually, the conversation turns to headcount. "We need more CSMs."

And sometimes, that's absolutely true. But having spent much of my career building and scaling customer organizations, I think there are some important questions worth asking before reaching for the hiring plan. Are we delivering the right level of service to the right customers? Are our CSMs spending their time on activities that genuinely create value? Are we making it easy enough for customers to accomplish things themselves? And have we designed an operating model that can actually support the growth we're expecting?

Because adding more people to an inefficient operating model doesn't necessarily solve the problem. Sometimes it just makes the inefficiency more expensive.

Start with the customer, not the CSM ratio

One of the most important decisions in scaling Customer Success is determining what level of engagement different customers actually need. It's tempting to think that great Customer Success means giving every customer a dedicated CSM, regular meetings, business reviews and plenty of personal attention. But that's not necessarily what every customer wants, and it certainly isn't always what every customer needs.

A large enterprise customer implementing a complex solution across multiple departments may benefit enormously from an experienced CSM who understands their business, coordinates resources and helps drive organizational adoption. A smaller customer using a relatively straightforward product may be perfectly happy with an intuitive onboarding experience, excellent self-service resources and timely assistance when something goes wrong. In fact, requiring that smaller customer to attend regular meetings might make their experience worse.

This is why thoughtful customer segmentation matters so much, and I don't think ARR alone is enough. Implementation complexity, product usage, growth potential, customer maturity and the level of assistance required to achieve meaningful outcomes should all influence the service model. Once we understand those needs, we can design CSM portfolios accordingly.

A CSM managing 20 complex enterprise accounts may be just as busy as someone supporting 100 relatively straightforward customers. Simply comparing account counts or ARR under management doesn't tell us whether either portfolio is appropriately sized. I'd rather understand the actual work involved, the outcomes we're trying to deliver and the capacity required to deliver them. That's a much better starting point than an arbitrary customer-to-CSM ratio.

Understand what it actually costs to serve a customer

There's another dimension to this that I think often gets overlooked. We spend considerable time understanding customer acquisition costs, recurring revenue and retention. But how well do we understand the cost of delivering the customer experience after the sale? Not just CSM salaries, but the combined effort involved in onboarding, support, training, technical services, ongoing engagement and everything else required to help customers succeed.

Two customers generating the same amount of ARR can have dramatically different costs to serve. One may be relatively self-sufficient, adopt the product quickly and require little intervention. Another may need extensive onboarding, frequent technical assistance and considerable ongoing attention. That doesn't necessarily mean the second customer is less valuable, but it should influence how we design the service model and allocate resources.

Understanding cost-to-serve isn't about finding ways to give customers less. It's about understanding where our investments create meaningful value and where we're consuming resources without improving outcomes. Once we have that understanding, we can start making much better decisions about how to deliver the experience efficiently.

Make it easier for customers to help themselves

I've always believed that one of the best ways to improve the customer experience is to make it easier for customers to accomplish things without needing to contact us. Think about how often customers reach out for information that should be readily available. How do I complete this task? Where can I find this report? What's the best way to configure this feature? How do I add another user?

Every time a customer has to schedule a meeting, submit a ticket or wait for someone to answer a straightforward question, we're creating unnecessary effort while consuming capacity that could be used elsewhere. Good self-service isn't about avoiding customers. It's about giving them more control over their experience.

A well-organized knowledge base, useful tutorials, accessible learning resources, customer communities and contextual guidance can eliminate unnecessary interactions while helping customers become more capable and confident. And this is where I think Customer Success leaders need to look beyond their own departments, because sometimes the best Customer Success improvement is actually a product improvement.

If customers consistently need a CSM to explain a particular workflow, perhaps the workflow needs to be redesigned. If onboarding requires repeated meetings to walk through configuration, perhaps more of that guidance belongs directly in the product. The most scalable customer interaction may be the onethat never needs to happen because the product makes the right action obvious.

Create capacity without compromising the experience

Of course, self-service is only one part of the equation. AI and automation offer significant opportunities to reduce administrative work, support onboarding, identify adoption risks and help CSMs prepare for meaningful customer conversations. But I'd distinguish between automating activity and actually improving how the organization operates.

Sending more automated emails doesn't necessarily create a better customer experience. Neither does generating more alerts that nobody has time to act on. The real opportunity is to remove work that doesn't require human judgment. If AI can summarize customer histories, surface meaningful risks or help customers resolve straightforward questions, that's time we can redirect toward activities where people add genuine value.

We should also think differently about who performs the work. Not every activity within a Customer Success organization needs to be handled by a dedicated CSM. Shared services, specialized teams and strong external partners can all help expand capacity. I've seen how capable partners, including those operating in lower-cost geographies, can become valuable extensions of a customer organization when responsibilities, training, systems and service expectations are well defined.

The key is to avoid confusing a lower hourly cost with a better operating model. Poorly designed outsourcing simply moves the problem somewhere else. But thoughtful allocation of work can allow experienced CSMs to concentrate on the customer relationships, strategic conversations and business outcomes that justify their involvement.

Growth shouldn't require a proportional increase in cost

Ultimately, this is about building a customer organization with better operating leverage. If revenue grows by 30%, should Customer Success headcount automatically grow by 30%? I don't think so. But neither would I suggest that a team should simply absorb unlimited growth without additional investment.

The objective is to build an operating model where customer outcomes improve, capacity expands and the cost of delivering those outcomes grows more slowly than the business. That requires more than a new technology platform or a revised portfolio allocation. It requires a deliberate approach to customer segmentation, service design, staffing, self-service, product experience and the intelligent use of technology and partners.

And we need to measure whether it's working. Are customers achieving value faster? Is adoption improving? Are retention and expansion healthy? Are customers able to accomplish more independently? Are CSMs spending more time on meaningful engagement? And are we improving our cost-to-serve as the business grows? Those are the questions that tell us whether we've genuinely built a more scalable customer organization.

I don't think the goal should ever be to minimize the number of CSMs. There will always be situations where hiring another experienced person is exactly the right investment. But before we make that investment, we should be confident that we're adding capacity to an operating model designed to scale.

Because the real opportunity isn't simply to serve more customers with fewer people. It's to serve more customers better, while building a customer organization that can grow sustainably alongside the business.