The pipeline review your board actually wants to see
Most board decks show pipeline coverage. Boards want to know if the number is real.
Every board deck has a pipeline slide. Total pipeline, coverage ratio, stage breakdown by dollar amount. Almost none of it tells the board what they actually want to know: is this number going to hold up, and if not, when did you know?
The coverage ratio is the worst offender. A 4x coverage ratio means nothing if half the pipeline is stalled deals nobody has the discipline to disqualify. It rewards hoarding stale opportunities over running a clean funnel, and boards who’ve sat through a few misses eventually stop trusting it.
A pipeline review should answer three questions, not one. What closed and why. What’s genuinely on track for this quarter, deal by deal, with the last customer-facing action and next step. And what got pushed or lost, with the real reason: not “timing,” but what actually happened in the deal.
That third category is where the signal lives. If the same objection kills three deals in a row, that’s a product or pricing problem, not a rep-execution problem, and no amount of coaching fixes it. Most reviews never surface this because nobody’s tracking loss reasons at the level of specificity that makes them useful.
Building this kind of review takes discipline most founder-led teams don’t have bandwidth for. It means tagging every stage change and loss reason in the CRM, every time, and actually looking at the pattern. It’s one of the first things I put in place with a new engagement, because it’s the fastest way to tell a board the truth before they have to ask for it.
What's wrong with pipeline coverage ratio as a metric?
It rewards volume over quality. A rep can hit a healthy coverage number just by refusing to disqualify stalled deals, which hides risk instead of revealing it.
How often should a board-level pipeline review happen?
Monthly at minimum, with a lighter weekly version internally. Boards need a trend line, not a snapshot that could be lucky or unlucky.
Who should own tagging loss reasons in the CRM?
The rep, at the moment they lose the deal. Loss reasons reconstructed from memory weeks later are far less reliable than logging them in real time.