The Mock-Call Role-Play Workshop Reboot — 60-Min Training

Question

Pulse RevOps · The Machine · Accepted Answer

### Direct Answer

> **Most mock-call role-plays fail because they're low-stakes theater: the manager plays a soft buyer, there's no rubric, and nobody watches the tape.** Reboot the workshop with three structural changes: (1) build a **production-grade buyer persona brief** the AE prepares against, (2) score every rep on a **4-axis rubric — Discovery, Objection Handling, Value Framing, Next-Step Commitment** — out of 40 points, and (3) **record every rep and watch it back together**. The manager is coach, never buyer. Below is a runnable 60-minute agenda for a sales manager and 6-10 AE/SDR team in B2B SaaS ($25K-$500K ACV).

---

## Section 1 — Why Most Role-Plays Fail (5 min)

Open the meeting by naming the failure mode directly. Keith Rosen, in *Coaching Salespeople Into Sales Champions*, calls the typical mock call "the most wasted 15 minutes in sales management." Three reasons:

- **Low stakes.** Nobody watches the recording, nothing changes in the CRM, nobody gets coached again next week. The rep performs, gets a "good job," and forgets it.
- **Manager-as-buyer.** The manager softens objections, accepts weak discovery, and tips the rep toward the "right" answer. Anders Ericsson's deliberate-practice research (*Peak*, 2016) is unambiguous: practice without honest, immediate, expert feedback against a defined standard produces zero skill gain.
- **No rubric.** "That was good, work on your discovery" is not coaching — it's vibes. Force Management's MEDDICC role-play guidance and Pavilion's enablement playbooks both require a written scoring sheet before the call starts.

Tell the team: **today we fix all three.** Persona on paper, rubric on the table, camera on, manager silent.

## Section 2 — The Production-Grade Persona Brief (15 min)

Hand each AE one of these two persona cards. Do not let them improvise — read it verbatim.

**Persona A — "Skeptical RevOps Director, Mid-Market SaaS"**
- **Name:** Dana Okafor, Director of Revenue Operations, 480-person Series C HR-tech company.
- **Reports to:** CRO. Has been burned by two prior tool purchases that didn't get adopted.
- **Stack:** Salesforce, Outreach, Gong, ZoomInfo. Already over budget on tools by 12%.
- **Trigger:** CRO asked her to "fix forecast accuracy" — currently swinging ±18% per quarter.
- **Hidden objection:** She thinks the real problem is rep discipline, not tooling. Will say "we already have Gong" within the first 5 minutes.
- **Decision style:** Wants proof of ROI in writing. Will not move without a peer reference.

**Persona B — "Founder-CEO, 35-person Series A"**
- **Name:** Marcus Liang, CEO, 35-person developer-tools startup, $4M ARR.
- **Owns the deal personally** because there's no VP Sales yet.
- **Calendar:** Took the call only because a board member made the intro.
- **Trigger:** Just raised an $18M Series A; board wants pipeline coverage of 4x by Q4.
- **Hidden objection:** Worried any tool spend "looks bloated" to the board. Will push for a 6-month pilot at 50% off.
- **Decision style:** Fast, intuitive, but loops in two co-founders before signing anything over $40K.

Mike Weinberg's rule from *New Sales. Simplified.* applies here: **a persona without a budget, a trigger, and a hidden objection is a fantasy, not a prospect.** These three fields are what make the role-play production-grade.

## Section 3 — The 4-Axis Scoring Rubric (10 min)

Print and distribute this rubric. Every observer scores every rep. The manager publishes the average.

**Axis 1 — Discovery (0-10 pts)**
- **0-3:** Asked feature questions, never uncovered a business problem.
- **4-6:** Found a surface pain ("forecast is off") but didn't quantify it.
- **7-8:** Quantified the pain in dollars or hours, tied it to the persona's stated trigger.
- **9-10:** Got the prospect to articulate the cost of inaction in their own words.

**Axis 2 — Objection Handling (0-10 pts)**
- **0-3:** Argued, defended, or oversold past the objection.
- **4-6:** Acknowledged but pivoted too quickly back to pitch.
- **7-8:** Used a clarifying question to isolate the real concern before answering.
- **9-10:** Reframed the objection as a shared problem and got verbal agreement on the reframe.

**Axis 3 — Value Framing (0-10 pts)**
- **0-3:** Listed features. Said "AI-powered" more than twice.
- **4-6:** Connected one feature to one outcome.
- **7-8:** Tied value to the persona's specific trigger and metric.
- **9-10:** Used a peer-customer story with a named company and a specific result.

**Axis 4 — Next-Step Commitment (0-10 pts)**
- **0-3:** "I'll send some info."
- **4-6:** Vague follow-up, no calendar hold.
- **7-8:** Booked a specific next meeting with a stated agenda.
- **9-10:** Booked the next meeting, named the required attendees on the prospect side, and got a verbal yes to bring them.

**40 points total.** Anything under 28 means the rep does it again next week.

## Section 4 — The Role-Play Block (10 min)

Two reps go. **8 minutes each, hard stop.** Manager hits record on

The Mock-Call Role-Play Workshop Reboot — 60-Min Training

Direct Answer

Section 1 — Why Most Role-Plays Fail (5 min)

Section 2 — The Production-Grade Persona Brief (15 min)

Section 3 — The 4-Axis Scoring Rubric (10 min)

Section 4 — The Role-Play Block (10 min)

Section 5 — The "Video It Back" Recording Loop (15 min)

Section 6 — Close, Commit, Calendar (5 min)

FAQ

Sources

The Mock-Call Role-Play Workshop Reboot — 60-Min Training

Direct Answer

Section 1 — Why Most Role-Plays Fail (5 min)

Section 2 — The Production-Grade Persona Brief (15 min)

Section 3 — The 4-Axis Scoring Rubric (10 min)

Section 4 — The Role-Play Block (10 min)

Section 5 — The "Video It Back" Recording Loop (15 min)

Section 6 — Close, Commit, Calendar (5 min)

FAQ

Sources

What does the score mean?