# Building a Recruitment BD Team: Roles, Onboarding and Pay

> A recruitment BD team works best when roles are clearly split: a business developer or appointment setter opens doors and books meetings, consultants run the meetings and deliver. Hire for phone stamina and coachability, onboard with a fixed script and daily call blocks, and tie variable pay to meetings that actually take place and clients that actually sign.

Source: https://hiring-intelligence.io/en/blog/building-a-recruitment-bd-team
Author: Philipp Kaming · Published: 2026-11-08

Most recruitment agencies hit the same ceiling. The founder wins the clients, the consultants fill the roles, and as soon as the founder gets busy with delivery, new business dries up. A few months later the pipeline is empty and everyone is back on the phone in a panic.

The fix is not "everyone does a bit more BD". It is a business development function that keeps running whether the desks are full or not. That means deciding who opens doors, who closes, how you train them and how you pay them.

This guide covers the roles, the order in which to hire, a practical onboarding plan and the logic behind BD pay, without pretending there is one magic number.

## Do you need a separate BD role or should consultants do their own BD?

There are two basic models, and most agencies end up with a mix.

| Model | How it works | Works well when | Watch out for |
|---|---|---|---|
| Consultants do full-cycle BD (360) | Each consultant finds clients and fills roles | Small team, deep niche, consultants enjoy selling | BD stops whenever delivery gets busy |
| Dedicated BD role | A business developer or setter books meetings, consultants take over | You need steady meeting flow, consultants are stretched | Handover gaps, BD books meetings nobody wants |

The question is not which model is "right". It is where your bottleneck sits. If your consultants have more roles than they can fill, a dedicated BD person adds even more load. If your consultants are half-empty and hate the phone, a BD role is usually the fastest lever. For a deeper comparison, see [360 vs. split desk recruitment](/en/blog/360-vs-split-desk-recruitment).

## What does a recruitment business developer actually do?

Keep the role narrow. The clearer the job, the faster someone gets good at it.

**The BD role (setter):**

- Works through a daily list of companies with live vacancies.
- Gets past the switchboard and reaches the decision maker.
- Qualifies the need: which role, since when, by when, how many.
- Books a meeting with a consultant, ideally for tomorrow or the day after.
- Logs every call, outcome and note in the CRM.

**The consultant:**

- Runs the meeting and agrees terms.
- Takes the job brief.
- Delivers candidates and manages the process.
- Grows the account once the first placement is made.

The BD role does not negotiate fees or promise candidates. Its job ends when a qualified meeting is in the diary and the consultant has the notes.

## Who should you hire first?

For a first BD hire, look for behaviour, not a polished CV:

- **Phone stamina.** They will spend hours a day on the phone. Ask how they handled a job where rejection was normal: sales, hospitality, call centres, fundraising.
- **Coachability.** Give them a short script in the interview, let them try it, give one piece of feedback, and let them try again. The improvement between attempts tells you more than anything else.
- **Discipline.** Can they work a list in order, log notes properly and show up for the call block at the same time every day?
- **Curiosity about the niche.** They do not need to know your market, but they should want to understand what a site manager in Dallas or a ward manager in Manchester actually does.

Recruitment experience is a plus, not a requirement. Someone who has sold anything on the phone often learns faster than a former consultant who only ever did delivery.

## How do you onboard a new BD hire?

A new BD person needs a fixed routine, a script they know by heart and fast feedback. A simple four-week plan:

| Week | Focus | What good looks like |
|---|---|---|
| 1 | Product, niche, CRM, listening | Can explain your specialism in one sentence, knows the CRM stages, has listened to calls |
| 2 | Script and first call blocks | Uses the opener and the yes-question naturally, logs every call |
| 3 | Objections and booking | Handles the common objections, books the first meetings |
| 4 | Independent list work | Prepares their own list the day before, runs full call blocks without support |

### The script they learn first

Give them one opener and make them master it before you change anything. Built around the live vacancy, it sounds like this:

> "Hi {first name}, it's {name} from {agency}. I'm calling about the {role} you're hiring for in {city}. That's still open, right?"

Then one or two questions about the need:

> "I take it you'd like to fill it soon, right? When does the person need to start?"

Then the pitch as a yes-question:

> "Okay, then it's good I called. We specialise in {specialism}. Quick question: if we put really strong, qualified candidates from your area on your desk, would you want to meet them, even if they come through an agency?"

And straight into the diary:

> "Then let's look at the diary. How does tomorrow look for you? Or does later this afternoon work?"

The full structure, including objections, is in our [recruitment cold calling script](/en/blog/recruitment-cold-calling-script).

### Daily routine

- **Day before:** list prepared, contacts checked, vacancies still live.
- **Morning:** first call block, no email, no meetings.
- **Midday:** short review with the team lead: two calls listened back, one thing to change.
- **Afternoon:** second call block, call-backs at the agreed times.
- **End of day:** CRM complete, meetings handed over with notes.

## How should you pay a recruitment BD team?

There is no single right figure, and market rates differ a lot between London, Leeds, Chicago and Dallas. What you can get right is the logic. For a BD role, a fixed base salary plus a variable component is the obvious starting point. The questions are what the variable part is tied to and when it is paid.

### What to tie variable pay to

| Trigger | Upside | Risk |
|---|---|---|
| Meetings booked | Simple, immediate | Rewards quantity, weak or unwanted meetings |
| Meetings that took place | Rewards real appointments | Setter has limited control over no-shows |
| Qualified meetings (agreed criteria) | Focus on quality | Needs clear, written criteria |
| New client signed terms | Rewards outcomes | Long gap between effort and reward |
| Share of first placement fee | Aligns BD with revenue | Very delayed, depends on delivery |

A balanced setup combines two triggers: a smaller amount for every meeting that actually takes place with a decision maker, and a bonus when that client signs terms or the first placement invoices. That keeps the setter focused on quality without making them wait months for every reward.

### Rules that prevent arguments later

- **Define "qualified" in writing.** For example: decision maker present, live vacancy, role within your niche, company within your size range.
- **Say what happens with no-shows.** Paid only once the meeting is rescheduled and held, or not at all.
- **Fix the handover rule.** Who gets credit if the client was already in the CRM? Write it down before the first dispute.
- **Pay on a fixed rhythm.** Monthly, based on CRM data both sides can see.
- **Review after a quarter.** Look at whether the pay plan drives the behaviour you want, then adjust.

Make sure any variable pay scheme is set up properly in the employment contract and complies with local employment law; take advice on that rather than improvising.

## Which numbers should a BD team track?

Track activity and outcomes separately, so you can see where the funnel leaks:

- Dials and conversations with decision makers.
- Meetings booked and meetings held.
- Meetings that turned into terms agreed.
- New clients with a first role on.

Set targets from your own data after the first month, not from someone else's benchmark. More on this in [recruitment business development KPIs](/en/blog/recruitment-business-development-kpis).

## Giving the team the right tools

A BD team is only as good as the list it calls and the system it works in. Two things make the biggest difference: a fresh daily supply of companies with live vacancies, and a CRM that tells each person who to call next.

[LeadFlow](/en/services/leadflow) delivers companies that are hiring in your niche, with the decision maker, straight into your CRM every day. [SalesPower](/en/services/salespower) sets up Close for agencies, with a dialler, pipeline stages and automations, so a new BD hire can start calling in the right order from day one.

## Key takeaways

- Decide where your bottleneck is before choosing between 360 and a dedicated BD role.
- Keep the BD role narrow: reach the decision maker, qualify, book the meeting, log everything.
- Hire for phone stamina, coachability and discipline rather than recruitment experience.
- Onboard with one script, fixed daily call blocks and daily feedback.
- Tie variable pay to meetings that take place and clients that sign, and write the rules down.
- Set targets from your own data, not from someone else's benchmark.

## FAQ

### What is the difference between a business developer and a recruitment consultant?
A business developer or appointment setter focuses on opening doors: reaching decision makers, qualifying the need and booking meetings. A recruitment consultant runs those meetings, agrees terms and delivers candidates. In 360 models one person does both.

### When should a recruitment agency hire a dedicated BD person?
Usually when consultants have capacity for more roles but are not generating enough new clients themselves, or when BD stops every time delivery gets busy. If consultants are already overloaded with roles, more meetings will not help until delivery capacity grows.

### How do you structure commission for a recruitment business developer?
A base salary plus a variable part is the usual starting point. One sensible logic is a smaller amount per meeting that actually takes place with a qualified decision maker, plus a bonus once the client signs terms or the first placement is invoiced. Write down what counts as qualified and how no-shows are handled.

### How long does it take to onboard a recruitment BD hire?
It depends on the person and your niche, but a structured plan helps: a first week on product, niche and CRM, then script practice, objection handling and independent list work. Daily feedback on recorded or listened-in calls speeds this up considerably.