The Deal Review Scoring Rubric: How to Grade a Pipeline Deal in 90 Seconds

You have 90 seconds per deal on the forecast call. Your VP needs a number — not a narrative about why this deal feels good. A scoring rubric gives you a defensible position in the time it takes to read a slide.

Most CROs have tried to install a scoring system at some point. MEDDIC, MEDDPICC, custom qualification checklists, weighted scorecards. They work for a week, then die — replaced by "I talked to the team and we feel good about this one."

The problem isn't that AEs don't understand the framework. It's that most rubrics are built wrong. They have too many dimensions, no weighting, and no evidence requirement. The result is a scoring system that's really just structured optimism.

This rubric fixes that. Five dimensions, 0–2 scoring on each, total out of 10. Every point requires evidence, not opinion. Score any deal in 90 seconds. Use the total to drive commit vs. best case vs. pipeline decisions with consistency your VP can trust.

Why most scoring rubrics fail

Before the framework: the three structural problems that kill scoring systems in the field.

Too many dimensions. When a rubric scores executive alignment, competitive positioning, product fit, pricing flexibility, champion enthusiasm, procurement readiness, legal complexity, and 6 other variables — you've built a CRM hygiene checklist, not a forecast signal. Every added dimension dilutes the ones that actually predict outcome. Five dimensions that matter beat fifteen that don't.

No weighting. In most scorecards, "champion is supportive" counts the same as "economic buyer confirmed budget." These are not equal. An AE who hasn't spoken to the economic buyer and has a wildly enthusiastic champion is in a comfortable illusion — not a committed deal. Weighting forces you to confront the hierarchy. This rubric builds the hierarchy into the axis selection itself: the five dimensions that get scored are the five things that actually drive close rates.

No evidence requirement. This is the fatal one. If a score of 2 means "AE believes the buyer is sold," the rubric doesn't measure deal quality — it measures AE confidence. Those two things are not correlated. A score of 2 must mean: the buyer said it, did it, or confirmed it. Something observable and documented. Everything else is a 1 at most.

The 5-axis rubric that actually works

Each axis scores 0, 1, or 2. 0 = no evidence exists. 1 = partial or assumed. 2 = confirmed through documented buyer behavior. Total possible: 10.

Axis 1: Economic Buyer Engaged

Does the person who controls the budget know this deal exists — and have they personally expressed support?

Score	What it means	Concrete example
2	Direct conversation confirmed; buyer has shown authority and intent	"CFO joined the business case call on April 28th and approved the $340K range verbally"
1	Champion vouches for EB support; no direct AE contact yet	"Sarah says the CFO is behind it, but you haven't spoken to him"
0	Unknown who the economic buyer is, or known but unengaged	"We're working through the VP of Ops; not sure who signs"

Axis 2: Pain Quantified

Has the buyer put a number on the cost of the problem they're solving?

Score	What it means	Concrete example
2	Buyer-sourced dollar or time figure, documented in writing or call notes	"VP of Ops confirmed $2.1M annual impact from manual reconciliation — documented in discovery call notes"
1	Qualitative pain clearly expressed; no quantification	"They said the process is broken and costing them headcount, but no number attached"
0	Pain assumed by AE; buyer hasn't acknowledged the problem explicitly	"They must be losing time on this — every company at their scale does"

Axis 3: Decision Process Mapped

Do you have a complete map of who approves this, in what order, on what timeline?

Score	What it means	Concrete example
2	Full process documented: all approvers, sequence, and realistic timeline with dates	"CFO → Legal (2 weeks) → Procurement (1 week) → Sign. Champion mapped this; legal kickoff is May 15"
1	General shape known; gaps in approvers or timeline	"We know CFO approves but haven't confirmed the legal and procurement steps"
0	No process map; close date is AE-driven, not buyer-confirmed	"Close date is June 30 because it's end of quarter"

Axis 4: Next Customer Commitment Secured

Is there a buyer-owned next step — something they agreed to do — locked on their calendar?

Score	What it means	Concrete example
2	Specific buyer action with confirmed date; on their calendar, not just discussed	"Technical validation session confirmed for May 20; champion sent the invite"
1	Next step discussed and agreed; not yet calendared or confirmed in writing	"Champion said she'd get the security team in a room next week"
0	AE is driving all next steps; no buyer commitment exists	"I'm sending a follow-up tomorrow to try to schedule something"

Axis 5: Compelling Event Confirmed

Is there an external deadline — not your quarter — that forces the buyer to make a decision by a specific date?

Score	What it means	Concrete example
2	Buyer-named forcing event with a date; they articulated the consequence of missing it	"Current vendor contract expires July 1. Buyer said they can't renew — they need us in place before then"
1	Urgency exists but buyer hasn't explicitly named a forcing event; inferred	"Q2 budget close is coming and they seem motivated, but no hard deadline stated"
0	No urgency; deal moves at buyer's convenience or not at all	"They'll get to it when they get to it — no rush mentioned"

Scoring Helix Logistics $340K in 90 seconds

Here's a real-feeling deal. Helix Logistics, $340K ARR, forecasted to close June 30. You have this in commit. Your VP is about to ask why.

Run the rubric:

The read: Champion vouches for CFO support but you haven't spoken to him directly — that's a 1 on EB Engaged. Pain is confirmed at $2.1M annual impact, documented from the VP of Ops — that's a clean 2. Decision process: you know CFO approves but haven't confirmed legal and procurement steps — 1. Technical validation is locked for May 20 on the champion's calendar — 2. Q2 budget close is coming but the buyer hasn't explicitly said they must decide by then — 1.

Score: 7. That's Best Case, not Commit. Your VP will figure this out in 30 seconds. Better to move it yourself and own the story: "I'm putting Helix in Best Case this week. EB access is the open item — I have a call scheduled with the CFO on May 16. If that confirms, I'm moving it to Commit."

That's what a disciplined AE sounds like. That's what earns trust.

See also: Sample $180K AI fintech deal at 8/10 — Economic buyer confirmed via exec session, $2.4M pain quantified from internal audit, full decision process mapped.

Using the rubric to drive pipeline coverage decisions

The rubric isn't just for individual deal quality — it's how you manage coverage at the portfolio level. Once every deal in your pipeline has a score, the math becomes honest.

Score	Bucket	Coverage implication
8–10	Commit	Count at 90%+ toward forecast. Needs no qualification — evidence is strong.
5–7	Best Case	Count at 40–60%. Has path to close but material gaps remain. One step from Commit if gaps close.
3–4	Pipeline	Count at 10–20%. Early or thin. Needs more development before entering forecast.
0–2	Requalify / Cut	Do not count. Evidence is too thin to carry. Invest time or disqualify.

Run this across your whole pipeline going into a forecast call and you'll know in five minutes exactly where your coverage gaps are — and what actions would move scores up before the quarter closes. That's how CROs want their AEs operating. Not intuition about deals, but a documented map of where the gaps are and what it takes to close them.

See how this connects to structuring each deal's evidence for the weekly forecast call →

Common scoring mistakes

The rubric only works if the scores are honest. Here's where they stop being honest:

Inflating champion strength to compensate for missing EB access. The most common mistake. "My champion is rock solid — she's been pushing this internally for months." That's a 2 on champion engagement and a 0 on economic buyer engagement. They're separate axes. Conflating them is how a deal gets into commit when the CFO has never heard of you. See also: why champion-only deals slip →

Scoring intent as evidence. "The buyer said they're definitely moving forward this quarter." That's intent. It's not a signed commitment, not a calendared next step, not a confirmed procurement timeline. Buyer intent is a 1 on Next Customer Commitment — not a 2. A 2 requires something they did, not something they said they'll do.

Pre-scoring the compelling event. "Their contract expires in Q3, so there's definitely urgency coming." That's future urgency — it doesn't exist yet. Score on what's confirmed today. If the buyer hasn't told you they must decide by a date and explained what happens if they miss it, Compelling Event is a 0 or a 1. Score the deal you have, not the deal you're hoping for next month.

Rounding up to protect forecast position. A 6.5 is a 6 — Best Case. Don't round it to 7 and tell yourself it's close enough. The whole point of a rubric is to eliminate rounding in the wrong direction. If the score is 7, it's Best Case. Put it there, own the story, and focus on the specific axis that needs to move to get it to Commit.

See the full deal review structure that sits underneath this rubric in the enterprise deal review template → And if you want to see how a VP reads a deal review artifact, there's a walkthrough in how to write a deal review your VP will actually read →