A cold call script you can actually say out loud
Gong’s cold calling page says the calls that work run “an average 5:50 minutes” while the ones that go nowhere average 3:14. I opened that page on 20 Aug 2026 to check the figure hadn’t quietly moved. Almost three minutes of difference, and most of it gets decided in the first eight seconds. So the B2B SaaS cold call script below is laid out the way you’d say it, with the pauses marked, instead of the way an article reads.
A script is rails, not a cage. Flat delivery of good words still sounds like a recording, and nobody stays on the line for a recording. Read each block out loud twice before you dial. The second pass is where you catch the phrases that don’t fit your mouth, and those are the ones to swap for words you’d actually use.
Say it out loud before you dial
Written English and spoken English break in different places. On a page, “we help revenue teams reduce ramp time for newly hired reps” is fine. Out loud it’s fourteen words with nowhere to breathe, and somewhere around word nine the person on the other end works out that you’re reading to them.
Four mechanical rules that survive contact with a live call:
- No clause longer than about twelve words without somewhere to breathe.
- Contractions everywhere. “We’re”, “you’re”, “I’d”. A rep who says “we are” sounds like a letter being read aloud.
- End statements downward. Rising pitch on a statement turns it into a request for permission, and you haven’t earned permission yet.
- Speak numbers, don’t recite them. “About forty dials” lands. “39.7 dials” does not.
HubSpot’s sales statistics roundup reports that “46% of cold callers open calls with a direct introduction and purpose statement”. That’s the majority, which is also why so many openers sound identical from the receiving end. The wider mechanics of dialling sit in our cold calling tips for 2026.
The opener: eight seconds, three moves
Gong’s research found that “How have you been?” hit “a 6.6x higher (10.01%) success rate than the baseline”, while “Did I catch you at a bad time?” managed “a 0.9% success rate”. Same rep, same list, roughly a tenfold gap on one line. Saying “the reason for my call is…” out loud “increases your success rate by 2.1x” in the same analysis.
Three moves, in order.
1. Name, then pattern break
“Hey [first name], it’s [your name] from [company]. How have you been?”
Then stop. Two seconds of silence feels like ten to you and like nothing to them. It’s the most productive silence in the whole call, and new reps talk straight through it every single time.
2. Honest frame
“So, you and I have never spoken. Give me thirty seconds and then you can throw me out.”
3. Reason for the call
“The reason for my call is I noticed you’ve added three reps since June. Teams I speak to at that point tend to hit the same wall in month two.”
All of that is under fifteen seconds spoken at a normal pace. Longer than that and you’ve spent the goodwill before you’ve asked for anything with it.
Four objections, and what to say back
The Gong sales-stats page reports that top reps answer an objection with a clarifying question “54.3% of the time” against “31% for average performers”, pause about “5 times longer” after hearing one, and hold a steady “176 words per minute” while anxious reps accelerate to “188 wpm”. Slow down. Ask one question. Then answer the actual thing.
| What they say | What it usually means | What you say |
|---|---|---|
| “Send me an email.” | A polite hang-up, most of the time. | “Sure. What do you want it to answer, so I’m not sending you a brochure?” Then, after they tell you: “If it answers that, is fifteen minutes next week fair?” |
| “We already use [competitor].” | Good news. They’ve already bought the category. | “That’s useful, it means you’re already recording calls. What made you pick them? And what’s the one thing you wish it did that it doesn’t?” |
| “Not interested.” | Reflex, fired before they heard anything. | “Fair enough. Before I go, is that because coaching isn’t a priority this quarter, or because something like this burned you before?” |
| “No budget.” | Two very different problems wearing one sentence. | “Understood. Is that no budget until January, or no budget for this category at all? Those are different conversations and I only want one of them.” |
Every row follows the same shape: one clarifying question, one short answer, one ask. It’s repetitive and it works, mostly because the reflex objection was never a real position in the first place. Our guide to handling sales objections goes wider than these four.
One thing to watch while you’re doing it. Gong puts top performers at “46% talk, 54% listen” and average reps in the “high 60s”, which means the failure mode after an objection is almost always talking more, not talking better. The numbers behind that are in our post on talk-to-listen ratio on sales calls.
The close: ask for the calendar, not for interest
“Does that sound interesting?” is a question you can lose outright. “Thursday at 2, or Friday at 11?” is a question where you can only lose half.
Gong’s cold call analysis notes that “In some of the most successful cold calls we looked at, ‘Next Steps’ consumed about half of the sales conversation”. Half. Not a polite thirty seconds at the end after the demo pitch has run long.
Say it like this:
“I’m not going to sell you anything on a cold call. What I’d like is twenty minutes where I show you what your last ten calls looked like, and you tell me whether that’s worth anything. Thursday at 2, or Friday at 11?”
If they ask what it costs, answer. Gong found that “Discussing pricing on the first call increased win rates by 10%”, and dodging the question on a first call teaches the buyer that the price is embarrassing. Here’s what a defensible answer sounds like, using numbers I pulled on 20 Aug 2026 from craqly.com/pricing rather than from memory: Pro is $38 a month, or $19 a month billed yearly. Pro Max is $59, Ultra is $99, and there’s a free Starter tier at $0. The allowance is credits, and the pricing page says this and nothing more about them: “1 credit = 1 minute of live session · credits reset every month”. Stealth is on all four tiers, free one included. Real number, what it buys, and the date you last checked. That’s the whole trick.
The whole B2B SaaS cold call script, in one block
Read this aloud with a timer running. If you haven’t reached the ask by about fifty-five seconds, cut something out of the middle.
“Hey [first name], it’s [your name] from [company]. How have you been?”
(Pause. Let it be awkward.)
“So, we’ve never spoken. Give me thirty seconds and then throw me out if it’s rubbish.”
(Pause. A grunt counts as a yes.)
“The reason for my call is I saw you’ve added three reps since June. Teams I speak to at that point usually have the same problem, which is that the new reps end up copying whoever sits nearest to them, because nobody has forty minutes spare to listen back to a call.”
“We record the call, mark the moments where the deal actually moved, and hand the rep the two minutes that mattered instead of the forty that didn’t.”
“Is that a real problem for you, or have you already sorted it?”
(Listen. All the way to the end of their sentence, including the bit after the pause where they say the true thing.)
“Right. Twenty minutes then. Thursday at 2, or Friday at 11?”
What to change after forty dials
Cognism’s cold calling statistics put the average cold calling success rate at “2.3%”, note that “on average, connecting with a lead takes three cold call attempts”, and report average call length at “93 seconds in 2025, up from 83 seconds”. Forty dials is roughly one meeting at that rate. It’s also about the smallest batch worth drawing a conclusion from, so resist rewriting the opener after four bad calls on a Monday morning.
Change one line per batch. Opener first, because it’s cheap to test and it gates everything after it. Then the reason-for-the-call sentence. The objection replies change last, since you need enough conversations to hear the same objection more than twice.
Here’s the part I’m unsure about. That “How have you been?” opener has sat in a widely read Gong post for years, and it’s quoted in enough SDR onboarding decks that it may well be burning out on the receiving end by now. If it stops landing for you, the transferable bit was never the words. It was the pattern break, and you can build a different one.
If you’d rather have the objection replies in front of you while the call is happening instead of in a doc you reread afterwards, that’s the argument for real-time objection handling. Either way: print the block, put it face-down next to the keyboard, and dial forty times before you decide it doesn’t work. Then ask the one question worth asking after a bad call. Did they hang up on the script, or on the way you read it?
