10 Sales Roleplay Scripts — Cold Calls, Discovery, Demos, and Tough Objections

Most sales roleplay dies in the first thirty seconds — not because roleplay doesn't work, but because nobody prepared the scene. "Okay, you be the buyer" produces a buyer with no motivations, no context, and no resistance, and the whole exercise collapses into two colleagues grinning at each other. A good roleplay script fixes that: it gives the buyer a character — a role, a mood, a hidden concern — and gives the rep a specific skill to drill. Below are ten complete scripts covering the moments that actually decide deals. Each one has the setup, the buyer's secret motivation (don't show the rep!), a dialogue to run or riff on, and the coaching points to debrief against.

How to run these scripts well

Three rules before you start, learned from watching hundreds of roleplays succeed and fail:

1. The buyer gets private instructions. The magic ingredient is the hidden motivation — the thing the buyer knows and the rep must discover. If the rep reads the buyer's brief, the exercise is theater, not practice.
2. The dialogue is a starting rail, not a cage. Run the opening lines as written to set the scene, then improvise. The script's job is to establish the character and the tension; the rep's job is to handle what comes.
3. Debrief against the coaching points, not vibes. "That felt good" teaches nothing. Each script below ends with 2–3 specific things to check — did they happen or not?

1. The SaaS cold call (opener under fire)

The scene: Rep sells a project-management platform. Buyer is a VP of Operations at a 300-person logistics company, mid-afternoon, between meetings.

Buyer's hidden brief: You're not hostile, but you've had three cold calls today. You'll give exactly one honest opening: if the rep earns 30 seconds, you'll admit your team runs on spreadsheets and it's becoming a problem. If they pitch features, hang up politely.

Buyer: "Hello — who's this?"

Rep: "Hi Dana, it's Sam at Flowline. I'll be straight with you — this is a cold call. Want to hang up, or can I take 30 seconds and then you decide?"

Buyer: (small laugh) "You've got 30 seconds."

Rep: "Thanks. I saw you're hiring two ops coordinators this quarter — usually when ops teams scale that fast, the spreadsheet system that worked at 200 people starts cracking at 300. Is that close to home, or way off?"

Buyer: "…Uncomfortably close, actually. We're duct-taping Sheets together."

Rep: "That's the pattern. What breaks first for you — version chaos, or things falling through between teams?"

Buyer: "Handoffs. Things vanish between warehouse and dispatch."

Rep: "Got it. I won't fix that in a cold call — but that exact handoff gap is what we built for teams like Hendricks Logistics. Worth 20 minutes Thursday to see if it maps to your setup? If not, you'll know in ten."

Coaching points: Did the rep name the cold call honestly (permission beats pretense)? Did the 30 seconds contain a specific observed trigger (the hiring) rather than a value prop? Did they resist pitching when the pain surfaced and instead ask one more layer down? (More openers in our 75 cold-call hooks.)

2. Healthcare prospecting (the gatekeeper-plus-clinician call)

The scene: Rep sells a patient-scheduling platform to private clinics. Buyer is a practice manager at a 6-physician orthopedic clinic — the real decision influencer, though the senior partner signs.

Buyer's hidden brief: You've been burned: the last software vendor promised easy EHR integration and it took nine months. You will not admit this unless the rep asks what you've tried before. Any rep who says "seamless integration" gets a frosty "that's what the last one said."

Rep: "Hi Maria, this is Jordan from ClinicFlow — I work with orthopedic practices on scheduling. Honest question before anything else: is scheduling even a problem worth talking about at your clinic, or do you have it handled?"

Buyer: "It's… a known issue. No-shows mostly. But we're not really shopping."

Rep: "Fair. Can I ask — 'not shopping' because it's not a priority, or because shopping for software has bitten you before?"

Buyer: (pause) "…The second one. Our last vendor promised the EHR integration would be quick. Nine months, Jordan. Nine."

Rep: "That's brutal — and honestly the most common story I hear in ortho. Can I ask what the no-shows are actually costing you while the scar tissue heals? Ballpark, per week?"

Buyer: "We figure ten, twelve slots a week. At our rates… you can do that math."

Rep: "That's real money against a nine-month-old bruise. Here's a low-risk version: we run integration validation before you sign anything — you see it working against your EHR sandbox first. Would that change the conversation?"

Coaching points: Did the rep surface the past failure instead of walking into it ("what have you tried?" is the pain funnel's most underrated question)? Did they quantify no-show cost in the buyer's numbers? Did the close address the actual objection (integration risk) rather than a generic demo offer?

3. Real estate discovery (the seller who won't name a price)

The scene: Residential agent meets homeowners considering selling a 3-bed they've owned for 19 years. Not B2B — which is exactly why it's a good stretch script for tonal range.

Buyer's hidden brief: You're emotionally attached and terrified of underpricing. You have a secret number ($850K, roughly $75K over market) that you won't volunteer. If the agent asks about your plans before your price, you warm up fast.

Agent: "Before we talk about the house at all — what's pulling you two toward selling? Where does life go next?"

Seller: "Our daughter's in Denver. Grandkids. We'd move within the year if… things worked."

Agent: "If things worked. What would 'worked' look like?"

Seller: "Getting what the house is worth. We've put a lot into it. Honestly, we've seen the place on Elm go for eight-fifty and ours is nicer."

Agent: "You know your street — Elm was a full renovation flip, which is doing a lot of that number. Can I show you the three closest true comps and walk through what buyers paid for? Then you tell me if my logic holds."

Seller: "…Alright. But we're not giving it away."

Agent: "You shouldn't. My job isn't to get you a price — it's to get you to Denver with the most money the market will actually pay. Sometimes that means listing sharp and letting buyers compete. Can I show you how that played out two blocks over?"

Coaching points: Did the agent open with motivation before money (the Denver detail is the leverage for every later pricing conversation)? Did they challenge the anchor with evidence rather than argue? Did they reframe their role as aligned ("get you to Denver") instead of adversarial?

4. The enterprise demo (three stakeholders, three agendas)

The scene: Rep demos a data-analytics platform to a buying committee: a VP Data (champion), a Head of Security (skeptic), and a CFO delegate (silent, taking notes).

Buyer's hidden briefs: Champion: you want this to succeed but you're worried the security lead will kill it — you'll go quiet if conflict starts. Security: you're not hostile, you're burned-out on vendors dodging your questions; one straight answer wins you over. CFO delegate: you speak only if someone mentions cost — you're tracking one thing: will this reduce the BI contractor spend?

Rep: "Before I share my screen — I know each of you cares about different things. Priya, you told me speed-to-insight. Marcus, I'm guessing security review is your job to protect. And Elena, I don't want to assume — what would make this demo worth your 30 minutes?"

CFO delegate: "We spend a lot on BI contractors. I want to know if this changes that."

Rep: "Then I'll show you the self-serve piece specifically. Marcus — want to fire your hardest security question now, so it's not hanging over the whole demo?"

Security: (surprised) "Fine. Where does our data physically live, and who at your company can see it?"

Rep: "Your region, single-tenant. And by default, nobody — support access requires your explicit grant per incident, logged and revocable. I'll send the SOC 2 and the access-policy doc today. Fair start?"

Security: "…Fair start."

Rep: "Good. Priya — the workflow you showed me, the Monday reporting crunch. Let me build exactly that, live, and Elena, watch how much of it needs zero contractor hours…"

Coaching points: Did the rep make every stakeholder's agenda explicit in the first two minutes? Did they invite the skeptic's hardest question early (containment beats avoidance)? Did the demo content map each stakeholder to a specific moment, rather than a generic tour? (This is multi-threading in miniature.)

5. BANT qualification (the inbound lead who "just wants pricing")

The scene: SDR qualifying an inbound lead who downloaded a pricing guide. Buyer is a marketing manager at a 50-person agency.

Buyer's hidden brief: You have no budget authority — your CEO decides everything — but you're embarrassed to say so. You'll deflect with "just send pricing." If the rep asks how decisions get made without making you feel small, you'll reveal the CEO angle and become a genuine ally.

Buyer: "Honestly I just wanted the pricing. Can you email it?"

Rep: "Absolutely, I'll send it today. So I send the right pricing — most agencies your size land in one of two setups. Quick version: is this for a specific client problem, or something internal that's been bugging the team?"

Buyer: "Internal. Reporting eats our Fridays."

Rep: "The whole team's Fridays, or mostly yours?"

Buyer: "Mostly mine, honestly."

Rep: "Been there. If the pricing looks reasonable — how do things like this usually get across the line at your shop? Walk me through the last tool you brought in."

Buyer: "…Miguel — our CEO — signs off on everything. Last time I built a little comparison doc and he decided in a week."

Rep: "That's actually perfect. What if I make you the best-armed person in that conversation — a one-pager with pricing, the Friday-hours math, and what to ask any vendor including us? You hand Miguel a decision, not a homework assignment."

Coaching points: Did the rep agree to send pricing immediately (fighting the request kills trust)? Did they uncover authority by asking about the process ("walk me through the last tool") rather than the insulting "are you the decision-maker?" Did they convert the blocker into a champion with an arming offer? (Full modern phrasing in the BANT guide.)

6. MEDDIC discovery (the enterprise deal that's too friendly)

The scene: AE on a second call for a $150K deal. Buyer is a Director of RevOps who loves the product. Everything feels great. That's the trap.

Buyer's hidden brief: You genuinely want the product — but you've never bought anything over $20K, you don't know your own procurement process, and your CFO hasn't heard of this project. Stay enthusiastic; reveal the gaps only under direct, specific questions.

Buyer: "Team's excited. I think we're basically there — send over the contract and let's get moving."

Rep: "Love the energy — and I want to make sure 'basically there' survives contact with your procurement team. Can I ask a few unsexy questions?"

Buyer: "Shoot."

Rep: "When your company last bought software at this price — what happened between 'the team wants it' and a signature?"

Buyer: "Hm. I… actually don't know. My biggest purchase was about twenty grand, card and done."

Rep: "Super common. At $150K there's usually a security review, legal redlines, and a CFO conversation. Who owns budget at that level — and have they heard about this yet?"

Buyer: "That'd be our CFO, Rado. And… not yet. I wanted the details tight first."

Rep: "Smart instinct — let's make it easy. What if we build the business case together — the metrics you'd defend in Rado's language — and you set up 20 minutes with him where I take the vendor questions so you don't have to? What would need to be true for you to feel good making that intro?"

Coaching points: Did the rep resist celebrating the happy-ears moment and instead test the Decision Process? Did they surface the Economic Buyer gap without deflating the champion? Did they end by building the champion (co-authored business case + supported intro) rather than just noting the risk?

7. The price objection at close (hold the number)

The scene: Final call. Rep quoted $36K/year last week. Buyer — a COO — opens with the squeeze.

Buyer's hidden brief: You have budget for $36K and approval already. You want a discount because getting one is your job, and you've found reps cave if you go quiet. If the rep holds calmly and re-anchors to value, you'll sign at full price and respect them more. If they instantly discount, push for even more.

Buyer: "Look, we like it. But $36K isn't happening. Get it under thirty and we can sign today."

Rep: (no rush) "Help me understand — is thirty a budget ceiling someone gave you, or the number you'd feel good about?"

Buyer: "Does it matter? It's what I'm ready to sign at."

Rep: "It matters a lot. If it's a real ceiling, we should talk about scope — fewer seats, phased rollout — because I'd rather cut scope than credibility. If it's negotiation, I'll be straight: the price is the price, and the reason is that your own math three weeks ago put the Friday-reporting cost at $140K a year. At $36K that's paid back in Q1."

Buyer: (silence, four seconds)

Rep: (says nothing)

Buyer: "…You're not going to move at all?"

Rep: "On price, no. On terms — I can do quarterly billing instead of annual up front, and I'll throw in the onboarding workshop we quoted separately. That's me showing up to the table. The unit price staying firm is why my customers don't wonder if the next guy got a better deal."

Coaching points: Did the rep diagnose before responding (ceiling vs. sport)? Did they survive the silence — the four seconds where most discounts are born? Did they trade on terms and scope instead of price, and re-anchor to the buyer's own quantified pain? (Deeper playbook: handling "it's too expensive".)

8. The multi-stakeholder kickoff (selling after the sale)

The scene: The deal closed. First implementation kickoff with the champion, two end users, and one manager who wanted the competitor and lost.

Buyer's hidden briefs: Champion: you oversold internally ("this fixes everything") and you're nervous. End users: you weren't consulted and are quietly annoyed. Manager: you're professional, not sabotaging — but you'll note every gap versus the tool you preferred.

Rep: "Before timelines — I want to hear each of you on one question: ninety days from now, what would make you personally say this was worth the disruption? Tomas, you first — and I know we weren't your first choice, so I especially want your honest bar."

Manager: (caught off guard) "…Appreciated. My bar: the export workflows my team runs daily can't get slower. That's where the other tool was strong."

Rep: "Then that's our first migration test, in week one, with your team in the room — and if it's slower, I want to know before you do. Ana, Luis — you two live in this thing daily. What's the one task you'd hate for this to complicate?"

End user: "Honestly? Nobody asked us anything until today, so… the Monday batch entry."

Rep: "Then that's test number two, and you're both in the pilot group with veto power on the rollout pace. Sofia — you carried this deal internally. Let's define the win we report up in 90 days so the story writes itself."

Coaching points: Did the rep name the awkward dynamics (the losing manager, the unconsulted users) instead of pretending everyone's aligned? Did every stakeholder leave owning a concrete checkpoint? Did they protect the champion by co-defining the 90-day success story?

9. The post-demo follow-up (the deal going quiet)

The scene: Great demo two weeks ago, then silence. Two emails unanswered. The rep finally gets the buyer — a Head of Sales Enablement — on the phone.

Buyer's hidden brief: The project lost internal priority — a re-org ate the quarter. You're avoiding the rep out of mild guilt, not lost interest. If they make it safe to say "not now," you'll tell the truth and genuinely want to restart in Q2. If they push for a meeting, you'll go vague and dark again.

Rep: "Hey Sam — thanks for picking up. I'll be honest about why I'm calling: two weeks of quiet after an energetic demo usually means something changed on your side, and it's almost never about the product. What happened?"

Buyer: (exhales) "…We're mid-re-org. Enablement budget's frozen while the dust settles. I should've just told you."

Rep: "You just did, and I appreciate it. Truly — no meeting pitch coming. Two questions and I'll let you go: when the dust settles, is this still a problem you own? And is it still worth solving?"

Buyer: "Yes and yes. Realistically Q2."

Rep: "Then here's all I'll ask: I'll check in the first week of April — you pick the week — and meanwhile I'll send the ramp-time benchmarks we discussed, because they'll be useful in your re-org conversations regardless of us. Deal?"

Buyer: "That's… actually helpful. First week of April works."

Coaching points: Did the rep name the silence pattern directly (making truth cheaper than avoidance)? Did they not punish the honesty with a meeting push? Did they leave with a buyer-chosen date and a value-add that serves the buyer's current (re-org) reality?

10. The churn-save call (listening under fire)

The scene: CSM/AE hybrid on a call with a customer who emailed "we're not renewing." Mid-market account, 14 months in.

Buyer's hidden brief: The real reason isn't the stated one. You'll open with "budget cuts," but the truth is your team stopped using the product after a botched feature migration in month 9 — and nobody from the vendor noticed. If the rep probes usage history with genuine curiosity instead of defending, you'll admit it. A real apology plus a concrete restart plan could actually save this.

Buyer: "I'll save you the speech — it's budget. We're cutting tools across the board."

Rep: "Understood, and I'm not here to give the speech. But before we process it — can I be honest about something in our data? Your team's usage fell off a cliff in March and never came back. Budget decisions usually follow that, not the other way around. What happened in March?"

Buyer: (long pause) "…The migration. The new dashboard broke our saved workflows. My team rebuilt some, gave up, went back to spreadsheets."

Rep: "So for six months you paid for something your team stopped trusting, and nobody from our side called. That's on us — I'm not going to spin that."

Buyer: "It's not personal. It just… stopped being worth the fight."

Rep: "If the workflows worked again — actually worked — is the underlying problem still worth solving, or has spreadsheets-forever won?"

Buyer: "The problem's still real. Fridays are still hell."

Rep: "Then here's a proposal, not a pitch: give me two weeks before the paperwork. My team rebuilds your top three workflows with your two power users — if they're not living in it by day fourteen, I'll help you write the cancellation email myself."

Coaching points: Did the rep challenge the stated reason with evidence (usage data) while staying curious, not defensive? Did they own the failure plainly — no "sorry you feel that way"? Was the save proposal concrete, time-boxed, and reversible ("I'll help you write the cancellation email") rather than a desperate discount? (The listening mechanics here are the active-listening moves under maximum pressure.)

Make it a program, not an event

One roleplay is a team-meeting novelty. The teams that actually get better run these like a training block: one script per week, everyone rotates through the rep seat, buyers get their hidden briefs privately, and the debrief sticks to the coaching points. Rotate the buyer role too — playing the skeptical CFO teaches reps more about CFOs than any battle card.

And the honest limitation of partner roleplay: your colleagues are too nice, too available at exactly one time slot, and too familiar — by round three, everyone knows everyone's moves. That's the gap solo practice fills: the same ten scenes, against a buyer who holds character, resists like a stranger, and is available at 7am before the real call.

Run all ten scripts tonight — no partner required.

Every scenario on this page maps to a SalesArmor session: pick the scenario (cold call, discovery, demo, negotiation), set the buyer's attitude from friendly to hostile, layer on BANT, MEDDIC, or Sandler — or paste a real LinkedIn URL and make the buyer your actual prospect. The AI holds character, pushes back like the hidden briefs above, and scores you on the exact coaching points. Roleplay without the scheduling, the niceness, or the grinning.

Start a roleplay now →

Frequently asked questions

How do you write a sales roleplay script? Four parts: a specific scene (who, what company size, what moment in the deal), a hidden buyer motivation the rep must discover, 6–12 exchanges of realistic dialogue to launch the scene, and 2–3 coaching points to debrief against. The hidden motivation is the part most teams skip — and it's what separates practice from performance.

What makes sales roleplay effective? Specificity and resistance. Generic scenes ("sell me this pen") train improv, not selling. Effective roleplay recreates a particular hard moment — the price squeeze, the silent stakeholder, the churn call — with a buyer who genuinely pushes back, followed by a debrief against defined criteria.

How often should sales teams roleplay? Weekly beats quarterly workshops by a wide margin — skills built through repetition decay without it. A sustainable cadence: one scenario per week in team practice, plus individual reps drilling their personal weak spot (usually objections or price) between sessions.

Can you do sales roleplay without a partner? Yes — AI roleplay platforms simulate the buyer's side with a persona, an attitude, and scored feedback, which solves partner roleplay's three chronic problems: scheduling, over-politeness, and familiarity. Most strong teams now use both: human roleplay for team culture and observation, AI roleplay for volume and hard-mode drilling.

A note on sources

These scripts draw on the roleplay and training literature across the industry: the scenario libraries published by the major sales-training platforms and academies; classic script traditions from Zig Ziglar's Selling 101 and the discovery dialogues in The Challenger Sale; the deliberate-practice research underpinning why repetition with feedback works; and — for the hidden-motivation technique — Keith Johnstone's Impro, the theater-improv classic on what makes a scene partner worth playing against. The ten scenes above are the practitioner's contribution: written to be run out loud, with the tensions that actually show up in real deals.