Sales Deal Review Checklist: 12 Questions

There is a version of the deal review that everybody in enterprise sales has sat through. The rep talks for eleven minutes. The manager asks when it will close. Somebody notes an action that is really a reminder. The meeting ends, nothing about the deal has changed, and the same opportunity appears on the same slide a fortnight later.

That is status theatre. It feels like inspection because it uses the vocabulary of inspection, but it examines the seller's narrative rather than the deal's evidence.

A real deal review does one thing: it separates what is known from what is believed. Every claim in a pursuit is a fact the customer has confirmed, an assumption the team is carrying, or an unknown nobody has looked at. The questions below are designed to force that separation, and to end with owned actions rather than follow-ups.

Why a status update is not a deal review

A status update reports movement. A deal review tests whether the movement means anything. The two get confused because activity is easy to evidence and commitment is not — a calendar full of meetings looks like progress even when the buyer has committed nothing.

The distinction matters most in the deals that look safest. A pursuit with plenty of contact, an engaged champion and a positive tone is exactly the kind of deal where nobody asks awkward questions. It is also where the largest unverified assumption usually lives.

So run the review against evidence quality, not against enthusiasm. For each answer, the only follow-up that matters is: how do we know? If the answer is 'the champion said so in a meeting', that is seller-heard information. If it is 'the CFO's office scheduled the business case review for the 14th', that is a fact.

Urgency: is there a reason to act at all?

The most expensive competitor in complex B2B is not another vendor. It is the customer deciding to do nothing this year. These first two questions test whether that outcome has been ruled out.

1. What happens to the customer if they do nothing? Ask for the consequence in the customer's own words — a cost, a risk, a deadline, an obligation. If the only answer is that the current process is inefficient, there is no compelling event.
2. What buyer-owned event sets the timing? Budget cycles, contract expiry, a regulatory date, a system decommission, a board commitment. A date the seller picked to make the quarter work is not a timing event.

Value: is the business case theirs or ours?

A value case that the customer cannot defend internally will not survive the first finance challenge. These questions test ownership, not arithmetic.

3. Which numbers in the business case came from the customer? Cycle times, headcount, error rates, contract values. A case built on vendor benchmarks is a proposal; a case built on their figures is an internal argument.
4. Who inside the customer will defend the case when we are not in the room? Name the person. If nobody is identified, the case has no sponsor and will not clear an approval forum.

Stakeholders: who actually decides?

Single-threaded pursuits fail quietly. These questions test breadth and power rather than warmth of relationship.

5. Have we met the person with budget authority, and what did they say the priority was? Being told about the economic buyer is not access to them.
6. What evidence do we have that our champion has influence, not just enthusiasm? Look for what they have done: brought colleagues in, shared internal material, secured time with executives, argued for the project without being prompted.

Decision and close credibility: how does the purchase happen?

Deals rarely die at the decision. They die in the machinery after it — the approval forum nobody mapped, the security review nobody scheduled.

7. What is the approval path from recommendation to signature, and who confirmed it? Steps, forums, dates, signature authority.
8. What procurement, legal, security or privacy dependencies exist, and have they started? These have their own calendars and rarely compress.
9. What is the next action the customer owns, with a date and an outcome? A scheduled buyer action is the single most reliable indicator of real intent. 'They'll come back to us' is not a next step.

Competition and execution: what could still take this away?

The last three questions test the position against alternatives and the honesty of the review itself.

10. What is the customer's realistic alternative — an incumbent, an internal build, a delay, or doing nothing — and what evidence do we have about how it is regarded? An assumed competitive position is the most common source of a late surprise.
11. What evidence changed this week? Not activity — evidence. Something confirmed, something disproved, something newly known. If the answer is nothing, the deal did not move.
12. What is the biggest load-bearing assumption we still have not verified? If it turned out to be wrong, would we still win? This is the question the whole review exists to reach.

Run the review by exception

Reviewing every deal to the same depth guarantees that none of them are reviewed properly. Managers only have so much attention, so spend it where the gap between recorded confidence and available evidence is widest.

A workable rhythm: take the deals that matter most by value or strategic weight, and inspect the ones where confidence is high and evidence is thin. Deals that are honestly early do not need this treatment — they need discovery. Deals that are well evidenced need clearing, not inspecting.

Pick three to five significant pursuits per cycle rather than the whole list.
Prioritise deals carried as near-certain where questions 1, 5 and 9 have weak answers.
Ask the rep to show evidence, not summarise belief.
Track whether the answers improved since last time — movement is the signal.

Turn each gap into one owned action

A review that ends in a list of follow-ups has failed. Each gap should become exactly one action with a named owner, a date, and the specific evidence it is meant to produce.

The format is simple: the gap, the action, the owner, the date, and what will be true afterwards. 'Chase the CFO' is not an action. 'Ask the champion to introduce us to the CFO's finance lead before the 12th so we can confirm which numbers finance will accept' is.

Cap it. Two or three actions per deal that genuinely change the evidence base will do more than ten that restate intent.

A readiness diagnostic is not a forecast

It is tempting to convert a review into a number and roll it up. Resist half of that instinct. Scoring a pursuit is useful — Onden scores readiness 0-100 across six weighted dimensions precisely so the weak dimension is visible — but the score describes the present state of the evidence, not the likelihood of winning.

A readiness diagnostic is not a win probability and not a forecast probability. The moment it enters a commitment conversation, sellers start managing the number upward instead of using it to improve the deal. Keep the diagnostic where it belongs: in the review, pointing at the weakest dimension and the evidence that would move it.

The CRM remains the system of record for stage, amount and close date. The review is where you decide whether what is recorded there deserves to be believed.

Key takeaways

A deal review tests evidence; a status update tests narrative. Ask 'how do we know?' after every answer.
Classify every claim as fact, assumption or unknown — the unverified load-bearing assumption is the point of the meeting.
Review by exception: inspect high-value deals where confidence is high and evidence is thin.
End each gap with one owned action, a date and the specific evidence it should produce.

Frequently asked questions

What is a sales deal review?

A sales deal review is a structured inspection of a single opportunity that tests the evidence behind it — customer urgency, quantified value, stakeholder access, decision process, competitive position and execution — rather than reporting recent activity. Its output is a small set of owned actions that close specific evidence gaps.

How often should you run a deal review?

For significant enterprise pursuits, a fortnightly or monthly cadence is usually enough to see whether the evidence has moved, with additional reviews around a major milestone such as a business case submission or a competitive decision point. Reviewing every deal every week tends to produce status reporting rather than inspection.

What is the difference between a deal review and a pipeline review?

A pipeline review looks across the portfolio at coverage, stage distribution and roll-up. A deal review goes deep on one opportunity and examines whether the conditions required to win it are actually evidenced. They answer different questions and should not be run in the same meeting.

What makes a deal review objective?

Objectivity comes from separating fact, assumption and unknown for every claim, and from asking what the customer has done rather than what the seller believes. Using a consistent set of questions and tracking whether the answers improve over time removes most of the variability introduced by individual confidence.

Run these questions against a real opportunity

Onden works through the same evidence dimensions on a live deal and shows where the pursuit is thin, what is still an assumption and what to do about it next.

Analyse a live deal free

What OnDen does·Pricing

Continue reading

Deal readiness AI deal coaching All insights