Recruitment business development as a system, not a personality

Recruitment business development is not a confidence problem. It is a sequencing problem. A call only lands when three things line up: a live vacancy, the person who actually owns that hire, and timing that hasn't already slipped past the point where the role is spoken for. Most advice on this topic talks about tone, persistence and scripts, as if the missing ingredient is nerve. It isn't. Get the sequence right and an average script on a live ad beats a great script on a dead one, every time.

This piece sets out that sequence as a system: how to judge whether an ad is still worth a call, how to find the person who owns the hire instead of the one who merely answers the phone, how to tell a direct employer ad from an agency repost, and what a week actually costs when you add up the hours. The arithmetic at the end is the part most BD advice skips.

Recruitment business development is a sequencing problem, not an effort problem

Three variables decide whether a BD call turns into anything: a vacancy that is genuinely still open, a contact who has the authority to say yes to a candidate, and a window where the hiring manager hasn't already moved on. Miss any one of them and effort doesn't fix it. Calling harder into a role that closed last week, or calling confidently into HR instead of the hiring manager, just produces more calls with the same zero outcome.

This is why two consultants with identical scripts get different results. The difference usually isn't delivery. It's that one of them is working ads that are three days old to the person who owns the brief, and the other is working ads that are eleven days old to whoever picked up the switchboard.

A job ad is a dated signal, and it decays fast

A job ad is a timestamp, not a standing invitation. The moment it's live is the moment a hiring manager has a problem and hasn't yet solved it. Every day after that, the odds rise that they've briefed an agency, shortlisted internally, or handed the search to someone else entirely.

As a practical cutoff, treat the first 48 hours as the window where a cold call reads as helpful rather than late. By day five or six, most live roles have already had movement, either a shortlist forming or an agency engaged, and a BD call starts sounding like you're behind the market rather than ahead of it. A reposted ad resets that clock, which is a separate signal worth checking before you call: reposting usually means the first run didn't produce a hire, which is a different conversation to open with than a brand-new ad.

Calling the wrong person wastes the call before it starts

HR and reception answer the phone. They rarely own the hire. The person who owns it is the one who will manage the new starter, who wrote the brief in their head before anyone wrote the ad, and who feels the gap every day it stays open: the site manager on a construction vacancy, the director of nursing on a registered nurse role, the branch manager on a payroll officer ad, the practice principal on an accounts role.

Getting routed to the wrong person doesn't just fail to help. It spends the one shot the live ad gave you. Once you've been filtered to HR and given the generic "we'll pass it on" response, you can't credibly call back in three days and ask for the hiring manager directly, you've already been filed as a cold call.

Agency ad or direct employer: the tells nobody writes down

Agency-posted ads rarely say "posted by a recruitment agency." They say "our client," which is the single biggest tell, since no direct employer describes itself as someone's client. A missing company logo on an ad that otherwise looks professional is the second tell, because direct employers almost always brand their own listing.

Beyond phrasing, check these before you call:

• The application email domain is generic (a Gmail or Outlook address) rather than the company's own domain, which direct employer ads almost always use.
• The exact same ad text appears in the listings within the same week under different poster names, a pattern agencies produce when they cross-post the same brief.
• The job title is generic and the location is a broad region rather than a specific suburb or site, a pattern agencies use when writing one ad to cover several client openings at once.

Skip the agency ads. You're not calling to compete with another agency for the same brief, you're calling the employer who hasn't engaged one yet.

The arithmetic: where a $90,000 recruitment business development week actually goes

Here's a worked example, with the assumptions stated so you can swap in your own numbers. Take a BD consultant on $90,000 AUD base. Add 25% for super, leave and overhead, which gives a loaded cost of roughly $112,500 a year, or about $54 an hour across a 40-hour, 52-week year.

Now spend that week the way most desks actually spend it: 8 hours scanning the listings for new ads in the target industries, 6 hours working out which of those ads are agency reposts versus direct employers, 8 hours finding the right name on a professional network once the ad looks genuine, and 4 hours guessing email formats and absorbing the bounces. That's 26 hours gone before a single genuine conversation happens, leaving 14 hours for the actual calling, and at realistic connect rates on cold outbound, that usually yields somewhere around four to six real first conversations with a confirmed hiring manager on a confirmed live role.

Four to six genuine conversations from a $112,500-a-year hire is the maths worth sitting with, because the problem isn't the calling. It's everything that happens before the phone is picked up.

The bottleneck is list building, not calling

The scarce resource on a recruitment desk isn't dial time or nerve. It's a correctly targeted, verified, still-live contact to call. Everything in the arithmetic above that isn't the final 14 hours is list building: finding the ad, checking it's genuine, finding the name, guessing the email.

That's the part worth buying back, because the hours spent on it don't produce revenue, they produce the right to make the call that might. How Rectask finds the hiring manager is built around exactly that: it picks up new employer job ads every 30 minutes and finds the hiring team, drops the agency ads and duplicates, and ranks the people most likely to own each hire with a one-line reason, hiring manager first. Emails are verified and revealed for a credit rather than guessed and bounced. Against the arithmetic above, a plan starting at US$349 a month for 2,000 credits is worth weighing against what 26 hours a week of a $54-an-hour consultant's time actually costs, laid out on the pricing and enrichment credits page.

Selling recruitment services once you're through to the right person

Everything above gets you to one thing: a live, correctly targeted first conversation with the person who owns the hire. It deliberately doesn't write the pitch for that conversation. What you say once the hiring manager picks up, how you open, how you handle "we're already using an agency," how you ask for the brief, that's still the consultant's job and no system replaces it.

If your niche genuinely produces two or three live ads a week across the whole market, speed to the brief isn't your constraint, volume is, and no amount of faster targeting manufactures ads that don't exist. In that situation, the better use of the week is working existing client relationships and referral networks, not optimising the hunt for a handful of ads. If you're weighing tools generally rather than building your own list by hand, Where Rectask fits next to Lusha, Apollo and ZoomInfo covers where a job-ad-triggered approach differs from a database you search.

A weekly operating rhythm, with numbers

A rhythm only means something with numbers attached, so here's one worked version with its assumptions stated. Assume a desk targeting 15 new companies a week, drawn from live, direct-employer ads less than three days old. Each contact gets three touches, a call, a follow-up call two days later, and one email, spread across ten business days.

If there's no response after the third touch, the contact gets dropped rather than chased further, and the slot is replaced by a fresh ad the following week. Chasing past three touches on a cold outbound contact rarely changes the outcome and it crowds out the time that should go to the next new ad. The tradeoff is real: some of those dropped contacts would have converted on a fourth or fifth touch, and this rhythm accepts losing them in exchange for keeping the pipeline running on genuinely live signals instead of stale ones.

Common questions

What's the real difference between recruitment business development and recruitment lead generation?

Lead generation is building the list of companies and contacts. Business development is what you do once you're on the phone with the right one. Most people lose the day in the first part and blame the second.

How do I tell if a job ad is from a direct employer or another agency?

Check for "our client" phrasing, no company logo, a generic email domain on the application, and whether the same ad text is running elsewhere under a different poster name.

How many new companies should a recruitment consultant approach each week?

It depends on desk and market, but the number only means something alongside how many touches each contact gets and the rule for when to drop one, covered above in the weekly rhythm.

Does recruitment lead generation software replace the BD call?

No. It replaces the hours spent building and checking the list. The call, and the pitch on it, is still the consultant's job.

Treating recruitment business development as a system rather than a trait doesn't remove the phone call, it just stops spending the week on everything that happens before it. If you want to see the targeting part working on real ads before changing anything else, the plan finder works out what it's worth to your desk, and a $49 trial runs it on your own markets.