← Perspectives · Operating model

Scaling CS without scaling headcount: operating model design.

Petar Mihajlovic12 August 2026

1 minute read

The most common response to a CS capacity problem is a hiring plan. Sometimes that's the right answer. Often, it's a way of adding cost to a structural problem that a different operating model would solve.

A different pattern in the companies that scale well.

The organisations I've seen scale post-sale functions most efficiently share a pattern: they treat CS capacity as a scarce resource to be architected around, not a variable to be adjusted up.

That means segmentation that's sharp enough to differentiate engagement intensity. It means tech-assisted coverage for lower-complexity cohorts that frees senior capacity for strategic accounts. It means playbooks that are specific enough to reduce variability in execution — so a less experienced CSM can execute consistently rather than improvising.

Leverage in a post-sale function comes from architecture. A well-designed operating model lets you add twenty percent more ARR under management without a proportional increase in headcount.

The right question to ask.

A poorly designed operating model means every revenue milestone triggers a headcount request. A well-designed one absorbs growth into the system that's already in place — and surfaces a hiring need only where the model genuinely demands it.

The question isn't how many CSMs you need. It's what the operating model is that determines that number — and whether you've actually designed it.