The SaaS Cold Call Script for Reps Dialling CROs, VPs of Sales and RevOps Leaders

1. 1

   Before you dial — 90 seconds, out loud

   Answer these four out loud before the phone rings. If you can't, don't dial yet. 1. WHO: Exact title and tenure. "Priya Raman, CRO, in seat since March, came from a company that IPO'd." A CRO eleven months in is defending a plan she inherited. A CRO four years in is defending a plan she wrote. A VP of RevOps is defending a stack someone else bought. A Director of Sales Development is defending reply rates that fell off a cliff and weren't their fault. 2. TRIGGER: Funding round in the last 18 months, a new CRO or VP of Demand Gen hire, twelve AE reqs posted then quietly pulled, a G2 category shift, a pricing page that moved from per-seat to consumption, layoffs in CS. No trigger? The segment is the trigger: "every Series C SaaS company we talk to is in the same consolidation exercise right now." 3. THE ONE PROBLEM: Written down, one sentence. Not three. Match it to title — NRR and expansion to the CRO or VP of Customer Success, reply rate and meetings-per-SDR to the Director of Sales Development, stack utilisation and warehouse sync to the VP of RevOps. 4. THE ASK: "Twenty minutes, Thursday 2 or Friday 9." Say the words now so they come out flat and certain later. Have the follow-up email drafted in another tab. Have the calendar invite half-built. You are sending it while they're still on the line.

2. 2

   The opener — name, honest frame, permission, pause

   "Priya — it's Marcus at Cordell. We've never spoken, this is a cold call. Can I give you thirty seconds on why I rang, and you can tell me to get lost?" Then stop. Two full seconds. Do not fill it. Tonality: end "thirty seconds" on a downward inflection. Cold call nerves push your rate up about a third — deliberately speak slower than feels right. Match their energy within one notch; if they answered clipped, do not come in bright. Variants: Pattern interrupt — "Priya, Marcus at Cordell. You don't know me. Bad time?" (Most say "depends what it's about," which is permission.) Trigger-led — "Priya, Marcus at Cordell — I saw you pulled four AE reqs off the careers page in the last month and kept both CS ones. That's actually why I called. Got a minute?" Peer-aware, for a Director of Sales Development or VP of Sales who does this for a living — "Priya, this is a cold call, and I know you approve the dialer license, so you'll grade me on it. Thirty seconds?" Never: "How are you today?" "Did I catch you at a bad time?" "I'll be brief." "The reason for my call is to introduce myself and our platform."

3. 3

   The reason — problem statement by title

   Two sentences. Who else like them, what's happening, the specific consequence, then a check-in question with a graceful exit. FOR THE CRO / VP OF SALES: "We work with revenue leaders at Series B and C SaaS companies, mostly 40 to 150 reps. The thing that keeps coming up is NRR sliding from around 118 into the low 100s, and when they dig in it isn't logo churn — it's customers re-baselining seat counts at renewal, so downgrades outnumber cancellations and nobody can tell the board whether that's product, CS coverage or macro. Is that anywhere near your world, or have you got a clean answer for that already?" FOR THE VP OF REVOPS: "We mostly get pulled in by RevOps leaders who've just had finance send over the SaaS spend report with seat-level utilisation requested on every line. Forty-odd tools, three of them inherited from a predecessor, and a warehouse everything is supposed to sync to and doesn't. Is that exercise happening at you right now, or is that not this quarter's fire?" FOR THE DIRECTOR OF SALES DEVELOPMENT / VP OF DEMAND GEN: "Talking to a lot of SDR leaders whose reply rates went from four or five percent to under one, all at once — bulk sender rules, domain reputation, buyer fatigue, landed in the same quarter. So coverage reads 3x on the board but half of it is stage-two deals with no next step booked, and forecast calls have turned into arguments about hygiene. Sound familiar, or are your reply rates holding?" FOR THE HEAD OF GROWTH: "Most of the PLG teams I speak to have healthy self-serve signups and flat conversion to paid, and the sales team keeps dialling into accounts that already have a free workspace, which annoys the champion. Usually because nobody's agreed what a PQL actually is or who owns the account past that line. Is that a live argument there or have you settled it?" No product name yet. None. And do not ask "are you the right person for this?" — it tells them you didn't do the homework.

4. 4

   Two questions maximum, then close

   You are not running discovery. You are getting just enough to make the meeting relevant. Narrow, factual, answerable in one breath: - "Is the expansion number owned by CS or by the AEs today?" - "Roughly what's your NRR sitting at now — 105ish or lower?" - "How many of your reps are actually ramped and carrying full quota versus what the capacity model says?" - "Is that on the roadmap for this fiscal or are you just living with it?" - "Is that one person in RevOps or do you have a middleware layer?" Banned on a cold call: "What are your top three priorities this year?" "Walk me through your current process." "What would fixing that be worth to you?" You haven't earned those, and you'll burn the reason to hold the next meeting. Listen for the admission. "Yeah, that's the argument we're having." "We've been meaning to look at that." "Honestly, we don't know." The moment you hear it, stop asking and start closing.

5. 5

   The ask — small, specific, two slots

   "Here's what I'd suggest. Twenty minutes, not a demo — I'll walk you through what the expansion gap looks like in numbers for a company at your ARR and rep count, and you tell me on the call whether it's worth a second conversation. I've got Thursday at 2 or Friday at 9. Which is less bad?" Elements that raise the take rate: name the length (20 or 25 beats 30 — it sounds considered), say what it is not, give two options rather than an open calendar, and state the exit. If they're a CRO who'll want RevOps in the room, pre-empt it: "If it's useful, bring whoever owns your Salesforce objects — half the questions are integration questions and I'd rather answer them once." The moment they say yes: "Sending it now — can you confirm it landed?" Do not hang up before the invite is accepted. A meeting calendared after the call no-shows at a much higher rate than one confirmed on it.

6. 6

   The soft no and the recycle

   If they won't book, the job changes: get a dated reason to call back and one piece of intelligence. "No problem. Last thing and I'll leave you alone — is this a timing thing or a not-a-priority thing? … Got it. When does next year's planning actually lock — October? … Perfect, I'll come back to you the first week of October. I'll send one email so you've got my name." Useful intelligence to walk away with: when the fiscal year starts, whether the consolidation exercise has a deadline, which two vendors are on the chopping block, whether the expansion number sits with CS or sales, and who the VP of RevOps is by name. A cold call that ends with "call me in October, we lock the plan then, and it's Dev who owns the stack decision" is a good call. A cold call that ends with "send me an email" and nothing else is a polite hang-up you recorded as a win.

7. 7

   Gatekeeper, chief of staff, or 'what is this regarding?'

   Short, calm, specific. Never cute, never claiming a prior relationship. "It's about their net revenue retention number and where expansion is leaking at renewal — Marcus at Cordell, she won't know me. Is she the right person or does that sit with someone in RevOps?" That last half-question often gets you a name and a direct line, which is worth more than the connect you were chasing. If they ask how you got the mobile — answer straight, no defensiveness: "A contact database. I filter for Series B and C SaaS with 40-plus reps, and you fit. That's the whole story." Your buyer probably pays for the same database. Owning it lands better than dodging.

8. 8

   Voicemail — under 20 seconds, no ask

   "Priya, Marcus at Cordell — you don't know me. Calling about the expansion side of NRR: specifically seat re-baselining at renewal showing up as downgrades rather than churn. It's a pattern at your stage. I'll try you again Thursday morning. 415-555-0148." The voicemail's job is name recognition for attempt two and the email that follows it. No calendar link, no "looking forward to connecting," no ask.

9. 9

   Immediately after — five minutes, non-negotiable

   Subject line references the call, not your company: "Our call just now — seat re-baselining at renewal." Three lines maximum. Their words, not yours. If they said "downgrades are eating us alive," that phrase goes in the email and it goes in the discovery call. Log the disposition honestly. "Interested" is not a disposition. "Booked Thu 2pm, wants RevOps lead on it" is. "Callback first week of October, plan locks then, cutting the enrichment contract" is.

1. Rep

   Priya — it's Marcus at Cordell. We've never spoken, this is a cold call. Can I have thirty seconds on why I rang, and you can tell me to get lost?

2. Buyer

   I know what a cold call is, I approve the dialer license. You've got twenty.

3. Rep

   Fair. We work with CROs at Series B and C SaaS companies, forty to a hundred and fifty reps. The pattern that keeps coming up is NRR sliding out of the high teens down into the low 100s, and when they dig in it isn't logo churn — it's accounts re-baselining seat counts at renewal, so downgrades outnumber cancellations. Is that near your world or have you got a clean answer on it?

4. Buyer

   Careful. You're describing two different things. Our logo churn is flat, GRR is basically where it was. What moved is expansion. If you're going to pitch me on retention, know which number you're talking about.

5. Rep

   You're right, and that's the distinction that matters — GRR holding while NRR drops means it's a dollar expansion problem, not a save-the-account problem. Which usually means seats came back at renewal rather than anybody leaving. Is that what's happening, or is it price uplift you're not getting?

6. Buyer

   Seats. Customers came in at forty, renewed at twenty-eight because half the licenses never got used. Look, I get twenty of these calls a week and about six of them open exactly like you just did. What do you actually sell?

7. Rep

   One sentence: we watch product usage inside existing accounts and tell your CS and AE teams which logos are heading for a seat cut ninety days before the renewal call, and which ones have a second or third team quietly spinning up that nobody's called. That's it.

8. Buyer

   We're PLG. Half our growth comes from self-serve. Outbound tooling pitches don't map to how we grow and I usually kill them in the first thirty seconds.

9. Rep

   Agreed, and I'm not pitching cold spray into your motion — you'd hate it and your champions would hate it more. Different question: how many free workspaces are sitting inside accounts that already have two or three paid teams on the product, and who's working those?

10. Buyer

    …Nobody, really. That's a fair hit. We've never agreed what a PQL is so those just sit there. But it doesn't matter, because finance has me in a consolidation exercise. Forty-one tools, seat-level utilisation requested on every line. I can't buy anything new without naming what comes out, in writing.

11. Rep

    Then let me ask the useful version of that — which lines are you cutting?

12. Buyer

    The enrichment contract is gone at renewal. The intent vendor is probably gone too — we ran it for a year, everybody was 'in-market,' the same four hundred accounts surfaced every Monday and the SDRs stopped opening the list.

13. Rep

    That's the standard failure mode — topic-level intent scored at the domain, which surfaces anyone whose marketing team read a blog post. Ours is first-party usage inside your own product, so the account either has a new team in a workspace or it doesn't. And here's the test: send me your closed-won and your downgraded accounts from the last two quarters and I'll run the signal backwards against them. If it doesn't flag the downgrades before they happened, I've saved you a pilot and you never hear from me.

14. Buyer

    Alright, that's a better answer than most. Send me something and I'll circulate it internally.

15. Rep

    Happy to — who's it going to, and what do they need to see? Because if it's RevOps they'll want the Salesforce objects and the warehouse sync, and if it's finance they want cost per seat and which line item comes out.

16. Buyer

    Dev, my head of RevOps. And she is one person, she is underwater, and if this needs six weeks of her time it's dead on arrival regardless of what I think.

17. Rep

    Understood, and that's exactly the conversation I'd rather have live than in a PDF. Twenty minutes with you and Dev — not a demo. I'll show you the backtest against your own downgraded accounts and Dev can interrogate the integration in the first five minutes and kill it if it's heavy. Thursday at 2 or Friday at 9?

18. Buyer

    Thursday, 2. If the first slide is your funding round I'm dropping off.

19. Rep

    There are no slides. Invite's going out now, Dev copied — can you confirm it landed before I let you go?

What should the first line of a SaaS cold call script be?

Name, company, and an honest admission that it's a cold call: "Priya, it's Marcus at Cordell. We've never spoken, this is a cold call. Thirty seconds?" Naming it collapses the suspicion loop — they stop trying to place you and start listening. Avoid "how are you today" (outs you as a script-reader) and "did I catch you at a bad time" (hands them a scripted no). With a VP of Sales or Director of Sales Development, you can go one step further and acknowledge they run this play themselves; peer framing buys you more room than pretending they don't recognise the technique.

How do you cold call a CRO who cold calls for a living?

Assume they will grade your call in real time and that technique alone won't carry you. What earns the next thirty seconds is relevance density and correct vocabulary. Lead with a problem that only fits their world — NRR sliding from 118% into the low 100s driven by seat re-baselining rather than logo churn, or coverage reading 3x while half the pipe is stage-two with no next step. Get the jargon exactly right: NRR is not GRR, bookings are not ARR, and a downgrade is not a churn event. One imprecise term in front of a CRO and the call is over regardless of how good your opener was.

Which metrics should I put in the script itself?

Two, maximum, and always as their numbers rather than your claims. For a CRO or VP of Customer Success, use net revenue retention and the expansion-versus-churn split. For a VP of RevOps, use seat-level utilisation across the stack. For a Director of Sales Development or VP of Demand Gen, use reply rate and pipeline coverage. For a Head of Growth or a company heading into diligence, CAC payback in months and the magic number. Never invent a benchmark or quote a market statistic you can't source — this buyer builds spreadsheets for a living and will ask where the number came from.

How do I handle the tool-consolidation objection on a cold call?

Join the mandate instead of arguing with it. Ask which lines they're cutting, then say out loud which of those you'd expect to displace, and roughly what comes out of the spend report. If nothing gets displaced, admit it and go for a scoped pilot on one team's budget rather than claiming you're somehow free. Finance has asked for seat-level utilisation on every line, so "net reduction in vendors" is a sentence your prospect can repeat internally. "Great ROI" is not.

Is 'send me a deck' ever a good outcome on a SaaS cold call?

Only if you get a name attached to it. At a company fielding twenty pitches a week it's a polite hang-up. Trade for something: who's it going to and what do they need to see, or two facts about their motion, or a callback date tied to when next year's plan locks. A call that ends with "come back the first week of October, planning locks then, and Dev owns the stack decision" is a productive call. A call that ends with an unopened PDF and no name is a logged activity, not pipeline.

How long should the meeting ask be, and when do I send the invite?

Twenty or twenty-five minutes — it sounds considered in a way thirty doesn't — plus a clear statement of what it isn't ("not a demo, no slides") and two specific slots rather than an open calendar. Send the invite while they are still on the phone and ask them to confirm it landed. If the buyer is a CRO or VP of Sales, offer to include their RevOps lead up front; the integration questions are coming either way, and answering them once with the right person in the room is faster than losing the deal to a vague answer later.

• All SaaS playbooksEvery call type for SaaS, in one place.

Other SaaS calls

• Demo CallThe SaaS Product Demo Script for Selling Into a Revenue Team That's Already Cutting Tools
• Discovery CallDiscovery Call Questions for SaaS: A 25-Minute Diagnostic Playbook for CROs, RevOps and Growth Buyers
• Manager Coaching CallSales Coaching Roleplay for SaaS Teams: The 1:1 After Two Missed Quarters
• Pricing Negotiation CallThe SaaS Pricing Negotiation Script: Holding Price After the Technical Win
• Renewal CallThe SaaS Renewal Call Script for a Save Call You're Six Weeks From Losing
• Upsell CallThe Upsell Script for SaaS Customers That Survives a Seat Utilization Report
• Warm CallWarm Call Script for SaaS: Cashing a Referral With a CRO in Four Minutes

The same call in a neighbouring market

• Cold Call for Financial ServicesFinancial Services Cold Call Script: Getting a Wealth Management COO to Give You 25 Minutes
• Cold Call for InsuranceThe Insurance Cold Call Script That Keeps a Claims Leader on the Phone
• Cold Call for HealthcareHealthcare Cold Call Script: Getting a CMIO or VP of Clinical Operations to Give You 20 Minutes

Related reading

• Building a Dial Block That Survives Past 10:40amMost reps don't have a dialling problem, they have a forty-minute problem. Here's the mechanical build for a 90-minute cold call block that holds all the way to the timer.
• Your First 90 Days as an SDR: What to Master in Week One, Month One, Quarter OneA ruthless prioritisation guide for new SDRs: what to master in week one, month one and quarter one, what to ignore, and how to get coached when your manager is busy.