How to use these scripts
Read the script once to get the arc, then run it out loud against a partner or an AI buyer and let them go off-script — the whole value is in what you do when the buyer does not say the line the page expects. The scripts below deliberately stack objections easy to hard, the way real calls do. After each one I have noted the coaching point and what an evaluator listens for, because a script without a scorecard just teaches you to talk. Names, companies, and products here are all fictional — swap in your own account when you practice.
Script 1 — SaaS cold call to a VP of Operations
You are cold-calling Marcus Deel, VP of Operations at Talloak Logistics, a mid-market carrier, about a routing platform called RouteBeam. He picked up expecting a dispatcher and gives you thirty seconds.
Marcus (VP Ops)
Deel here. Who is this? I’ve got about thirty seconds.
Rep
Thirty seconds is fair. Carriers your size usually bleed margin two ways — empty return miles and drivers waiting unpaid at docks. A regional carrier a lot like Talloak cut their empty miles double digits last quarter. Which of those two is the bigger headache for you right now?
Marcus (VP Ops)
Look, just email me something and I’ll get to it.
Rep
I’ll earn the email — one question first. When a truck runs back empty, does anyone catch it that day, or does it only show up in the month-end numbers?
Marcus (VP Ops)
We run everything on spreadsheets and it works fine. Why would I change?
Rep
Spreadsheets get a lot of carriers a long way — I’m not going to tell you they’re broken. The one thing they can’t do is react in real time, so when a load falls through, the backhaul sitting twenty miles away never surfaces. That gap is exactly what I’d want to size with you.
Marcus (VP Ops)
We looked at software like this two years ago. Total waste of a quarter. Not again.
Rep
I get it — a rollout that eats a quarter makes this call annoying, and I don’t blame you for being skeptical. I’m not asking you to relive that. All I’m suggesting is a short working session on your actual empty-mile numbers. If there’s nothing there, you’ve lost thirty minutes, not a quarter.
Marcus (VP Ops)
Fine. Call me next quarter and we’ll see.
Rep
Rather than let it slip to next quarter, let’s hold thirty minutes so it’s on the calendar. I’ll bring the empty-mile and detention benchmarks for carriers your size and we’ll size Talloak’s number together. Does Thursday at 8am before dispatch ramps work, or is early next Tuesday better?
Marcus (VP Ops)
Thursday. Send the invite.
Coaching note: The rep never pitched a feature and never accepted the email or the "next quarter" fade. Every objection got acknowledged first, then redirected to business value and a low-risk next step. What an evaluator listens for here: did you earn the first thirty seconds with a specific pain instead of a generic opener, cite a peer proof point rather than a feature list, refuse to feature-dump or talk price, and close on a booked meeting with a day, time, and agenda — not "send me something"?
Run the cold-call scenario
Practice this exact cold call against an AI VP of Operations who gives you thirty seconds and stacks the brush-offs — then get scored on your opening, objections, and close.
Practice this scenarioScript 2 — SaaS discovery call
A scheduled discovery call with Priya Solberg, Director of Customer Success at Halden Benefits, about a CS platform called Kestrel. She agreed to the call but is guarded and downplays pain.
Priya (Dir. CS)
Thanks for making time. Honestly things are mostly running fine on our side — but I said I’d hear you out.
Rep
"Mostly fine" is usually where the interesting stuff hides. Before I say a word about us — how does your team find out an account is at risk today? Walk me through the last one that surprised you.
Priya (Dir. CS)
Our CSMs keep an eye on their accounts. It’s pretty manual, spreadsheets and support tickets.
Rep
So the signal is a person noticing. When one slips through, what does that cost you — is that a churned renewal, or a downgrade?
Priya (Dir. CS)
Both, sometimes. Our net revenue churn has crept up a bit this year, if I’m honest.
Rep
Crept up from where to where? I ask because retention is revenue — if we can put a dollar figure on that drift, it tells us whether this is even worth your time.
Priya (Dir. CS)
It went from about 8% to 12% over the last year.
Rep
That four-point move on your recurring base is a real number — that’s the cost of the reactive approach, not a software problem. Who else feels that number? Does it land on you, or does your VP of CX own the retention target?
Priya (Dir. CS)
The VP owns the number. And IT would have to approve any new tool.
Rep
Then let’s get them in the room early so we’re not doing this twice. My proposal: a thirty-minute working session with you and your VP where we map that four-point churn drift to specific at-risk accounts, and I’ll bring IT’s security questions handled in advance. Does next week work to get the three of us together?
Priya (Dir. CS)
That’s reasonable. Let me check the VP’s calendar and I’ll get back to you.
Rep
Perfect — I’ll send two time options today so it’s easy to forward. And to be clear, the goal of that session is to size the churn number together, not a demo. If it’s not costing you enough to care about, we’ll both find that out fast.
Coaching note: The rep got past "things are fine" with layered questions, quantified a vague worry in dollars, found the economic buyer and the IT approver, and multi-threaded before proposing anything. Note the rep never discounted — the pain got anchored on the cost of inaction instead. What an evaluator listens for: layered discovery that surfaces the churn drift, the pain quantified in dollars, the economic buyer and approver identified early, and a close that books a real next step with the buyer present rather than "just send me a deck".
Run the discovery-call scenario
Practice deep discovery against a guarded AI buyer who downplays pain — earn the churn number, quantify it, find the economic buyer, and book the next meeting.
Practice this scenarioScript 3 — Pharma rep and physician access conversation
A rare five-minute window with Dr. Alana Reyes, a high-volume cardiologist, about Cardevia (a fictional oral anticoagulant). She is time-pressed and loyal to an entrenched therapy. No product-name or price language — coverage and access only.
Dr. Reyes
You’ve got five minutes — what do you have for me? I’ve got patients waiting.
Rep
Thanks for the five minutes — I’ll be direct. I came because I think Cardevia can help keep your renal-impaired AFib patients out of the hospital. For that group specifically, it holds its stroke protection without the dose reduction your current agent needs when kidney function drops. Can I show you where it fits on your panel?
Dr. Reyes
My patients are stable on what they’re on. Why would I switch anyone who’s doing fine?
Rep
You’re right not to move patients who are doing well — I’m not asking you to. Keep your stable patients where they are. The ones I mean are your renal-impaired patients, where the current agent needs a dose reduction that can undercut protection. Those are the patients you least want ending up in the ER.
Dr. Reyes
And what does the data actually show? Quickly.
Rep
One number worth knowing: in the CARDIA-AF study, Cardevia cut stroke or systemic embolism by 21% versus the standard agent, and it held that up in moderate renal impairment without a dose reduction. So for your kidney-compromised AFib patients, it protects them without the workaround your current option forces.
Dr. Reyes
Most of my panel is Medicare. Is this even going to be covered for them?
Rep
That’s exactly the right question for your panel, and I don’t want to hand-wave it. Rather than guess, we have a dedicated access support pathway that can run a coverage check for your typical Medicare mix and handle prior authorization so it doesn’t fall on your staff.
Dr. Reyes
If access isn’t a fight, I’d consider it for the right patients.
Rep
Then here’s what I’d suggest: try Cardevia with your next one or two appropriate renal-impaired patients. I’ll run the coverage check for your Medicare mix this week, and I’ll come back in two weeks to see how those patients did. Fair?
Dr. Reyes
Fair. Talk to my practice manager about the coverage piece.
Coaching note: Every word stays in coverage and access language — no product comparisons by name, no price talk, because that is the rule for pharma. The rep confirmed her current approach, narrowed to the one subgroup with a real gap, tied the data to her patients, and closed on a specific prescribing commitment with a follow-up booked. What an evaluator listens for: purpose stated early, current treatment confirmed before positioning, the single most relevant data point tied to her patients, the coverage question treated as a real barrier with an access-support path, and an explicit prescribing ask for a specific patient type.
Run the pharma access scenario
Practice this five-minute window against an AI cardiologist who screens reps and is loyal to an entrenched therapy — coverage and access language, scored on your close.
Practice this scenarioScript 4 — Medical device rep and surgeon conversion conversation
You have ten minutes with Dr. Nolan Frey, a high-volume orthopedic surgeon who has run a competitor knee system for a decade, about the fictional Vantage Knee System. He is protective of his OR time and has been burned by a rep who vanished after launch.
Dr. Frey
I’ve got ten minutes between cases. I’ve been doing Ridgeform knees for a decade — what could you possibly show me?
Rep
Honestly, if your revision rate is where you want it, I’m not here to blow up what works. Ten minutes to show you one thing: five-year registry data and a tray setup that doesn’t cost your OR time. Before that — what’s your current revision rate running, and how fast does your team turn over your trays?
Dr. Frey
Revisions are low and I’m proud of it. My team is fast on the Ridgeform trays. Why risk that?
Rep
That’s the right question, and I wouldn’t risk it lightly either. Here’s the evidence, straight: in the ASCENT registry, Vantage showed a lower cumulative revision rate at five years versus the category benchmark, driven mainly by reduced aseptic loosening. I’m not claiming it beats your personal number — I’m saying it’s credible enough to be worth one look.
Dr. Frey
A new system means my OR team slows down. That costs me block time I don’t have.
Rep
Fair, and that’s the part reps usually gloss over. Vantage runs on fewer instrument trays than Ridgeform, so it’s a streamlined setup, not a bigger one. I’d be in the room for your team’s first cases so the turnover time doesn’t take a hit while they learn it.
Dr. Frey
I’ve heard "I’ll be there" before. Last rep promised the world at launch and I never saw him again.
Rep
I know that story and it’s exactly why surgeons don’t switch. So let me be specific: I’ll personally cover every one of your first cases and run the education for your team, in writing, not a verbal promise. If I’m not there, that’s on me.
Dr. Frey
You’re persistent. What are you actually asking for?
Rep
One evaluation case. Not a conversion — one case, with me in the room for full coverage, on a patient you’d consider appropriate. You judge it against your own outcomes. If it doesn’t hold up, we’re done. Can we pick a case for the next block?
Dr. Frey
One case. Full coverage. Let’s see it.
Coaching note: The rep established credibility fast, presented the registry data accurately without overclaiming — even conceding it may not beat the surgeon’s personal number — solved the OR-time fear with a concrete workflow story, and killed the "reps disappear" objection with a written coverage commitment. The close is deliberately small: one evaluation case, not a full switch. What an evaluator listens for: current outcomes and OR workflow understood before positioning, evidence presented without overclaiming, the OR-time and "reps vanish after launch" fears both answered concretely, and a close that asks for one low-risk evaluation case — not a full conversion.
Run the surgeon-conversion scenario
Practice earning ten minutes with a competitor-loyal AI surgeon — present the evidence without overclaiming and close for one evaluation case, scored against a rubric.
Practice this scenarioScript 5 — Interview-setting mock call (role-play round)
A sales interview. The hiring manager, Rosa Kwan, hands you a one-page scenario and plays a prospect. "Sell me our analytics tool — I run a 30-person support team and I’m skeptical." This is the role-play round.
Rosa (Hiring Mgr, as buyer)
Okay, I’m the buyer. I run support for a mid-size SaaS company. I’m busy and I’ve seen a hundred of these tools. Go.
Candidate
Then I’ll skip the tour and ask instead of pitch. Support teams your size usually lose time two ways — agents hunting for answers across tabs, and no early signal on tickets about to blow up. Before I assume, which of those actually costs your team more today?
Rosa (as buyer)
The escalations, probably. We find out a customer’s furious when it’s already at my desk.
Candidate
So the first time you hear about it is when it’s already a fire. What does one of those late escalations cost you — a churned account, or just a brutal afternoon?
Rosa (as buyer)
Both. We lost two accounts last quarter that we should have caught earlier.
Candidate
Two accounts is a real number to put in front of your leadership. That’s the cost of finding out late — and it’s exactly the gap our tool is built for: it flags the tickets trending toward escalation before they land on your desk. Can I ask how you’d even measure "trending badly" today?
Rosa (as buyer)
We don’t, really. That’s the problem. But I don’t control the budget — that’s my VP.
Candidate
Then the smart move is to get your VP in the room early with the two-accounts number in hand, so we’re not selling this twice. Would you be open to a thirty-minute session where we map those escalations to what an early signal would’ve caught — with your VP there?
Rosa (as buyer)
That I could do. Let me pull them in.
Candidate
Great — I’ll send two times today so it’s easy to forward. And the goal of that session is to size the number, not a demo. If the early-warning gap isn’t costing you enough to act on, we’ll both find that out fast.
Coaching note: In an interview, the role-play is testing whether you sell like the scenario says — not whether you memorized the product. This candidate asked before pitching, quantified the pain, surfaced that they don’t control budget, multi-threaded to the VP, and closed on a specific next step. That is what gets the offer; a feature dump ending in "let me send you some info" is what gets filtered out. What an interviewer listens for is the same as any scorecard: discover before pitching, quantify the pain, handle the objection without caving, and — the one candidates most often skip — explicitly ask for a specific next step. Treat the role-play exactly like a live call.
Run the interview role-play scenario
Practice this exact role-play round against an AI hiring manager who plays a skeptical buyer, downplays their pain, and hides who owns the budget — then get scored on discovery, objections, and your close.
Practice this scenario