Hiring Signals as a BD Trigger: How Recruiters Turn Open Roles Into Pipeline

The Best BD Question Isn't "Who Should I Contact?" - It's "Who's Hiring Right Now?"

Most recruitment agency BD looks the same: a target list of dream logos, a sequence in a sales tool, and a quiet pipeline that takes months to warm up. The agencies that consistently win mandates do something different - they let *timing* drive the list, not the other way around.

That timing signal is simple: a company is actively hiring for a role you place. Everything else - the personalisation, the channel, the message - is downstream of that one fact.

This post is a practical walkthrough of how to build BD around hiring signals: what counts as a signal, how to read them, and how to turn them into booked calls without burning your sender reputation.

What Counts as a Hiring Signal (And What Doesn't)

Not every "trigger" is worth acting on. Be ruthless about this - most lists you can buy or scrape are full of noise.

Strong signals (act within days):

• A new job posting for a role in your niche, live on LinkedIn / company careers page
• Multiple open roles in the same function (Engineering hiring 4 backend devs → real scaling pressure)
• A senior hire who will need to build a team (new VP Engineering, new Head of Sales)
• Funding round announced in the last 30 days
• A re-posted role that has been open 30+ days (the in-house team is stuck)

Weak signals (skip unless paired with a strong one):

• "We're hiring!" social posts with no specific role
• General growth news from 6+ months ago
• A logo on a "fastest-growing companies" list
• LinkedIn intent data with no underlying role

The rule: if you can't name the specific role and the team it sits in, it's not a signal you can sell against.

Why Open Roles Beat Every Other Trigger for Agencies

For recruitment specifically, an open job posting is the highest-quality BD signal that exists. Here's why:

• The pain is current. Someone is sitting in a Monday standup explaining why the role still isn't filled.
• Budget already exists. A posted role means a sign-off has happened. You're not selling the *need* to hire - only the *better way* to hire.
• The hiring manager is identifiable. Job descriptions tell you the reporting line, the team, the seniority. You can find the right inbox.
• Competition is bounded. Even if other agencies are reaching out, the in-house TA team is usually the bottleneck - not other vendors.

Compare this to a "scaling SaaS company" trigger. Without an open role, you're guessing at what they need and competing with every BD person in the agency world.

The Operating Model: Signal → Match → Message → Send

Build the workflow around four stages. Each one has a clear input and output.

1. Signal capture

Pull open roles daily from the boards where your niche posts: LinkedIn, the company careers site, vertical boards (Seek for AU/NZ, jobs.ch for Switzerland, etc.). Don't rely on a single source - LinkedIn alone misses ~30% of postings in most niches.

Filter aggressively at this stage:

• Roles you actually place (title, seniority, location)
• Companies in your ICP (size, industry, geography)
• Posted in the last 7 days (older = colder, and the in-house team has had time to make progress)

2. Hiring manager match

For each role, identify the *one* person you'd want on a call. That's almost never the recruiter who posted it. It's the function head one level above - VP Engineering for an engineering role, Head of Sales for an AE role.

Read the job description for the reporting line. If it says "reports to the VP of Data", you have your target. If it doesn't, walk up the org chart on LinkedIn until you find the most senior person in that function at that company.

3. Message

The single biggest mistake recruiters make on outbound: writing a generic "saw you're hiring" email. The hiring manager has had ten of those this month.

What works instead:

• Reference the specific role and one detail from the JD ("the Snowflake + dbt requirement on your Senior Data Engineer role")
• One concrete piece of evidence you can help (a recent placement in the same stack, a shortlist you could send by Thursday)
• A small, specific ask - not "interested in a call?", but "want me to send three pre-qualified profiles for the Senior Data Engineer role by Friday?"

Keep it under 90 words. Send from your own mailbox, not a marketing domain.

4. Send and track

Send during business hours in the recipient's timezone. Don't send Monday before 10am or Friday after 3pm. Track opens and replies, but don't optimise for opens - optimise for replies and booked calls.

The Cadence: How Often to Re-engage

A signal-based pipeline gets out of date fast. Two rules:

• Re-check open roles weekly. A role that's still open after 21 days is a much stronger signal than one posted three days ago - the in-house team has had time to fail.
• Don't reach out to the same hiring manager more than twice per quarter unless the role is genuinely new. Recruiter inbox fatigue is real.

A reasonable rhythm for one recruiter: 20–30 fresh hiring-signal leads per week, two-touch sequence, then move on. That's around 50–60 sends per week - small enough to keep each one personal, large enough to fill a pipeline.

What to Measure

Vanity metrics will lie to you here. The numbers that matter:

• Reply rate from hiring managers (not from recruiters or auto-replies). Healthy benchmark: 8–15%.
• Meeting-to-mandate conversion within 30 days. If you're booking calls but not winning mandates, the signal is fine - your pitch isn't.
• Time from signal to first send. Under 48 hours is the goal. Past a week and the in-house team has often made progress.

If reply rates drop below 5%, the problem is almost always one of: stale signals, wrong hiring manager, or a generic message. In that order.

The Build vs Buy Decision

You can run all of this manually - scraping job boards, matching hiring managers, writing emails. Plenty of recruiters do. It's roughly 8–12 hours of focused work per week for one recruiter's pipeline.

The reason most agencies eventually move to a tool: not because the work is hard, but because *it doesn't scale linearly with revenue*. Your best biller doesn't want to spend Tuesday mornings doing data entry on a LinkedIn search.

Leedo is built specifically for this workflow - daily hiring-signal scraping, hiring manager identification, and a drafted recruiter-style first message per lead. If you'd rather try the workflow than build it, start with the demo - the first leads land within a day.

The Bottom Line

Hiring signals beat dream-account lists for one reason: they're time-bounded. A company that posted a Senior Backend Engineer role on Tuesday has a problem on Tuesday. Reach them by Thursday with something specific, and you're competing against a stretched in-house team - not against the rest of the agency market.

Build the workflow around the signal, keep the messages short and specific, and measure replies - not sends.