How to Get Fluent in a New Vertical in Two Weeks (Because Your Patch Just Changed)

Territory reshuffles do not come with a reading week. Somebody moves a line on a map in January, and on Monday you own construction instead of martech, or claims instead of ecommerce, and you are expected to dial on Tuesday. Nobody is going to give you a month.

I have had to do this a few times, and I have watched a lot of reps do it badly. The bad version is reading. You download a market report, you skim a couple of vendor whitepapers, you build a persona deck nobody asks for, and two weeks later you sound exactly like a person who has read about an industry and never spoken to anyone in it. Prospects clock that in the first sentence. They cannot always tell you why, but they know.

Here is the thing that took me too long to understand: fluency is not vocabulary. Fluency is knowing what is boring. A native speaker of an industry knows which topics are clichés, which complaints are real, and which vendor pitch they have already heard four times this quarter. That is what you are actually trying to acquire in two weeks, and you can get most of the way there with four specific things.

The four things that make you sound native

Everything else is optional. If you only have two weeks, you are collecting these:

Three metrics your buyer is personally measured on

Not industry metrics. Not the ones in the analyst report. The three numbers that show up in your buyer's own performance review and get read out loud in front of their boss.

This is the single highest-leverage thing on the list, because it is what lets you connect your product to their comp instead of to their department. A VP of Operations at a commercial general contractor does not care that you "increase efficiency." He cares about margin fade — the gap between what the job was bid at and what it actually came in at — because that gap is the thing he has to explain in the Monday meeting.

Get three. Know which one hurts most right now.

Five nouns they use that you currently do not

Nouns, not adjectives. Specific objects and artifacts in their world. In construction those are things like punch list, RFI, submittal, change order, retainage. In claims they are FNOL, subrogation, leakage, reserve, pending inventory.

The test for whether a noun counts: it is a thing that physically exists in their week. It arrives, it gets processed, it sits in a pile, it makes someone angry. Abstract industry jargon does not help you. "Digital transformation in the built environment" is not a noun anyone uses on a jobsite.

Five is enough. You are going to use one or two per call, not all five. Using all five is how you sound like you crammed.

The two roles that block deals in that industry

Every vertical has a pair of roles that kill deals late, and they are almost never the roles that kill deals in the vertical you came from. In SaaS-selling-to-SaaS, it is usually security review and procurement. In construction, it is the field superintendent who has to actually use the thing and will not, and the owner or project executive who signs and hates recurring cost. In insurance, it is compliance and vendor management, and vendor management at a carrier moves like a glacier.

If you do not know these two roles by the end of week one, you will run a beautiful discovery cycle into a wall in month three.

One recent event you can reference

One. Something that happened in the last quarter that your buyer knows about. A big carrier's earnings call where they talked about severity. A CAT event. A materials price move. A state regulation. A large acquisition in their market.

You are not going to lecture anyone about it. You are going to use it once, as a clause, to prove you live in their world: "with everything that happened after the storm season, I'm hearing pending inventory per adjuster is the thing nobody can dig out from." That clause does more than a page of research.

Where to actually find this

Most reps go straight to Google and get the worst possible material. Here is the order I would go in.

Your own call recordings, first. Before anything external. Pull ten recordings of calls with customers in that vertical — not demos, not pitches, but discovery calls and QBRs where the customer is doing most of the talking. Listen at normal speed with a notepad and write down every noun you do not recognize. That is your vocabulary list, and it comes pre-filtered for relevance because these are people who bought.

If your company has no customers in the vertical yet, listen to lost-deal calls. Losses are more instructive anyway.

Job postings for your buyer's exact title, second. This is the trick I would give a new rep first if I could only give one. Pull three or four current job descriptions for "VP of Operations, commercial general contractor" or "Claims Operations Manager, P&C carrier." The responsibilities section is a list of the metrics that role is measured on, written by the person who manages that role. The requirements section is a vocabulary list. It is free, it is current, and it is specific to the company size you sell to.

Earnings calls, third. If there is a public company in the vertical, read the transcript of the most recent quarterly call, and read the analyst Q&A rather than the prepared remarks. Prepared remarks are marketing. The Q&A is where an analyst asks the CFO why a specific number moved, and the CFO explains the operational reason. That explanation is your industry's actual anxiety, in the industry's actual language. This is also where your one recent event usually comes from.

Trade press, fourth, and only the operator-facing kind. Construction Dive and ENR for construction. Claims Journal and Insurance Journal for claims. Read headlines for a week, not archives. You are calibrating for what is current, not building a history.

A conversation with your CS team, fifth. Thirty minutes with whoever supports your existing accounts in that vertical. Ask three questions: what do these customers complain about that other verticals do not, who was the person who almost killed each deal, and what do they call us internally. That last one gets you the category name your buyer uses, which is often not the one your marketing team uses.

Conference agendas, if you have time. Look up the big association event in that industry and read the session titles. Somebody paid money to program those sessions against what practitioners will actually leave the office for. It is a ranked list of pain, published free.

What to skip

Skip the analyst market report. Skip your own vendor's industry whitepaper — it was written by a marketer who did the same research you are doing, badly. Skip the history of the industry. Skip the full text of any regulation; you need to know that compliance blocks deals, not the statute. Skip building a slide deck about the persona. Skip memorizing acronyms you cannot use in a sentence.

And skip trying to become a subject matter expert. You are not going to out-construction a superintendent with twenty-five years in the field, and if you try, he will enjoy taking you apart. Your job is to be credible enough that he keeps talking. Credible is a much lower bar than expert, and it is reached almost entirely through nouns and metrics.

The test

At the end of two weeks, there are exactly two deliverables, and they take fifteen minutes to write and about a hundred dials to validate.

One: a 25-second opener that contains one vertical noun and one vertical metric. Twenty-five seconds because that is roughly how long you have before someone decides whether you are worth the rest of the call. If you cannot get the noun and the metric in without rushing, your opener is too long or your noun is too obscure.

Two: a written prediction of the first objection, verbatim. Not the category of objection. The actual sentence, in their words, in their accent. "We've got a guy who does that." "We already bought something like this and nobody used it." "Call me after the season."

If you cannot predict the first objection word for word, you are not fluent yet. And this is the honest test, because you find out on the first ten dials whether you were right. Reps who guessed correctly get a small jolt of confidence that changes their voice for the rest of the day. Reps who guessed wrong now have the real objection written down in the prospect's own language, which is better material than anything they read.

Write the prediction down before you dial. Otherwise you will convince yourself afterwards that you knew.

Worked example: SaaS rep moving into construction

Say you sold marketing software and now you own commercial contractors and specialty trades.

Metrics. Margin fade — bid margin versus as-built margin on a job. Schedule, specifically days behind on the critical path, because that is what the owner calls about. Safety, which shows up as a recordable incident rate and drives what they pay for insurance. Cash is a strong fourth if you want one: retainage outstanding and days to get paid.

Nouns. Punch list. RFI. Change order. Submittal. Retainage. You should also know that a "sub" is a subcontractor, a "super" is the field superintendent, and "self-perform" means the GC does that trade with its own crews instead of subbing it.

Blockers. The field superintendent, who has an existing way of doing things and whose non-adoption quietly kills the deal in month four. And the owner or project executive, who signs, is often the founder's family, and treats software as overhead. Note what is not on that list: there is frequently no real IT function to fight, which changes the whole shape of the cycle compared to what you are used to.

Recent event. Read one quarterly call from a public contractor and one week of construction trade headlines. You will find something about labor availability or material costs within a day.

Now the opener. Something like: "Dave, Timothy calling — this is a cold call, you can throw me off in ten seconds. Reason I'm calling: I keep hearing from ops guys running four or five jobs that the daily report lands at nine at night, so by the time you know the crew lost half a day you can't do anything about it, and it shows up as margin fade at closeout. Is that anywhere near your world, or are you already tight on that?"

One noun, one metric, one exit ramp offered on purpose. And the first objection you should predict: "we've already got Procore" or some version of "our guys aren't going to use another app." If you want the shortcut, the construction and trades cold call script for VPs of Operations and general superintendents is essentially this exercise already done, with the objection handling attached — reading it is the fastest fluency hack I know for that vertical, because it is a compressed version of thirty calls you have not made yet.

Worked example: SaaS rep moving into insurance claims

Same rep, different patch. Now you sell to claims leaders at carriers and TPAs.

Metrics. Cycle time — average days to close a file. Loss adjustment expense, which is what it costs to handle the claim as distinct from what they pay out. Leakage, which is money paid that should not have been paid. Pending inventory per adjuster is the one that makes an ops leader wince, because it is the number their people complain about.

Nouns. FNOL, the first notice of loss. Subrogation. Reserve. Severity. SIU, the special investigations unit. Know the difference between a desk adjuster and a field adjuster, and know that a TPA is not a carrier.

Blockers. Compliance, because claims handling is regulated at the state level and anyone can point at unfair claims practice rules to stop a project. And vendor management, because carrier procurement and security review is a long, formal process that no amount of champion enthusiasm shortens. If you came from selling to fast-moving tech companies, this is the adjustment that will hurt.

Recent event. A carrier earnings call discussing severity trends, or a catastrophe event that spiked volume.

Opener: "Sarah, cold call, I'll be quick. I'm calling claims ops leaders because the thing I keep hearing is that pending inventory per adjuster hasn't come back down since the last surge, and cycle time is the number your boss actually looks at. Is that a fair read on your team, or have you already gotten that under control?"

Predicted first objection: "we're in the middle of a core system replacement," or "anything that touches a claim file has to go through compliance." The insurance cold call script for keeping a claims leader on the phone walks that exact wall, and it is worth reading before you dial rather than after you have burned fifty names learning it live.

The pattern holds for other patches. Freight and 3PL buyers have heard the same pitch so many times that the opener has to acknowledge it directly, and a plant manager will give you time only if you open on something happening on their floor. Different nouns, same four-item checklist.

The calendar

Week one, days one and two: call recordings and vocabulary list. Day three: job postings and one earnings call transcript. Day four: trade press and pick your one event. Day five: thirty minutes with CS, then write the opener and the objection prediction.

Week two is dialing. Days six through eight, run the opener as written and log every objection in the prospect's exact words — not your paraphrase. Day nine, rewrite the opener using the three phrases that came back most often. Days ten onward, run version two.

That is it. You are not fluent at the end of two weeks. You are credible, which is the only thing the first call requires, and you now have a machine for getting fluent that runs on live dials instead of reading.

What I would do next

The part that breaks is week two. Reps write a decent opener and then deliver it badly on the first live call, get flustered by an objection they predicted correctly, and quietly go back to the generic pitch that does not work but is comfortable. The fix is reps — say the new opener fifty times before a real prospect hears it. That is exactly why I built DrillCall: AI role-play against a buyer in your vertical so the first construction super who tells you his guys will not use another app is not the first time you have heard it. If your patch just changed, I would spend one evening drilling the opener out loud before I spent another week reading.