Sales Training By Anthony Calise Updated August 15, 2026

12 sales roleplay scenarios worth drilling

Most sales roleplay fails for the same two reasons: the scenario is too vague ("okay, sell me the product") and the fake buyer is too nice. A colleague playing a prospect will fold in ninety seconds because they want you to succeed and they feel awkward being difficult. Real buyers feel no such obligation. Below are twelve scenarios with the buyer written properly - what they want, what they're hiding, and how hard they should push - plus what to actually score.

Quick Answer

A useful roleplay scenario needs three things the generic version lacks: a specific buyer with a motive (not "a prospect"), a defined difficulty (how hard do they push, and what makes them fold), and one thing you're scoring rather than a vague sense of how it went. Run scenarios in the order below - reflexive brush-off, then discovery, then objections, then multi-stakeholder - because each one assumes the skills from the one before. Ten minutes on one scenario beats an hour of freestyle roleplay.

What makes a scenario worth running

The three-part spec

The buyer's motive. Not "a VP of Ops" but "a VP of Ops who has already been burned by a tool like yours and has to justify the last purchase to her boss."

The difficulty setting. How hard do they resist, and what specifically makes them open up? A buyer who folds to anything teaches nothing; one who never folds teaches despair.

The single scored skill. One thing. "Did the rep get to a real problem before mentioning the product?" A roleplay that scores everything scores nothing.

Tier 1: The first thirty seconds

1. The reflexive brush-off

Buyer: Busy, mid-task, not hostile - just running the standard dismissal without thinking. Says "not interested" before the rep finishes their second sentence.
Difficulty: Repeats the brush-off once. Engages only if the rep asks a specific question rather than pitching.
Score: Did the rep resist the urge to argue or pitch, and instead ask one concrete question?

2. The gatekeeper

Buyer: An assistant whose job is to prevent this call. Polite, immovable, offers to take a message.
Difficulty: Will not transfer to a vague pitch. Will consider it if the rep is specific, honest, and treats them as a person with authority - which they have.
Score: Did the rep respect them or try to trick them? Tricks fail and poison the account.

3. "Send me some info"

Buyer: Mildly interested but wants the call over. Genuinely will not read the email.
Difficulty: Repeats the request twice. Concedes to a specific short next step, never to "when would be good?"
Score: Did the rep find out what "info" was standing in for? See the full breakdown.

Tier 2: Discovery

4. The buyer who won't say the problem

Buyer: Interested, agreeable, answers every question with something pleasant and useless. "Yeah, it's fine, we manage."
Difficulty: Concedes a real problem only after the third specific, non-leading question. Immediately retreats if the rep pitches.
Score: How many questions before the rep mentioned the product? More is better. Most reps break by question two.

5. The over-sharer

Buyer: Talks for ten minutes about three problems, two of which you can't solve.
Difficulty: Keeps going unless interrupted. Doesn't mind being interrupted.
Score: Did the rep isolate the one problem they can address, and say plainly that they can't help with the others? Honesty here builds more trust than any feature list.

6. The wrong person

Buyer: Enthusiastic, engaged, has zero budget authority and won't volunteer that.
Difficulty: Answers direct questions about authority honestly, but only if asked.
Score: How long before the rep established who signs? Deals die here more than anywhere.

Tier 3: Objections

7. The price objection

Buyer: Wants it, thinks it's expensive, hasn't quantified the problem it solves.
Difficulty: Pushes for a discount twice. Accepts value framing only if the rep has established a cost of inaction earlier in the call.
Score: Did the rep discount immediately? That's the fail state. See handling the price objection.

8. The incumbent competitor

Buyer: Already using a competitor. Signed it themselves, so criticism of it is criticism of them.
Difficulty: Defensive if the rep attacks the competitor. Opens up if asked what they'd change about it.
Score: Did the rep trash the competitor? Instant fail. See the incumbent objection.

9. "We don't have budget"

Buyer: Real constraint, but the timing is soft and there's discretionary spend if the problem is urgent enough.
Difficulty: Holds firm on "no budget" until the rep separates the money from the priority.
Score: Did the rep accept the objection at face value and leave? Most do.

10. The bad-experience buyer

Buyer: Bought something similar, it failed, they took the blame internally.
Difficulty: Hostile to promises, receptive to specifics about implementation and failure modes.
Score: Did the rep acknowledge the risk honestly, or promise it'd be different this time? The second one loses.

Tier 4: Late-stage

11. The multi-stakeholder deal

Buyer: A champion who wants it and a sceptical finance stakeholder who joins halfway through.
Difficulty: The champion advocates badly and misrepresents a detail. Finance asks the question the champion can't answer.
Score: Did the rep correct the champion's error in front of finance? Uncomfortable, and necessary - letting it stand kills credibility later.

12. The deal that went silent

Buyer: Was engaged, then stopped replying for three weeks. Priorities shifted; slightly embarrassed about the silence.
Difficulty: Responds well to a direct, unbothered re-open. Withdraws further if guilt-tripped or chased.
Score: Did the rep make it easy for the buyer to come back without apologising?

How to run these properly

  1. One scenario per session. Ten minutes on the price objection beats an hour of drifting.
  2. Set the difficulty before you start. Both people should know exactly what makes the buyer fold. Otherwise the buyer improvises mercy.
  3. Run it three times. First is a mess, second is thinking, third is where the skill actually forms. Stopping after one is why most roleplay doesn't work.
  4. Score one thing. Write it down before starting. Feedback on everything is feedback on nothing.
  5. Record it. Reps consistently misremember their own calls, particularly how early they started pitching.

The full method is in how to run a sales roleplay that actually helps.

The problem with practising against colleagues

Every scenario above depends on the buyer staying in character while being difficult. That's precisely what colleagues can't do. They know you, they want you to do well, and holding a hostile persona for ten minutes against a friend is socially exhausting - so they soften, and you practise against a buyer who doesn't exist.

They also aren't available. Roleplay requires two calendars to align, which is why it gets scheduled monthly and happens quarterly. The reps who improve fastest are the ones who can run scenario 7 fifteen times on a Tuesday evening without asking anyone for anything.

That's what CloserLab is for: an AI buyer generated from your actual offer, holding character at the difficulty you set, pushing back the way a real prospect does, and scoring the call the second you hang up. Voice or text, no colleague required.

Practice it before it costs you a deal

CloserLab generates AI buyers from your actual offer, holds character through the whole call, and scores you the second you hang up. Voice or text, no account required. Free on the App Store.

Download CloserLab - Free

Frequently Asked Questions

What is a good sales roleplay scenario?

One with three things specified: a buyer with an actual motive rather than a generic job title, a defined difficulty setting including what makes them open up, and a single skill you are scoring. "Sell me this product" fails all three, which is why it teaches nothing. "A VP who bought a competing tool last year and has to justify that decision to her boss, who opens up only if asked what she would change about it" is a scenario you can actually learn from.

How often should a sales team run roleplays?

Short and frequent beats long and rare. Ten to fifteen minutes on one specific scenario, two or three times a week, produces far more improvement than a monthly hour-long session - partly because skills form through repetition and partly because the monthly session gets cancelled. Run the same scenario three times in a row rather than three different ones once each; the third attempt is where the behaviour actually changes.

Why doesn't roleplay with coworkers work well?

Because your colleague wants you to succeed. Holding a difficult persona against someone you like is socially uncomfortable, so they soften, concede early, and accept answers a real buyer would push back on. You end up rehearsing against a buyer who does not exist. The scheduling problem compounds it: roleplay needs two people free at the same time, which is why it tends to be planned monthly and to happen far less often than that.

What should you score in a sales roleplay?

One specific, observable behaviour, decided before the call starts. Good examples: how many questions the rep asked before mentioning the product, whether they discounted before establishing value, whether they attacked the incumbent competitor, whether they established who has signing authority. Vague scoring like "how did that feel" produces vague improvement, and scoring everything at once means the rep leaves with no clear thing to change.

Related Articles

Scope

These scenarios are training exercises, not scripts. Adapt the buyer personas to your actual market - the difficulty settings that make a scenario useful for an SDR calling small businesses are wrong for an enterprise AE, and vice versa. CloserLab is made by the author of this site.