Pick Your Vertical Carefully: The Industry You Dial Into Shapes Your Whole Career

The two-year fork

Take two people who start their first SDR job on the same Monday. Same age, same energy, same willingness to make the calls. One lands at a security vendor and spends two years dialing SOC managers and directors of information security. The other lands at a construction tech company and spends two years dialing VPs of operations and general superintendents.

Two years later they are not the same rep. They are not even close. They speak different languages, they book meetings different ways, they get paid on different curves, and when they go to interview somewhere new, completely different doors open for them.

Neither one made a mistake. But most of the people I talk to did not choose. They took the first offer that cleared their salary floor and let the vertical happen to them. That is the part worth fixing, because the vertical you dial into for your first two or three years is the single biggest input into what your career looks like at year seven, and it is one of the few things about early-career sales you actually get to pick.

So let me give you the way I think about it. Four axes. Then the part almost nobody works on deliberately, which is how you get fluent fast enough for it to matter.

Axis one: deal size and cycle length

This is the obvious one, and people still get it backwards.

Big deals with long cycles are not automatically better. What a long cycle buys you is exposure to complexity — procurement, security review, multi-threading across a buying committee, executive sponsors who go on parental leave halfway through. What it costs you is reps. If your deals take three quarters to close, you will personally live through very few full cycles in your first two years. You will learn what a complex deal feels like, but you will not learn it many times.

Short cycles are the opposite trade. Sell something a regional contractor can approve in two calls and you will run more cycles in a year than a big-enterprise AE runs in three. You get pattern recognition fast. You learn objection handling in your bones because you hear the same five objections four hundred times. What you do not get is practice navigating a security questionnaire or a legal redline or a CFO who wants a business case in a format you have never seen.

When I was selling inside AWS and Dell, the thing that struck me was how differently reps thought depending on which end of that spectrum they came up on. The transactional reps were faster, more comfortable on the phone, better at getting to a no. The enterprise reps were more patient and much better at reading a room they were not in. Both skill sets are real. Neither one is free.

The practical question to ask yourself: do you want to be dangerous quickly, or do you want to be expensive eventually? If you are twenty-three and you need reps, go somewhere the cycle is short and the phone is busy. If you already have three years of volume behind you and you keep losing to reps who know how to run a committee, go get the complexity. Just do it on purpose.

One warning about the long-cycle side. A slow vertical with a weak product is a career trap, because it takes eighteen months before anybody — including you — can tell whether the problem was you or the pipeline. In a fast vertical you find out in a quarter. Slow markets hide bad situations.

Axis two: how transferable the domain knowledge is

This is the axis people underweight, and it is the one that decides how much leverage you have when you want to leave.

Some domain knowledge is portable across a whole industry. If you spend two years learning how hospitals actually make purchasing decisions — who a CMIO is, why clinical workflow disruption kills deals that look won, how a health system's capital budget cycle works, why the person with the pain has no budget and the person with budget has no pain — that knowledge applies at every healthcare vendor in the market. There are a lot of healthcare vendors. Our healthcare cold call script for getting a CMIO or VP of clinical operations to give you twenty minutes exists because that buyer is genuinely hard to reach, and being one of the people who can reach them is a durable asset.

Security is the same story with a different accent. Learn what a SOC actually does all day, what alert fatigue means in practice, why a director of security cares about mean time to respond, and you can walk into any security vendor and be useful in week one.

Other knowledge is portable but narrow. If you learn one very specific compliance regime that applies to a handful of companies, you have knowledge that is extremely valuable to those companies and worth almost nothing anywhere else. That can still be a great career — being the person who knows the one thing is a fine business — but understand that you are building a specialty, not a passport.

And some knowledge does not transfer at all. Product knowledge of a proprietary platform is not domain knowledge. If everything you learned in two years is how your own product's admin console works, you learned nothing you can sell with somewhere else. I have interviewed people who could describe their product beautifully and could not tell me a single thing about the buyer's business. Those people have a hard time changing jobs.

Here is the test I would apply to any offer. Ask yourself: after two years here, will I know things about my customers' business that are true regardless of who employs me? If the honest answer is no, the compensation had better be exceptional, because that is all you are getting.

Axis three: how brutal the phone actually is

Every vertical is hard on the phone. They are hard in completely different ways, and the difference matters more than people expect, because it determines what you get good at and how long you last.

Security buyers are professionally suspicious. That is the job. A SOC leader's entire discipline is assuming the inbound thing wants something from them. They are also pitched constantly, by a market with more vendors than any human can track. The brutality there is intellectual — you get about one sentence to prove you know what you are talking about, and if you use a word wrong you are done. Not rude. Just done. The cybersecurity cold call script for getting a SOC leader to book twenty-five minutes is built around that reality, because the opener has to earn the next fifteen seconds on credibility alone.

Construction is brutal in a physical way. The person you want is on a job site. There is wind in the microphone. He has four subs waiting on him and a concrete pour that started late. He is not hostile, he is busy, and busy is harder to sell through than hostile because hostile at least means he is listening. The skill you develop is compression — say the thing in one breath, make it about schedule or rework or labor, and get to a yes or a no fast. That is why the construction and trades cold call script for VPs of operations and general superintendents reads so differently from the security one. Same call, different physics.

Freight and logistics is brutal in a third way: exhaustion. Those buyers have heard the pitch. They have heard your specific pitch, from four of your competitors, this month. The brutality is not suspicion or busyness, it is a flat, patient boredom that is very hard to break through with enthusiasm. If you go into freight, you will learn to be interesting, which is a rarer skill than being polished. Our freight and 3PL script for getting past "I've heard this pitch four times" is basically an exercise in that one problem.

Healthcare is brutal because of gatekeeping and pace. Clinical leaders are protected, scheduled to the minute, and genuinely doing more important work than taking your call. You learn patience, respect, and how to be worth someone's twenty minutes.

Pick the flavor of hard you can sustain. I mean that literally. Some people are energized by an intellectual gauntlet and destroyed by boredom. Some are the reverse. You will make thousands of calls into whichever one you choose, and the only wrong answer is the one that makes you quit picking up the phone in month five.

Axis four: where the hiring will be in three years

You are not choosing where the money is today. Today's money is already priced into today's offers. You are choosing where you want to be a known quantity when the market shifts.

I am not going to pretend to forecast this precisely, and you should be suspicious of anybody who hands you a confident number about it. What I will say is that the useful signal is not "which industry is hot," it is "which industry has a structural problem that software has only started to touch." Hot industries attract vendors, and vendors hire reps, but hot also means crowded, and crowded means your calls compete with everyone else's calls.

The places I would look hardest are industries where the buyers are still doing important work in spreadsheets and on the phone, where the workforce is aging out and the knowledge is walking out the door with them, and where a single operational failure costs real money that everyone in the building can name. Those conditions produce vendors for a decade, not a quarter.

Also look at whether the industry has money. This sounds crude but it is the thing that sinks careers. An industry with a genuine pain and no budget will keep you busy and broke. Ask where the budget actually sits, whether it is capital or operating, and whether the person with the pain can reach it.

The compounding advantage nobody talks about

Here is the thing that made me care about this topic in the first place.

A generalist rep calls a director of manufacturing operations and says, "I wanted to see if you're looking at ways to improve efficiency on the floor." A rep with vertical fluency calls the same person and says, "Most of the plants I talk to are running two changeovers a shift and losing the first forty minutes of each one to setup. Is that roughly your situation, or are you cleaner than that?"

The second rep gets a conversation. Not because the script is cleverer, but because the buyer can tell in five seconds that this person has talked to people like them before. You cannot fake that with a discovery framework. It comes from knowing what an outage minute costs a SOC. What a fill rate means to a 3PL and why theirs is the number their biggest customer beats them up about. What claims cycle time means to a payer, and why shaving it is a board-level metric rather than a nice-to-have. What rework means to a superintendent and why it is the word that will make him stop walking.

And it compounds, which is the whole point. Every conversation in a vertical makes the next conversation better, because you accumulate specifics you can trade. You start being able to say "the last three companies your size told me X, is that your read too?" — and that sentence, honestly said, is worth more than any opener I have ever written. A generalist starts over every call. A specialist starts each call further along than the last one.

That compounding is also why switching verticals gets more expensive every year you stay. Not impossible. Expensive. At year one it costs you almost nothing. At year six you are trading a real asset for a fresh start. Which is exactly why the choice deserves more thought than it usually gets.

How to get fluent in ninety days

Assume you have picked. Here is how I would build the fluency, and it is not by reading your own company's collateral.

The first two weeks are vocabulary. Find the industry's trade publications — every vertical has two or three, and they are almost always unglamorous, badly designed, and full of exactly what you need. Read them daily. Write down every term you do not understand and look it up. Your goal is not expertise, it is the ability to hear a word and not flinch. Listen to the industry's podcasts on your commute, the ones made for practitioners, not the vendor-sponsored ones. The practitioner podcasts are where people complain honestly.

Weeks three through six are metrics. Find out what your buyer is measured on. Not what your product improves — what shows up on their quarterly review. Then find out what a good number and a bad number look like, and what the buyer does when the number goes bad. This is where the industry playbooks earn their keep as a starting map: they tell you which metrics that specific buyer actually owns, so you are not guessing. Then go past the map. Ask your own AEs, ask your customer success team what customers complain about, and ask in the calls themselves.

Weeks six through ten, get the org chart in your head. Who reports to whom. Who has budget and who has pain and how far apart those two people sit. Which title is a decision maker in a company of two hundred and a rubber stamp in a company of twenty thousand. Draw it out. Most reps carry a fuzzy version of this and it is why their multi-threading is random.

The last month is talking to actual humans. Ask five customers for twenty minutes, not to sell, to learn. Tell them the truth: you are new to the industry and you want to understand how their day works. Most people say yes to that, because almost nobody asks. Then take the language they use — their actual phrasing, not your marketing team's — and put it in your openers.

Do that and by day ninety you will not be an expert. You will be something more useful for a salesperson: credible. Credible is the bar that gets meetings.

What I would do next

If you are sitting on two offers right now, stop comparing the base salaries for a minute and compare the buyers. Read the cold call script for each vertical and imagine saying those words two hundred times a week. One of them will feel like work you can do and one will feel like a costume. That is real information.

Then go make the calls in a place where a bad one costs you nothing. When I built DrillCall, the thing I wanted was somewhere a rep could dial a difficult buyer from a specific industry over and over, get the objections that vertical actually throws, and find out in a week rather than a year whether that conversation is one they want to have for the next three years. If you are deciding between verticals, that is the test I would run before you sign anything.