Customer Success Capacity Planning

Most CS leaders plan capacity the way a kitchen handles a dinner rush — reactively, account by account, pulling in help only after something has already broken. In S&OP, capacity planning runs the opposite direction: you decide, before the week starts, exactly which hours go where, sized against a fixed number of labor-hours and a known segmentation of demand. I've started running my team's week the same way, and it's changed what “prioritization” actually means for us.

The habit is really three decisions, made in order: segment the book, size the week against a fixed number, and hold back a buffer for what you can't predict. Skip the order and you end up with a to-do list dressed up as a plan.

Segment the book before you schedule it.

In supply planning, you'd never build a production schedule before classifying SKUs by value and variability — the classification is what tells you how much capacity each item deserves. I run the same split on my book: how much revenue is at stake, and how unpredictable the account has been. High-value, high-variability accounts earn dedicated capacity. High-value, stable accounts are anchor accounts — they need less hand-holding than their revenue would suggest. Low-value, volatile accounts go on a watch list. Everything else runs on pooled or automated coverage. None of this touches a calendar yet. It's just deciding who deserves capacity before deciding how much.

Quadrant diagram segmenting accounts by value and variability into anchor accounts, dedicated capacity, watch list, and pooled or automated coverage.

Plan against a fixed number, not an aspiration.

Once the book is segmented, I size the week the way a plant manager sizes a shift: against a fixed number of hours, not an open-ended list of things I'd like to get to. My team has roughly 40 CSM-hours a week per account manager. I block those hours by segment before Monday starts — a set allocation for dedicated Tier 1 coverage, a smaller block for pooled Tier 2 work, a thin slice for the automated tier, and a reserved chunk nobody touches yet. A to-do list expands to fill whatever time exists. A capacity plan doesn't — it forces the tradeoff before the week does it for you.

Stacked bar showing a fixed 40-hour weekly CSM capacity plan divided into dedicated, pooled, automated, and reserved buffer blocks.

Build in a buffer, and know where it comes from.

Every S&OP plan carries slack, because demand never lands exactly where you forecast it. I carry the same slack in a CS capacity plan — a reserved block of hours, sized to the volatility of the book, that exists specifically so a spike doesn't quietly cannibalize someone else's committed time. When a Tier 2 account blows up mid-week, the buffer absorbs it. Tier 1 coverage doesn't get shorted to compensate, and nobody's working a sixty-hour week to cover a gap that should have been planned for. The teams without a buffer aren't more disciplined — they're just one bad week away from finding out they never had a plan at all.

Diagram showing a planned weekly capacity block reallocating its reserved buffer hours to absorb a mid-week volume spike in one account tier.

I used to think “reactive” and “busy” were different problems. They're the same problem, just wearing different hours. If you run a CS team, I'd be curious how you size a week's worth of capacity — fixed blocks, a running list, or something else entirely?