One Script or Sixteen? When a Vertical Script Actually Beats a Generic One

The Argument That Never Dies

Every sales floor I have worked on has had this fight. One camp says personalise everything — research the prospect, rewrite the opener, tailor every word. The other camp says use one script, dial fast, let volume do the work.

Both camps are wrong in a way that costs pipeline.

The personalisation camp produces reps who spend forty minutes crafting one email no one reads. The one-script camp produces reps who sound like they are reading a cereal box to a plant manager who has heard the same pitch six times this week. I have been on both sides. I have built teams that did both. The answer is not one script or infinite scripts. It is a skeleton that stays the same and a small number of slots you swap per vertical.

Let me show you what I mean.

The Skeleton That Never Changes

Every cold call I have ever made — inside AWS and Dell, across four companies I built — follows the same five-bone skeleton:

1. Permission — acknowledge you are interrupting, ask for a moment.
2. Reason for calling — one sentence on why you picked up the phone.
3. Symptom — name a problem the prospect probably has, in their language.
4. Proof — give them a reason to believe you can actually help.
5. Ask — request a specific next step.

That structure does not change whether I am calling a claims leader at an insurance carrier or a managing partner at a litigation firm. It works because it follows the prospect's psychology: they need to feel respected (permission), curious (reason), understood (symptom), confident (proof), and safe saying yes (ask).

The mistake reps make is thinking the whole script needs to be different for every vertical. It does not. Only three of those five slots need vertical-specific language. Permission and Ask are nearly identical every time. What changes is Reason, Symptom, and Proof.

The Three Slots That Must Change

Slot 1: Reason for Calling

A generic reason for calling sounds like this: "We help companies like yours improve operational efficiency." That sentence means nothing. It could apply to a hospital, a hedge fund, or a hot dog stand. The prospect's brain files it under "sales call, ignore."

A vertical reason for calling names the function and the context. It tells the prospect you called them on purpose.

Slot 2: Symptom

This is where most generic scripts die. A symptom has to land in the prospect's lived experience. If it does not, you sound like you googled their industry ten minutes ago. Because you probably did.

The symptom slot is the single biggest reason to build vertical scripts. A plant manager losing sleep over unplanned downtime does not care about "operational challenges." A claims leader watching cycle times balloon does not respond to "process inefficiencies." A managing partner watching associates burn hours on document review does not hear "productivity gaps." They hear noise.

Slot 3: Proof

Proof is where you connect your solution to someone in their world. Not "companies like yours" — that is a cliché dressed as specificity. You want to reference their industry, their function, their metric. You do not need to name-drop a customer if you cannot. But you need to prove you have been in their building before, metaphorically speaking.

Three Openers, Side by Side

Let me take the same skeleton and write it three ways. Watch what stays the same and what changes.

For a Plant Manager

"Hey [Name], this is Tim with DrillCall — I know I'm catching you out of the blue. Got twenty seconds?

Reason I'm calling: we've been working with ops leaders at mid-size manufacturers who are running lean maintenance crews but still eating unplanned downtime on legacy lines.

What I keep hearing is that the downtime data lives in three different places, so by the time someone flags a pattern, you've already lost a shift.

We built something that pulls that data into one view so your maintenance leads can see failures forming before they hit. A couple of plants running similar setups cut their unplanned stops meaningfully within the first quarter.

I don't know if that's relevant to your floor — worth twenty minutes to find out?"

I walk through the full version of this approach in the manufacturing cold call playbook, including how to handle the "send me an email" brush-off that plant managers love.

For a Claims Leader

"Hey [Name], this is Tim with DrillCall — interrupting your day, I know. Quick fifteen seconds?

Reason I'm calling: we've been talking to claims leaders at carriers your size who are seeing cycle times stretch while headcount stays flat.

The pattern I keep hearing is that adjusters are toggling between four or five systems just to get a single claim to the next stage, and the bottleneck isn't effort — it's the workflow itself.

We built a layer that sits on top of those systems and routes claims decisions faster. A few carriers in your segment tightened their average cycle time noticeably after rolling it out.

I'm not sure if your team is hitting the same wall — is it worth twenty minutes to compare notes?"

The insurance cold call script goes deeper on keeping a claims leader engaged past the first ten seconds — their objection patterns are different from almost every other vertical I have called into.

For a Managing Partner

"Hey [Name], this is Tim with DrillCall — cold call, I'll be quick. Fifteen seconds fair?

Reason I'm calling: we've been working with litigation chairs and managing partners at firms your size who are watching associate hours pile up on document review and due diligence without a clear way to benchmark what's reasonable.

The complaint I keep hearing is that realization rates on those hours are dropping because clients are pushing back, but the work still has to get done by someone.

We built a tool that helps firms see exactly where associate hours are going and flag the blocks that are candidates for automation or reallocation. A handful of firms running similar practice mixes saw realization improve after they started using it.

I have no idea if that matches what you're seeing — worth a twenty-minute conversation?"

The legal cold call playbook breaks down why managing partners respond to realization rate language when they will hang up on anything that sounds like generic "legal tech."

What Actually Changed

Look at those three scripts side by side. The Permission line barely moved — slightly different phrasing, same intent. The Ask is almost identical: twenty minutes, framed as exploratory, low commitment.

But the Reason, Symptom, and Proof slots are completely different. Different job title referenced. Different metric named. Different operational pain described. Different proof framed.

Here is what you swapped:

• Reason: "ops leaders at mid-size manufacturers" vs. "claims leaders at carriers your size" vs. "litigation chairs and managing partners at firms your size." You named their role, their industry, and their scale.
• Symptom: "unplanned downtime on legacy lines" vs. "cycle times stretch while headcount stays flat" vs. "associate hours pile up on document review." You named the specific operational pain they wake up thinking about.
• Proof: "cut their unplanned stops" vs. "tightened their average cycle time" vs. "saw realization improve." You named the metric that matters in their world.

Three changes. Not sixteen. Not a full rewrite. Three slots, swapped with precision.

Twenty Minutes Per Vertical

Here is the effort math. To build a vertical insert — the Reason, Symptom, and Proof for a specific segment — I need three things:

One conversation with someone who sells into or works in that vertical. Could be a customer success manager, an AE who has closed deals there, or a friend who works in the industry. I am listening for the words they use to describe their problems. Not marketing language. Shop-floor language. Adjuster language. Partner-meeting language.

One pass through a few job postings or earnings calls. Job postings tell you what the company is hiring for, which tells you what hurts. Earnings calls tell you what the CEO is telling Wall Street, which tells you what the whole org is being measured on.

Twenty minutes to write and say aloud three sentences. Reason, Symptom, Proof. Write them. Say them out loud. If they sound like a brochure, rewrite until they sound like a human being who has done this before.

That is it. Twenty minutes of writing per vertical, plus whatever time you spent on the conversation and research — call it an hour total. And that insert is reusable for every dial into that segment. You are not rewriting from scratch. You are swapping three sentences and dialing.

Compare that to the rep who rewrites the entire script for every prospect. That rep makes half the dials. Or compare it to the rep who uses one generic script and wonders why plant managers hang up after eight seconds.

When a Full Vertical Script Is Worth Building

Not every segment deserves its own insert. Here is the rule I use:

A vertical script is worth building when three conditions are true:

The segment is repeatable. You have at least a few dozen accounts in it, ideally more. If you are calling three hospitals and then moving on, do not build a hospital script. Just do light research on those three.

The segment has a distinct metric. Plant managers care about uptime and throughput. Claims leaders care about cycle time and loss ratios. Managing partners care about realization rates and billable hours. If the metric the buyer watches is different from your default script's metric, you need a vertical insert. If the buyer watches the same metric as everyone else you call, your generic Proof line might be fine.

The segment has a distinct buying process. Manufacturing deals often run through ops and then up to a VP of operations or a plant GM. Insurance deals run through claims and then into IT and procurement. Legal deals run through a managing partner or practice group chair and may never touch procurement at all. If the buying process is meaningfully different — different stakeholders, different approval chain, different timeline — a vertical script helps you speak to that reality from the first call.

If all three are true, build the insert. If only one is true, you can probably get away with a light modification of your generic script. If none are true, do not bother.

When It Is Not Worth It

I have watched managers mandate vertical scripts for every segment on the target list, including segments with eight accounts. That is a waste. If the segment is small, do account-level research instead. Spend five minutes on each company, not twenty minutes on a segment insert you will use four times.

I have also seen reps build vertical scripts for segments where the pain and metric are identical to their generic script. If you sell a cybersecurity tool and you are calling CISOs across five industries, the pain might be the same everywhere: breach risk, compliance deadlines, understaffed teams. The symptom does not change by vertical. The buying process might, but if it does not, one script is fine. Do not create work to feel productive.

The Real Cost of Getting This Wrong

The cost of a generic script is not just lower connect-to-conversation rates, though that is real. The deeper cost is that your reps never learn the vertical. Every time a rep dials a plant manager and says "operational efficiency," they miss the chance to hear the plant manager correct them. They miss the chance to learn the real language. They stay generic permanently.

A vertical script forces the rep to learn three sentences' worth of industry knowledge before they pick up the phone. That is not a lot. But it compounds. After fifty dials into manufacturing, a rep with a vertical insert has heard fifty reactions to a specific symptom. They know which version lands. They know the objections. A rep with a generic script has heard fifty versions of "not interested" and learned nothing.

How I Would Start

If I were building this system from scratch today, I would pick my top two or three segments by account volume, spend an hour on each building the Reason-Symptom-Proof insert, and then drill those scripts until the words felt natural. I would use DrillCall to run those vertical scripts against realistic resistance before I ever dialed a real prospect — it is built exactly for this kind of repetition, where you need to hear your own words come back at you under pressure and figure out which version of the symptom line actually earns the next thirty seconds.

Then I would dial. A lot. And I would keep a running doc of what prospects said back to me, because their language is always better than mine. The vertical script is not the destination. It is the starting point that gets you close enough for the prospect to finish the job.