Skip to main content
DoneThat

AI Adoption GuideSalesDiscover

Methodology scorecard

An LLM scores calls against MEDDPICC, SPIN, or Sandler frameworks, using tools like Hyperbound.

Sales processProspectQualifyDiscoverProposeNegotiateCloseHandoffRenew

By Don, DoneThat’s AI coach · updated

Score the call against the play you publish

A methodology scorecard rates one recorded call against the single play your team already trains, with a cite on every element. It is not a second forecast, a ranking of AEs, or a number you pay on.

Pick one methodology and publish it. This page uses MEDDPICC because that is the play most enterprise teams already print on the opportunity. Use SPIN or Sandler if that is what you certify. Scoring the same recording against all three is the usual failure: the intro fails Paper Process, fails Need-payoff, and fails the Up-Front Contract, and the AE cannot tell which miss was in scope.

Publish the play that enablement already teaches. For each MEDDPICC element, write what covered sounds like, what missed sounds like, and which call types treat it as out of scope. Hidden criteria make the score look like a trap.

Tools in this class include Hyperbound, Gong, Chorus, and Salesforce. They sit on recordings, practice tapes, and the opportunity. This page does not rank them. None of them should move stage, write Closed Lost, or open a PIP because a number came back low.

The card answers one question: did the rep run our play on this call? A rep who closes while scoring badly is information about the play, or about the call type you scored, not automatic proof the rep is the problem.

Quote each element, or mark it out of scope for this call

Label every MEDDPICC element covered, missed, or out of scope. Covered and missed need a cite. Out of scope needs the call type.

Covered means a quote: speaker, date, timestamp. "Champion identified" is not a cite. "Avery, 18:02: I will bring our VP of Ops to a working session" is a cite.

Missed means this call type required the element and it never appeared. Write the probe you wanted. Do not invent a buyer number, a paper process, or a competitor to complete the card.

Out of scope means this meeting was never supposed to carry that element. Scoring a first intro as if it were a complete discovery is how a clean twenty-minute call looks like a failure. Paper Process and a full Competition pass do not belong on a first meeting unless the buyer brought them.

Write the call-type map beside the rubric so the model cannot fail an intro for skipping Paper Process:

  • First intro: Identify Pain, a Champion if one showed up, Decision Process only if the buyer described next steps. Metrics only if they volunteered a number. Economic Buyer, Decision Criteria, Paper Process, Competition: out of scope unless the buyer raised them.
  • Working discovery: Metrics, Identify Pain, Champion, Decision Criteria, Decision Process, Competition if a rival was named. Paper Process stays out of scope until procurement or legal is in the room.
  • Late-stage review: the full MEDDPICC set, including Paper Process.

MEDDIC auto-extraction writes suggested Salesforce fields from the same transcript and leaves blanks blank. That is CRM hygiene. This card is coaching. A blank Metrics field might be an extraction miss, an out-of-scope intro, or a rep who never asked. Only the quote tells you which.

If you need the questions still open for the next meeting, use the discovery gap analyzer. Do not average gaps, extracted fields, and play scores into one number. You will coach the number instead of the call.

Illustrative review: Westbrook Freight, first discovery

The following is a made-up coaching review, not a case study and not reported results.

An AE manager reviews a first discovery with Westbrook Freight, a mid-market 3PL. The recording runs twenty-four minutes. The published play is MEDDPICC. The model returns a low overall score because Metrics, Economic Buyer, Paper Process, and Competition are empty, and empty is treated as failed.

The manager reads the quotes, not the overall score.

  • Identify Pain, covered. Buyer at 06:40: "Peak week we still build the labor plan in a spreadsheet, and we overstaff or understaff by a day either way."
  • Champion, covered. Same speaker at 18:02: "I will bring our VP of Ops if we do a working session."
  • Decision Process, thin. Buyer at 19:10: "We would need a security review before anyone else joins." No sequence after security, no date.
  • Metrics, missed and in scope. The labor-plan pain was on the table and the AE never asked what a missed peak week costs.
  • Economic Buyer, out of scope. The VP was named, not on the call.
  • Paper Process, out of scope.
  • Competition, out of scope. Nobody named a rival.

The manager leaves the opportunity in Salesforce where the AE left it. No stage slip, no Closed Lost, no performance file. The coaching note is one line: next meeting, cost the spreadsheet miss, and get the VP of Ops in the room.

They do not repair the score by stacking SPIN implication questions and a Sandler Up-Front Contract onto the same card. Those extra frameworks would have failed the same intro for different reasons and still would not have taught the AE the Metrics probe.

Outliers go to the manager. The deal stays open.

Run this loop: score with quotes, queue outliers, coach in 1:1, leave the opportunity alone.

Queue lows (in-scope elements with no quote) and suspicious highs (perfect scores on obvious intros, which often means the model rewarded a talk track). The AE's manager reviews those. Ops can build the queue. Ops does not close the coaching.

A low score is a coaching note. It is not quota, a SPIFF gate, or automatic input to a PIP. Pay or punish the overall number and the calls start being performed for the scorer. Reps will drop a Metrics sentence into the last two minutes so the model hears a digit, whether or not the buyer owned it.

Do not auto-fail the deal. A missed Metrics probe on a first discovery is unfinished work. Suggested CRM next steps belong in post-call summary and CRM auto-update, and the AE confirms before anything overwrites. The scorecard itself does not write fields and does not change stage.

Do not use the score as quota. A team target on average score turns the rubric into weekly activity. You will see more scored calls and shallower discovery. Watch whether managers reviewed the outlier queue, whether the note named a next probe, and whether the same in-scope miss shows up on the next working session. Do not publish a lift in scores and call that enablement.

If the AE disputes a miss, argue from the quote. No quote means the miss stands, or you relabel it out of scope. A single ugly intro is not a trend. Look at the next in-scope working session before you escalate. A PIP is a people decision, not a threshold on this card.

Keep live prompts and role-play off this card

Live guidance during the call is a separate surface. Real-time call coaching can surface a probe while the buyer is still talking. Do not add ignored prompts as extra penalty points on MEDDPICC. An ignored prompt is a 1:1 topic.

Calibrate on practice tapes before you score production. Negotiation role-play simulator is the rehearsal lane against the same published play. Score those tapes against calls your best managers already scored by hand. If the model and the manager disagree on in-scope misses, fix the rubric. Do not correct the manager to match the model.

Leave Hyperbound, Gong, Chorus, and Salesforce as a class. The operating rule is one published play, a quote on every in-scope element, a manager on the outliers, and a deal that does not fail because an intro was not a full discovery.

Is this worth automating for you?

Whether this pays back depends on how much time it takes your team today. Most teams estimate that from memory, and the estimate is usually wrong in one direction or the other.

DoneThat reconstructs where the time actually went, with no timers to forget, so you can measure the baseline before committing to a project and check the gain afterward.

Measure the baseline first