Building an outbound team, in the right order

The instinct when outbound matters is to hire a salesperson to do it. Done too early, that hire inherits a job with no map and fails at it, and the failure looks like the person when it was really the timing.

Prove it before you hire

Outbound headcount scales a system that works, which assumes you already have product-market fit before outbound. If you do not yet know your ICP, your message and your numbers, there is no system to scale, and a new hire is left to invent one under pressure.

The founder or an early team member should get outbound working first, even roughly: enough replies to prove the message lands, enough conversations to know the ICP is right. That evidence is what a hire steps into.

What must exist before headcount

A hire needs something to be handed. The minimum:

• A validated ICP, so they are not guessing who to contact.
• A message that has earned replies, not a blank page.
• A defined process and the tools to run it.
• Known numbers, kept in one outbound reporting dashboard, so targets are grounded in reality, not hope.

The order of roles

Outbound usually starts with a founder or generalist doing everything, then splits as volume justifies it. The common first specialist hire is an SDR to run top-of-funnel outreach, freeing a closer to work the conversations it produces.

Splitting sourcing, sending and closing across people comes later, when volume makes specialisation pay. Hiring specialists before there is volume just creates idle, expensive roles.

In-house, agency, or both

Building a team is not the only path, and often not the first one. An agency can run outbound while you learn what works, or carry it entirely, which is frequently cheaper and faster than a first hire that has to be recruited, trained and equipped. The trade-offs are laid out in in-house SDR vs. agency and choosing an agency.

Manage what you can measure

Once people are doing outbound, manage the leading activity, not just the closed deals. Contacts reached, replies, conversations booked, the KPIs that let you coach in time rather than discover a bad quarter at the end of it. A team without leading metrics is flying blind between results.

What a first outbound hire really costs

The salary is the visible part. A first SDR also needs data subscriptions, sending infrastructure, a CRM seat, and the tech stack to run sequences, which together commonly add several hundred euro a month before a single email goes out. Then there is ramp: most SDRs need three to four months before they produce at full rate, and someone senior has to spend hours each week coaching them through it.

None of that is an argument against hiring. It is an argument for hiring into a system where the ramp is short because the playbook already exists. The same money spent discovering outbound from scratch buys far fewer meetings than the same money spent scaling a message that already earns replies.

A realistic first-year sequence

1. Months 1 to 3: founder-led proof. One person runs the whole loop, from list to reply to booked call. The goal is signal, not volume: does the ICP respond, does the message land.
2. Months 3 to 6: write it down. Turn what worked into documents a stranger could follow: the ICP definition, the sequences, the reply handling, the benchmarks you expect.
3. Months 6 to 9: first hire or first agency. Hand the documented system to an SDR or an agency, keep the founder on closing, and compare the new numbers to the proven baseline.
4. Months 9 to 12: scale what holds. Add volume, mailboxes and eventually people only where the numbers stay healthy. Use capacity planning to size the infrastructure before the headcount.

Common team-building mistakes

• Hiring a closer to do sourcing. Senior salespeople resent list building and are expensive at it. Match the role to the work that exists today, not the work you hope for.
• One hire, no backup plan. A single SDR who leaves after six months takes the whole channel with them. Documented process is your insurance.
• Targets copied from blog posts. Quotas set from someone else's funnel produce either sandbagging or despair. Set targets from your own proven numbers.
• No dedicated data budget. An SDR without good lists spends half the week researching instead of reaching out. Budget for data as seriously as for salary.
• Scaling the team before the message. Two people sending a message that does not work produce twice the silence at twice the cost.

If you are thinking a good salesperson will figure it out

Some will. Most will not, and the failure is expensive to diagnose because it looks like a hiring mistake rather than a sequencing mistake. A strong SDR dropped into a company with no ICP, no message and no numbers has to do founder work without founder context or founder authority. When they miss quota, the company concludes outbound does not work, fires the person, and loses a year. The cheaper experiment is to prove the channel first with the people who already understand the offer.

Building outbound teams in Europe

European teams face one constraint American playbooks skip: language. An SDR who covers the UK cannot cover the DACH market, and a native-level German speaker who can write and take calls in German is a different, scarcer hire than an English-speaking one. The same applies to French, the Nordics and Central Europe. Teams selling across several European markets either hire per language, which multiplies the headcount question, or work with a partner that already covers the languages. This is a large part of why companies expanding across Europe start with an agency: buying multilingual coverage as a service is faster than recruiting it, and it keeps the language experiment reversible. GDPR adds a second constraint: whoever runs your outbound needs to know the compliance rules, because a hire who learns them by trial and error learns them at your domain's expense.

The pattern that works

Prove it lean, write the process down, then hire to scale a known-good system in the right order. The teams that struggle hired to discover outbound; the teams that scale hired to multiply an outbound they had already made work.