The instinct is understandable. The new market needs revenue, salespeople bring revenue, so the first hire for the new market is a salesperson. An SDR usually follows: a junior hire, working in service of that salesperson to keep their pipeline full.
I have watched this movie several times, from inside companies I sold for and from alongside companies I now work with. It usually ends the same way: a frustrated hire, a quiet couple of quarters, and a board update concluding that "the market is harder than expected." The market may genuinely be hard. But the hire did not fail because the market is hard. It failed because it came first, when it should have come second.
This piece makes the sequencing argument in full: what your first salesperson actually needs to succeed, why the same logic applies to the SDR who follows, and to your first marketer and RevOps hire, and what the work before those hires looks like.
What a salesperson walks into in a new market
A salesperson is hired to close. Closing multiplies what already exists. Look at what exists on day one in a new market:
- A playbook that says who to target and what to say: does not exist yet.
- Warm accounts that have heard of you: none.
- Messaging tested against how buyers in this market actually describe the problem: none.
- A way to tell whether silence means wrong message, wrong segment, or wrong market: none.
Drop a good closer into that vacuum and you get an expensive prospector: someone paid to close, spending their quarters doing top-of-funnel work they were not hired for and often do not enjoy. The good ones leave.
And when it does not work, you cannot tell whether you learned "this market is bad" or "this approach was bad." You paid for a year of activity and received no decision-grade evidence. That is the expensive part.
The same logic, three more times
The salesperson is just the most common first hire. The argument repeats for each of the other three.
An SDR is the classic second hire, junior and brought in to feed the salesperson's pipeline. An SDR is an execution role too, and hired before a playbook exists they do not execute your market entry strategy. They improvise it. Which means you have delegated your market entry strategy to your most junior commercial hire, in the market you understand least, with the least feedback to correct them. That is not a headcount decision. That is a strategy decision made by accident.
A marketer needs message-market fit to amplify. In a new market the messaging is still a translation of what worked at home, untested against local objections, local competitors, and local pain language. Amplifying an untested message does not validate it. It just makes the guess louder.
A RevOps hire needs data. Pipelines, conversion patterns, cycle lengths, segment behavior. In a greenfield market there is nothing to operate on yet. You are asking someone to instrument an engine that has not been built.
Four roles, one pattern: each multiplies something that does not exist yet in the new market. The missing ingredient is the same in all four cases: first traction and proof.
The gap is a research function, not a junior role
So what fills the gap between "we want this market" and "this market is ready for hires"?
Research, in the practical sense. The first 30 to 90 days of a new-market motion are about producing evidence: which segment responds, what the real pain language is, which message survives contact with buyers, whether the beachhead deserves more investment at all.
This is senior work. Not because the tasks are harder than SDR tasks, but because it is judgment work: choosing the narrowest beachhead worth winning, writing a positioning bet, reading ambiguous replies honestly, and killing hypotheses you were fond of. A junior hire cannot carry those calls, and should not be asked to.
What "before" looks like in practice
Concretely, the pre-hire work has four parts. They are sequential, and none of them requires a headcount.
Write the beachhead hypothesis down
Not "we are expanding into the Nordics." Rather: which 100 to 200 accounts, in which segment, with which pain, and what evidence makes you believe it. Writing it down matters because a hypothesis you cannot state is one you cannot test, and because this document is the first piece of commercial IP your future team inherits.
Build the account list from signals, not directories
Firmographics tell you who could buy: industry, size, geography. Signals tell you who might buy now: hiring moves, expansion announcements, new leadership, regulatory pressure. A list built on timing evidence produces conversations a static list never will, and it keeps the test honest. If the best-timed accounts in the market do not respond, that is real information.
Run small batches and keep score in writing
50 to 150 accounts per iteration. Small enough that one result is readable; large enough to matter. Every message is a test of the positioning bet. Every week the replies, the silences, and the meetings get read against the hypothesis, and the next batch targets what the last one taught. Keep the running record in writing. Six months from now, that learning record will be worth more than any individual meeting it produced.
Make the call: go, pivot, or stop
The point of the work is a confident decision backed by evidence. Go means the beachhead responds and deserves investment, possibly including that first sales hire. Pivot means the market is interesting but the segment or message was wrong. Stop means the evidence says this market does not want what you sell, at least not now, and you just saved yourself a year of fixed cost proving it the expensive way. A confident no-go is a paid-for outcome. It only feels like failure if you mistook the goal for meetings.
When the sales hire is exactly right
None of this is an argument against salespeople, or against the SDR who follows them. It is an argument about order.
There is a moment when the hire stops being a gamble: a validated playbook exists, a warm account base means the first conversations are not cold, the messaging has survived real objections, and there is data to manage against. Hired into that, a salesperson closes instead of prospecting, and the SDR you add later executes a motion instead of improvising one. Both ramp faster, perform better, and stay longer, because they were set up to execute rather than to improvise.
Everything the pre-hire work produced becomes their starting inventory: the playbook, the engaged accounts with interaction history, the learning record of what was tried and why. Your first hire starts with a map instead of a blank one. That handover is the whole point.
The sequencing rule
Validation before execution. Proof before headcount.
If you can write the playbook your first hires would run, the market may be ready for them. If you cannot write it yet, it is too early, and no quality of candidate fixes that. The honest move is to produce the proof first, with a system small enough to kill if the evidence says so.
That pre-hire system is the work I do. If you are weighing this decision for your own market entry, the methodology page walks through what an operator-led validation phase looks like, end to end.