Renewal Forecasting: A CS Framework

In my last post I introduced what I call the S&OP lens — the discipline of forecasting, segmentation, and capacity planning I brought with me from supply chain into Customer Success. This week I want to go deeper on the first piece: forecasting itself, and specifically how I think about renewals.

Most CS orgs treat the renewal number the way a retailer might treat a single sales report: pulled together right before the QBR, presented once, then set aside until next quarter. In supply chain, that would be considered poor practice. A demand plan isn't built once a quarter and left alone — it's reforecast on a rolling basis, usually monthly, so that every new signal gets folded back into the number before it becomes a surprise.

A renewal number is a snapshot. A renewal forecast is a habit

When I built my first renewal forecast, I ran it the way I'd run a rolling demand plan: same accounts, same fields, reforecast monthly, not just at renewal. MOM/ YOY trends, ticket volume, sentiment from the last call, an unanswered email — none of that waits for the QBR calendar, so the forecast shouldn't either. The output isn't a single number I defend once. It's a moving picture I keep current, and the variance between this month's forecast and last month's is often more informative than the number itself.

Line chart comparing a one-time renewal snapshot to a rolling monthly forecast that updates as new signals arrive.

Build a buffer for the accounts you can't fully predict

Supply planners don't pretend every input is knowable. That's why safety stock exists — a deliberate buffer sized to the volatility of the demand, not the average of it. Some renewal accounts behave the same way. A champion leaves, a reorg hits, a budget freezes — the signal was often there, just noisy. I've started sizing a forecast buffer the same way a planner sizes safety stock: wider for accounts with high variability, tighter for stable, long-tenured accounts. Treating every miss as equally surprising is the mistake; the volatility was often visible in advance.

Diagram showing forecast buffer width scaled to account volatility, similar to safety stock sizing in supply planning.

Not every account deserves equal forecasting rigor

In S&OP, you don't run the same forecasting cadence on your top SKU and your long-tail item — you classify by value and variability and route your planning effort accordingly. I run my book the same way. High-value, high-variability accounts get weekly forecast reviews and dedicated CSM attention. Stable, low-variability accounts get a lighter monthly check-in, often automated. The forecasting rigor should scale with what's actually at risk, not be applied uniformly out of habit — that's how CSM time turns into a capacity-planning decision instead of a to-do list.

Diagram matching forecasting cadence to account value and variability, from weekly reviews to automated monthly check-ins.

I didn't expect a demand-planning habit to become the backbone of how I run retention. It has. If you lead CS, I'd love to hear how you think about the cadence, or the lack of one, behind your own forecast.