A 9-step cold call structure for SDRs, with the formula and example script for each step. Built from the calls we run for clients.
Most cold calls fail in the first 30 seconds because the rep pitches before the prospect has said anything. The fix is a structure that gets the prospect to name their own problem, then asks for the meeting. This guide gives you that structure in 9 steps, with the formula and an example line for each.
A good cold call runs in this order: earn 30 seconds, let the prospect sort themselves into a problem, get them to say what is stopping them, dig into why, connect it to a number they care about, ask permission to pitch, pitch in one sentence, confirm it is a priority, then ask for a short exploratory call on a specific day.
Every step is a question except the pitch. The prospect does most of the talking, which is the point.
Before a rep picks up the phone, they should be able to fill in four things about the person they are calling. These four drive every question in the call.
Example for a prospect who runs a sales team: the core challenge is not enough qualified pipeline. The pain is a team that keeps missing quota. The leading indicator is reps not booking enough meetings. The lagging indicator is pipeline coverage below target.
Each step has a purpose, a formula you can adapt, and example lines for two common situations: a team that has pipeline but struggles to convert it (the scaling challenge), and a team that cannot generate enough of it (the pipeline challenge).
Purpose: earn the next 30 seconds and get a yes to a few questions.
Formula: "Hey [Name], this is [Your name] from [Company]. We've been working with other [role or industry] at companies like [similar clients] who were dealing with [common challenge]. Mind if I ask a couple of questions to see if this is worth exploring for your team?"
Example: "Hey Sarah, this is Alex from [Company]. We've been working with other sales leaders at B2B firms who were struggling to generate enough qualified opportunities. Mind if I ask a couple of questions to see if this is worth exploring for your team?"
Why it works: naming people like them creates curiosity and credibility. Asking permission lowers their guard instead of forcing the conversation.
Purpose: let the prospect tell you which problem they have, so you don't assume.
Formula: "Do you have the [desired outcome] to support [key business goal]?"
Example: "Do you have the pipeline coverage to hit your revenue targets consistently?"
If they say yes, they likely have a scaling challenge: volume is there, conversion is the problem. If they say no, they have a pipeline challenge: they can't generate enough.
Why it works: a neutral question gets an honest answer and steers the rest of the call.
Purpose: get the prospect to say the frustration out loud.
Formula: "What's stopping you from [solving the challenge]?"
Scaling challenge: "What's stopping your team from hitting quota consistently?"
Pipeline challenge: "What's stopping you from generating enough qualified opportunities?"
Why it works: a problem they name is one they believe. Their answer tells you where to go next.
Purpose: move from how they feel to the signal behind it.
Formula: "Why do you think that keeps happening?"
Scaling challenge: "Why do you think the team struggles to close even when there's pipeline?"
Pipeline challenge: "Why do you think your reps aren't booking enough meetings?"
Why it works: it makes them think about the root cause, which sets up the cost question.
Purpose: tie the warning sign to a number that matters.
Formula: "What impact does [leading indicator] have on your [business metric]?"
Scaling challenge: "What does your conversion rate do to your ability to hit the revenue goal?"
Pipeline challenge: "What does the drop in meetings do to your pipeline coverage?"
Why it works: once they say the cost out loud, the problem feels urgent.
Purpose: make the move to your solution feel like their idea.
Formula: "If you could [fix the leading indicator], would that help [improve the lagging indicator]?"
Scaling challenge: "If you could lift the team's conversion rate, would that help you hit quota more consistently?"
Pipeline challenge: "If you could book more meetings with qualified buyers every week, would that get pipeline back on track?"
Why it works: they agree that fixing it has value before you say what you sell.
Purpose: show how you fix the leading indicator. Benefits, not features.
Formula: "That's exactly why companies work with [Company]. We help [fix the leading indicator] so you can [reach the goal]."
Scaling challenge: "That's why sales teams use [Company]. We help reps spot deal risks early so more of the pipeline closes."
Pipeline challenge: "That's why outbound teams use [Company]. We help reps book more meetings by tightening who they target and what they say."
Why it works: the pitch answers the problem they just described, in their words.
Purpose: get a yes that this matters now.
Formula: "Is [the positive outcome] something you're prioritizing right now?"
Scaling challenge: "Is improving quota attainment a priority this quarter?"
Pipeline challenge: "Is growing outbound pipeline a priority for you right now?"
Why it works: a spoken yes makes the meeting the obvious next step.
Purpose: make the meeting feel small and easy to say yes to.
Formula: "That's exactly why I called. We've been working with [similar companies] on this, and I'd like to see if it makes sense for you too. Worth a quick call to explore it? How's [day] at [time]?"
Why it works: a specific day and time is easier to accept than "when are you free?", and "explore" keeps the stakes low.
If your team has SDRs but no one coaching them on calls every day, that is what our Fractional SDR Management does. If you're not sure outbound works for your market yet, start with a Proof Sprint.
