Most CRO pipeline reviews are theatre. The CRO asks about big deals. The VP provides a narrative. The narrative is optimistic because pessimistic narratives create follow-up meetings nobody wants. The CRO leaves feeling informed. The VP leaves feeling relieved. Nothing changes.
The problem isn't that CROs don't care about pipeline accuracy. They do. The problem is that the questions CROs ask in pipeline reviews produce comfort instead of information. Asking "how's the IBM deal?" invites a story. Stories are entertaining. They are not diagnostic.
A CRO who wants to know the truth about their pipeline needs to ask questions that are hard to answer with a story and easy to answer with a fact.
The Three Questions That Actually Matter
1. What Has the Buyer Done Since Last Week?
Not what has the rep done. Not what has the SE done. What has the buyer done? This single question exposes the difference between a deal that's moving and a deal that's being worked.
A deal where the rep has sent three follow-up emails, prepared a custom demo, and built an ROI model — but the buyer hasn't responded to any of them — is not progressing. It's a one-sided relationship. The rep's activity is irrelevant if the buyer isn't reciprocating with actions of their own.
When a VP tells you "the team is working hard on this deal," redirect: "I understand. What has the buyer done?" If the answer is vague — "they're really interested" or "they said they'd get back to us" — the deal is not where the CRM says it is.
Buyer actions that matter: meetings attended, stakeholders introduced, internal processes started, information shared, timeline confirmed. These are facts. "They seem really engaged" is an interpretation.
2. Who on the Buying Side Has Confirmed the Timeline?
Every deal in the forecast has a close date. Very few of those close dates have been confirmed by someone on the buying side. This question exposes the gap between "when we think it'll close" and "when the buyer has said it'll close."
The distinction matters enormously. A close date set by the rep based on their quota deadline is a wish. A close date set by the buyer based on a contract expiration, a board mandate, or a fiscal year boundary is a fact. The first slides endlessly. The second rarely does.
Ask your VP: "For the deals in commit, which ones have a close date confirmed by the buyer — not assumed by us?" If the number is low, your commit number is unreliable. If the VP can't answer the question, your pipeline review process isn't asking it.
3. What Happens If This Deal Doesn't Close This Quarter?
This is the question that produces the most useful information and the most discomfort. It forces the VP to think about the deal without optimism bias and to articulate the downstream impact.
If the answer is "it closes next quarter," ask why. What changes in three months that hasn't changed in the last three? If nothing changes, the deal is stalled — not slipping.
If the answer is "we miss the number," now you have a different conversation. How dependent is the quarter on any single deal? What's the plan if two of the top five deals slip? A CRO who only learns about single-deal dependency in the last week of the quarter has been failed by the review process.
This question also exposes whether deals have genuine urgency. If a deal can slip a quarter with no real consequence to the buyer, the buyer doesn't have urgency — which means the timeline was always fiction.
What to Listen For in the Answers
Narratives vs. Facts
Listen for the difference between a story and an evidence statement. "The champion is really excited and we had a great meeting last Tuesday" is a narrative. "The champion introduced us to the CFO on Tuesday and they scheduled a 45-minute budget review for next Thursday" is evidence.
When you hear narratives, ask for the specific buyer action underneath. Not because you don't trust your VP — but because narratives are how optimism travels through an organisation without being checked. By the time a rep's optimism has been filtered through a manager and a VP, it sounds like a fact. It isn't.
Confidence Without Evidence
Watch for deals where the confidence level is high but the evidence is thin. "We feel really good about this one" paired with "the buyer hasn't started legal yet" is a contradiction. Feeling good is not a forecast input. Started legal is.
The most dangerous deals in any pipeline are the ones where everyone is confident and nobody can articulate why. These are the deals that produce forecast surprises. Ask for the evidence behind the confidence, and if it isn't there, challenge the forecast category.
The "Slipping" Pattern
If a deal has moved close dates more than once, it is telling you something. Not every slip means the deal is dead — procurement delays happen, reorganisations happen, budget cycles shift. But multiple slips without a clear, buyer-confirmed reason suggest the deal was never on the timeline the rep believed.
Ask: "How many of our current commit deals slipped from last quarter?" If it's more than 20%, your forecast accuracy problem is a qualification problem.
The Questions CROs Should Stop Asking
"What's the number?" — This produces a number. It doesn't produce understanding. Ask about the deals that compose the number instead.
"Are we going to hit?" — This produces "yes" because nobody wants to say no to the CRO. Ask what has to be true for the number to land, and assess whether those things are likely.
"What's the upside?" — Upside in a CRO review is aspirational. It makes the room feel better. It doesn't change the commit. Ask instead: "What's the biggest risk to the commit number, and what's our plan if that risk materialises?"
"Why did we lose that deal?" — In a pipeline review, this is a post-mortem question that derails the forward-looking conversation. Save it for a dedicated win/loss review. Use pipeline review time for deals you can still influence.
Building a CRO Review Cadence
A CRO doesn't need to review every deal every week. That's what your VPs and frontline managers do. A CRO review should focus on three things:
The commit stack: The 10-15 deals that compose the quarter's commit number. Review these weekly with evidence questions. Are they on track? What buyer actions have occurred? What's the risk?
The pipeline shape: Monthly, look at coverage by segment, stage distribution, and aging. Is enough entering the pipeline? Is it progressing? Where are the bottlenecks? This tells you about next quarter, not this one.
The patterns: Quarterly, look at trends. Are deal cycles lengthening? Are win rates declining? Is average deal size changing? These are strategic signals that individual deal reviews will never surface.
The goal of the CRO review is not to manage deals. It's to manage the system that manages deals. If the system is working — if managers are running evidence-based reviews, reps are maintaining pipeline hygiene, and forecast categories are meaningful — the CRO review is a validation exercise. If it isn't, the CRO review is where you find out.
For the complete diagnostic framework — the 38 questions that expose what your pipeline and forecast are hiding from the executive level — download the Pipeline & Forecast Framework. Because the forecast was never as real as the room pretended.