How to Rewrite a Cold Call Script for an Industry You've Never Sold Into
New patch on Monday, dialling Wednesday: how to transfer a cold call script into an industry you have never sold into by swapping three variables, not starting over.
You get an email on Monday. The patch is changing. You have been dialling SaaS VPs of Sales for two years and now you own construction, or legal, or utilities, and the pipeline review is still on Thursday so nobody is giving you a week to read up.
The instinct is to open a blank doc and write a new script. Do not do that. A blank page will cost you two days and you will end up producing something worse than what you already have, because the thing you already have has been beaten into shape by a few thousand live calls and the new thing has been tested by nobody.
What you should do instead is transfer. Keep the structure. Replace three variables. That is the whole method, and you can do it in an afternoon.
Why the structure survives and the content does not
A cold call opener is doing four jobs in about twenty-five seconds. It is proving you are a person and not a dialler. It is buying permission for the next fifteen seconds. It is putting a specific, uncomfortable, recognisable problem in front of the buyer. And it is handing them an easy way to say no so that the yes means something.
Those four jobs are identical whether you are calling a RevOps leader or a general superintendent standing next to a concrete pour. The human on the other end is busy, was not expecting you, and is deciding in the first few seconds whether you are worth the interruption. That decision process does not change by vertical.
What changes is the evidence you use to prove you are worth it. And the evidence lives in three places.
The three variables
1. The metric the buyer owns
Not the metric your product improves. The metric that appears next to this person's name when their boss is unhappy. Those are frequently different things and reps conflate them constantly.
A VP of Sales owns attainment and forecast accuracy. A VP of Operations at a general contractor owns schedule and margin fade on the job. A litigation chair owns realisation and utilisation and, quietly, whether the good associates stay. A head of asset management at a utility owns unplanned outages and whether the capital plan survives the regulator.
When you name the metric someone actually owns, you sound like you have been in the room. When you name an adjacent metric — the one your marketing team likes — you sound like you read a landing page. The buyer cannot always articulate the difference but they can hear it.
2. The failure mode they have lived through
Problems are abstract. Failure modes are stories. The failure mode is the specific bad afternoon this person has already had, at least twice, and remembers.
For a sales leader it is the forecast call where a deal that was committed slips and they have to explain it having already told the board it was landing. For an ops leader in construction it is finding out at the Monday look-ahead that a trade did not show up on Wednesday, by which point the float is gone and the owner is asking who is paying for the delay. For a managing partner it is the write-off conversation on a matter where the time went in late and thin and cannot be defended to the client.
You are not selling a product in the opener. You are demonstrating that you know what their bad afternoon looks like. That is the entire trade.
3. The words they would actually use for it
This is the one that gets missed and it is the one that gets you hung up on.
Every industry has an internal vocabulary and an external one. The external one is what appears in vendor marketing. The internal one is what people say to each other. If you use the external vocabulary you are immediately, obviously, a vendor, and the call is over before you finish the sentence.
Construction people say float, look-ahead, punch list, RFI, backcharge, margin fade. They do not say project management optimisation. Lawyers say matter, not deal. They say realisation, not revenue capture. They say associate leverage, not headcount efficiency. Utilities people say asset health, derating, outage window, and they will use acronyms you have to look up.
Get one term wrong and you are a tourist. Get three right and they will assume you have sold into this space for years, which is exactly the assumption you want them making while you are still learning it.
Doing it live: one opener, three industries
Here is a SaaS opener close to the shape I would use calling a VP of Sales. It is the same skeleton that sits underneath the SaaS cold call script for reps dialling CROs, VPs of Sales and RevOps leaders, stripped back so the moving parts are visible.
Hey Sarah, Tim here. I know I am an interruption — can you give me thirty seconds and then tell me if it is worth continuing?
Thanks. So I spend most of my week talking to VPs of Sales at companies around your size, and the thing that keeps coming up is ramp. People hired at the start of the year are still not carrying a full number, so the forecast has a hole in it, and it is not a hole anyone wants to explain on the board call.
Is that anywhere near what is happening on your team, or are you in better shape than most?
Now the same call to a VP of Operations at a mid-sized general contractor. Watch what moves.
Morning Dave, Tim here. I will be quick — thirty seconds and then you can tell me to get lost if it is not relevant.
Appreciate it. So I spend most of my week talking to ops leaders running four or five jobsites at once, and what keeps coming up is that they are finding out about a slip at the Monday look-ahead instead of on the day it happened. By then the float is gone, the follow-on trades are stacked up, and they are into a conversation with the owner about who eats the delay.
Does that sound like your world at the moment, or have you got that pretty well covered?
And the same call to a litigation chair. This one shifts furthest, and the reasons why are worth sitting with — the fuller version of this call is in the legal cold call script for getting a managing partner or litigation chair to book twenty minutes.
Ms Okafor, Tim here. Thirty seconds, and then you can tell me it is not for you.
Thank you. I speak with litigation chairs at firms around your size, and the thing I keep hearing is that associate time is going in late and going in thin. Narratives get written Friday for work done Tuesday, the billing partner writes off what he cannot defend to the client, and realisation takes the hit before anybody has had the actual conversation.
Is that live for you at the moment, or is it handled?
What survived
The skeleton did not move at all. Name, my name, an acknowledgement that I am interrupting, a time-boxed ask, an explicit permission to end the call. Then a peer frame — I talk to people like you. Then a failure mode with a consequence attached. Then a check question that offers a graceful out.
The permission ask survived word for word, near enough. The peer frame survived structurally but the peer group changed, and note that in construction it became four or five jobsites rather than company size, because scale in that world is counted in sites and crews, not headcount or ARR.
The check question survived but the register changed. Get lost works on a jobsite. It does not work on a managing partner, where the register is more formal and the out is shorter and drier.
What would have got me hung up on
If I had taken the SaaS version and only swapped nouns, I would have said something like this to Dave: I work with VPs of Operations and the issue that keeps coming up is visibility across the project portfolio at scale.
That is a dead call. Portfolio, visibility and at scale are all vendor words. None of them describe a bad afternoon. Dave has never once stood in a trailer and thought that he lacks visibility across his portfolio. He has thought that the drywall crew did not show and now the painters are sitting idle and he is going to have to explain the backcharge.
Same with the legal version. Efficiency is a trap word in a law firm. Say it to a managing partner and you are telling him his firm is a factory, which he has spent his career insisting it is not. Realisation is the same idea and it is a word he uses himself, so it lands as insight rather than insult. The construction and trades opener fails in the mirror-image way — get too formal and too abstract with a superintendent and he will decide you have never been on site, because you have not.
Q1 and Q4 also die. Construction runs on seasons and schedule, legal runs on matters and court dates. Calendar quarters are a SaaS artefact and using them tells everyone where you came from.
Sourcing the vocabulary before Wednesday
You do not need a month of industry immersion. You need forty or fifty terms and about six failure modes, and there are four places to get them fast.
Job posts. This is the highest yield per minute and almost nobody does it. Pull ten live job ads for the exact title you are calling, plus ten for the role one level below them. The responsibilities section tells you what that person is accountable for, written by the person who will manage them. The requirements section names every system they touch, which tells you your integration story and your competitive landscape without a single discovery call. Read the ads from the companies in your patch specifically, not from the giants.
Trade forums and the trade press. Not the glossy stuff. The places practitioners complain to each other. Contractor forums, engineering boards, the law firm subreddits, utility operator communities. You are mining for phrasing, and specifically for how people describe the moment something went wrong. Copy the sentences verbatim into a doc. You are going to use their sentences, not yours.
Public failure records. Every regulated industry publishes its disasters. Safety citations, incident reports, regulator filings, disciplinary notices, the risk factors section of any public company's annual report. Risk factors in particular are a gift: it is a legally-reviewed list of everything the leadership team is afraid of, written in their own language. For a patch like energy and utilities, where thirty seconds with a head of asset management is all you get, the regulatory record is most of your prep.
Your own company's tickets and recordings. If you have even two customers in the new vertical, the support queue is a list of the things that actually go wrong, in the customer's own words, with the emotional temperature attached. And if anyone at your company has ever sold into this patch, spend twenty minutes with the implementation or customer success person who onboarded them. Ask what surprised them. Ask what the customer complained about in month two. Those two answers are worth more than a day of reading.
One more, and it is uncomfortable: call three people in the industry who cannot buy from you. A retired superintendent, a mid-level associate, someone two levels below your buyer. Tell them plainly you are new to the space and ask them to tell you what their boss worries about. Most people will talk. I have never had someone hang up on that ask.
Pressure-testing in ten dials
Do not commit to a rewritten script on the basis that it reads well. It always reads well. You wrote it.
Block out enough time for ten connected conversations — not ten dials, ten actual humans picking up — and run the script verbatim. Same words every time. The temptation to tune it mid-block is enormous and you have to resist it, because if you change the script on call four you cannot tell whether call seven went badly for a script reason or a Dave reason. Record all of them if you legally can.
What you are listening for is not whether you booked anything. Ten calls is nowhere near enough to tell you about booking rates and anyone who says otherwise is selling you something. You are listening for four signals.
First: where did they interrupt? An interruption is data. If they cut you off at the metric line, you named the wrong metric or you named it in the wrong words. If they cut you off before you finished the permission ask, your opening is too long or your energy is off.
Second: did anyone correct your vocabulary? This is the single most valuable thing that can happen in the block. When a superintendent says we do not really call it that, we call it a backcharge, stop, write down the exact phrase, and thank him. You have just been handed the word by the only person qualified to give it to you.
Third: did anyone repeat your language back? If a buyer picks up your phrasing and uses it in their own answer, you have found a live term. Circle it. That line stays in the script permanently.
Fourth: what shape were the nos? There is a world of difference between a confused no and an informed one. What? and Sorry, who is this? mean the opener failed structurally. We handle that internally means the opener worked, the problem was recognised, and you are into objection territory, which is a completely different fix.
After ten, change one variable. Just one. Rerun ten more. If you change the metric, the failure mode and the phrasing all at once and it improves, you have learned nothing you can use next time you switch patches — and you will switch again.
The thing that actually makes this work
The transfer method works because your competence was never industry-specific in the first place. Knowing how to hold a call open, how to take a hit without flinching, how to ask a question that invites a real answer instead of a polite one — that is portable. Across four businesses and selling inside AWS and Dell, the mechanics of the first twenty seconds have not changed for me. Only the nouns changed.
What you are short of on Wednesday is vocabulary and specificity, and both of those can be bought with an afternoon of reading and ten disciplined calls. What you cannot buy in an afternoon is the reflex to keep talking when someone says what is this about in a flat voice. If that reflex is shaky, the new patch will expose it.
So before Wednesday I would take the three converted versions of my opener, load them into DrillCall, and run the construction one against an ops persona until I stop reaching for SaaS words under pressure. Ten minutes of that will surface the lines you have not actually internalised, and it costs a lot less than finding out on a live dial with the best account in the new patch. Then go make the ten calls that matter.