How to Qualify B2B SaaS Deals in a Velocity Motion (The 5-Point Rubric)

Every bad forecast starts the same way: a deal that should never have entered pipeline, entered pipeline. It sat there for six weeks, absorbed two demos and nine follow-ups, inflated coverage, and died the death it was always going to die. Multiply by ten and that's a quarter.

The fix is not a heavier framework. In a velocity motion (ACVs of $2K to $24K, cycles under 90 days), you cannot spend 45 minutes excavating Metrics, Economic Buyer, and Decision Criteria on a deal worth $8K. The fix is a rubric: five binary questions, scored in under a minute, applied to every deal with zero exceptions.

What is a sales qualification rubric?

A sales qualification rubric is a fixed scorecard a sales team uses to decide whether a deal deserves to enter and stay in the pipeline. In a velocity sales motion it has five binary dimensions: trigger (a specific event created this conversation), fit (the account matches the ICP), authority (the contact can buy or directly convene the buyer), cost of status quo (the buyer stated what doing nothing costs them), and path (a buyer-committed next step with a date exists). Each dimension scores 0 or 1 based on evidence from the conversation, never on the rep's optimism. Deals scoring 4 or 5 advance, 3 gets one targeted gap-closing action, and 0 to 2 moves to nurture. The same rubric is reused to requalify stalled deals, which keeps pipeline coverage honest.

Why not just use BANT or MEDDIC?

Because both were built for a different weight class. BANT front-loads budget, and velocity buyers often don't have a named budget line for a $6K tool; they have a problem and a credit card. MEDDIC is a committee-navigation system for six-figure deals with 6+ stakeholders; running it on a 14-day cycle is like filing a flight plan to cross the street. I've written the full comparisons in BANT vs MEDDIC and MEDDIC Doesn't Work for $10K Deals.

What velocity qualification needs is speed with discipline: few enough questions that reps actually run them on every deal, binary enough that two reps score the same deal the same way.

The 5 points, and what earns the point

1. Trigger. Why this conversation, why now? Something happened: they hired reps, lost a deal, missed a quarter, got budget, churned off a competitor. The point is earned when the buyer names the event. No trigger means no urgency, and no-trigger deals are where follow-up sequences go to die.
2. Fit. Are they actually your ICP? Company size, motion, industry, use case: whatever your ICP definition says. The point is earned by facts you can verify, not by "they could probably use it." Selling outside ICP is how you win deals that churn in month four.
3. Authority. Can this person buy? At velocity ACVs there is usually one buyer. The point is earned when your contact either owns the decision or has directly agreed to bring the owner into the next call. "I'll share it with my boss" scores zero; "I've booked my boss for Thursday" scores one.
4. Cost of status quo. What does doing nothing cost them, in their words? Not your pitch reflected back. The buyer says something like "we're losing about two deals a month because nobody follows up." That sentence is the point. If they can't articulate a cost, they won't fight for the purchase when something else competes for the money.
5. Path. Is there a buyer-committed next step with a date? A demo on the calendar, a decision meeting booked, a pilot scoped. Committed and dated, by the buyer. This is the same standard the weekly pipeline review holds every live deal to; deals without it aren't deals yet.

Scoring: what happens at each score

The number that matters most is the 3. Teams without a rubric let 3s pile up in pipeline because each one individually feels close. A rubric forces the discipline: a 3 gets exactly one gap-closing action, then it either becomes a 4 or leaves the pipeline. "Develop" is a state with a timer on it, not a parking lot.

Where the rubric runs

• End of discovery. Score the deal in the last two minutes of the call, while the evidence is fresh. The five points map to the five discovery questions, so a well-run discovery call produces the score as a byproduct.
• Entry into pipeline. No deal enters the CRM as an opportunity below a 4. This single rule does more for forecast accuracy than any forecasting method, because it stops fiction at the door.
• Requalification of stalled deals. When the weekly pipeline review flags a deal past its time-in-stage benchmark twice, the stalled-deal protocol's first option is "requalify": run the rubric again with current evidence. Triggers expire. Authority changes. A deal that scored 5 in March can be a 2 in May, and the rubric is how you notice.

The failure modes to watch

• Scoring hope instead of evidence. The fix is the phrase "in their words." Every point needs a sentence the buyer actually said. If the CRM note can't quote it, the point wasn't earned.
• Rubric drift. Reps under quota pressure start rounding 3s up to 4s. The counter is public scoring: the score gets said out loud in the pipeline review when the deal enters, and anyone can challenge a point.
• Treating nurture as failure. A 2 with a real trigger arriving next quarter is future pipeline. Move it to nurture with a revisit date and it comes back warm. Force it into pipeline now and it burns 20 rep-touches dying slowly.

And if the deeper problem is that "qualified" means something different to every rep on your team, that's not a rubric problem. That's a missing playbook. The SAILS engagement builds the rubric calibrated to your ICP and motion, then installs it in discovery, CRM fields, and the weekly review cadence.