The short version: Run a deal review in seven steps — check last session’s actions, ask for deltas only, qualify against a fixed question set, pressure-test the one assumption the number depends on most, check the competitive picture, convert everything to owned actions with names and dates, and only then ask whether the close date still holds. Timebox it — 10–15 minutes per deal in a multi-deal session, 30–45 minutes for a single-deal deep dive — and frame the entire meeting as examining the deal, never the rep.
Here’s how I learned that last part.
Early in my career, at a global analytics company, I had to present a deal review for an opportunity five times larger than anything I’d ever worked. That’s exactly why the review existed — and I had almost no guidance on what to cover.
Before the meeting, a pre-sales consultant I worked with — technical, sharp, and a veteran of dozens of these sessions — gave me the best advice I’ve ever received on the subject. She’d watched account executives walk into these meetings and pitch: why the deal is the greatest thing ever, how big it is, how it’s going to make their quarter and their quota. And she’d watched every one of them get grilled on the back end, because they never talked about the risks. The room found the risks anyway. It always does.
So I flipped the script. I opened with: here are the three biggest risks in this deal, here’s why they’re the biggest, and here’s what I think we can do to mitigate each one. The reason I’m here is to get your collective expertise — tell me what I’m missing, and what else can we do about these risks?
The dynamic of the meeting inverted. Instead of a panel probing for the holes I was hiding, I had a room full of experienced people working my problem. That’s the entire thesis of running these sessions well, seen from the rep’s side of the table: the review isn’t a trial of the account executive’s competence. It’s the deal getting access to more brains. Everything below — every step, every script — is about building a meeting where that’s true by design, not left to whether an individual rep happens to have the nerve (or the good advice) to open with their risks.
This is the facilitator’s guide: what to actually do and say, minute by minute, from the manager’s chair. If you’re setting up the process from scratch — which deals to select, who attends, what cadence — start with the complete pillar guide and come back here for execution.
Deal Reviews vs. Structuring a Pipeline Review: Two Different Meetings
One clarification before the steps, because search results — and plenty of sales organizations — blur these together. There’s a lot written about running the perfect sales pipeline review meeting. This is not that guide, and the distinction matters.
A sales pipeline review goes wide: it’s a visual representation of how opportunities progress through the sales funnel, covering every open opportunity the team is actively working. Pipeline review meetings assess coverage against quota, sales velocity, opportunity quality, and stage distribution across the overall pipeline — they answer “is there enough of the right stuff moving, and where is the funnel leaking?” Reviewing pipelines is a breadth exercise, and it’s how revenue leaders keep a read on pipeline health week to week.
A deal review goes deep: one specific deal at a time, examined properly — the stakeholders, the buying process, the competition, the evidence behind the sales forecast. It exists to find the thing that could kill a deal while there’s still time to act.
Run them separately, always. When pipeline reviews and deep-dive sessions merge into one meeting, you get shallow coverage of everything and real inspection of nothing — and the deals across the team that most needed scrutiny get four minutes of narration instead. Running sales pipeline reviews well is its own discipline; what follows is the other meeting, the one where individual deals actually get worked.
The First Step: 60 Seconds Before Deal One
The first step happens before the first deal: confirm the list and the order.
Prioritize by risk, not by size. The instinct is to start with the biggest opportunity. Resist it. Start with the one in the most trouble — the deal that slipped, the one with a competitor moving, the one whose champion went quiet. Troubled deals need the room’s freshest thinking, and if time runs short, it’s the healthy ones that can safely wait a session.
Then state the timebox out loud: “Two deals today, fifteen minutes each, hard stop.” Saying it aloud isn’t ceremony — it licenses you to redirect later without it feeling personal.
Tooling: CRM open, battlecards open for any deal with a named competitor, nothing else. If you need eight tabs to run the meeting, the preparation didn’t happen (here’s what prep should look like, for both sides of the table).
The Seven Steps: Qualify, Pressure-Test, and Convert to Action
Here’s the sequence, then each step expanded with what it actually sounds like in the room.
- Open with last session’s actions
- Ask for deltas only
- Qualify against the fixed questions
- Pressure-test one load-bearing assumption
- Run the competitive check
- Convert everything to owned actions
- Close with the forecast-honesty question
Step 1: Open with last session’s actions (2 minutes)
Done, not done, why — and nothing else. This is an accountability check, not a discussion.
The trap is what happens when actions weren’t done. Handle it wrong and you’ve turned the session into a prosecution in the first two minutes; every answer after that will be defensive.
What it sounds like: “The required action was to get time with their CFO by Friday — where did that land?” … “Okay. Is the blocker on our side or theirs? … Right — same action carries forward, and let’s use part of today to figure out a different route in.”
Note what that script does: it treats the undone action as information about the deal (“we can’t get to the CFO” is itself a finding) rather than a verdict on the rep.
Step 2: Ask for deltas only (3 minutes)
“What’s changed since last time?” New stakeholders, new information, competitor movement, anything shifted on the buyer’s side of the table. Not a recap — you’ve both read the opportunity record, and if you haven’t, the meeting has a different problem.
The most common derailer in any review session is the rep who answers a delta question with the deal’s full history. The redirect:
What it sounds like: “Hold that — I’ve got the background from the record. Just the last two weeks: what’s new, what moved?”
Say it warmly and say it every time, and within three sessions your sales people arrive with deltas prepared. The meeting trains its own participants.
Step 3: Qualify against the fixed questions (5 minutes)
Your sales team should have six to ten agreed questions, asked on every deal, every time — covering qualification, stakeholders, competition, and confidence in the number. This is where you inspect the evidence: what challenges the prospect is facing in their own words, their decision criteria, their decision-making process, and whether the exit criteria for the current stage are genuinely met before anyone talks about the next stage. (The full question set lives in the main guide; the short version: the two I never skip are “who has veto power that we haven’t met?” and “did we hear that from them, or about them?”)
The rule that keeps this step moving: when the rep doesn’t have an answer, don’t dwell. Log it, assign it, move on. The gap is the finding.
What it sounds like: “Don’t know is a fine answer — better than a guess. Action for you: find out before next session. Next question.”
That one script does more for honesty than anything else in this guide. The first time a rep says “I don’t know” and the sky doesn’t fall, you’ve changed what your reviews can surface. If “I don’t know” costs a sales rep more than a confident bluff, you will be systematically bluffed.
Step 4: Pressure-test one load-bearing assumption (5 minutes)
This is the heart of the meeting, and it’s a choice you should have made during prep: of everything this deal’s forecast depends on, which single assumption is doing the most work? The champion’s claimed influence. The “budget is approved.” The close date. The “the CIO is fine with our architecture.”
Then interrogate just that one, using the evidence-vs-hope test: is it verified — heard directly from the relevant person, or seen in a document — or assumed?
What it sounds like: “The whole commit rests on procurement finishing by the 20th. Walk me through where that date comes from. Did their procurement lead give it to us, or did we back into it from our quarter-end? … What did they actually say, word for word?”
One assumption, tested properly, beats ten skimmed — and it’s how the room builds a deeper understanding of the deal than any dashboard can give. The deals that blindside you are almost never the ones where nobody had information — they’re the ones where a soft assumption sat unexamined for months because every session skimmed past it. I opened the main guide with a seven-figure lesson on exactly this.
Step 5: Run the competitive check (5 minutes)
Three questions, every time there’s a named competitor: Who’s actually in this deal, and how do we know? Why is the buyer considering them? What’s our counter-play — and have we validated that our differentiator matters to this buyer?
Two facilitation notes. First, “no competitors” from the rep gets one probing follow-up, because buyers rarely volunteer the competition:
What it sounds like: “Maybe — but have we seen anything in their language or their requirements that sounds like someone else’s messaging? Any objections arriving strangely well-formed?”
Second, before you move on, capture what’s new. If the rep learned something about a competitor in the last two weeks — a pricing move, a claim they’re making, a weakness a buyer let slip — that goes back into the shared battlecard now, in the meeting, not “later.” This is the loop that makes competitive selling repeatable rather than heroic (it’s the loop we built Playwise HQ around, and it’s worth running with or without a tool): intel comes into the session from the battlecard, and what the deal teaches goes back out to it.
Step 6: Convert everything to owned actions (5 minutes)
Every risk and every gap surfaced in steps 1–5 becomes an action with one owner and one date, entered in the CRM against the opportunity while the meeting is still running. Not after. “After” is where actions go to die. Every session should conclude with clear action items or it was a conversation, not a review.
The conversion script matters, because raw discussion produces wishes, not next steps:
What it sounds like: “Okay — ‘we should get in front of the CIO’ isn’t an action yet. Who asks, through whom, by when? … So: you draft the ask today, our exec sponsor sends it Thursday, meeting requested for next week. That’s what goes in the record.”
Step 7: Close with the forecast-honesty question (1 minute)
“Given everything we just discussed — does the close date and forecast category still hold?”
This is deliberately the last question, not the first. The moment the session becomes a negotiation about whether the deal can be called commit, evidence stops flowing — the rep starts arguing a case instead of examining a deal. Diagnose first; only then ask what the diagnosis means for the sales forecast. And the answer feeds your forecast call — it doesn’t turn this meeting into one.
Keeping the Session Focused
Should these meetings be time-boxed? Yes, but the size of the box depends on the format, and it’s worth being precise, because there are really two formats:
The cadence session — the weekly or biweekly rhythm where a manager and rep work through several deals. Here: ten to fifteen minutes per deal, four to five deals per session maximum, visible timer, hard stop. The constraint isn’t a limitation on quality, it’s the mechanism that creates it. Infinite time produces narration; scarce time produces preparation.
The deep dive — a session dedicated to a single deal, usually triggered by size, stage, or risk: the must-win opportunity, the deal entering procurement, the one that justifies a bigger cross-functional room. (My analytics-company story at the top was exactly this format.) Give it thirty to forty-five minutes. The seven steps hold, but step 4 expands from one load-bearing assumption to the top two or three, and the competitive check gets the time a genuine counter-play discussion needs. What doesn’t change is the hard stop, more time doesn’t remove the narration risk, it feeds it, and an unbounded deep dive becomes a ninety-minute history lecture with worse decisions at the end.
In either format, anything unresolved at the buzzer goes to the parking lot: it becomes either an action item or the opening topic of the next session.
Beyond the clock, focus is about handling the three derailers every facilitator meets:
The historian narrates the deal from first touch. Redirect: “I’ve got the history — take me to what’s changed.”
The defendant hears every question as an accusation and answers with justification. Redirect: “This isn’t about whether you’ve worked it right — I’m trying to find what the deal needs next. What would you probe if this were someone else’s opportunity?”
The optimist hand-waves risk (“the demo went great, they love us, it’s fine”). Redirect: “They might. A great demo isn’t a decision, though — what’s our evidence, and if we’re wrong about that, where does this deal break?”
Each redirect shares a shape: it declines the unproductive frame and re-points at the deal. That’s the sales manager’s job in this room, condensed to one sentence — and it’s the part of sales management that no dashboard replaces.
What Happens After the Session
How you document outcomes: actions in the CRM, against the opportunity, with owner and date, visible to both rep and manager, and checked as item one of the next session. That closed loop is the documentation system. What you don’t need: meeting minutes, summary emails, or a deck. If it isn’t an action or a change to a deal field, it doesn’t need writing down.
What escapes the room: competitive intel to the battlecard, novel objections and the answers that worked to the objection library, stakeholder patterns to wherever your team keeps collective memory. The actions loop closes this deal; the learning loop compounds every future one — and it’s how new sales hires inherit the team’s hard-won knowledge instead of relearning it deal by deal. (The main guide covers this flywheel in full.)
The ROI: What a Good Review Process Looks Like After 90 Days
You’ll know it’s working when: reps arrive with the fixed questions already answered and risks already listed, because they know exactly what’s coming; the “I don’t know” rate falls session over session, because unknowns get hunted between meetings; slipped-deal surprises decline, because soft assumptions get caught while there’s still time to act; and your battlecards visibly accumulate, because every competitive deal feeds them. Forecast accuracy tightens as a by-product, and deals close faster — not because anyone pushed harder, but because obstacles get tackled weeks earlier than they used to. That’s what actually helps accelerate a sales cycle: earlier evidence, not extra pressure.
One honest caveat: the first month feels slower. Early sessions surface a backlog of unverified assumptions that all become actions at once — you’re paying down assumption debt that built up under the old status-update regime, when questions were ad-hoc and preparation was optional. It clears. What’s on the other side is the meeting I stumbled into all those years ago by opening with my risks: not a trial, but a room full of expertise helping the rep tackle an obstacle in a deal that matters. Your job as the facilitator is to make that the default across your sales organization, so it never again depends on one rep getting one good piece of advice from one generous colleague.
Frequently Asked Questions
How do you run a B2B deal review?
In seven steps: check last session’s actions, ask for deltas only, qualify against a fixed question set, pressure-test one load-bearing assumption, run the competitive check, convert everything to owned actions in the record, and close by asking whether the number still holds. Ten to fifteen minutes per deal.
What’s the difference between this and a sales pipeline review?
Pipeline reviews go wide — coverage, velocity, and stage distribution across every open opportunity in the sales pipeline. A deal review goes deep on one specific deal: its stakeholders, buying process, competition, and risks. Run them as separate meetings; merging them produces shallow coverage of everything and real inspection of nothing.
What is the first step?
Before the first deal: confirm the list and order — highest-risk first, not biggest first — and state the timebox aloud. Within each deal: review the previous session’s action items.
How do you prioritize which deals to discuss?
By risk, not size. Slipped deals, competitive deals, and deals with quiet champions get the room’s freshest attention; healthy opportunities can wait a session if time runs short.
What happens after the meeting?
Every gap and risk becomes an action with one owner and one date, logged before the meeting ends. Competitive and objection insights get captured to shared team resources. The next session opens by checking those actions — reps working their respective deals know item one is always accountability.
How do you keep the meeting focused?
Hard timeboxes (10–15 minutes per deal in cadence sessions, 30–45 for a single-deal deep dive), a fixed question set, delta-only updates, and consistent redirects for the three derailers: the historian, the defendant, and the optimist.
What makes the process work long-term?
A sales process where the deal is examined rather than the rep, “I don’t know” is safer than a bluff, every session ends in owned actions, and what each deal teaches gets captured for the next one. Same questions, same structure, regular cadence — consistency is what turns reviewing deals from an event into a system.
