A rep’s first time handling a hard price objection shouldn’t be with a real prospect on the line. Role-play gives reps a place to stumble, get feedback, and try again — so the version a buyer actually hears is the practiced one, not the first draft.
Ready to go digital?
Discover how Zoomforth can help you.
Join 500+ enterprise sales, marketing and HR teams building trackable microsites — no developer needed.
Rated 4.5/5 on G2 · Trusted by Fortune 500 teams
Why role-play works, and how to run a session
The value of role-play isn’t the script itself — it’s the repetition with feedback. A rep who runs through a price objection scenario twice, hears what landed and what didn’t, and tries it again with the adjustment has rehearsed the actual skill: staying calm, listening past the objection, and responding without getting defensive. Reading the same objection response silently on a battlecard doesn’t build that reflex.
A session works best structured simply: 5 minutes to set the scenario (who the prospect is, what’s already happened in the deal, what the rep is trying to accomplish), 5-8 minutes to run the conversation out loud, and the remaining time for feedback — what the rep did well, what to try differently, and a second attempt if there’s time. A manager or a peer can both play the prospect. A manager’s feedback tends to focus on deal strategy; a peer often plays a more realistic, less cooperative prospect, since they know what buyers actually say.
The four scenarios below cover situations that come up across most B2B sales cycles: a price objection, a discovery call with an evasive prospect, a stalled deal at the “I need to check with my team” stage, and a call where the prospect is actively comparing a competitor. Each includes a model exchange and coaching notes on what to listen for — not a script to recite, but a shape to practice.
Scenario 1: the price objection
Setup: Mid-way through a proposal review call. The prospect has seen the pricing and pushes back before the rep finishes the walkthrough.
Prospect: “Honestly, this is more than we budgeted for. I’m not sure we can make this work.”
Rep: “That’s fair to raise now rather than at the end — can I ask, is the concern the total number, or is it more about how it compares to what you’d budgeted for this category?”
Prospect: “Mostly the total. We were thinking closer to half this.”
Rep: “Got it. Before we talk about ways to adjust scope or timing, can I check — when you budgeted that number, was it based on a comparable tool, or more of a rough placeholder?”
Prospect: “Honestly, more of a placeholder. We hadn’t priced anything out yet.”
Rep: “That’s useful to know. Let’s look at what’s actually driving the cost here, and I can show you a couple of ways teams typically phase this in if the full scope is more than this year’s budget allows.”
Coaching notes: The rep doesn’t defend the price or immediately offer a discount — the first move is to understand what the number is actually anchored to. A placeholder budget and a researched one call for different responses, and asking closes that gap before proposing anything.
Scenario 2: the evasive discovery call
Setup: Early discovery call. The prospect gives vague, guarded answers and seems reluctant to share real information.
Rep: “What prompted you to start looking at this now, rather than a few months ago?”
Prospect: “Oh, just doing some general research. Nothing specific.”
Rep: “Makes sense to explore options early. When you say research — is there a particular process today that’s not working the way you’d like, or is this more about seeing what’s out there?”
Prospect: “A bit of both, I guess.”
Rep: “That’s a common starting point. If it’s helpful, I can walk through how a couple of teams in a similar spot approached this — sometimes that surfaces what’s actually the priority faster than starting from a blank page. Would that be useful?”
Coaching notes: Pressing directly on a guarded prospect (“come on, there must be a reason”) tends to make them more guarded. Offering a low-commitment alternative — sharing how other teams approached it — often gets a vague prospect to engage without feeling interrogated.
Scenario 3: “I need to check with my team”
Setup: End of a proposal call. The prospect seems positive but stalls on next steps.
Prospect: “This all looks good — I just need to run it by my team before we move forward.”
Rep: “Absolutely, that makes sense. Just so I can make sure they have what they need — is there anyone on the team you expect might have questions or concerns, based on what we’ve covered?”
Prospect: “Probably our ops lead, she’ll want to know about the rollout timeline.”
Rep: “Good to know. Would it help if I put together a short summary addressing the timeline specifically, so you’re not starting that conversation from scratch? And would it be useful to have me on a short call with her directly, if questions come up I can’t anticipate?”
Coaching notes: “I need to check with my team” is often real, not a brush-off — the mistake is treating it as one and pushing for a firm date. Asking who specifically and what they’ll likely ask turns a vague stall into a concrete next step the rep can actually support.
Scenario 4: the competitor comparison
Setup: The prospect mentions they’re also evaluating a named competitor.
Prospect: “We’re also looking at [Competitor]. Their pricing seemed a bit lower.”
Rep: “Good to know you’re doing a real comparison — that’s the right approach. Can I ask what stood out most from what you’ve seen of them so far?”
Prospect: “Mostly just the price, and they seemed to have similar features on paper.”
Rep: “That’s useful context. A lot of the difference between us and [Competitor] shows up less in the feature list and more in [the specific area where the rep’s product genuinely differs — e.g. onboarding time, security certifications, or usage analytics]. Would it help if I showed you exactly what that looks like, so it’s a fair comparison rather than just a feature checklist?”
Coaching notes: Don’t disparage the competitor or panic about the price gap. Acknowledge the prospect is doing real diligence, then redirect to the dimension where the rep’s product genuinely differs — a feature-list comparison rarely favors either vendor, but a concrete difference in a category the buyer cares about does.
Adapting these to your own deals
None of these exchanges should be memorized verbatim — a rep who recites a script sounds like it the moment a real prospect says something slightly different. Use them as a shape: acknowledge what the prospect said, ask a clarifying question before responding, then address the real concern rather than the surface one. Swap in the objections and competitor names that actually come up for your team, and run the scenario again once a rep has tried it with the generic version.
The same discipline that makes SPIN selling and a strong discovery call work applies here — the goal of both role-play and a real call is understanding before proposing. Practicing that sequence out loud, with feedback, is what turns it into a habit rather than a framework a rep read about once. Scenario 1 above is the practiced version of the diagnostic approach covered in more depth in our sales objection handling framework — practice the shape here, then use that framework to work through objections that don’t fit these four scenarios. A sales enablement program that includes role-play scenarios by deal stage gives new reps a starting point instead of learning objection handling live, deal by deal.
Where practice shows up in the real deal
The point of rehearsing these scenarios isn’t the session itself — it’s what a prospect notices afterward. A rep who has practiced staying curious instead of defensive during a price objection carries that into the real call, and the proposal or follow-up that comes next should reflect the actual concerns raised, not a generic template sent regardless of what was discussed.
Ready to see how a trackable proposal reflects what actually came up in the conversation, instead of a one-size-fits-all deck? Request a demo.
Frequently asked questions
Why does sales role-play work?
Role-play works because it lets a rep make mistakes and recover from them before a real buyer is on the other end of the conversation. A rep who has already stumbled through a price objection in front of a manager, gotten feedback, and tried again is far more likely to handle it smoothly with a live prospect than one hearing the objection for the first time mid-deal.
How long should a sales role-play session be?
15 to 20 minutes per scenario is enough: 5 minutes to set the scenario and roles, 5-8 minutes to run it, and the rest for feedback. Running one scenario well with real feedback beats rushing through three without discussing what worked.
Who should run sales role-play with reps?
A manager or a peer rep both work, and each has a different value. A manager can coach on deal strategy and give feedback tied to what leadership expects. A peer rep often surfaces more realistic objections, since they're closer to what prospects actually say, and the practice feels lower-stakes.
Should reps memorize role-play scripts word for word?
No. A script is a structure to internalize, not a line to recite. A rep who memorizes exact wording sounds scripted the moment a real prospect deviates from the expected path. The goal is to practice the shape of a strong response — acknowledge, reframe, ask — until it comes naturally in the rep's own words.
What's the difference between a role-play script and a battlecard?
A battlecard is a reference document a rep checks during or before a call — talking points, competitive facts, objection responses written as bullet points. A role-play script is something a rep practices out loud, with another person playing the prospect, so the response becomes a reflex rather than something they have to look up.
