How do you coach a rep to run a deal review that uncovers risks before the forecast call in 2027

The Tuesday that breaks the quarter

Picture a mid-market SaaS team in the third week of a quarter. A rep — call the deal Northwind Logistics, $180K, "Commit," close date the 28th — walks into deal review with a slide that says "verbal yes from the VP, contract with procurement, expecting signature this week." Everybody nods. It rolls into the forecast call unchallenged. On the 29th it moves to next quarter, and the manager finds out on the 30th that procurement never had it, the VP is not the economic buyer, and there is a security review nobody mentioned.

Nothing in that story is unusual. What is worth noticing is *where* the failure happened. The deal did not die in the deal review; the deal review simply failed to find what was already true about it. Every piece of the miss — no economic buyer, no paper path, an unscheduled security review — was knowable two weeks earlier by asking a question the rep was never coached to ask themselves. The information existed. The ritual didn't go get it.

This is the gap coaching has to close. A deal review that reads like a status update ("where are we, what's next, when does it close") produces a forecast call full of confident numbers built on unexamined assumptions. A deal review that runs like a pre-mortem produces a forecast call where the number is smaller, uglier, and roughly correct. Most managers say they want the second one and then run the first one, because the first one is faster, more pleasant, and doesn't require anybody to admit that a Commit deal has a hole in it.

The coaching job has three parts and they have to happen in this order. First, change what the rep is *asked* — swap open-ended "how's it going" for a fixed risk inventory the rep runs on their own deals before the meeting. Second, change what the rep is *rewarded for* — a rep who surfaces a killer risk on their own $180K deal should get visible credit, not a lecture. Third, change what happens *after* — every risk that gets named turns into a dated action with an owner, or the whole exercise becomes theater and the rep learns that honesty costs them and buys nothing.

Notice also what the scenario says about timing. The review has to happen far enough before the forecast call that a discovered risk can still be worked. A risk found on the same morning as the forecast call is just a downgrade. A risk found ten days out is a security questionnaire you can start, a procurement contact you can get introduced to, a business case you can go quantify. In practice that means deal review sits mid-week, one full week ahead of the forecast commitment, and it is a different meeting with a different tone — not the first fifteen minutes of pipeline.

The adjacent version of this problem shows up everywhere revenue is forecast against human judgment. Professional services firms reviewing project staffing before a utilization forecast, agencies reviewing retainer renewals before a revenue call, even a channel team reviewing partner-sourced pipeline before a QBR — all of them run some version of "the person closest to the work reports on the work, and their optimism is a systemic input to the number." The coaching pattern travels. Only the checklist changes.

How a risk-hunting review actually works

Mechanically, a good deal review is a state machine, not a conversation. The rep enters with a filled-out risk inventory. Each item resolves to one of three states: verified (there is evidence — a name, a date, a document, an email), assumed (the rep believes it but has no artifact), or unknown (nobody has asked). Assumed and unknown are the entire point. A deal where every line is verified is not interesting to review; a deal with three assumptions holding up a $180K Commit is the one you spend twenty minutes on.

The inventory itself should be short enough to run in ten minutes and fixed enough that the rep can run it alone. A workable one has seven lines:

Economic buyer. Not "the champion," not "the VP who likes us." The named person whose budget the money leaves. Verified means the rep has been in a meeting with them or has a written statement from them about this purchase. If the rep says "the VP said he'd handle it internally," that is *assumed*, and it is the single most common reason a Commit deal slips.

Paper path. Every step between verbal yes and countersignature: legal review, security review, procurement, vendor onboarding, PO issuance, signature authority. Verified means the rep can name the step, the owner, and the elapsed time each takes at *this* account. Most reps can name two of six.

Compelling event. Why this quarter and not next. Verified means an external, dated forcing function — a contract expiry, a fiscal deadline, a system sunset, a headcount plan. "They want to get started soon" is not a compelling event; it is a mood.

Business case. The number the buyer will use to defend the spend internally, in the buyer's own units. Verified means the rep can state it the way the buyer would state it to their CFO. If only the rep can articulate the ROI and the champion can't, the deal has no defense when it hits the budget committee.

Competitive position. Who else is in it, including "do nothing" and "build it internally," which are the two most common winners in any pipeline. Verified means the rep has heard the alternative named by the buyer, not inferred it.

Multithreading. How many people at the account have engaged, at what levels, and what happens if the champion leaves. Single-threaded deals are the ones that vanish without explanation.

The slip question. Direct and last: "If this deal slips, what will the reason be?" Reps almost always know. They will tell you if the question is asked flatly and the answer is not punished.

Here is the flow the manager and rep run together:

The coaching move that makes this work is deceptively small: the manager asks for the artifact, not the opinion. "How confident are you?" invites a number the rep made up. "Show me the email where procurement acknowledged the request" produces either an email or a silence, and both are useful. Reps learn the standard fast — after two reviews where the artifact was requested, they start collecting artifacts before the meeting, which is the actual behavior change you were after.

The second coaching move is modeling the answer you want. The first few times, the manager should run their own deal review out loud on a deal they own or once owned, including the part where they say "I had no idea who the economic buyer was and I called it Commit anyway." A rep will not admit a hole in a $180K deal in front of peers until they have watched someone senior do it and survive.

The third is a language rule: risk gets stated as a *condition*, never as a probability. "There's a security review we haven't scoped, and it took eleven weeks at a similar account" is actionable. "I'd say 70%" is noise. RevOps can enforce this at the field level — if the CRM has a free-text "risk" field, require it to contain a noun and a date, and reject entries that are just adjectives.

Numbers worth calibrating against

Be careful with benchmarks here — published win-rate and slip statistics vary wildly by segment, deal size, and how the vendor collecting them defines a stage, so treat any single figure as directional. What holds up is the *shape* of the pattern and the internal math each team can compute for itself. That internal math is the real benchmark, and RevOps can produce all of it from CRM history.

Compute your own slip rate first. Take every deal your team called Commit at the start of the last four quarters and count what fraction closed in that quarter at that value. Teams doing this exercise honestly for the first time are frequently unpleasant surprised. If your Commit-to-close is running well under what your comp plan and board deck assume, you do not have a forecasting problem, you have a deal review problem — the number was never tested before it was reported.

Time-boxing the meeting. A useful working structure: 45 minutes, three to five deals, roughly 8–12 minutes each, plus a hard stop. Reviewing twelve deals in an hour guarantees a status update, because there is no time to press on anything. It is better to deeply review the four deals that carry the quarter than to skim everything. Select by exposure — deals where the value times the uncertainty is largest — not by close date order.

Prep time. Budget 15–25 minutes of rep prep per deal reviewed. If the rep is filling out the inventory during the meeting, the meeting becomes data entry. Managers who protect this prep block on the calendar get materially better reviews; managers who don't get a rep improvising, and improvised answers are optimistic by default.

Cadence and lead time. Deal review weekly, forecast call weekly, deal review at least three to five business days ahead of the forecast commitment. In a long-cycle enterprise motion you can go biweekly on the full inventory and weekly on exceptions. The non-negotiable is the gap: enough runway that a discovered risk has time to be worked.

Paper-path elapsed times. Have RevOps pull the median days from "verbal commitment logged" to "countersigned" over the last 12 months, segmented by deal size and by whether a security review occurred. Most teams find the security-review cohort takes several weeks longer than the non-security cohort. Once a rep knows their own account base's real median, "signature this week" becomes a claim they can check themselves instead of a hope.

Stage-to-stage conversion by rep. A rep whose Proposal→Closed-Won rate is far below the team's is usually not bad at closing; they are advancing deals to Proposal too early. That is a review finding, not a coaching-on-negotiation finding, and you only see it if RevOps reports conversion by stage by rep rather than a single aggregate win rate.

Age-in-stage as an early alarm. Set a threshold at roughly 1.5× the median days-in-stage for each stage. Anything past it gets auto-pulled into the next deal review regardless of what the rep called it. This is cheap to build, runs itself, and catches the quiet deaths — deals that never fail loudly, they just stop moving while the close date keeps getting pushed a week at a time.

Push counts. Count how many times a deal's close date has moved. Two pushes on the same opportunity is a strong signal that the compelling event was never real. Surfacing "this close date has moved three times" in the review, automatically, saves the manager from having to remember it.

Forecast accuracy as the scoreboard. The metric that tells you the coaching is working is not a bigger pipeline and not a higher win rate — it is a narrowing gap between called and actual, in *both* directions. Sandbagging is a forecasting failure too. Track the absolute error, quarter over quarter, at the rep level. A rep whose calls tighten from ±30% to ±10% is doing the review correctly even if their win rate is flat.

What you give up, and the alternatives

Every version of this has a cost, and pretending otherwise is how good processes get abandoned in month three.

The direct cost is time. Weekly deal review plus prep runs somewhere around two to three hours per rep per month of pure overhead. On a ten-rep team that is real selling capacity. The honest defense is that the alternative cost — building a quarter's plan on a number that turns out to be 25% wrong — is larger and lands all at once, but a manager who cannot articulate that trade-off will lose the calendar fight the first busy week.

The second cost is candor risk. If risk-surfacing ever gets punished, the process inverts and becomes actively worse than no review at all, because now you have a formal ritual that manufactures false confidence. The failure mode is subtle: no manager says "don't tell me bad news." They just get visibly tense, ask three skeptical follow-ups, and mention the deal again in the team meeting. The rep updates accordingly and starts pre-filtering.

The third is checklist decay. A fixed inventory is what makes the review repeatable, and it is also what makes it possible to fill in mechanically. After a quarter, "economic buyer: yes" starts appearing on deals where nobody has met one. The counter is periodic spot-audit — pick two "verified" lines at random each week and ask for the artifact.

The alternatives are worth knowing because each is right in some context:

Exception-only review lets CRM signals — stalled age-in-stage, pushed close date, no activity in 14 days, single contact — pull deals into the meeting automatically, and leaves everything else alone. It is efficient and it scales, and its blind spot is the deal that looks healthy on every metric and is quietly single-threaded to a champion who is interviewing elsewhere. Signals see activity, not fragility.

Peer roundtable — where reps present to each other and the manager mostly moderates — produces the sharpest questions when the culture supports it, because peers know exactly which claims are soft. It degrades into performance when the team is competitive or when comp is heavily ranked, and then everyone presents their cleanest deal.

Automated scoring (an AI or rules engine that flags deals as at-risk) is genuinely useful as an input and useless as a replacement. It reads what is in the system. The whole premise of a risk-hunting review is that the important facts are *not* in the system yet — that is why the review uncovers them. Use scoring to pick which deals get reviewed; don't use it to skip the review.

The blend most teams land on: full inventory on every open deal once a month or at stage change, exception-triggered review weekly, peer roundtable once a quarter on the largest deals, automated signals feeding the selection for all three. RevOps owns the signal layer and the reporting; the manager owns the meeting; the rep owns the artifacts.

One adjacent note. The same structure applies to renewals and expansion, with two lines swapped: replace "compelling event" with "renewal date and auto-renew terms," and replace "competitive position" with "usage trend and executive sponsor continuity." Customer success teams that borrow the deal review pattern for renewal forecasting tend to catch churn a quarter earlier, for exactly the same reason — the risk was knowable, nobody was asked.

Where this goes wrong

The review becomes a forecast call. This is the most common collapse. Once the meeting starts producing the number, the rep's incentive flips from finding risk to defending their commit, and you have two forecast calls and zero deal reviews. Keep them separate: different day, different agenda, and the deal review explicitly does not set the number — it stress-tests deals so the forecast call can.

The manager talks more than the rep. If the manager is narrating the deal, the rep is not the one thinking, and no coaching occurred. Rough target: the rep does 70% of the talking. The manager's contribution is questions and one or two pattern observations from having seen the failure before.

"Verified" gets rubber-stamped. Covered above; spot-audit is the fix. Two random artifact checks a week is enough to keep the standard honest without turning the meeting into an interrogation.

Risks are named but never owned. Every identified risk exits the meeting with a person and a date, logged where both parties see it. Un-owned risks reappear verbatim three weeks later, and the rep correctly concludes the exercise is decorative.

The checklist gets long. Someone adds a line every quarter until it's twenty-two fields and reps fill it out at 4:55pm on Friday with whatever passes validation. Cap it at seven to nine lines. If you must add one, remove one.

Only big deals get reviewed. The quarter is often broken by five mid-size deals slipping together, not by the one whale. Select by aggregate exposure, and rotate so every rep gets at least one deal reviewed per cycle — reviewing only the top-of-pipeline means your newest reps, who need the coaching most, never get it.

The rep is coached but the system isn't. If a rep surfaces "we never scoped a security review" and the fix is a note in their 1:1, you fixed one deal. If RevOps adds a required "security review status" field on any deal over a threshold, you fixed the class. Every recurring risk found in review is a candidate for a field, a validation rule, or a stage-exit criterion. That is the durable output of the whole practice.

No memory between quarters. Keep a running list of the reasons deals actually slipped last quarter, and open the first deal review of each new quarter by reading it aloud. It takes four minutes and it recalibrates the entire team's definition of "Commit" faster than any training deck.

Related questions

How far before the forecast call should deal review happen?

At least three to five business days, ideally a full week. The gap has to be long enough that a newly discovered risk — an unscheduled security review, a missing procurement contact — can be worked before the number is committed, not merely reported.

Who should attend a deal review?

The rep and their manager at minimum. Add a solutions engineer or a peer for large deals. Keep it small — attendance above five people turns the review into a presentation, and reps stop volunteering weak spots in front of an audience.

What is the single best question to ask in a deal review?

"If this slips, what will the reason be?" Asked flatly, without follow-up punishment, it surfaces the rep's real concern faster than any structured qualification framework, because reps almost always already know.

Should the CRM enforce the risk inventory?

Enforce the few fields that are genuinely binary and auditable — economic buyer named, compelling event dated, security review status. Leave judgment fields in the conversation. Over-enforcement produces compliant data entry and no thinking.

Does AI deal scoring replace this?

No. Scoring reads what is already in the system; the review exists to extract what isn't. Use scoring to choose which deals to review and to flag stalled ones automatically, then run the human review on the deals it surfaces.

FAQ

How do I get a rep to admit a Commit deal is weak?

Make it safe and make it visible. The manager models it first by dissecting one of their own past deals, including the embarrassing part. Then, the first time a rep voluntarily downgrades their own deal with a real reason, that gets praised out loud in front of peers. Reps read incentives accurately — if candor costs them, they stop. If it earns them credibility, it becomes the norm within about a quarter.

What if the rep genuinely doesn't know the answers?

That is the finding. "Unknown" is a legitimate state and should be recorded as one rather than smoothed into a guess. The output is a dated action: find out who signs, ask the champion what the internal approval path looks like, get the compelling event in writing. A deal with four unknowns is not a Commit deal, and saying so in the review is exactly what the review is for.

How do you keep deal review from turning into another status meeting?

Structural separation. Different day from the forecast call, different agenda, and a standing rule that no number is set in this meeting. Then use the state machine — verified deals get two minutes, deals with assumptions get the rest of the hour. If everything is getting equal airtime, the meeting has already reverted to status.

Should the same process apply to a $20K deal and a $500K deal?

Same seven questions, very different depth. A transactional deal might get a two-minute pass on the inventory and only escalate on a red flag. A large enterprise deal deserves the full treatment plus a peer challenge. What should stay constant is the vocabulary — verified, assumed, unknown — so the pipeline is comparable across segments.

What does RevOps actually own here?

The signal layer and the feedback loop. RevOps builds the age-in-stage and push-count alerts that select which deals get reviewed, computes the historical Commit-to-close accuracy per rep, and converts recurring risk themes into fields, validation rules, or stage-exit criteria. The manager owns the meeting; RevOps makes sure the meeting is aimed at the right deals and that its findings persist.

How long until this changes forecast accuracy?

Expect roughly one to two quarters. The first quarter usually looks worse on paper because reps start pulling weak deals out of Commit, and the reported number drops. That is the process working. The signal to watch is the shrinking absolute gap between called and actual, in both directions, not the raw commit total.

Sources

• https://hbr.org/2013/07/dismantling-the-sales-machine
• https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights
• https://www.salesforce.com/resources/articles/sales-forecasting/
• https://www.hubspot.com/sales
• https://www.gartner.com/en/sales
• https://www.forrester.com/blogs/category/b2b-sales/
• https://hbr.org/2017/03/what-salespeople-need-to-know-about-the-new-b2b-landscape
• https://www.atlassian.com/team-playbook/plays/premortem

Related on PULSE

• How do you build a forecast category definition your whole team applies the same way?
• What CRM fields actually predict a deal slipping?
• How do you run a pipeline inspection meeting that isn't a status update?
• How do you coach a rep who consistently sandbags their forecast?
• What does a healthy stage-to-stage conversion curve look like by segment?
• How should RevOps structure age-in-stage alerts without alert fatigue?