Sales Readiness Scoring: From Gut Feel to Evidence

A readiness score must gate something named

One line in a ramp plan separates sales readiness scoring from reporting: Gate: mid-market discovery scenario. Pass bar: all exit criteria met on 3 consecutive scored roleplays. Grants: solo discovery calls. Signed: the rep's manager, dated. Every word is load-bearing. The scenario is named, the pass bar is observable, the privilege is concrete, and a person signs it.

A readiness threshold must grant or block something specific: solo discovery calls, lead-tier routing, demo certification. If a rep crosses the threshold and nothing changes about what they are allowed to do, you built a dashboard. A readiness score that never grants or blocks a named privilege is reporting, not readiness scoring.

The signature matters as much as the threshold. We recommend that leadership set the pass bars so gates stay consistent across teams, and that the frontline manager sign each decision, because the manager owns the consequence when an unready rep takes a live buyer. Every checkpoint carries one of three outcomes: advance, repeat, or escalate. Gut feel survives wherever nobody has to put a name on the call.

What should a sales readiness score measure?

Score observable behaviors: actions a manager could verify from the transcript without sitting in on the session or trusting anyone's memory. If two managers reading the same transcript could disagree about whether the behavior happened, the row is written wrong. No rubric row belongs on a readiness scorecard unless a manager can verify it from the transcript alone.

Three example rubric rows set the standard. Builds the cost of inaction before naming a solution. A pass sounds like an implication question in the SPIN sense: You said the missed handoffs cost you the Q3 renewal. What happens if that repeats next quarter? A fail sounds like product capabilities arriving before any cost has been established. Isolates an objection before answering it. A pass sounds like: If pricing were solved, is anything else stopping a start date? A fail sounds like a discount offered one turn after the buyer says the price is high. Rows like it come straight out of scored objection drills.

Secures a buyer-verified next step. A pass sounds like the buyer confirming date, attendees, and purpose in their own words. A fail sounds like: I'll send some information and follow up next week. A row without a described fail lets every borderline attempt through.

What should you ignore when scoring readiness?

Ignore any input a rep can improve without getting better in front of a buyer. Course completions, quiz scores, activity counts, self-ratings, and confidence in the debrief rise with tenure and effort; none survives contact with a buyer who pushes back. They measure participation. Sales readiness is performance.

One input stays on the scorecard but never becomes a pass bar: talk/listen ratio. It sits on real scorecards, including our own scoring model, as a diagnostic to investigate. A lopsided ratio tells you where to read the transcript; it cannot tell you what went wrong by itself. Scoring the ratio pass/fail teaches reps to perform silence instead of asking better questions.

Polish belongs on the ignore list too. Smooth delivery reads well in the room and vanishes in a transcript. A hesitant rep who isolates the objection outscores a fluent rep who answers the wrong one.

Trend readiness per rep, per scenario

Readiness is scenario-specific. A rep who passes the mid-market discovery scenario can still fail the renewal-negotiation scenario, and averaging the two produces a number that describes neither. One blended score across scenarios is the surest mark of a fake readiness system. Blending is how a rep who has never survived a pricing objection gets rated ready because their discovery scores were strong.

The working view is a grid: reps down the side, named scenarios across the top, each cell holding the latest result and its direction across attempts. Gate decisions read one cell, never a row average. Direction matters as much as the latest score; we recommend 3 consecutive passes on the same scenario before any gate is signed, because one pass after four fails is a good day, not a capability.

The same-scenario rule invites a fair objection: by run 3, the rep has heard the buyer's moves twice, so a pass may prove recall rather than skill. We accept the trade-off and blunt it by varying the inside of the scenario while the shell stays fixed: the buyer's resistance level, the order objections arrive in, which detail the buyer withholds. The scored behavior and its exit criterion never change, and the pass bar resists scripting on its own; buyer-verified evidence has to be earned live, no matter how familiar the setup feels.

Trended per rep per scenario, ramp decisions stop being debates. When a manager and a skip-level disagree about whether a rep is ready for solo discovery calls, the tiebreaker is not seniority. It is the same three transcripts, read against the same rubric rows.

How do you measure sales training effectiveness?

Measure sales training effectiveness by gate movement, not by average scores. Two signals do the work: whether reps reach signed gates in fewer attempts than the cohort before them, and whether passes hold when a scenario is re-tested weeks later. Average scores drift upward for reasons unrelated to skill, including rubric drift and scorer sympathy. Gates resist inflation because someone signs them and owns the result.

Measurement needs a steady supply of scored attempts, so readiness scoring sits on top of a weekly practice format that produces scores rather than quarterly certification events. A weekly cadence gives every rep repeated attempts per scenario, enough to show a trend instead of a snapshot. It also surfaces program-level signals: which scenario stalls the most reps, which gate takes longest to sign, where passes decay on re-test.

The drill card: certify the next-step close

A gate needs a drill that produces its evidence. One drill card certifies one behavior for one gate; the card here feeds a solo-calls gate.

Roles: the manager plays the buyer, working from a live deal in the pipeline; the rep runs the scenario as themselves. · Time-box: we recommend 10 minutes live and 5 of debrief, plus about 10 minutes of manager prep beforehand to pick the scenario and the rubric row. · Rep count: we recommend 2 reps per session, alternating between running the scenario and observing with the rubric row in hand; an observed-then-run attempt still counts toward a gate, because the buyer's resistance and objection order change between runs. · Behavior scored: securing a buyer-verified next step, with date, attendees, and purpose, before the conversation ends.

Pass bar: the buyer confirms all three elements in words the rep did not feed them. The rep proposing them is not enough; exit criteria are buyer-verified evidence, not rep opinion. A failing attempt sounds like: Great conversation. I'll send a recap and we can find time next week. No date, no attendees, no purpose, nothing for the buyer to confirm.

Debrief script: the rep self-diagnoses first: Where did I try to land the next step, and what did the buyer actually confirm? The manager names one behavior, only one: You proposed Tuesday but never asked who else needed to be in the room. The re-run is scheduled then and there. Re-run rule: a failed drill re-runs the same scenario, not a fresh one. A new scenario hides whether the behavior changed; the same scenario proves it.