Doing More With Less in Customer Success
At some point most CS leaders get a version of the same meeting. Headcount is frozen, or the team just got smaller, and the retention target didn't move. Sometimes it went up.
The instinct is to ask everyone to work harder and hope the quarter is kind. That works for about six weeks, and then the good people start answering recruiters.
There's a better response, and it starts with being honest about what you're going to stop doing.
Decide what you're cutting, on purpose
When capacity shrinks and expectations don't, something gets dropped. The only question is whether you choose it or your team does, one skipped meeting at a time.
Chosen cuts are survivable. Accidental ones are how you end up discovering in month nine that nobody has spoken to a set of accounts since onboarding. So make the decision explicitly: which segments keep a named CSM, which move to a pooled or programmatic model, which activities stop entirely.
Then tell your team and your leadership what you decided and why. A leader who says "we're no longer running quarterly reviews below this account size, and here's what those customers get instead" is managing. A leader who says "we'll do our best to keep everything going" is setting the team up to fail quietly.
Protect the revenue first
Not all accounts deserve equal attention when attention is the scarce resource. Rank by revenue at risk rather than by size alone: renewal date, expansion potential, current health, how much would be hard to win back.
The work that most directly protects revenue is renewal preparation, risk intervention and the expansion conversations that are already warm. That's what I'd protect before anything else. Reporting, internal projects and tooling improvements can wait a quarter without a customer noticing.
This is also when the difference between gross and net retention gets sharp. Expansion can flatter a quarter while the base quietly erodes, which is why gross retention is the number to watch when the team is stretched.
Get the low-value work off their plates
Before cutting customer-facing time, look hard at everything else a CSM does in a week. In most teams there's real time buried in preparing decks nobody reads, updating two systems with the same information, assembling reports by hand, and meetings that could be a message.
Some of that is automation, and some of it is just a leader deciding that a thing no longer needs to exist. Both are faster than hiring. AI tooling helps here too, mostly on preparation and summarizing rather than on the conversations themselves, which I've written about in scaling CS without losing the human part.
One habit worth keeping: ask the team directly what they'd stop doing if it were up to them. They usually know, and they're usually right.
Scale the things that don't need a person
A one-to-many program isn't a consolation prize. For a lot of customers, a good onboarding sequence, a clear help center and a monthly office-hours session beat a quarterly call with a CSM who's covering too many accounts to prepare properly.
Build those deliberately for the tiers you've decided to serve that way, using playbooks written for each tier, and measure whether they work. If your segmentation model is already in place, this is mostly a question of resourcing it rather than designing it from scratch. And if your books were too big before the freeze, this is the moment to face that, because the right coverage number doesn't change just because the headcount did.
Don't pretend it's fine
Your team knows the situation. Telling them it's an exciting opportunity insults them, and telling them nothing lets everyone assume the worst.
What helps is being specific: what you're protecting, what you've dropped, what you're asking of them, and for how long. Then take something off their plate yourself, publicly. A leader who cancels their own reporting meeting to buy the team back an hour is more convincing than any amount of encouragement.
Watch the load, too. Constraint for a quarter is manageable. Constraint with no end date and no change in scope is how you lose your strongest CSMs, and replacing one costs more than the headcount you were denied.
Use it as evidence
Keep a record of what the constraint actually cost: the accounts that got less attention, the ones that churned, the expansion nobody had time to chase. Not as a complaint, but as the case you'll make next planning cycle.
That's the argument that gets headcount back. Not that the team is busy, but that a specific amount of revenue went unprotected, and here's the number.
If you're leading a stretched team and want to compare notes, let's talk.
