Learn a New Vertical in Five Days: The Research Sprint Before Your First Dial

The assignment nobody prepares you for

Somebody reshuffled the patch. You used to sell into logistics and now you own insurance, or utilities, or pharma, and the manager who told you said it like it was good news. Then he said the quarter starts Monday.

So you do what everybody does. You download an analyst report, skim forty pages of it, highlight three sentences you don't understand, and open a tab called "industry trends 2025." By Thursday you have a folder of PDFs and no idea what to say when somebody picks up.

I have gone through this more times than I can count — four businesses of my own, plus selling inside AWS and Dell, where the segment you cover can change because of a slide in someone else's deck. The thing I learned is that reading is not research. Research is the process of building one opinion you can defend on the phone for thirty seconds. That's the whole deliverable. Not a briefing document. One opinion.

Here is the five-day sprint I run. It's a day of real work each, four or five hours, not a full-time immersion. You can do it while still dialing your old book.

Day one: the money

Before anything else, learn how firms in this industry make money and where it leaks.

Every industry has a shape to its P&L that everybody inside it understands and almost nobody outside it does. Insurers take in premium and pay out claims, and the gap between those two things — before you even get to expenses — is the number the whole company organizes around. Utilities largely can't set their own prices; they go to a regulator and argue for them, and that argument is built on what they spent and what they need to spend. Pharma spends enormous sums on trials that may produce nothing, so the clock on a patent is the clock on the business. Telcos build capital-heavy networks and then spend years trying to get more traffic across the same fiber.

You don't need the numbers. You need the shape. Ask yourself four things and write the answers in your own words:

Where does revenue come from, and who pays it? In insurance it's premium from policyholders and, further up the chain, from brokers who could move the book somewhere else. In utilities it's ratepayers, mediated by a commission. Knowing who actually cuts the check tells you who has leverage.

What's the biggest cost line? For an insurer it's claims. For a utility it's capital projects and maintenance. For a hospital system it's labor. The biggest cost line is where the CFO's attention lives, and it's where your buyer either gets funded or doesn't.

Where does money leak? Every industry has a known, named form of waste that people inside it complain about constantly. Leakage in claims. Truck rolls that didn't need to happen in field service. Trial sites that under-enroll. Churn in consumer telco. Find the named leak. It usually has a term of art attached to it, which is convenient, because you need those anyway on day three.

What's the cycle? Some industries are quarterly. Some run on rate cases that take a year. Some run on storm season, or open enrollment, or a regulatory filing date that everybody has tattooed on their forearm. If you call a claims leader during catastrophe season you are calling at the worst possible moment, and knowing that is worth more than any talk track.

Where do you get this? Public company earnings calls. Not the deck — the transcript, and specifically the Q&A section, where analysts ask the questions the IR team didn't want. Read three of them from three different companies in the vertical. You will see the same two or three anxieties come up every time. Those anxieties are your material.

Day two: the job

Day one was the industry. Day two is one person.

Pick the exact title you'll be calling. Not "operations leaders." Head of Network Operations at a regional carrier. Director of Claims Operations at a mid-size P&C insurer. Head of Asset Management at a distribution utility. One title, one company size, one region if it matters.

Now reconstruct their day in hours. When do they get in? What is the first system they open? What meeting do they sit in every Monday? Who calls them when something breaks, and what breaks? How much of their week is theirs and how much is reacting?

This sounds soft. It is the single highest-leverage thing in the sprint, because it determines whether your opener lands in their world or in yours. A field medical leader at a pharma company and a clinical ops director have almost nothing in common in terms of how their day is shaped, which is exactly why the pharma cold call script has to change depending on which one you got. Same company, same building, entirely different pressure.

How to reconstruct it without a customer to ask: job postings. Read ten job descriptions for the exact title. Skip the boilerplate at the top and read the responsibilities section, which is written by the hiring manager and reads like a confession. "Manage escalations from the twenty-four-hour operations center." "Own the quarterly reporting package for the regulator." "Coordinate with third-party adjusters during surge events." That's the job. Then read the requirements section for the tools — you now know what software they live in.

Second source: conference agendas. Find the industry association's annual event, pull up last year's session list, and read the titles of the operational track. Practitioners choose those sessions with their own time. The panel called "Retaining Adjusters in a Tight Labor Market" exists because a lot of people wanted to be in that room.

Write one paragraph at the end of day two: a Tuesday in the life of my buyer. Present tense. Specific hours. If you can't write it, you don't know them yet and no script will save you.

Day three: the vocabulary

On day three you're building two lists.

Twenty terms you must pronounce correctly

These are the words that appear in every conversation inside the industry and never outside it. Not jargon for its own sake — the load-bearing words. In insurance: subrogation, indemnity, loss adjustment expense, reserving, first notice of loss, combined ratio. In utilities: outage management, vegetation management, load, feeder, asset health, rate base. In telco: backhaul, provisioning, churn, latency, peering, RAN. In pharma: protocol, site, enrollment, adverse event, medical affairs, payer.

Twenty is the number because it's enough to sound native and few enough to actually memorize. For each one, write a one-sentence definition in plain English and — this is the part people skip — say it out loud. Some of them are acronyms said as words and some are spelled out letter by letter, and getting that wrong is worse than not knowing the term at all, because it announces that you learned it from a screen this week.

If you can find a podcast made for practitioners in the industry, put an hour of it on while you drive. You are not listening for content. You're listening for pronunciation and cadence — how fast they say these words, how casually, which ones they abbreviate.

Five terms you should never use

Every industry has words that are radioactive from the outside. Sometimes it's because the word is a vendor word: "digital transformation," "single pane of glass," "AI-powered." A network operations leader has been pitched a single pane of glass every quarter of their career and the phrase now functions as a signal to stop listening, which is why the telecommunications cold call script works better when you name a specific operational problem instead of a category.

Sometimes the word is radioactive for reasons you'd never guess from outside. Calling a claims handler an "agent" when the company uses "adjuster." Saying "patients" when the correct word in that conversation is "subjects." Saying "customers" to a utility that says "members" because it's a co-op. These aren't stylistic. They tell the person on the phone whether you have ever talked to anyone like them before.

Find these by reading how the industry writes about itself — trade press, association newsletters, LinkedIn posts by people with the exact title. When a practitioner corrects somebody's language in the comments, that is a free gift. Write it down.

Day four: three failure stories

This is the day that separates people who learn a vertical from people who read about one.

Go find three specific, documented times something went badly wrong in this industry. Not "companies struggle with data silos." Actual incidents. A regulator fined a carrier. A utility's outage response got picked apart in a public hearing. A trial got paused. A network went down during a holiday weekend and made the news.

These are findable. Regulatory bodies publish enforcement actions. Public utility commissions publish hearing transcripts. Trade press covers outages obsessively. Court filings are public.

Why three? Because one is an anecdote and three is a pattern, and the pattern is your point of view. Read all three and ask what the common thread is. Very often it isn't the technology. It's that somebody knew and couldn't get the information to the person who could act, or the process worked exactly as designed and the design was wrong.

This is where I would look hard at asset-heavy industries in particular, because the failure stories are so public and so specific. Everything in the energy and utilities cold call script about opening a head of asset management comes back to the fact that these people are judged on things that happen in public and get written up afterwards. They already know the failure stories. If you know them too, you are a different kind of caller.

Write each one as three sentences: what happened, what it cost them in terms they'd recognize, what the thing was that would have caught it earlier. Those three sentences are the raw material for your opener.

Day five: ten dials to build a hypothesis

On Friday you make ten calls. You are not trying to book anything. If you book, fine, but that's not the measure.

The measure is: does my opinion survive contact?

Make the ten dials to companies you would be slightly annoyed to lose — real targets, but not the top of your list. Open with the point of view you built on day four. Something like: "I've been reading through the enforcement actions from last year and the same thing shows up in three of them — the field team knew about the issue weeks before anybody in the office did. I called because I want to know if that's real or if that's just what makes the press."

Then shut up.

What you're listening for is not "yes, tell me more." You're listening for whether they engage with the premise at all. There are three possible reactions and each one teaches you something.

They correct you. This is the best outcome. "That's not really how it works — the field team reports it same day, the problem is it goes into a queue nobody owns." Congratulations, you just got a better hypothesis than the one you built alone, and you got it from a practitioner. Write the exact words down.

They agree flatly and move on. Usually means your point of view is true but boring. Everybody knows it. You need to go one layer deeper.

They don't understand what you're asking. Your language is wrong. Go back to day three.

Ten dials on a Friday will not give you statistical anything and I'm not going to pretend otherwise. What it gives you is the sound of the vertical in your ear, which no amount of reading produces. After ten calls you will know which of your twenty terms you're saying awkwardly, because you'll hear yourself hesitate before them.

The four questions that shortcut all of this

If your company already has customers in this vertical, you can compress five days into one conversation. Ask a customer success manager to introduce you to a friendly account and ask the customer four questions. Be honest about why — say you're new to the industry and you'd rather learn it from someone who lives in it than from a report. People are generous about this far more often than reps expect.

"What did your boss get asked about in the last board or leadership meeting?" This gives you the executive agenda in plain language, which is different from what the industry publishes about itself.

"What's the thing that goes wrong that everybody has just accepted?" The accepted failures are where the money is. Nobody's running a project on them, which is why they're still there, and naming one on a cold call is startling in a good way.

"When you were evaluating us, who inside your company was against it, and what was their argument?" This is the objection you will hear on every call this quarter, delivered in advance, with the reasoning attached.

"What did we say early on that made you think we didn't understand your business?" Painful and enormously valuable. This is your never-say list, sourced directly.

One call. Thirty minutes. I would do this before day one if I could get it.

How to know your point of view is ready

Here's the test. Say your opener out loud to somebody who works in the industry — a customer, a former colleague, anyone — and watch whether they nod politely or lean forward and start arguing.

Polite nodding means you've said something true and generic. Arguing means you've said something specific enough to be wrong, which is the only kind of statement worth opening a cold call with. A claims leader who tells you "no, that's not the bottleneck, the bottleneck is X" has just stayed on the phone with you, which is the entire objective of the first thirty seconds and the whole reason the insurance cold call script is built around a claim about their operation rather than a question about their priorities.

The second test: can you say it without notes, in your own words, twice in a row, differently? If you can only recite it, you don't own it. You'll fall apart on the first interruption, and there will be an interruption.

The third test, and the honest one: would you be comfortable if they asked "where did you hear that?" If the answer is a named public source, an incident, a filing, an earnings call, you're fine. If the answer is "a blog post about the industry," you are not ready, and they will smell it.

Five days gets you to a defensible opinion and a working vocabulary. It does not make you an expert and you should not pretend to be one. The most effective thing I've ever said on a call into an unfamiliar industry is some version of "I'm newer to this space than you are — here's what I think is true, tell me where I'm wrong." People will teach you. They enjoy it. What they won't tolerate is somebody performing expertise they don't have.

If I were starting a new vertical Monday, I'd do the five days above, and then I'd spend an hour practicing the opener out loud before I dialed anyone real — which is exactly what we built DrillCall for, running the same thirty seconds against a buyer who interrupts and pushes back until the words stop feeling borrowed. The research gives you the opinion. The reps give you the ability to say it while somebody is trying to get off the phone.