Cold Call Script Framework

Use this framework to build and iterate on cold call scripts for your SDR team. This is not a word-for-word script — reps who read verbatim sound like robots and get hung up on. Instead, this gives you a structure with talk tracks that each rep should internalize and then deliver in their own voice.

The Cold Call Structure

Every cold call follows this 5-phase framework. Total target duration: 2-4 minutes to secure a meeting, 30 seconds if they are not interested.

[1] Pattern Interrupt (5 seconds)
[2] Context Bridge (10 seconds)
[3] Permission Check (5 seconds)
[4] Value Statement (15 seconds)
[5] Close / Objection Handle (30-120 seconds)

Phase 1: Pattern Interrupt

The first 5 seconds determine whether the prospect stays on the line. You need to break the automatic “not interested” response.

The openers below use a fictional example: Sam from Ridgeway Data calling Maria, VP of Sales at Northwind Logistics. Swap in your own names and research.

Option A — Honest opener:

“Hi Maria, this is Sam from Ridgeway Data. This is a cold call — I know that’s not your favorite thing. Got 30 seconds for me to tell you why I’m calling?”

Option B — Trigger-based opener:

“Hi Maria, this is Sam from Ridgeway Data. I noticed Northwind just opened an office in Denver and had a thought about it. Quick question before you tell me to get lost?”

Option C — Referral opener:

“Hi Maria, Sam from Ridgeway Data. Priya Shah mentioned your name when we were discussing sales territory planning. They thought it’d be worth a quick chat.”

What NOT to do:

• “How are you today?” — They know you do not care, and now they trust you less.
• “Did I catch you at a bad time?” — You are giving them an easy exit.
• “I’m calling from Ridgeway Data, we help companies like yours…” — You lost them at “we help.”

Phase 2: Context Bridge

Explain why you are calling this specific person at this specific company. Generic calls get generic rejections.

“The reason I’m calling — I’ve been looking at Northwind’s job postings and it seems like you’re doubling the sales team this year.”

The evidence can be job postings, press releases, LinkedIn updates or tech stack data; the observation should be about their situation, not your product.

Examples:

• “I saw you just posted 6 new AE roles. When sales teams grow that fast, the outbound motion usually breaks before the new reps hit full ramp.”
• “Your team is using Salesforce and Outreach but I noticed you don’t have a centralized reporting layer. Most RevOps teams at your stage spend 8+ hours a week pulling data manually.”
• “I read the blog post your CEO published about moving upmarket. The SDR playbook that works for SMB almost never translates to enterprise without a full rebuild.”

Phase 3: Permission Check

Give them an out. Counterintuitively, this increases engagement.

“Does that resonate at all, or am I off base?”

Or:

“Is that something you’re dealing with, or am I way off?”

If they say “no” or “we’re all set” — go to the objection handling section below.

If they say “yeah, actually…” — listen. Do not immediately pitch. Ask one follow-up question.

Phase 4: Value Statement

Keep this to 2-3 sentences. Focus on the outcome, not your product features.

Structure: who you work with (the buyer’s role and two or three reference customers), the problem that usually brings them to you, and one result from a named customer with a before, an after and a timeframe.

Example (fictional companies and numbers, for illustration):

“We work with SDR ops teams at companies like Brightline Freight and Harbor Parcel. They come to us when their reps are spending more time on data entry than actual selling. Brightline’s team went from 3 hours of admin per rep per day to about 40 minutes after they centralized their outbound workflow.”

Phase 5: Close

Do not ask “would you be interested in learning more?” — this is vague and easy to decline.

Direct close:

“Would it make sense to spend 20 minutes this week looking at how this would work for your team? I’m open Tuesday afternoon or Thursday morning.”

Soft close (for hesitant prospects):

“I’m not asking for a commitment — just a 15-minute call where I can show you what Brightline Freight’s setup looks like. If it’s not relevant, you’ll know in 5 minutes and we can end early.”

Always offer two specific time slots. “Sometime next week” is too vague and leads to ghosting.

Objection Handling Quick Reference

Objection	Response
”Not interested"	"Totally fair — can I ask what you’re currently using to track outbound activity? Just want to make sure I’m not wasting your time on something you’ve already solved."
"Send me an email"	"Happy to. So I can send something relevant and not a generic pitch — what’s the biggest challenge your team is dealing with around outbound reporting right now?"
"We already have a solution"	"Good to hear. Out of curiosity, which tool are you using? Most teams I talk to use a spreadsheet next to the CRM, and the main gap I hear about is that the numbers never match. Is that your experience too?"
"Bad timing"	"Understood. When would be a better time to revisit this — Q2 planning, next quarter? I’ll put a note in my calendar and follow up then."
"How did you get my number?"	"Your contact info is in our database — I know cold calls aren’t fun to get. I’ll be quick: we help sales teams cut the admin time their reps spend logging calls. If it’s not relevant, I’ll remove your info."
"I’m not the right person"	"Appreciate you telling me. Who on your team handles sales operations? I want to make sure I’m reaching the right person.”

For a deeper framework on objection handling, see the B2B objection handling playbook.

Call Scoring Rubric

Use this rubric to evaluate call recordings in Gong or Chorus. Score each call on a 1-5 scale:

Criteria	1 (Needs Work)	3 (Solid)	5 (Excellent)
Opening	Read from a script, generic	Natural delivery, mentioned trigger	Pattern interrupt, prospect laughed or engaged
Research	No personalization	Referenced company info	Connected trigger event to specific pain
Listening	Talked over prospect	Let prospect finish	Asked follow-up questions based on answers
Objection handling	Gave up or argued	Acknowledged and pivoted	Turned objection into discovery question
Close	Vague ask or no ask	Asked for meeting with time	Offered specific value and two time options

Track team averages weekly and review trends in your analytics dashboard.

Call Block Schedule

Structure calling time in focused 45-minute blocks:

Time	Block	Note
8:00-8:45 AM	Power Hour Block 1	Decision-makers answer early
10:00-10:45 AM	Power Hour Block 2	Mid-morning, good pickup rates
2:00-2:45 PM	Power Hour Block 3	Post-lunch, reasonable pickup rates
4:00-4:45 PM	Power Hour Block 4	End-of-day, direct dials work well

Between blocks: research prospects, update CRM, send follow-up emails.

How to Customize

• Adapt the opener to your buyer’s seniority. C-suite prospects respond best to the honest opener (Option A) because they respect directness. Mid-level managers respond better to trigger-based openers (Option B) because it shows you did homework.
• Build vertical-specific value statements. A fintech SDR team and a healthcare SDR team need different reference companies, different pain points, and different metrics. Create 3-4 versions of Phase 4 mapped to your top verticals.
• Record and share “golden calls.” When a rep nails a cold call, pull the recording from Gong and add it to a shared library. New reps learn 10x faster from hearing real conversations than from reading scripts. Review these during your weekly pipeline reviews.