12 Sales Role Play Scenarios You Can Run This Week, With Buyer Briefs and a Scorecard

The scenario is the difference between role play that people dread and role play that works. “You be the customer, I'll be the rep” produces five awkward minutes and vague feedback. A card that says who the buyer is, what they open with, and what they are hiding produces a conversation you can run twice and compare.

Most lists of sales role play scenarios stop at a title and a sample dialogue. A dialogue shows one way the call could go. It does not tell the person playing the buyer what to do when the rep says something else, which is always. The scenarios here are written as briefs instead, so they survive contact with a real rep.

One disclosure: SnapSDR runs on Tough Tongue AI's agent infrastructure, and Tough Tongue AI offers AI sales roleplay. It is named once below, next to tools from other vendors. Everything else on this page works with two people and a printed card.

Five parts. If a scenario is missing one, the run usually falls apart in a predictable way.

The twelve cover the moments where calls most often go wrong: the first ten seconds, the buyer who will not talk, the executive who joins late, the price conversation, and the renewal. Each takes five to ten minutes per run.

The first three are about earning the next thirty seconds. In the brush-off and the gatekeeper, the rep passes by being plain about why they are calling. The inbound callback is the easiest of the twelve and the one most teams never practise, even though a fast, competent first call is the whole point of speed to lead. If your team makes outbound calls at volume, pair these with our comparison of AI cold calling tools.

These four test whether a rep can keep asking questions when the buyer makes it uncomfortable. The one-word buyer punishes closed questions. The founder who says “just show me the product” punishes reps who treat discovery as a checklist to finish before the demo starts. In the demo scenarios the pass criteria are about stopping: stop the walkthrough for the CFO, stop bluffing about the missing feature. Our guide to product demo best practices covers what the full demo should look like around these moments.

The last five share a pattern. The stated objection is not the real one, and the hidden fact is the real one. “It works fine” hides low adoption. “Take 30% off” hides a start date. “Why am I paying more” hides a support ticket. A rep who answers the stated objection fails the scenario even with a good answer, which is exactly the habit you want them to lose before a live deal.

Use three people: a rep, a buyer, and an observer who scores. Run the scenario twice. The second run is where the learning is, and it is the part that gets cut when a session has no clock.

Three rules keep it honest. The buyer does not break character, even to be kind. The rep gives their own feedback first, because people fix what they noticed themselves. And the observer limits feedback to one thing to keep and one thing to change. A list of nine improvements guarantees that none of them shows up in the rerun.

With six reps, split into two groups of three and rotate roles across three scenarios. Everyone gets one turn in each seat in an hour.

Score five things, one to five each, the same way every time. Four of the rows apply to any sales conversation. The fourth row, the hard moment, is where the scenario's own pass criteria go.

Keep the scores. A rep who goes from 13 to 19 on the same scenario over three weeks has something concrete to point to, and a manager who sees the whole team stuck at 2 on “Next step” knows what next week's session is about.

Hard enough that the rep fails some runs, and no harder. Every scenario above can be played at three levels by changing how the buyer behaves, without rewriting the card.

Move a rep up a level after two runs at 21 or above, and down a level after two runs under 15. Staying on a level where every run passes feels good and teaches little.

All three, for different jobs. The question is which repetitions deserve a person's time.

AI roleplay tools take a brief much like the cards above and turn it into a voice conversation. PitchMonster and Quantified publish their own scenario lists, Yoodli offers AI roleplays, and Tough Tongue AI describes its sales roleplay as AI buyers that push back, with structured feedback after each session, and lists a free tier with 25 one-time minutes (pricing page, November 2026). A card from this page pastes into any of them: the buyer brief and hidden fact become the persona, and the pass criteria become the scoring rubric.

We compare the tools themselves in 5 best AI sales coaching tools and in our list of Hyperbound alternatives. Whatever you pick, keep a person in the loop for the scenarios tied to a live deal. An AI buyer can tell a rep whether they asked about timing. It cannot tell them whether this account's CFO will care.

You do not need all twelve. Pick the three scenarios closest to the calls your team lost last month, rewrite the buyer brief with your own industry and numbers, and run one 20-minute session this week with a rerun and a score.

Our recommendation: use people for the first run of a new scenario and for anything tied to a live deal, and use an AI buyer for the repetitions in between. Keep the scorecard the same in both, so a 19 means the same thing whoever played the buyer.