Outbound for recruiters: the two-sided pipeline

Recruitment agencies run two pipelines, not one: clients with roles to fill, and candidates to place in them. The two must roughly balance — roles without candidates burn credibility, candidates without roles burn goodwill — and outbound serves both sides, but in different registers. Client-side outbound runs on hiring signals; candidate-side runs on speed and specificity; and in recruitment, speed is typically worth more than in any other B2B service business, because the first credible call commonly wins the role.

This structural quirk makes recruitment the most distinctive entry on the industry map in Growth Systems by Industry. Every other service firm builds one pipeline; a recruiter builds two and keeps them level.

Why must the two pipelines balance?

Because each side is the other side's product. When a recruiter wins roles faster than they can source candidates, then placements slip, clients quietly add a second agency, and the desk's reputation erodes. When they attract candidates without live roles, then good people register, hear nothing, and are gone — usually placed by whoever called them back. Most agencies drift towards whichever side the founder finds easier and starve the other. A system removes the drift by giving each side its own defined, always-on motion instead of leaving allocation to whoever's inbox is loudest.

What does client-side outbound look like?

Signal-driven, not list-driven. A firm that is hiring is telling you so publicly, which makes recruitment one of the few sub-verticals where the buying trigger is directly observable.

The mechanism we build:

1. Watch the signals. Job posts, new funding, office openings, headcount growth in the niche you serve. Each is a firm with live hiring pain, timestamped.
2. Build the segment. A verified database of hiring managers and HR leads in one niche — we build these as a £950 fixed deliverable — refreshed as signals fire, not compiled once and left to rot.
3. Sequence with discipline. 4 emails over 14 days, referencing the observable fact: the role they've posted, the pattern in their niche, your relevant placements. Sent at 25–40 emails a day per inbox so deliverability holds. The full sending mechanics are in the UK B2B outbound playbook.
4. Route replies to a human, fast. Around 4% positive replies is a realistic outcome for a well-targeted campaign, and in recruitment each one is time-critical: the role may be gone in a fortnight.

The register is commercial and evidence-led — this buyer wants to know you have placed this role type, in this sector, recently.

What does candidate-side outreach look like?

Different register entirely. A candidate is not a buyer evaluating suppliers; they are a person deciding whether you are worth a career conversation. Two things carry the message: specificity — the actual role, the actual salary band, the actual location, and why this person's profile fits, because good candidates ignore "exciting opportunity" mail on sight — and speed, because an in-demand candidate is typically in play for days, not weeks. The system's job is to make first contact specific and near-instant, and to keep past candidates warm with occasional, genuinely relevant roles rather than newsletter noise.

Why does speed matter so unusually much?

Because recruitment is a race with a visible finish line. When a company posts a role, then every agency on that patch sees the same signal within hours, and the first credible call typically wins the mandate. The same race runs on the candidate side against counter-offers and rival agencies. Response-time discipline — the subject of the five-minute rule for inbound leads — applies to most B2B firms as good practice; in recruitment it is closer to the whole game. An agency that replies to a hiring signal in a day is not slightly behind the one that replied in an hour; it is usually out of the race entirely.

How does a system keep both sides warm without the founder living in their inbox?

By assigning the repetition to machinery and reserving the founder for conversations. Signal monitoring runs automatically; sequences send on schedule to both sides; replies are triaged and flagged the moment they land; follow-ups that humans forget — the candidate placed eighteen months ago, the client whose contract cycles annually — fire from the CRM on time, every time. The founder's calendar then contains the two things only a person can do: qualifying a client's role properly, and talking to a candidate about their career.

That is the configuration we install as the Outbound Engine: both motions defined, running weekly, in accounts the agency owns. It is a different shape from the single-pipeline version an agency in another sector needs — compare outbound for marketing agencies to see how much the same machinery changes with the industry.

---

Next step: the Growth System Audit — £450, seven days, credited against any build — maps where your growth system leaks and what to build first.