Every CRO reports forecast accuracy to the board. Close to the number — good. Off the number — bad. The metric is universal, the calibration well understood, and the conversation predictable.
The metric is also incomplete. And in some cases, dangerous.
What accuracy tells you.
Forecast accuracy tells you the calibration of your call. Did you land within your stated range. Did your commit hold. Did your best case stretch but not break. This is useful information. It is also entirely backward-looking. By the time you can measure forecast accuracy, the quarter is over and the slope has either held or wobbled. Accuracy grades the past. It does not protect the future.
What survivability tells you.
Forecast survivability is a forward question: if a specific element of the call disappears, does the rest of the call hold?
Run the exercise. Pull the top deal out of the commit. Does the commit still hit? Pull the top rep's number. Does the team still land? Pull the strongest vertical. Does the segment math still work?
If the answer to any of these is no — and no is the answer more often than leaders want to admit — you don't have a forecast. You have a hope, scaffolded by one or two events that are quietly carrying the rest of the call.
The three survivability tests.
- Top deal removal. Strip the single largest deal out of commit. What's left? If the gap exceeds your comfort threshold, you have single-deal concentration risk — regardless of how good the deal looks.
- Top performer removal. Strip the top rep's quarter. What's left across the rest of the team? If the team plan only hits with one rep at 200%, you don't have a team plan. You have a hero in a costume.
- Strongest play removal. Strip the deals coming through your most-named, highest-conviction play. What's left in the other plays? If everything else converts at half the rate, the slope is dependent on the play running cleanly every quarter — and one weak quarter on the play will break the slope before anyone names it.
The first time a leadership team runs the exercise honestly, the room goes quiet. Not because the answers are catastrophic — they rarely are — but because the gap between what the team had been calling a healthy quarter and what the math actually shows is wider than anyone had been willing to articulate. The temptation, in that quiet, is to argue with the exercise. The discipline is to write down what the exercise revealed and put it on the agenda for the next forecast call as a standing line item. That single move — making survivability a recurring inspection, not a one-time crisis — is what separates the orgs that learn from the exercise from the ones that file it and forget.
Why most orgs don't run the check.
Because the answers are uncomfortable. The exercise often reveals that a quarter you called confident is, structurally, single-deal dependent. And once that's named, it has to be addressed — which means scoping work no one wanted on the roadmap, or having a harder conversation with the board than the accuracy number alone would have required.
The pattern is consistent: the orgs that compound run survivability quarterly, even when the forecast looks healthy. The orgs that surge and plateau run it only after they've missed.
Accuracy is how the past graded you. Survivability is what tells you whether the future will.