SaaS · Warm Call
Warm Call Script for SaaS: Cashing a Referral With a CRO in Four Minutes
Somebody's VP of RevOps downloaded your renewals teardown, replied with two lines, and said "you should call Priya, she's the CRO at Northbound." Priya picked up. That's the whole gift. She can name your referrer and she cannot name what you sell, and she is sitting in a quarter where NRR went from 118% to the low 100s, finance has pulled a 43-line SaaS spend report demanding seat-level utilisation, and half her 3x coverage is stage-two deals with no next step booked. She has taken twenty pitches this month. Yours is the one with a name attached, which is worth about ninety seconds and nothing more.
That's the whole problem with a warm call script for SaaS: warmth is a loan, not a grant, and it decays at the speed of generic. Two sentences of "so let me give you a bit of background on us" and you've converted a warm call into a cold call the prospect now feels mildly embarrassed to be on. Worse, you've spent someone else's credibility to do it. The referrer's pain — three ops people reconciling renewal dates across two CRMs after a merge — is their shop, not the prospect's, and a CRO can hear a transplanted problem in about four words.
What follows is the sequence that works into SaaS buyers specifically: a 25-second provenance open, a relevance bridge that names out loud why you might be irrelevant, three questions instead of eleven, and a close with a date, a length and the name of the RevOps person who's going to ask what objects you write to in Salesforce. Plus the objections you will actually get — stack consolidation, "we're PLG," the intent vendor that burned them — and how to handle each without arguing with a mandate the CFO handed down.
The warm call script
Say it in your own words. The structure is the part that matters.
- 1
Pre-call: write the provenance line out loud
One sentence, said aloud before you dial, small and checkable: "[Referrer] mentioned you because [specific reason]." Good: "Nadia pulled down our teardown on seat re-baselining at renewal last month and said you'd taken the CRO seat at Northbound in January and inherited the same NRR conversation." Dead: "Nadia thought you'd be interested in what we do." Also pre-decide three things. One: exactly what the referrer said, word for word — if Nadia said "you should call Priya," you say that. Never inflate it to "Nadia said you'd be really interested," because VPs of RevOps at two Series C companies absolutely compare notes and you lose both relationships in one move. Two: your relevance hypothesis about *their* world — new in seat, a funding round, an SDR job ad that's been open eleven weeks, a pricing page that just moved to seat-based tiers. Three: assume the intro email was skimmed on a phone and archived. Write the 15-second re-brief now.
- 2
The open — name, referrer, provenance, permission (25 seconds)
"Priya — Sam Whitfield, from Harlow. Nadia Okonkwo suggested I call. She picked up our thing on seat re-baselining at renewal and said you'd taken the CRO seat at Northbound in January with the same NRR problem she's been living with. She may have been overselling my usefulness. Have you got four minutes for me to find out whether that's actually true, or shall I come back?" Four beats, that order, no deviation. If they say "yes, Nadia said you'd call" — that's your entire warmth budget being handed over. Do not spend it on "so how do you know Nadia?" Five words and move: "Good, she said she'd flag it. Then I'll be quick."
- 3
If they don't remember the referrer
Don't argue them into remembering. It was a two-line intro on a Friday. "No reason you would — it was two lines on a Friday afternoon. Short version: we work on the expansion side of NRR, specifically spotting when a second or third team inside an existing logo starts using the product before the renewal conversation, so CS isn't finding out at re-baselining time. Nadia thought your situation might rhyme. Worth four minutes or not really?" No company overview. No founding story. Their language, their problem, then hand the decision back.
- 4
The relevance bridge — the move the call lives or dies on
Referrer's world → the specific difference → a question that hands them control. Inside the first minute. "What Nadia was dealing with was CS finding out about a seat downgrade nine days before renewal, because usage data sat in the warehouse and nobody pushed it into Salesforce. That's her shop, though — she's sales-led, single motion, and you've got a self-serve funnel she doesn't have. So honestly, I don't know if this lands with you. When one of your customers re-baselines seat count at renewal, how early does anyone see it coming?" Naming the reason you might be irrelevant is the fastest credibility move available on a warm call. It reads as honest and it disarms the brace for a pitch. Never do the opposite — "Nadia was drowning in this, so I imagine you are too" — because a CRO hears that as "you researched my referrer and not me."
- 5
Discovery: three questions, four maximum
This is not a booked discovery meeting. You have four to twelve minutes and no agenda they agreed to. Eleven questions reads as an abuse of the referral. 1. Mechanical current state: "Who actually touches that today — is that CS, or does RevOps run the report?" 2. Cost in their numbers: "When you look at the split, is the NRR drop coming from downgrades or from expansion just not happening? Because those are two different fixes." Or: "What's your CAC payback sitting at now versus this time last year?" 3. Priority test: "Is that a this-quarter problem or a live-with-it problem?" Optional fourth: "Who else would care about this besides you — does your VP of Customer Success own the renewal number or do you?" Listen for the correction. When a CRO says "it's less the visibility, it's more that nobody's agreed who owns the account once a free workspace crosses the PQL threshold" — that's the call working. Write the phrasing down verbatim. It goes in the follow-up email and the second-meeting agenda.
- 6
Reading the cool-off
Warmth withdraws politely in SaaS. The tells: answers shorten to "yeah, makes sense"; they start narrating logistics — "can you send something over for Diego?"; they ask pricing per seat before you've established a problem; or they invoke the referrer as an exit — "well, if Nadia rates you." Stop and name it: "I'm getting the sense this isn't the pressing thing this quarter — which is completely fine, Nadia was guessing. Is it not the problem, or not the moment?" A clean "not the problem" is a good outcome. It protects the referral source and stops you spending a quarter chasing a ghost through someone else's goodwill.
- 7
The close — a date, a length, their words, a name
"Then here's what I'd do. You said the argument isn't the data, it's that nobody owns the account once a second team signs up. Give me thirty minutes and I'll show you how [peer company, same PLG-plus-sales-assist shape] drew that line and what it did to their expansion ARR. I'd want Diego on it, because within four minutes he's going to ask what objects this writes to in Salesforce and I'd rather he asks me directly. Thursday morning or Monday after your forecast call?" All four components or it isn't a close: date, length, a reason built from their words, and who else attends. If they genuinely can't commit: "I'll send two paragraphs and one screenshot — the screenshot's a customer's expansion signal list, not a product tour. Tell me Thursday whether it's worth thirty minutes." Diarise it on your side, not theirs.
- 8
Close the loop with the referrer — same day, two lines
"Nadia — spoke to Priya, thanks for that. Her issue is a bit different to yours; hers is ownership of the account once a second team signs up, less the renewal reporting. Meeting her and Diego Thursday. Appreciated it." Three jobs: thanks them, tells you whether you can use their name again, and it is the only reliable way a referral source produces a second referral. Sources who never hear back stop referring, and in a category where everyone has worked at three of the same companies, that's expensive.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Priya — Sam Whitfield, from Harlow. Nadia Okonkwo suggested I call. She picked up our teardown on seat re-baselining at renewal and said you'd taken the CRO seat at Northbound in January and walked into the same NRR conversation. She may have been overselling my usefulness. Four minutes to find out whether that's true, or shall I come back?
Buyer
Nadia. Yeah, she sent something on a Friday, I think I archived it. Four minutes, fine. I'll save you some of it though — if this is outbound tooling, we're PLG. That's not how we grow.
Rep
Understood, and I'm not pitching cold spray into a self-serve motion. Different question then: how many free workspaces are sitting inside accounts that already have three or more teams on the product — and who's working those?
Buyer
That's a real question, at least. Nobody's really working them. Growth owns the PQL definition, sales pokes at the list when pipeline's thin, and then a rep calls into an account where the champion's already got two teams live and it annoys everyone. We've had that argument three times this year.
Rep
So the threshold exists but the ownership doesn't. When a second team signs up inside an existing logo — who's supposed to see that, and how do they see it?
Buyer
Honestly? Nobody, until renewal. Which is the actual problem — NRR went 118 to 103 over two quarters, and it's downgrades, not churn. Customers re-baselining seats. The board wants to know if that's product, CS coverage, or macro, and I don't have a clean answer. Before you keep going, though — finance pulled our SaaS spend report. Forty-three lines, seat-level utilisation on every one. I can't add a vendor without killing one, in writing.
Rep
Then let's work with that rather than around it. Which lines are you cutting?
Buyer
The intent vendor's up in March and it's going. That data was garbage — everyone was in-market. Same four hundred accounts every Monday. Reps stopped opening the list by week three.
Rep
That's the standard failure mode — topic-level intent at the domain level, so you get the same accounts recycled and no rep ever acts on it twice. What signal would you actually have acted on?
Buyer
Something inside my own product, probably. Not someone reading an article. But look, a backtest on closed-won isn't going to tell me anything about retention, which is the thing I'm actually being measured on.
Rep
Agreed, so don't run it against closed-won. Run it against your last two quarters of seat expansions and your last two quarters of downgrades. If we can't show a usage signal that preceded the expansions and a different one that preceded the downgrades, by a useful margin — thirty, sixty days — then this doesn't fix your NRR and I've saved you a pilot.
Buyer
Maybe. Look, send me a deck and I'll circulate it internally.
Rep
Happy to — who's it going to, and what do they need to see? Because a deck for you and a deck for RevOps are different documents.
Buyer
Diego, our head of RevOps. He's one person, he's underwater, and he's mid-migration to Snowflake. He'll want to know exactly what this writes to in Salesforce and whether it needs custom fields, and if you're vague about it he'll kill it before I see it.
Rep
Fair, and he should. Short version so you can repeat it: native Salesforce app, writes to Account and Contact, one custom object for the signal history, no changes to your opportunity schema. Reverse-ETL into Snowflake if you'd rather own the pipe. Implementation is about six hours of Diego's time, spread over two weeks. I'd honestly rather say that to him directly than have it survive a forward.
Buyer
He's not going to give you thirty minutes mid-migration.
Rep
Then twenty-five, and I'll spend ten of it on the integration so he can rule it out fast. The reason for the meeting is your sentence, not mine — nobody owns the account once a second team signs up, and you can't tell the board whether 103 is coverage or product. Thursday morning, or Monday after your forecast call?
Buyer
Thursday. Nine fifteen, and I mean twenty-five minutes. If Diego says the write-back is a problem, we're done.
Rep
That's a fair test. Thursday 9:15, twenty-five minutes, you and Diego. I'll send one paragraph tonight — your words, not a deck — plus the two lists I'd want for the expansion-and-downgrade backtest so Diego can see the data ask before he's on the call. And I'll tell Nadia it was useful; she'll want to know.
Buyer
Do that. And tell her she owes me one.
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “Our stack is already bloated — finance is running a consolidation exercise. I'm cutting tools, not adding them.” | Don't argue with a mandate that came from the CFO. Join it. "Which lines are you cutting?" Then map to displacement: if this replaces the enrichment contract and the intent subscription, it's a net reduction in vendors and spend, and you should be able to name the two line items you'd expect to come out and roughly what they cost. If you genuinely can't displace anything, say so out loud — "then I'm additive, and I know what that means right now" — and go for a scoped pilot on one team's budget rather than pretending you're free. On a warm call this lands better than anywhere else, because honesty is what the referrer implicitly vouched for. |
| “We're PLG — outbound tooling pitches don't map to how we grow.” | Agree, then narrow immediately. "Totally — I'm not pitching cold spray into a self-serve motion." Then the question that changes the call: how many free workspaces are sitting inside accounts that already have three or more teams on the product, and who's working those? Most PLG companies are leaving expansion on the table because nobody is watching for the second and third team signing up inside an existing logo, and the sales-assist layer calls in blind and annoys the champion. Frame the whole thing as expansion intelligence, not outbound. If they push back that the PQL definition is contested, that's not an objection — that's the problem, and you should say so. |
| “We tried an intent vendor last year and the data was garbage — everyone was 'in-market'.” | Name the failure mode before they finish describing it: topic-level intent at the domain level surfaces the same four hundred accounts every week and reps stop opening the list by the third Monday. Then ask what signal they'd actually have acted on — the answer is almost always something inside their own product or their own install base. Be specific about what your signal is and why it's structurally different, then offer the cheapest possible proof: run it against their last two quarters of seat expansions and downgrades. If it doesn't surface the accounts that actually moved, you've saved them a pilot and kept the referrer's credibility intact. |
| “Send me a deck, I'll circulate it internally.” | At a company taking twenty pitches a week this is a no with extra steps, and on a warm call it's often politeness rather than interest. "Happy to — who's it going to, and what do they need to see?" If it's the VP of RevOps, they want the integration and data-flow picture: what objects it writes to, whether it needs custom fields, how many hours of their one RevOps person's time it costs. If it's finance, they want cost per seat and what comes out of the stack. Getting a name means the follow-up has a target and gives you the second attendee for the meeting. Not getting a name tells you this was manners, and you should test the temperature: "Is it not the problem, or not the moment?" |
| “Everything has to write back to Salesforce and our warehouse, and RevOps is one person who's underwater.” | This is a real objection, not a brush-off, and vagueness here kills the deal before you've met. Be precise: native app or middleware layer, which objects it writes to, whether it needs custom fields, whether it can push through reverse-ETL to their warehouse, and the actual number of hours of their RevOps time implementation takes. Give the CRO a version short enough to repeat, because it will be repeated without you in the room. If you can name a customer on the same CRM setup with an equally thin RevOps bench, use it. Then get the RevOps lead into the second meeting so the answer doesn't have to survive a forward. |
| “We don't have budget until the new fiscal year.” | Find out whether that's a genuine freeze or a prioritisation problem. Ask what got funded this quarter that wasn't in the plan — in SaaS, something always does, usually security or a data tool. Then work the timeline backwards out loud: if they need this live for Q1 so it's affecting NRR before the board meeting, security review and procurement take six weeks, so the decision has to happen now regardless of when the invoice lands. On a warm call you have the standing to say that directly rather than hinting at it. |
| “How is this different from the six other tools that pitched me this month?” | Don't list features and don't reach for the category. Pick the one thing you do that the others structurally cannot, and say it in a single sentence. Then turn it round: "What did you buy last, and why did it disappoint you?" The answer tells you which box they're mentally filing you in — conversation intelligence, intent, enrichment — and you either accept that box knowingly or explicitly climb out of it: "Then I should be clear, we're not that. Closest thing to us in your stack is the warehouse, not the intent vendor." |
Questions reps ask about this call
- How is a warm call script for SaaS different from a cold one?
The opener and nothing else changes structurally — but that change is worth about ninety seconds of suspended disbelief. A cold call has to earn the right to ask a question; a warm call already has it, so you skip the interest-building and go straight to a real diagnostic question about their operation. The trap is treating warm as qualified. The referrer's problem is not the prospect's problem until the prospect says it is, and a CRO can tell within four words whether you researched them or just their referrer.
- What do I say when the CRO can't remember who referred them?
This happens constantly — the intro was two lines on a phone on a Friday and it got archived. Don't argue them into remembering it. Say "no reason you would," give a fifteen-second re-brief in their language with no product in it — "we work on the expansion side of NRR, specifically spotting when a second or third team inside an existing logo starts using the product before renewal" — and then ask for four minutes. Never open with "as per the email below" or "following on from Nadia's note."
- How much discovery can I run on a warm call with a VP of Sales or Head of RevOps?
Three questions, four at the absolute most, in four to twelve minutes. Current state mechanically — who actually touches this today. Cost in their numbers — is the NRR drop coming from downgrades or from expansion not happening, or what's CAC payback at now versus a year ago. And the priority test: is this a this-quarter problem or a live-with-it problem. Running MEDDIC in sequence on a call they didn't book reads as an abuse of the referral and gets shut down with "can you just send me a deck."
- Should I quote the referrer's numbers or name their company?
Name the company and describe the shape of their problem, never their numbers. "Nadia was finding out about seat downgrades nine days before renewal" is fine and useful. Quoting her NRR or her magic number is a confidentiality breach that will get back to her, and SaaS revenue leaders talk to each other constantly. The same rule applies to what the referrer said about the prospect: if they said "you should call Priya," say exactly that, and never inflate it to "Nadia said you'd be really interested."
- What counts as a successful warm call if they don't book a meeting?
A clean "not the problem" is a genuinely good outcome — it protects the referral source and stops you spending a quarter on a ghost. A pleasant call that ends in "send me some info" is the failure case, because it feels like progress and isn't. If they won't take a diary slot, take a smaller real commitment with a named date: two paragraphs and one screenshot, and you'll call Thursday for a yes or no on thirty minutes. Diarise it on your side, not theirs.
- Do I really have to go back to the referrer afterwards?
Yes, same day, two lines. It thanks them, it tells you whether you can use their name again, and it is the single most reliable way a referral source produces a second referral. In SaaS, where the same forty people rotate between VP of Sales, CRO and RevOps seats across a dozen companies, one source who feels well-handled is worth more than a quarter of prospecting. Sources who never hear back quietly stop referring.
- How do I practise this before a real call?
Rehearse the twenty-five second open and the relevance bridge out loud, because both fall apart the moment they're improvised — the bridge in particular, where you have to name the reason you might be irrelevant without sounding like you're apologising. Run it against the hard version of the buyer: the CRO with a consolidation mandate, a burned intent contract and a contested PQL definition. DrillCall lets you drill those exact personas on voice until the provenance line lands in one breath and you stop reaching for "so, a bit of background on us."