Sales Storytelling Practice: A Scored Drill

What does a scored customer story look like?

A scored customer story passes three rows, each of which a manager can check from the transcript alone: the story answers a pain the buyer already stated, it names the customer's situation and outcome without invented figures, and it ends on a question the buyer has to answer.

We recommend writing the rows on one card and scoring pass or fail per row. Do not blend them into a single number. Read the trend per rep, per scenario.

This is the sales call story rubric in full:

Why must the story answer a pain the buyer already stated?

The story earns its place only when it answers a pain the buyer has already named on the call. If the transcript shows no buyer turn stating a problem before the story starts, row one fails, and the rest of the story does not rescue it.

Verify it in two steps. First, find the buyer turn that states the pain. Second, check that the rep's lead-in refers back to it, in the buyer's words rather than the rep's paraphrase. A passing lead-in sounds like this: You said handoffs between your two teams are dropping requests. We worked with a customer who described the same split.

If discovery has not produced a stated pain, we recommend the rep asks another question instead of telling the story. That is a separate judgment from this rubric, and it is not a pass. The drill certifies the story, so a withheld story is a scenario that has not yet been passed. Note the restraint in the debrief, then re-run with the pain stated.

How do you keep a customer story free of invented figures?

Every number the rep says must trace to a source line on a story card you approved before the drill. If the card has no figure, the rep states the outcome in words and uses no number at all.

Build one card per story, with five fields: the customer or an anonymized descriptor, the situation before, what changed, the outcome, and the source of the outcome. The source line names where the claim lives, such as a closed case record or a customer-approved write-up.

Checking takes a minute. Highlight every number in the rep's story turn and match each one to the card. An unmatched number fails the row. A matched number passes even if it sounds modest.

A passing line with no figure: Their dispatchers had been re-keying every order by hand. After the change, orders flowed into the schedule without re-entry. A failing line: They saw massive gains almost immediately. It names no situation, no outcome, and nothing a buyer could ask a follow-up about.

Before you rely on this row, we recommend scoring a few transcripts alongside a second manager. The rubric calibration guide covers how.

How should the customer story end?

The story ends on a question tied to the buyer's stated pain, and the next turn in the transcript belongs to the buyer. A story that ends on a statement keeps control with the rep.

Two checks make row three verifiable. The last sentence of the rep's turn is a question. The very next speaker is the buyer, which means the rep stopped talking after asking.

Tie the question to the pain from row one. A passing close: How does that compare with what you described on your side? A weaker close that technically passes the question test but fails the tie: Make sense? We recommend failing it, because it does not point back at anything the buyer said.

End on a question so the conversation stays in discovery. If your playbook defines exit criteria for discovery, the buyer's answer is a candidate piece of evidence toward them. See the discovery exit criteria scorecard for how to define that evidence.

How do you run this sales story drill each week?

Run it as the weekly 30-minute format we recommend: 5 minutes of setup, 15 minutes of drill, 10 minutes of debrief. Be honest about the prep. You spend about 10 minutes beforehand picking a scenario from a live deal and choosing the rubric row you will focus the debrief on.

Build the scenario from a real deal where the buyer has a nameable pain. We recommend designing it so the buyer persona, played by you, a peer, or an AI persona, states that pain at a set point in the call. With a scripted pain moment, row one is straightforward to score. The guide to building scenarios from real calls shows how to extract one.

Hand the rep the approved story card at setup. Tell them the call has one job: surface the pain, then decide whether and when to tell the story. We also recommend agreeing a short spoken ceiling for the story at setup, so the buyer's turn comes quickly. That ceiling is a drill guardrail you set, not a research finding.

The re-run for a failed attempt is its own scheduled session, not part of this 30 minutes. Keep the pipeline 1:1 separate as well. This drill is practice, not deal review. The coaching vs deal review article explains why the two need separate calendar slots.

What is the pass bar for the drill this week?

The pass bar is all three rows passing in a single attempt on a scenario where the buyer states a pain. Two of three is a fail, and the failed row is what you re-run.

Run it this way:

1. Before the session, pick one live-deal scenario and write the buyer's pain line the persona will deliver. Approve one story card with a source line.

2. Open the session with the rep stating the call purpose. The persona states the pain after the rep has asked at least one question.

3. The rep decides when to tell the story. Do not prompt. Timing is part of row one.

4. Score each row pass or fail from the transcript, with the line number beside each verdict.

5. If the rep passes all three rows, schedule a second scenario with a different pain and a different story card. One pass on one scenario certifies one scenario.

Do not let the rep self-report a pass. The exit criterion is what the transcript shows: a buyer turn naming the pain, a story whose numbers all match the card, and a buyer turn following the closing question. If any of those three pieces of evidence is missing, the attempt fails.

What does a failing attempt sound like, and what is the re-run rule?

The failing attempt is a story told before discovery that the buyer never asked for. It fails all three rows at once.

Here is a sample:

Rep: Thanks for making time. Before we get into your goals, let me tell you about a company like yours. They had a lot of manual work, and we fixed it. Huge results, and they love us. So, any questions for me?

Buyer: Not yet. I'm not sure what you're comparing us to.

Score it row by row. Row one fails: the buyer had not stated any pain, and the rep said before we get into your goals. Row two fails: a company like yours names no situation, we fixed it names no outcome, and huge results is unsourced. Row three fails: any questions for me is not tied to a stated pain, and it asks the buyer to produce a pain from nothing.

The re-run rule: a failed attempt is re-run, never excused. Run a single debrief per the one-behavior debrief format. Pick the one moment that matters most, here the decision to tell the story before the buyer named any problem. Ask the rep to diagnose it first, in their own words. Then give your verdict. Before the debrief ends, put the re-run on the calendar as its own session within the same week, on a new scenario so the rep cannot simply recite the first one.

Where does this rubric not fit?

This rubric fits any methodology whose stage definitions place stories after the buyer states a pain. It fits poorly where your playbook asks for an insight early in the call, and it does not apply when you have no customer outcome to tell.

Challenger is the clearest case. Its teach-tailor-take-control sequence opens with a commercial insight that reframes the buyer's problem, which can come before the buyer has named a pain. If your team sells that way, we recommend rewriting row one to check the stage your playbook defines, and keeping rows two and three as written. We would not fail an early insight under a rule written for another playbook. Our position is that roleplay scoring only changes behavior when it is graded against the organization's own methodology and call stages, so load your stage rules into the rubric.

Two other limits. First, if a story card has no approved source, the rep has no story to tell yet, and drilling delivery is premature. Get the source first. Second, with a brand-new product there may be no customer outcome at all. In that case, the launch certification work in product launch sales enablement is the better starting point than a customer story.

Finally, this drill certifies one behavior: telling a sourced story at the right moment and handing control back. It does not certify that the buyer was persuaded. Treat persuasion as a separate scenario with its own exit criteria.