// Recruitment Technology, Business Development
Prospect, Lead, Client, Candidate: Sort Your Record Types Before Any BD
Published: 05 November 2026,
8 min to read
The bottom line
Most BD pipelines fail on definitions rather than on effort. When prospect, lead, client and candidate mean different things across a team, the board stops matching reality. People then stop opening it.
Agree one rule: client means signed terms, and everything else is a target. Build the pipeline stages around it.
Why BD pipelines quietly stop being used
A business development pipeline dies in a specific way. Quietly, and without a meeting about it.
The board gets built in a week of enthusiasm. Then one consultant logs every conversation as a lead. Another logs only companies with a live role. A third keeps the real list in a spreadsheet nobody else opens.
The lead vs prospect question sounds like semantics until you try to run a pipeline review on it.
Thirty-seven agencies have raised some version of this with us on recorded calls, and the pattern barely changes. The CRM works. The consultants are working. Nobody trusts the numbers on the board, so it gets updated before the Monday meeting and ignored for the rest of the week.
Lead vs prospect: what is the key difference on a recruitment desk?
A lead is a company or contact you have not tested yet. A prospect is a qualified lead. Direct contact has happened, a clear pain point is confirmed, and you know who holds decision making authority.
Four record types cover almost everything an agency desk touches.
Qualification runs at two levels, and collapsing them is where most boards go wrong. Organization level qualification asks whether the company deserves your time, judged on company size, hiring volume, sector and budget. Stakeholder level qualification asks whether this particular contact can sign anything.
A great company with the wrong contact is still a lead.
- Lead: a company or contact that fits your market but has shown no interest yet. It arrives from job ads, referrals, market mapping or a conference list.
- Prospect: a qualified lead. Someone has spoken with you, a pain point exists, and the stakeholder carries hiring authority or real influence over it.
- Client: signed terms. Not a verbal, not a warm lunch, not a framework agreement someone forwarded in March.
- Candidate: a person record. A marketable candidate can open a deal, but a candidate is never a pipeline stage.
How does a loose qualification process wreck pipeline accuracy?
Records drift upward when the qualification criteria live in people’s heads. A reply to cold outreach becomes a warm lead. A warm lead becomes an opportunity because it has sat there a while and someone feels bad about it.
Then the numbers stop meaning anything.
Two consultants work the same company from different record types. A lapsed client still shows as a client, so nobody makes the BD call. The forecast says 400k and the month closes at 60k.
Agency data says the gap is structural. Only 34.72% of agencies describe their processes as very well defined and consistently followed, in Atlas research covering more than 1,000 agency recruiters. Another 24.66% name a lack of standardized processes as the thing slowing their operation down.
The real damage shows up in behavior. Consultants stop logging activity once logging stops paying them back, and CRM adoption collapses from there. Clear qualification criteria fix more of this than any new feature will.
Which stages should a recruitment BD pipeline actually hold?
Build the distinct stages straight from the definition set and keep the count low. Six stages cover a recruitment desk comfortably.
Two rules keep the board honest. A record moves forward only on evidence, and a record is allowed to move backward.
Lead scoring helps once the stages mean something. Score a pipeline built on inconsistent definitions and you get confident nonsense, delivered in a nice chart.
The pattern holds well outside recruitment. Harvard Business Review found that companies with a formal sales process generate more revenue, and the mechanism in an agency is identical.
Candidate records still earn their place in this. A marketable candidate is a reason to call a target company, which sits at the heart of candidate-led business development. The deal belongs on the board, while the person stays in the database. Run that approach at scale through multi-touch outreach campaigns and the stage definitions become the thing keeping your reporting readable.
- Target: a lead that fits your market. No contact yet, no promises made.
- Engaged: outreach has landed and a discovery call is on the calendar.
- Qualified prospect: pain point confirmed, decision making authority mapped, fees discussed and a next step booked.
- Terms out: a document sits with the client and the decision has a date against it.
- Client: signed contract, live roles, agreed fees and a named owner on the account.
- Lapsed: a former client with no activity for a set period, ready for lead nurturing rather than a cold start.
Can your CRM hold these definitions without adding admin?
It can, provided the system reads record state from activity instead of waiting for a consultant to remember. Definitions survive when keeping them accurate costs nobody anything.
A board that maintains itself is the working version of that idea. The platform built around it is Atlas, an AI-powered recruitment platform that strips admin out of the recruiter’s day with agentic AI. Its business development workspace holds job leads, target clients, marketable candidates and live deals on one Kanban view.
Opportunities are named and renamed from the companies and prospects in each campaign, and the board recognizes which stage a deal belongs in. Scoring weighs interest signals, engagement patterns, momentum and conversion potential, so consultants prioritize leads on evidence rather than on who shouted loudest in the meeting.
Every call, email, note and meeting lands against the right record in the AI-powered CRM. Prospect status then reflects what happened this week.
The payoff shows up in activity. Origio Partners recorded a 125% increase in new client meetings after building their desk on Atlas. Ethea Solutions grew BD outreach by 500% while cutting over 15 hours of admin a week.
Clean record types also make reporting worth reading. Real-time dashboards can show conversion by stage only when every consultant means the same thing by qualified prospect.
Frequently asked questions (FAQs) on lead vs prospect definitions in agency BD
A lead is an unqualified company or contact that fits your market but has shown no interest. A prospect is a qualified lead, which means direct contact has happened and a pain point has been confirmed. The practical test is evidence. A prospect has told you something a lead never has.
When terms are signed. Verbal agreements, warm introductions, nods at a conference and framework paperwork nobody has countersigned all keep the record at prospect. A single rule here keeps forecasts honest across a team of any size. It also removes the most common argument in a pipeline review.
Yes, as an opportunity record rather than as a stage. A strong candidate in a scarce skill set creates a reason to approach a target company. The deal belongs on the board while the person stays in the candidate database. Keeping the record types separate stops the same activity being counted twice.
Five or six is enough for most desks. Every extra stage adds a judgment call and gives records somewhere new to stall. If a consultant has to stop and think about where something goes, the stages are cut too finely.
One person, usually the sales director or the agency owner. Criteria written by committee get reinterpreted by committee, and the definitions drift again within a quarter. Publish them, apply them in every pipeline review, and change them openly when the market moves.
Tie stage movement to evidence rather than to optimism, then run reviews with that evidence on screen. A platform that captures activity automatically settles most of the debate, because the record already shows what happened and when. Multiple stakeholders on a deal make this discipline more valuable, not less.
The definition set that makes a BD pipeline worth opening
Definitions are the cheapest business development improvement available to an agency. Settle the lead vs prospect line first. Client means signed terms, a prospect has been qualified against stated criteria, and everything else is a target you have not tested yet.
Once a team agrees on that, the pipeline has to stay accurate without anyone nursing it. Tracking and scoring every opportunity as the work happens is the capability Atlas puts behind the definition set, so the board updates from real activity rather than from memory.
If your board currently needs a translator, it is worth seeing what a self-maintaining pipeline looks like on your own desk.
