The Deal Review Framework I Run With Every Client

Every sales team I've ever worked with has the same problem: their pipeline is full of deals they can't close and forecasts they don't trust. The VP says "we're at $2M in pipeline." The CRO says "what's the weighted number?" The VP says "$800K." The CRO asks "what's the real number?" And then there's a long pause.

The gap between pipeline value and close-ready value is where deals go to die. Deal reviews exist to close that gap — to separate the real from the aspirational and to unblock the deals that are actually winnable.

In an environment where B2B sales cycles have lengthened by an average of 22% since 2023 — driven by larger buying committees, tighter procurement scrutiny, and the proliferation of AI-assisted vendor evaluation — the deal review isn't just a nice-to-have discipline. It's the primary mechanism for preventing deals from silently dying in the pipeline while the forecast tells leadership everything is fine.

Here's the framework I run. It's simple, it's weekly, and it works.

The Structure: 30 Minutes, Three Deals, Five Questions

Every week. Non-negotiable. The cadence is the system.

The sales leader picks three deals to review — not the largest, not the newest, but the ones where progress has stalled or where the outcome is most uncertain. These are the deals that benefit most from structured interrogation.

For each deal, five questions. Every question maps to a qualification element, but the framework isn't about ticking boxes. It's about forcing the rep to articulate — out loud, to a peer group — what they actually know versus what they're assuming. (For the broader philosophy behind pain-led discovery and MEDDPICC, see why your sales team is pitching features and losing. This framework is the weekly operating system that makes that philosophy stick.)

Question One: What's the Quantified Pain?

Not "what problem are they trying to solve?" That's too vague. The question is: what is the measurable cost of this problem, and who in the organisation feels that cost?

A good answer sounds like: "Their head of e-commerce told me they're spending 15 hours per week manually reconciling affiliate commissions across three networks. At their team's fully loaded cost, that's approximately $90,000 per year in operational overhead, before accounting for the errors that trigger partner disputes."

A bad answer sounds like: "They need a better affiliate management solution." That's a feature need, not a quantified pain. If the rep can't quantify the pain, the buyer's internal champion can't build a business case. And if there's no business case, there's no purchase order.

When the quantified pain is missing, the coaching action is specific: "Go back and ask them what this problem costs them in time, money, or risk. Get a number. Then help them understand the downstream implications of that number."

Question Two: Who's the Economic Buyer?

This question trips up experienced reps as often as junior ones. The person you're meeting with is rarely the person who signs the cheque. The economic buyer is the individual with the authority and the budget to approve the expenditure.

A good answer: "The economic buyer is their VP of Digital Commerce. She controls the Martech budget, and her direct report — our primary contact — has confirmed that she needs to approve any new vendor above $25K annual spend."

A red flag: "We're talking to the marketing manager. He says he has budget." Maybe he does. Maybe he has delegated authority for small purchases. But if this deal is $50K+ and you haven't confirmed that your contact can authorise it, you're building a proposal for someone who can say "yes, I like this" but can't say "yes, here's the money."

The coaching action: "Before the next call, ask your contact directly: who needs to approve this expenditure? What's their evaluation process? Can we get a meeting with them?"

Question Three: What's the Decision Process and Timeline?

This is the question that separates real pipeline from wishful pipeline. Most deals stall not because the buyer doesn't want the solution, but because the rep doesn't know what happens between "we like this" and "here's the contract."

A good answer: "They need to present a recommendation to their leadership team by month-end. If approved, procurement reviews the contract — typically a two-week process. Legal review is another week. Realistic close date is end of Q2."

A vague answer: "They said they want to move forward soon." That's not a process. That's a sentiment. Sentiments don't close deals.

The coaching action: "Map their internal process step by step. Ask who's involved at each stage, how long each stage typically takes, and what could cause a delay. Then build your follow-up cadence around their process, not your pipeline review schedule."

Question Four: Do We Have a Champion?

A champion is someone inside the buying organisation who is actively selling on your behalf when you're not in the room. Not someone who likes you. Not someone who took your meeting. Someone who is investing their internal political capital to get this deal done.

A good answer: "Our champion is their affiliate manager. She's the one who brought us in, she's built an internal comparison showing our platform versus their current setup, and she's scheduled a meeting with the VP next week to present her recommendation. She asked us for a one-page ROI summary she can use in that meeting."

A concerning answer: "Everyone we've talked to seems really positive." Positive sentiment without advocacy isn't a champion — it's politeness. The test is whether your contact is taking action on your behalf unprompted.

The coaching action: "If you don't have a champion, you need to build one. That means giving your best contact ammunition — ROI calculators, competitive battle cards, implementation timelines — that make their internal advocacy easier. And it means asking directly: 'Can I help you present this internally? What would make the strongest case to your leadership?'"

Question Five: What Happens If They Do Nothing?

This is the competition question, and the most dangerous competitor is always the status quo. If the cost of change (implementation effort, budget approval, organisational disruption) exceeds the cost of the current problem, the buyer will choose inertia. Every time.

A good answer: "If they do nothing, they continue spending $90K/year on manual reconciliation, they risk losing their two best-performing affiliate partners who are frustrated with late payments, and they miss their Q3 target for affiliate programme expansion — which their VP of Commerce has committed to the board."

A dangerous answer: "They're also looking at [competitor], but we have better features." Feature comparison is a game you can win or lose, but it's not the real threat. The real threat is the buyer deciding that the whole project isn't worth the organisational effort.

The coaching action: "Make sure the champion understands the cost of inaction. If the quantified pain isn't compelling enough to overcome organisational inertia, either the pain isn't big enough or you haven't surfaced it completely."

Running the Review

The five questions take 8–10 minutes per deal. Three deals per session: 30 minutes total.

The format is conversational, not inquisitorial. The rep presents the deal. The reviewer (sales leader, peer, or advisor) asks the five questions. Where answers are strong, acknowledge it and move on. Where answers are weak, coach the specific next action — not generic advice, but the exact question the rep should ask in the next meeting, or the exact asset they should create for the champion.

After each review, assign one action item per deal. Not three. Not five. One. The action that, if completed, moves the deal forward most. "Get the economic buyer into a meeting." "Quantify the cost of inaction." "Build a one-page business case for the champion." One clear action, due before the next review.

Why This Works

Deal reviews work because they force articulation. Most reps carry a mental model of their deals that feels complete but is actually full of assumptions. Speaking the answers out loud — to a peer group that asks follow-up questions — surfaces the gaps that private reflection misses.

They also work because they create a forecasting discipline. After a few weeks of reviews, the team develops a shared language for deal quality. "This deal has a champion and a quantified pain but no confirmed decision process" becomes meaningful shorthand. The forecast becomes a reflection of actual deal health rather than a collection of hoped-for close dates.

And they work because they're fast. Thirty minutes, weekly, no preparation required beyond knowing your deals. The barrier to execution is low enough that it actually happens.

The results compound. A commerce technology company I advise in Singapore implemented this framework in Q3 2025 with an 8-person sales team. Their forecast accuracy — measured as closed-won revenue divided by committed forecast 90 days prior — improved from 41% to 73% within two quarters. Pipeline value dropped 30%, but closed revenue increased 18% because the team stopped investing time in deals that were never going to close and redirected their energy to the deals that were. The CRO told me the single biggest shift was question five — "what happens if they do nothing?" — because it forced reps to confront whether the buyer had genuine urgency or was just collecting options.

---

FAQ

Q: Should the deals reviewed be the same every week?
No. Review the deals where progress has stalled or uncertainty is highest. Some deals will be reviewed multiple weeks in a row if they're stuck. Others rotate in and out as the pipeline moves.

Q: What if the rep can't answer one of the five questions?
That's the point. The review reveals what the rep doesn't know. The coaching action is to go find out — and the next review checks whether they did.

Q: Can this work for a solo founder without a sales team?
Absolutely. Run the review with an advisor, a mentor, or even a structured self-assessment. The questions are the same regardless of team size. The value is in the structured interrogation of your own assumptions.