Ten Days to Sound Credible in a Vertical You've Never Sold Into

Ten days is enough. Ninety is a fantasy.

Somebody moved your patch. Last quarter you sold to IT directors at mid-market software companies and now you own utilities, or claims, or clinical operations, and there is a Monday coming whether you are ready or not. Enablement will tell you there is a ramp plan. There usually is, and it is usually a deck about the product with three logos from the vertical pasted on slide nine.

That is not what you need. You do not need to become a subject matter expert. You need to stop sounding like a tourist within the first ninety seconds of a cold call, because that is the entire game. An operator can hear an outsider immediately. Not because you got a term wrong, but because you got the emphasis wrong — you led with something they stopped caring about in 2019, or you used a word that only vendors use.

So here is the ten-day plan I would run myself. It is built for a rep with a quota and a calendar full of existing pipeline, not for someone with a clean two weeks. Assume you have ninety minutes a day for this and nothing more.

What credibility actually is

Before the schedule, get the definition right, because most people ramp against the wrong target.

Credibility in a new vertical is not product knowledge. It is not knowing the regulatory landscape. It is not being able to explain how their industry works — they know how their industry works, they do it every day, and a rep explaining it back to them is one of the more irritating experiences in professional life.

Credibility is demonstrating, quickly, that you know what this specific person gets yelled at about. That is it. If you can name the thing that keeps landing on their desk at 4:45 on a Friday, you have earned the next four minutes. Everything below is in service of that one outcome.

Which means your ramp is not a study of the industry. It is a study of a job title inside the industry. "Utilities" is not a vertical you can learn in ten days. "The person who owns distribution asset data at an investor-owned utility" is.

Pick the single title you will call most. Learn that person. You can add the second persona in week three.

Days 1 and 2: the five numbers they are measured on

Every operator in every vertical lives inside a small set of metrics that show up on a dashboard their boss looks at. Find five of them. Not ten. Five, because five is what you can hold in your head on a live call.

For a utility distribution or reliability leader, that list runs through things like SAIDI and SAIFI — the average duration and frequency of customer interruptions — plus vegetation management spend, capital plan execution against budget, and whatever the current wildfire or storm hardening commitment is. For a claims operations leader, you are looking at cycle time from first notice of loss to close, severity, loss adjustment expense, reopen rate, and adjuster caseload. For a construction operations or equipment manager, it is utilization, idle time, unbilled change orders, rework, and how much gear walked off the last three jobs.

How do you find these when you do not know the vertical? Three places, in order of usefulness.

First, public earnings calls and investor decks if the target companies are public. Utilities in particular publish an enormous amount because regulators require it. Read one transcript. The CFO will tell you exactly which operational numbers the company has promised to move this year, and every operator below them is being compensated against those promises.

Second, job postings. Go to the careers page of three target accounts and pull the job description for the role you are calling. The "responsibilities" section is written by the hiring manager, who is your buyer, describing what they need help with. It is the most honest document any company publishes. I have gotten more usable language out of job postings than out of any analyst report.

Third, LinkedIn profiles of people in that role who are proud of something. "Reduced X by Y" bullets on a résumé tell you what counts as a win in that job.

Write the five metrics on an index card. Real card, on the desk. You will use it.

Day 3: the three acronyms, and how to say them

Every vertical has a handful of terms that function as a shibboleth. Say them wrong and the call is over, not because the buyer is petty, but because mispronunciation is a reliable signal that you learned the word from a slide instead of from a person.

In utilities it is things like NERC CIP, which people say as "nurk sip," and the interruption indices, which get said aloud as "say-dee" and "say-fee" rather than spelled out. In insurance, FNOL gets pronounced as a word by people who use it hourly, and subrogation is almost always shortened in conversation. In healthcare operations, HCAHPS is said as "H-caps" and nobody spells out the letters. Construction has its own set, and the ones that matter are usually the workflow nouns — RFIs, submittals, retainage, punch — used casually and without explanation.

You only need three. Pick the three that appear most often in the material you read on Days 1 and 2, and confirm how they sound out loud. YouTube conference talks and industry podcasts are the fastest confirmation. Search the acronym plus the industry, find a fifteen-minute panel, and listen to practitioners say it to each other.

Here is the rule that matters more than the pronunciation: use each term exactly once per call, in a subordinate clause, and never as the point of the sentence. "When you're pulling the data for your reliability reporting" is credible. "So how are you thinking about your SAIDI and SAIFI KPIs?" is a rep who read a blog post this morning. Domain language works as seasoning. It does not work as the meal.

Day 4: two trade publications, twenty minutes each

Every vertical has trade press that practitioners actually read, and it is never the publication a marketer would pick. It is usually ugly, ad-heavy, and specific. Utility Dive, Claims Journal, ENR, the state association newsletters. Find two. Spend twenty minutes on each, and do not read the feature articles.

Read the headlines from the last six months in one scroll. What you are looking for is repetition. If the same theme appears eleven times in six months, that theme is on your buyer's mind whether or not it is on your product roadmap. Storm response. Adjuster attrition. Materials lead times. Whatever it is, it is the ambient anxiety of the industry right now, and referencing it correctly makes you sound like someone who reads the same things they do.

Then read the comments, if there are any, and read the letters section. Practitioners complain in trade press comment sections in a way they never will on LinkedIn. That is unfiltered buyer language, free.

Twenty minutes each. Do not spiral into this. It is a scan, not a research project.

Days 5 and 6: recordings, not decks

This is the highest-value block in the ten days and the one most reps skip, because it is boring and there is no completion certificate at the end.

Go into Gong or Chorus or whatever you use and pull calls from this vertical. Not the closed-won showcase calls that enablement clipped. Pull the messy first calls from reps who own the patch, and pull at least a few that went nowhere. Listen to five or six of them at normal speed with a notepad.

You are listening for four things, and only four.

The words the customer uses for the problem, verbatim. Not the words the rep used. Write down their exact phrasing, including the ugly phrasing. If three different buyers all say "we're chasing paper," that is your opening line for the next six months and you did not have to invent it.

The question that made the buyer stop and think. There is usually one per good call. You will hear the pause. Steal it.

The moment the rep lost them. Usually it is a product feature introduced forty seconds too early, or a term used incorrectly, and you can hear the buyer's energy change. That is your list of what not to do.

The objections, in their real form. Not the enablement version of the objection — the actual half-sentence a busy operator mutters before they get off the phone.

If you do not have recordings in the vertical, this is the moment to borrow. Ask the top rep on the team for two calls and buy them lunch. Ask a CS manager who runs QBRs with these accounts to let you sit in on one. A single QBR with an existing customer will teach you more about what the vertical cares about than a week of reading, because you are watching a buyer explain their own priorities to someone they trust.

While you are doing this, get a structured version of the buyer's language in front of you. I keep vertical discovery playbooks open in a second tab as a cheat sheet — the energy and utilities discovery playbook for network and asset conversations, the insurance claims playbook when the patch is carriers and TPAs, and the construction and trades playbook for anyone selling into field operations. What I use them for is not the question list. It is the phrasing. Reading twenty-five minutes of questions written in a buyer's own vocabulary is the fastest way to stop translating from your old vertical.

Day 7: the stupid question call

Now you go get a human to teach you. This is the single fastest accelerant available and almost nobody does it, because it feels like admitting you do not know your job.

Find a friendly customer. Ideally someone your company already serves in this vertical who likes their rep, or a former colleague who moved into the industry, or someone one degree away on LinkedIn. Ask for thirty minutes. Here is roughly what I say, adapted:

"I've just picked up [vertical] and I'd rather learn it from someone who lives in it than from our marketing team. Thirty minutes, no agenda, no pitch, I'm not going to try to sell you anything on this call — I want to ask you some genuinely stupid questions and have you tell me where I'm wrong. Would you be up for that?"

People say yes to this far more often than reps expect. Operators are rarely asked what they think, and being the expert for half an hour is pleasant.

Then ask questions that make it safe for them to correct you. Four that work:

"If I called you cold and opened with [your current opener], what would you think?" Let them tear it up. Take notes without defending it.

"What's a thing vendors say to you that instantly tells you they don't understand your world?" This gives you the disqualifying phrases, which are worth more than the good ones.

"Walk me through a normal Tuesday. Where does the time go?" You are looking for the manual workaround, the spreadsheet, the second system they log into. That is where the pain is.

"Who else in the building has to say yes, and what do they care about that you don't?" There is your map of the buying committee, drawn by someone inside it.

End by asking for one more introduction to someone in a different seat. Do this twice and you have four hours of primary research from practitioners, which is worth more than everything else on this list combined.

Days 8 and 9: turn your gaps into questions

By now you have a list of things you still do not understand. Do not try to close those gaps by reading. Convert them into discovery questions.

This is the reframe that makes the whole thing work. A gap in your domain knowledge is only a liability if you try to hide it. Turned into a question, it becomes the exact thing that makes you sound like you have done this before — because experienced sellers in a vertical ask about variation, not about basics.

So "I don't understand how they schedule crews" becomes: "How much of the crew schedule is set the night before versus reshuffled in the morning?" You have not revealed ignorance. You have revealed that you know scheduling is contested, which is the actual insight.

"I don't know if they own the assets or lease them" becomes: "Is that fleet mostly owned or on rental at this point?" Neutral, specific, and it produces an answer that changes your entire pitch.

"I have no idea who signs" becomes: "When something like this has gone forward before, did it sit with operations or did finance end up owning the number?"

Write fifteen of these. Ten will be mediocre and five will be good. The five good ones become your call framework.

What you do not fake, ever

There is one hard rule and it costs people deals constantly. The moment you bluff a domain term, you lose the operator, and you do not get them back.

If a buyer says something you do not understand, you have exactly two acceptable responses. The first is to ask: "Say more about that — how does that work at your shop?" The second is to admit it cleanly: "I don't know that term. What is it?"

The second one feels like death. It is not. In my experience it is one of the fastest trust-builders available, because the buyer has spent their whole career watching vendors nod along at things they clearly do not understand. A rep who says "I don't know" once, early, gets believed later when they say "I do know."

What you must never do is repeat the term back with a confident inflection and move on. Operators test for this, sometimes deliberately. They will use a term slightly wrong, or use an internal nickname for a process, and watch whether you nod. Nod and you are filed under vendor.

The related version of this rule: do not claim experience you do not have. "We work with a lot of utilities" when you have one logo is a claim that gets checked. "You'd be the second in this space for me, which is honestly why I want to understand how you're set up" is a claim that gets rewarded. Newness is not a weakness unless you perform confidence you have not earned.

Day 10: get on the phone and expect to be bad

Block the morning. Make thirty calls into the new patch with your index card, your five metrics, your three terms, and your five questions.

The first ten will be rough. You will misuse a word, you will lead with the wrong problem, you will get the "we already have something for that" and freeze. That is the point. Ten days of preparation gets you to the starting line, not across it, and the last mile of ramp only happens in live conversation with someone who has no patience for you.

Record all of them. Listen back to three that afternoon and mark every place you sounded like an outsider. Fix two of them tomorrow. Do that for two weeks and you will be indistinguishable from a rep who has owned the patch for a year, because the actual gap was never knowledge — it was fluency, and fluency comes from reps.

One thing I would do differently if I were ramping into a new vertical today: I would not spend those first ten days practicing on real buyers. I would run the openers, the terms and the objections against a DrillCall simulation first, in the persona of the buyer I am about to call, until the vocabulary comes out without me thinking about it. Burning your first thirty conversations in a new patch learning to pronounce three acronyms is an expensive way to practice when the accounts are finite and the list is small.

Ten days. Five metrics, three terms, two publications, one honest conversation with someone who does the job. Then the phone.