Recruitment business development plan for a desk with no clients

Why most recruitment business development plans fail before week three

A workable recruitment business development strategy for a desk with no clients runs in three stages across 90 days. Weeks one and two define a patch narrow enough to actually work. Weeks three to six open contact at a volume you can sustain without burning out. Weeks seven to twelve turn first conversations into briefs and start compounding whatever is working.

The single most common failure happens before any of that: starting too broad. A new desk picks "manufacturing across Victoria" or "healthcare in Auckland" because it sounds like a big enough market to guarantee results. It isn't a strategy, it's a postcode with a job title attached. Effort spread across too many industries and too much geography never compounds in one place, so by week eight you've had forty scattered conversations and nothing that looks like a pattern you can repeat.

Business development in recruitment only works when the same person can hear about the same kind of role from the same small set of companies often enough to become the person they think of first. That requires a patch small enough to dominate.

Weeks one and two: define a patch you can actually work

A patch is workable when it passes four tests. First, it's an industry you can actually place into, meaning you have or can quickly build a candidate pool for the roles that industry hires. Second, it's a geography you can service inside a working day, so a site visit or an interview debrief doesn't cost you half your calling time. Third, it sits in a company size band where your fee clears a sensible minimum, since a $4,000 placement fee on a $45,000 role eats your margin before you've covered the hours. Fourth, it has enough companies in it to sustain a full year of calling without you running out of names by month four.

That fourth test is the one new desks skip, and it's the one you can actually calculate rather than guess at. Here's a worked example, with the assumptions stated alongside the number because this is arithmetic, not a measured fact. If a consultant can realistically hold 40 genuine touches a week once calls, emails and social messages are combined, and each company needs touching roughly every three weeks to stay warm without becoming noise, the rotation alone needs around 120 companies in active circulation. Add a buffer for companies that go quiet, get placed, or get parked for a quarter, and a patch that can sustain a year of this needs closer to 180 to 220 companies. If your patch has 60 companies in it, you will run out of fresh names before the quarter ends, no matter how good your calls are.

Building the call list: the recruiter's own research, not a shortcut

Once the patch is defined, the list gets built from a few plain sources: company registers (ASIC's business register in Australia, the Companies Office in New Zealand), the relevant industry association's member directory, and the live job ads inside that patch, which tell you who is actually hiring right now. None of this is exotic. It's the same research every agency BD has always done, just pointed at a smaller, better-chosen target.

Keep the list in one place from day one, a spreadsheet or a CRM, with a status field on every row: cold, contacted, conversation held, brief taken, placed, parked. Without that field you can't tell the difference between a list you're working and a list you're hoarding.

The thing that breaks a call list fastest is mixing it with candidate sourcing. A spreadsheet that has company rows and candidate rows in the same tabs, with the same columns doing double duty, stops being useful for either job within a few weeks. Company BD needs a status and a next-touch date. Candidate tracking needs availability and skills. Trying to run both through one undifferentiated sheet is how good lists turn into dead ones. When you are working from a live job ad, it's worth being able to see who actually owns the hire rather than guessing from the ad's contact line, which is very often HR, not the hiring manager.

Weeks three to six: the first contact cycle and the touch sequence

This is where the recruitment business development strategy either becomes a habit or stays a plan on paper. A realistic weekly rhythm for a solo desk is around 15 to 20 new companies added to the patch and roughly 40 touches made across the existing list, split between calls and the follow-ups that come off them.

A touch is not a repeat of the same pitch. It's a call, then a specific follow-up tied to something from that call, a note about a project they mentioned, a connection request with a one-line reference to the conversation, a short email when a call isn't answered. The honest point most plans skip: a call answered on the first attempt is the exception, not the rule, and most agencies give up at touch two because that's when it starts feeling like rejection rather than process.

A sequence worth running before writing a company off looks like this across three to four weeks:

• Call one, no answer, leave a specific voicemail if you leave one at all
• A short follow-up email or message within two days, not a repeat pitch
• Call two the following week, referencing the first attempt
• A third touch, often a message rather than a call, two weeks later
• A final call around week four before the company is parked, not deleted

Parking matters as much as the sequence. A company that doesn't answer in week one may be hiring in week fourteen.

Weeks seven to twelve: turning a first conversation into a brief

A conversation turns into a brief when you ask about their next hire, not when you pitch the agency. "What's the next role you're likely to need filled" gets further than any description of your service offering, because it treats the hiring manager as someone with a problem rather than someone you're selling to.

A flat no at this stage should be parked, not written off. Hiring need is cyclical and a no in March is often just a no for March. A sensible re-contact interval is around 90 days, long enough that you're not noise, short enough that you're there when the need resurfaces. Staying in touch between those points means short, relevant notes, not a generic newsletter.

The candidate channel: slower to build, harder to replace

Any recruitment business development strategy relies on company BD for pipeline speed, but candidate relationships are the asset a competitor can't copy by buying a list. A candidate you place well becomes a referral source for other candidates and a legitimate reason to call their employer again eighteen months later when that person has moved up and is doing the hiring themselves.

The mechanism, not the metaphor: every call that produces a strong candidate conversation, even one with no live role attached, gets logged with enough detail to be useful later, not just a CV on file. In the first 90 days, this runs alongside company BD rather than against it. A practical split is to let candidate conversations happen as a byproduct of the calls you're already making, asking a hiring manager who else they know who's good, rather than running a separate sourcing campaign that competes for the same hours.

The metrics that tell you it's working, and the ones that don't

Calls made is a vanity number. You can make forty calls a day and build nothing if none of them go anywhere. Three metrics actually tell you whether a recruitment business development strategy is working: conversations held, briefs taken, and companies that moved a pipeline stage in the week.

Track these weekly on the same spreadsheet that holds your patch, no new software required at this stage. A CRM, or how Rectask finds the hiring manager on new job ads as they appear, earns its place once a spreadsheet genuinely can't keep up, typically once a patch passes a couple of hundred companies or more than one consultant is working the same list. Before that point, a tool doesn't fix a volume problem, it just gives you a more expensive spreadsheet.

What to cut from your recruitment business development strategy when the quarter is going badly

When a quarter is going badly, the honest move is to cut breadth, not effort. Narrow the patch further, drop an industry you were chasing on the side, rather than trying to out-work a patch that was too wide to begin with. A smaller, denser patch worked properly beats a wide one worked thinly every time, because the touch sequence above only works if you can actually sustain it on every company in the list.

And sometimes the answer is to wait rather than buy a tool. If the real problem is that you haven't made enough calls this month, a lead list or a database subscription won't fix that. The gap is activity, not information, and no amount of Rectask compared with Lusha and ZoomInfo research will close an activity gap. Buy the tool once your bottleneck is finding who to call fast enough to keep up with a list you're already working hard on, not before.

Common questions

How many companies should a new recruitment desk contact each week?

Enough to add new ones faster than you exhaust touches on existing ones, which in practice means sizing weekly additions against your patch total so you don't run out of companies before the quarter ends.

How many touches before giving up on a company?

More than two. Most agencies stop too early; a workable sequence runs several contacts across a few weeks before a company is parked, not dropped.

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

Lead generation builds the list of companies worth calling; business development is the calling, the conversation and the follow up that turns a name on that list into a brief.

Should a desk with no clients focus on companies or candidates first?

Companies first for pipeline speed, but start the candidate channel in parallel from week one, since it is slower to build and becomes the harder asset to replace.

A recruitment business development strategy like this lives or dies on one thing: knowing who to call before the agency down the road does. That's the part Rectask handles, surfacing the person who owns each new hire within 30 minutes of the role going live, so the weeks above go into calling rather than guessing. See the pricing and enrichment credits if you want to know what that costs once your patch is big enough to need it.