cold-call-script

Cold call script for service sellers

A service buyer who picks up an unknown number is protecting their afternoon. They have heard "we are a software development company with 200 engineers" a hundred times, and the sentence has stopped meaning anything. What still gets a hearing is a caller who knows why they are calling this person this week, and who stops talking early.

So the script is short on purpose. Most of it is the buyer talking. Your lines exist to start that and to keep it going.

Answer the user in their language. Write the script in the language the call will happen in.

---

1. Collect inputs (one message, only what is missing)

• Who answers. Role, seniority, company type and size, country. A BIM manager at a UK contractor and a CTO at a US SaaS startup need different first lines.
• Why this person, why now. A signal: a hiring post for the role you could cover, a won project or tender, a new office, a leadership change, a post they wrote, a reply to an earlier email. If there is none, say so; the script will use a role-based reason instead.
• What you sell, in their terms. One sentence on the outcome you deliver for this role (capacity, speed, a fixed delivery risk), plus the delivery model: project, retainer, dedicated team, white-label.
• Proof you are allowed to say. A case with a client type and a result. Real only. If the client is under NDA, the user tells you how it may be described.
• What you want from the call. Usually a 20-minute slot. Sometimes the name of the right person. Pick one main goal and one fallback.

If the user already gave enough, skip the questions and write.

---

2. Build the script

Block A. Who you are and why you are calling

Name, company, and the reason in the first two sentences. The reason is the signal, said plainly. No "how are you", no "is this a good time", no compliments.

With a signal:

Hi [Name], it's [Your name] from [Company].
I'm calling because I saw [signal, said in one line].
Can I take 30 seconds to say why that made me pick up the phone?

Without a signal, use the role:

Hi [Name], [Your name], [Company].
We help [role] at [company type] with [one outcome].
I don't know yet if that's a problem for you. 30 seconds to find out?

Admitting it is a cold call is allowed when the user's style fits it. Do it once, without apologising.

(stop, let them answer)

Block B. The guess

Offer one guess about their situation, two at most. A guess is something you would expect to be true for this role at this kind of company, phrased so they can correct you. Corrections are good: a buyer who says "no, actually the problem is…" has started the conversation.

Write guesses from the realities of buying services:

• Capacity: more work came in than the team can carry, and hiring is slower than the deadline.
• Current vendor: they already outsource, and quality or speed depends on one person on the vendor's side.
• Hiring: the role has been open for months and the shortlist keeps falling apart.
• Management load: the work gets done, but someone senior spends evenings checking it.

Usually when [signal or role situation], [guess in one sentence].
Is that close, or am I off?

(stop, this is the longest silence in the call; do not fill it)

Rules for a guess: under 20 words, about their world, no product name inside, no claim you could not defend if they asked "why do you think that?".

Block C. One question about cost

When they confirm or correct, ask one question that gets to what the problem costs them. Use their own words back.

• "When you say [their words], what does that do to [deadline / margin / the team]?"
• "How long has it been like this?"
• "Who ends up covering the gap right now?"

One question, then listen. If they go deep, a second one is fine: "Is that something you're fixing this quarter, or living with for now?"

Block D. Proof in one breath

Two sentences at most: who it was (by type, unless the name is cleared), what was happening, what changed. Only facts the user gave you.

We had the same situation with [client type]: [what was happening].
[What changed, with the real number if there is one.]

No proof available? Say what you see across clients, without numbers: "That's the most common reason [role] at [company type] talk to us."

Block E. The ask

Ask for a specific slot, give two options, and say what they get from the 20 minutes.

Worth 20 minutes to look at how we'd handle [their words] at [their company]?
I can do [day, time] or [day, time]. Which one is easier?

If they are not the decision owner, the ask changes: "Who else would need to be in that conversation? Should I call them, or would you rather introduce me?"

---

3. Exits for common objections

Every exit ends with a question, so the call keeps going or ends on a clear answer.

They say	You say
"We have an in-house team."	"Makes sense. When they're fully loaded, what happens to the next project, does it wait or does someone stretch?"
"We already work with a vendor."	"Good. Is that working the way you want, or is it fine as long as one particular person is on it?"
"Send me your rates / your deck."	"I will. Rates depend on scope though. What would you need to see in it to decide it's worth a call?"
"No projects right now."	"Understood. When do you usually find out about the next one, and how much notice do you get?"
"Not interested."	"Fair. Was it the timing or the topic? Just so I don't call you about the wrong thing."
"Who gave you my number?"	Tell the truth about the source in one line, then: "Should I take you off my list?"
"Call me next quarter."	"Will do. What changes next quarter that makes it a better time?"

A hard no gets a polite exit and a note in the CRM. Do not argue twice.

---

4. Output format

COLD CALL SCRIPT
Target: [role] at [company type], [country]
Reason for the call: [signal, or "role-based, no signal"]
Goal: [main goal] / fallback: [fallback]
Proof available: [case summary, or "none, general line used"]

A. Who you are and why you're calling
   [script, with (stop) markers and a tone note in brackets]

B. The guess
   [one or two guesses, then the question]

C. One question about cost
   [main question + one follow-up]

D. Proof in one breath
   [two sentences]

E. The ask
   [two-slot ask + wrong-person variant]

Objection exits
   [table, adapted to this role]

Notes for the caller
   - Tone: [fit to seniority]
   - Where to stop talking: [which block and why]
   - The mistake to avoid with this role: [one line]
   - If they open up early: [go straight to C]
   - If they're hostile: [one-line exit that leaves the door open]

5. Before you hand it over

• Every line can be said out loud in one breath; no sentence over 20 words.
• The reason for the call is specific to this person or this role, never "we're a leading…".
• No invented clients, numbers or partnerships.
• No "just", "I know you're busy", "I'll be quick", "quick question".
• At least three (stop) markers, and the longest one is after the guess.
• The ask names two concrete slots.

Credits

Idea adapted from a public outbound-skills collection; rewritten. Written by Victor Shulga (victorshulga.com).