Why your first sales hire is usually the wrong move

27 Oct 2026

There's a moment most growing companies know well. Revenue is too slow, the product works, and someone on the board says: "You need a salesperson."

So you hire one. You find someone with a decent LinkedIn profile, a few years of sales experience on their CV, and enough energy to convince you they'll figure it out. You pay them £60,000 to £80,000, give them a laptop and a target, and wait.

Three months later, they're not hitting the number. Six months later, you're having a hard conversation. A year later, you've spent close to £100,000 (salary, NI, onboarding, lost time) and you're back where you started, except now you're also demoralised about sales.

This is one of the most common and most expensive mistakes growing companies make. The problem is almost never the person. It's that you hired someone to run a system that doesn't exist yet.

What a salesperson actually needs to function

Picture what a good SDR or AE needs to actually do their job. They need a list of people to contact. They need to know which companies fit your ideal customer profile, what their job title should be, and what pain they're likely experiencing. They need a CRM so leads don't get lost between calls. They need a proven sequence of messages. They need a way to track whether any of it is working.

Without those things, what you've hired is a person who will spend their first month building a spreadsheet, their second month sending emails they wrote themselves with no testing behind them, and their third month explaining to you that the pipeline is "building."

It is not building. It is guessing.

The expectation when you hire a salesperson is that they bring the engine with them. The reality, especially in a growing company, is that they're as new to your product, your market, and your positioning as anyone. They need a system to operate, not a blank canvas.

The system that has to come first

Before you can give someone a quota you can hold them to, a few things need to be in place.

You need a clear ICP: which company size, which industry, which geography, which job title, and which problem. "Logistics companies" is not an ICP. "UK logistics firms with 50–200 staff hiring their first SDRs" is an ICP. The difference matters because the second one lets you build a list. The first produces a spreadsheet of 40,000 companies and no idea where to start.

You need a data and enrichment layer. That means knowing where your contacts come from, how their email addresses are found, and how that information is kept current. Tools like Clay, Apollo, and specialist data providers handle this. Without it, your salesperson is manually researching companies one at a time, which is a poor use of what you're paying them for.

You need a sending infrastructure that keeps emails out of spam. This means domain warm-up, secondary sending domains, and technical setup that most salespeople have never had to think about because someone else handled it at their previous company. If you skip this, your open rates will sit around 10%, your reply rates will be near zero, and you'll assume the messaging is the problem when it's the plumbing.

You need tested messaging. Not a single email template written on instinct, but a sequence with a hypothesis behind it, enough volume to measure, and a process for improving it based on actual reply data.

None of this is what a newly hired salesperson is equipped to build from scratch. It's infrastructure work, and it takes longer than most leadership teams expect.

When the hire does make sense

This is not an argument against ever hiring a salesperson. It's an argument about sequencing.

Once you have a working system, the hire makes complete sense. At that point, you're not asking someone to build the machine from scratch. You're giving them a documented process, a live pipeline, and a set of tools that already work. Their job is to operate it, improve it, and close what comes through it. That's a job a good SDR or AE can actually succeed at.

The companies that get this right spend their first revenue investment on building the system, not staffing it. Some hire a GTM agency or specialist to build and prove the process first. Some use a build-operate-transfer model, where the system is built, run until it's generating consistent pipeline, then handed over to an in-house hire with full documentation. Either way, the logic is the same: the hire comes after the proof, not before it.

The build-operate-transfer model: an outside team designs and runs your outbound system until it generates consistent, repeatable pipeline, then hands it over to your in-house hire with full documentation and working infrastructure. You own the process from day one. You just don't have to build it alone.

The test worth running before you post the job

Before hiring, ask yourself: if this person left after 90 days, could someone else pick up exactly where they left off?

If the answer is no, you don't yet have a sales process. You have a plan for one person to figure something out. That's a fragile and expensive way to build a pipeline.

Get the system in place first. The hire will be cheaper, faster to ramp, and far more likely to succeed.

Want to build the system before the hire?

Scale Spark Revenue builds outbound GTM systems for companies scaling their go-to-market: ICP definition, data infrastructure, messaging, and sending setup. We then transfer full ownership to your team.