Sales & Revenue Enablement

How to Create a Sales Script: One Cold Call, Line by Line

A cold call script built block by block for a fictional vendor: the opener, the thirty seconds, the ask, and the five replies you need a line ready for.

Emre Ilıksu

Emre Ilıksu

October 23, 2026 · 12 min read

Most sales script guides give you a monologue: greeting, pitch, value proposition, close. Then the prospect says "not interested" eight seconds in and the monologue is useless. The call is decided by their first reply, not by your speech, so that is what this post scripts. We are going to write one complete cold call script, block by block, for a fictional vendor, and you will leave with the finished script and the skeleton to write your own.

One scope note. This is a cold call script. A discovery call does not get a script, it gets a question bank, and a demo gets an agenda. If you are writing for the phone and the person did not ask you to call, read on.

Start from who is on the line

A script is written for a person, not a market. Ours is Ledgerline, a fictional accounts-payable automation vendor whose ideal customer is a mid-market finance team on NetSuite with more than a thousand supplier invoices a month. The trigger that puts a company on Ledgerline's call list is a new controller in their first ninety days, and that trigger supplies the reason for the call. If you have not written down who you call and why now, do that first. What an ICP is, and how to build one covers it, with Ledgerline's own profile as the example.

The person on the line today is Mara, controller at Northgate Packaging, about two months into the job. Northgate moved to NetSuite in the spring. Tom from Ledgerline is calling her for the first time. Every line below is written for that call, and the last section shows which lines to swap for yours.

Block 1: the opener, fifteen seconds

The opener has four jobs and one time limit. Say who you are, say where you are from, say why you are calling this person today, and ask for a short window. All of it in under fifteen seconds, because that is roughly how long a stranger gives you before deciding.

The rubric Closemind scores cold calls against is specific about what fails here: rambling intros, filler like "how are you today", and burying the reason for the call. The reason has to arrive early and it has to be about them, which is where the trigger does the work.

The obvious line, the one most templates produce:

"Hi Mara, this is Tom calling from Ledgerline. How are you today? I'm reaching out because we help finance teams automate accounts payable and I'd love to find some time to tell you about it."

Nothing in that line is about Mara. The reason for calling is a description of the vendor, and "find some time to tell you about it" is a request for a meeting with no reason to grant it. Here is the line we write instead:

"Hi Mara, Tom from Ledgerline. I know this is out of the blue. You took over as controller at Northgate about two months ago, and I call controllers in their first quarter about one thing: how supplier invoices get approved after a NetSuite move. Can I have thirty seconds, and you tell me if it's off?"

Four things changed. The trigger is in the second sentence, so she knows within five seconds that this is not a list call. The reason is one thing, named plainly, in her world. The ask is thirty seconds, not a meeting. And "you tell me if it's off" hands her the exit, which is the fastest way to get a busy person to stay on.

One piece of vendor research worth knowing. Gong's analysis of 90,380 cold calls, published in 2018 and still the largest public dataset on openers, found that opening with the reason for the call raised the success rate by 2.1 times, and that "did I catch you at a bad time?" made reps 40 percent less likely to book the meeting. Treat the multipliers as correlations from one vendor's customers, but the direction matches what the rubric penalises.

Say the opener out loud before you write anything else. Read on paper, every opener looks fine. Said to someone who can hang up, half of them fall apart in the second sentence. Run it against an AI prospect who answers the phone clipped and busy, and on hard difficulty hangs up on a weak opener, and you will know in three attempts whether the line survives. The first minutes are free, no card required.

Block 2: the thirty seconds

You asked for thirty seconds. Now earn them, with three sentences and nothing else: one reason to care, one line on what you do, one question she can answer from her chair.

The rubric's relevance dimension is blunt about this block. One sharp reason to care, framed in the prospect's world, kept concise. A cold call is not the place for a feature dump or a discovery interrogation, and stacking a second pitch on the first is penalised as hard as rambling. The metric targets say the same thing in numbers: no single turn longer than thirty seconds, and at least one real question.

"Most controllers I talk to after a move find approvals still happen in email, so close waits on whoever is travelling. Ledgerline routes each invoice to the right approver inside NetSuite and chases them so you don't. How are approvals getting done at Northgate right now, in the system or around it?"

The reason to care is a situation Mara either recognises or does not, and either answer is useful. The product line is one sentence with no adjectives in it. The question is the only one in the script, and it is built so that she does not need to think, look anything up, or admit anything embarrassing. "In the system or around it" is a two-option question a controller can answer in four words, and the answer tells Tom whether there is a call to have.

Then stop talking. Whatever she says next is the most important thing on the call, and your job for the next ten seconds is to hear it.

Block 3: the ask

If the answer was "around it," you have a reason to meet, and the ask should follow within one sentence. The rubric's earning-the-meeting dimension wants a specific, low-friction next step with a proposed day and time and a clear agenda, assumptive but respectful. It penalises the vague "I'll send some info," the failure to ask at all, and the attempt to close the whole deal on a cold call.

"Then here's what I'd suggest. Twenty minutes next Tuesday or Wednesday. I'll show you the approval flow inside NetSuite and you tell me if it would have helped at this month's close. Does Tuesday at ten work?"

Twenty minutes, two days offered, a one-line agenda that is about her close rather than Tom's demo, and a closed question at the end. If she says yes, confirm the time, say you will send an invite, and get off the phone. The most common way to lose a booked meeting is to keep selling after it is booked.

If the answer to the question was "in the system, it works fine," believe her. "Good, then I'm not the call you need. If that changes at an audit or an acquisition, I'm the person to ring." Let go cleanly. The rubric scores that too, under respect for their time, and it penalises dragging the call past its welcome.

Block 4: the five replies you need a line for

Here is the part templates leave out, and the part that decides most calls. Before Mara hears the thirty seconds, she will very likely say one of five things. The brush-off dimension of the rubric describes the right response in one sentence: one calm, relevant re-hook that earns a few more seconds, without folding, arguing, or steamrolling past it. Write the line for each, word for word, and say them until they are boring. A little humour helps here, because it signals you are not reading, as long as it is one line and not a bit. Where there is a variant below, pick one and keep it.

"Not interested."

"Is that because I'm calling out of the blue, or because invoices already get approved inside NetSuite automatically?"

The line gives her a face-saving reason for the reflex and puts the real question next to it. "Out of the blue" is the opener's phrase, so the script sounds like one person. If the answer is "they're automatic," you are done, politely. If it is anything else, she has just told you there is a call.

"Send me an email."

"Happy to. Can I ask one question before I do?"

She says yes, because it is a small thing to say yes to. Then the question:

"Is that a polite way to say go away?"

Honest, light, and it hands her the exit. Most people laugh and then tell you the truth, which is worth more than the email. Two variants if that line is not you: "When did you last get an email that worked better than a conversation?" or "Do you want the long one with the one-pager and the jargon, or two lines and a calendar link?" The second pre-sells the meeting while she is still laughing.

"We already have something for that."

"Interesting. What would you change about it if you could?"

Mirror first, then ask. Do not argue with the incumbent. The workaround is the reason you are calling, and this question finds it without making her defend her choice. If she says it is fine as it is, the ask for this branch is a second opinion:

"Fair. Everyone has a family doctor, and I'm more of a second opinion. Twenty minutes next week, and you'll either feel reassured or very interested."

"I'm in the middle of something."

"Then I'll be quick. Is Thursday morning better for five minutes, or should I not call back?"

Take her at her word and offer a time and an exit. "Should I not call back" sounds like a risk and is the opposite. People say "Thursday is fine" far more often than "don't."

"How did you get my number?"

"I use LinkedIn for this. I'll take thirty-five seconds, and if it's not relevant, I promise you won't hear from me again."

Answer with wherever you actually got it, in one clause, then offer the exit and the time. Thirty-five is on purpose. An odd number sounds like you have counted, and the promise at the end is the part she will hold you to, so keep it.

And the sixth reply, which is a real no: "I said no." Say thank you and hang up. A script that cannot hear a no loses you the next call to that company.

The script, assembled

A white card titled the script, main path, showing the Ledgerline cold call in four labelled rows: the opener with name, company, the trigger and a request for thirty seconds; the thirty seconds with one reason to care, one line on what Ledgerline does and one question; Mara's answer that approvals happen around the system in email and a spreadsheet; and the ask for twenty minutes next Tuesday or Wednesday with a proposed time.

That is the whole main path: opener, thirty seconds, her answer, the ask. Beside it sit the five branches from the block above. On paper it is about 140 words from Tom, which is under a minute at a normal speaking pace, and well inside the cold call targets the product scores against: the rep talking between 45 and 65 percent of the time, no turn over thirty seconds, at least one question.

Make it yours: the five slots to swap

The skeleton is the same for any product that is sold by phone to someone who did not ask. Five slots change.

  1. The trigger. Whatever puts a company on your list this month: a hire, a funding round, a new location, a regulation, a product launch. It goes in the second sentence of the opener. If you do not have one, you are not ready to write the opener.
  2. The one thing you call about. Not your product. The situation your product fixes, named the way your buyer would name it. Ledgerline calls about "how supplier invoices get approved." It does not call about "AP automation."
  3. The question they can answer from their chair. Two options, four-word answer, no homework. The answer should split the world into "there is a call here" and "there is not."
  4. The ask with a time in it. Short meeting, two days offered, an agenda about their outcome. Change the length and the days, keep the shape.
  5. The five re-hooks. Your product's versions of the five replies, each ending in your question or an exit. Write them last and rehearse them first, because they are the ones you say under pressure.

What to cut when it runs long

Scripts grow. Every call that goes badly tempts you to add the line that would have fixed it, and six months later the opener is forty seconds. When it runs long, cut in this order.

  • Features. The product line stays one sentence. If you need a second, you need a better first.
  • The second question. One question on a cold call. Save the rest for the meeting you are asking for.
  • Your credentials. "We work with over 200 finance teams" buys you nothing with a stranger. The trigger buys you more.
  • "Does that make sense?" It never does anything except give them a place to say no.
  • Anything you are saying to calm yourself down. The "I know you're busy, I'll be really quick, I promise" run-up. Say the opener instead.

Test it on the person you are about to call

A script is a hypothesis about how a stranger will react, and the only test that counts is a stranger reacting. Before Tom calls Mara, he can call her first. Paste a prospect's LinkedIn profile or company site into Closemind and it is researched into a persona: the role, the company, the likely objections. Then run the script against that persona on the cold call scenario. The counterpart answers clipped and busy, brushes you off the way the real one will, and on hard difficulty hangs up on a weak opener. Afterwards you get a score on each block, opener, brush-off, relevance, the ask, and your own lines quoted back where they worked and where they did not.

Write the script. Then say it to someone who can hang up, five times, before you say it to someone who can buy.

#openers#objection-handling#sales-script#cold-calling

Summarize with AI

Open this article in your assistant of choice.

You've read the theory.Practice it out loud.

Run a live roleplay on exactly this, get scored on what you actually said, and close the gap between knowing and doing.

Practice makes it perfect. Free minutes on sign-up, no card.