On this page
Team roleplay fails for a predictable reason: the scenario is vague. “Pretend I’m a prospect” gives the buyer nothing to work with and the rep nothing to aim at, so the session turns into polite improvisation. The fix is a written scenario with a buyer who has a reason to say no, a goal the rep can hit or miss and a short list of things to score. Here are twelve you can run with your team, plus a session format that people do not dread.
What makes a roleplay scenario worth running
Every scenario below has the same five parts. Use them when you write your own.
- 1
A buyer brief
Role, company, situation and personality, in three or four lines.
- 2
A hidden concern
Something the buyer knows and the rep does not. It is what makes the scenario worth playing.
- 3
A goal the rep can hit or miss
“Book a meeting with the CFO” is a goal. “Have a good call” is not.
- 4
One or two curveballs
The line the buyer will use to test the rep, written down so it actually gets used.
- 5
Three things to score
Few enough that the observer can watch for them while the call runs.
The hidden concern does most of the work. It gives the person playing the buyer a reason to resist, and it rewards the rep for asking good questions instead of pitching harder. Hand it to the buyer in writing and keep it away from the rep.
12 sales roleplay scenarios by stage
The scenarios run in the order of a sales cycle, from the first cold call to the renewal. Pick the stage your team finds hardest right now and start there. All of them are fictional; change the industry and job titles to match your market.
1. The executive with 30 seconds
Cold call
- Buyer
- A head of sales at a mid-size company, picking up between meetings.
- Hidden concern
- The team just missed its target, and anything that sounds like a distraction gets a fast no.
- Rep’s goal
- Earn one real question, then book a 15-minute call.
- Curveball
- “You’ve got 30 seconds. Go.”
- Score on
- A clear opener, a relevant question, a specific ask.
2. The gatekeeper who protects the calendar
Cold call
- Buyer
- An executive assistant who screens every call for the CFO.
- Hidden concern
- She has been misled before by reps who claimed a call was expected.
- Rep’s goal
- Get a callback slot or the right contact without misleading her.
- Curveball
- “Is she expecting your call?”
- Score on
- Honesty, a specific reason for calling, asking for help instead of a transfer.
3. The happy incumbent customer
Cold call
- Buyer
- An IT manager who has used the same provider for years.
- Hidden concern
- Support response times have slipped, but switching feels risky and he does not want to admit the problem.
- Rep’s goal
- Uncover one gap in the current setup and agree to a short comparison call.
- Curveball
- “We already use someone for that, and they’re fine.”
- Score on
- Curiosity, not knocking the competitor, a low-risk next step.
4. The buyer who answers in one word
Discovery
- Buyer
- A VP of operations who took the call because her team asked her to.
- Hidden concern
- She owned a project that failed last year and is wary of being the sponsor again.
- Rep’s goal
- Find two problems with a measurable impact and a follow-up that includes her boss.
- Curveball
- Answers “fine” to any open question that is not specific.
- Score on
- Follow-up questions, sizing the impact, a dated next step.
5. The buyer who wants the demo now
Discovery
- Buyer
- The founder of a small business, keen and short on time.
- Hidden concern
- She is comparing two vendors and plans to decide this week.
- Rep’s goal
- Agree on ten minutes of questions first, then tailor the demo to what she says.
- Curveball
- “Can we skip the questions and just see the product?”
- Score on
- Negotiating the agenda, relevance of what you show, uncovering the comparison.
6. The skeptical technical evaluator
Demo
- Buyer
- A senior engineer asked to check whether the product will work.
- Hidden concern
- She expects any new tool to create maintenance work for her team.
- Rep’s goal
- Answer technical questions honestly, including “we don’t do that”, and agree on a next step.
- Curveball
- Asks about a feature your product does not have.
- Score on
- Honesty, handling “I don’t know” with a follow-up, linking features to her concern.
7. The late-stage price objection
Objection
- Buyer
- A director who has already agreed the product fits.
- Hidden concern
- Finance cut her budget last week, and she is embarrassed to say so.
- Rep’s goal
- Find out what the price is being compared with and explore options before any discount.
- Curveball
- “It’s just too expensive.”
- Score on
- Asking before answering, recapping value in her words, not discounting first.
8. Procurement wants a discount
Negotiation
- Buyer
- A procurement manager holding a cheaper quote from a competitor.
- Hidden concern
- He is measured on the savings he negotiates, not on which vendor wins.
- Rep’s goal
- Trade concessions such as term length, scope or payment timing instead of cutting the price.
- Curveball
- “Match their price and it’s yours.”
- Score on
- Staying calm, trading rather than giving, a clear agreement at the end.
9. The champion who has to ask the boss
Closing
- Buyer
- A team lead who likes the product and has pushed for it internally.
- Hidden concern
- He has not raised it with his boss yet and is worried about the answer.
- Rep’s goal
- Get a meeting with the economic buyer and a dated plan for the decision.
- Curveball
- “Let me run it by my boss and get back to you.”
- Score on
- Helping the champion sell internally, getting access to the decision maker.
10. “I need to think about it”
Closing
- Buyer
- A small business owner at the end of a call that went well.
- Hidden concern
- She is not sure her business partner will agree to the cost.
- Rep’s goal
- Find out what exactly needs thinking about and agree on a specific follow-up.
- Curveball
- “This all sounds good. I just need to think about it.”
- Score on
- A clarifying question, no pressure, a dated next step that includes the partner.
11. The angry customer
Customer service
- Buyer
- A customer who was charged twice and is threatening to cancel.
- Hidden concern
- She wants the mistake acknowledged before she hears any explanation.
- Rep’s goal
- De-escalate, fix the error with a clear timeline and keep her as a customer.
- Curveball
- “I want to speak to someone who can actually fix this.”
- Score on
- Acknowledgment first, taking ownership, a specific timeline.
12. The renewal where usage dropped
Account management
- Buyer
- The customer’s admin, whose team has quietly stopped using the product.
- Hidden concern
- A new manager has been asked to cut tools and has not been involved so far.
- Rep’s goal
- Find out why usage dropped and agree on a plan with the new manager before the renewal date.
- Curveball
- “Honestly, I’m not sure we still need this.”
- Score on
- Diagnosing before defending, bringing in the new decision maker.
Want more? The roleplay scenario library has full versions with an opening line, a sample exchange, curveballs and a scorecard for each, across cold calls, discovery, negotiation, closing and service.
How to run a 45-minute roleplay session
Focus each session on one skill and one scenario. The structure below keeps everyone practicing rather than watching. For the full manager's guide to formats, briefs, playing the buyer and debriefs, see how to run a sales roleplay.
- 0 to 5 min
Name the one skill for today, hand out the scenario and give the buyer role its hidden concern in writing.
- 5 to 12 min
Run a first round with the manager as the rep. Going first, imperfectly, makes it safe for everyone else.
- 12 to 35 min
Groups of three: rep, buyer and observer. Five-minute call, two minutes of feedback, then rotate until each person has played the rep once.
- 35 to 42 min
Run it back: replay the hardest moment from the rounds with a volunteer, trying a different approach.
- 42 to 45 min
Each rep writes down one thing they will use on a real call this week.
Briefing the buyer role
- Play the buyer as realistic, not impossible. A buyer who never budges teaches nothing.
- Reveal the hidden concern only when the rep earns it with a good question.
- Use the curveball at least once, even if the call is going well.
- Stay in character until the call ends. No coaching mid-call.
Giving feedback that sticks
- The rep speaks first: what went well, and what they would change.
- The observer gives one strength and one change, quoting the rep’s actual words.
- Skip “good job”. Name the moment and what it did to the buyer.
- End by having the rep say the better version of their weakest line out loud.
Score roleplays without making them an exam
Three criteria per scenario is plenty, scored as yes, partly or no. That is enough to guide feedback without turning practice into a test. Our sales call scorecard template has criteria for each stage of a call that you can copy into a scenario.
If several managers run sessions, calibrate once a quarter: everyone scores the same recorded roleplay separately, then compare. Where your scores differ, rewrite the criterion until you agree on what a yes looks like.
Write scenarios from your own deals
The best scenarios come from your pipeline. Look at the last few deals you lost, the objections that come up in call notes and the moments new hires struggle with. Turn each one into a brief using this template:
Scenario template
- Buyer: [role] at [type of company], [one line on personality].
- Situation: [what led to this conversation].
- Hidden concern: [what the buyer knows and will only share if the rep earns it].
- Rep’s goal: [a specific outcome, such as a dated meeting with a named person].
- Curveballs: [one or two lines the buyer will say].
- Score on: [three behaviors you can see or hear].
Change names and company details so no real customer can be identified, and keep the hidden concern close to what actually happened. That is what makes the practice transfer to real calls.
Keep practice going between sessions
A weekly session gives each rep a few minutes as the rep. Skills build with repetition, so give them a way to run the same scenario again on their own. In Vonvo, reps practice by voice with AI buyer personas that raise objections, and each call is scored on an NEPQ-based scorecard. On the Starter plan and up, the scenario builder lets you set your own personas, objections and goals, and scenarios can also be generated from your company profile and uploaded materials.
Live sessions still matter. Peers hear each other’s approaches, and managers see where the team is stuck. Use AI practice for the repetitions and the team session for discussion.
Frequently asked questions
How often should a sales team do roleplay?
Short and regular beats long and rare. A weekly 30 to 45 minute session focused on one skill keeps practice routine, and reps can repeat scenarios on their own between sessions.
How long should each roleplay be?
Five to eight minutes per call is usually enough to reach the hard part of a scenario. Longer calls drift, and the observer stops tracking the criteria. Keep feedback to a few minutes, then rotate.
How do I get reps to take roleplay seriously?
Use situations from their own deals, keep the buyer realistic rather than impossible, go first yourself, and keep roleplay separate from performance reviews. Reps engage when practice feels useful and safe.
Should the manager play the buyer?
Sometimes. Managers usually play tough buyers well, but reps also learn a lot from playing the buyer themselves, because they hear what a pitch sounds like from the other side. Mix it up.
What if a rep freezes during a roleplay?
Pause, rewind 30 seconds and let them try again, or offer a first line and let them continue from there. Freezing in practice is exactly what practice is for. Never turn it into a teaching moment in front of the group.
Keep going in the library
Scripts, objection responses, frameworks and free tools that go with this article.
