Loading
Loading
Every leader reports a number they couldn't defend under one hard question. Here's how to tell which of your numbers are governed and which are just hopeful.
Every revenue leader reports at least one number they couldn't actually defend if a board member pressed on it. The forecast that's "on track," but you can't say which deals carry it or whether delivery can execute them. The pipeline that "looks healthy," built on stages that measure momentum, not reality. The margin that's "fine," until someone counts what delivery actually cost. You report these numbers because everyone does. Then someone asks one question ("how do you know?") and the honest answer is: you don't.
Here's how to tell which of your numbers are governed and which are hopeful, and why the difference is about to matter more than ever.
There's a simple way to find your indefensible numbers. Take any figure you report (the forecast, pipeline coverage, gross margin, net retention) and ask yourself: if a board member asked "how do you know that's real," could I answer with evidence, or only with "the system says so"?
"The system says so" is not a defense. It's a citation to a tool that recorded what someone entered, not proof the number reflects reality. A governed number can be traced: you can show which deals compose it, why each is weighted the way it is, what operational facts support it, and what you're uncertain about. A hopeful number can't. It just is, because that's what the dashboard displayed.
Most forecasts are indefensible in the same way: they're built on CRM stage, which measures how far the sales conversation has gone, not whether the revenue is real, deliverable, and recognizable on schedule. If you can't say which deals in the forecast have validated delivery behind them, you can't defend the forecast. You can only hope it holds.
"Healthy pipeline" usually means "big pipeline." But a pipeline full of overdue, undispositioned, or stalled deals is inflated, not healthy. If you can't separate the deals that are genuinely progressing from the ones coasting on old stage labels, "healthy" is a description, not a defensible claim.
Reported margin often reflects assumed delivery cost entered at sale, not the real cost of execution. If change orders, expedited delivery, and cost-to-serve aren't reconciled back to the deal, your margin number is a starting assumption dressed up as a result, and it won't survive scrutiny.
As AI enters the revenue stack, the indefensible-number problem gets worse before it gets better. AI tools will confidently generate answers about your pipeline, your forecast, your risk (clean, assured, and often impossible to verify). The confident, unverifiable answer is the most dangerous kind, because it feels like knowledge while being untested.
This is where discipline becomes the differentiator. A tool that governs revenue well doesn't just produce an answer. It states its confidence, separates what it can observe from what it's inferring, tells you what it doesn't know, and shows the reasoning behind every flag. That discipline is exactly what makes a number defensible: not that the tool is certain, but that it's honest about the basis for its certainty. In a market where AI will happily hallucinate your forecast with total confidence, the disciplined, traceable answer is the one you can take to your board.
A number you can't defend isn't an asset. It's a liability with a decimal point, and it becomes one at the worst possible moment, under the hardest possible question. Revenue governance is what turns hopeful numbers into defensible ones: it doesn't just tell you the number, it tells you which part you can stand behind and which part is optimism you haven't tested yet. The goal isn't a more confident answer. It's an answer you can defend when it matters.
Which number are you reporting that you couldn't defend under one hard question? Run the revenue governance assessment →
An Executive Briefing starts with the same question this article does — ask it about your own operation.
Book an Executive Briefing →