CRM in recruitment: candidate and client pipelines

Recruitment is the only common B2B service business that runs two pipelines at once: candidates on one side, client vacancies on the other, and revenue only when a specific pair meets. A recruitment CRM therefore has to model both sides with their own stages and their own follow-up rules — and most agencies only build one side properly, because the ATS handles candidates and the client side lives in consultants' heads. That gap is where placements, and eventually the business's sale value, quietly leak.

How recruitment compares with the other UK B2B service sub-verticals is covered in the Growth Systems by Industry map; this piece is about the recruitment-specific CRM problem.

Why doesn't a standard CRM setup fit recruitment?

Because the unit of value is a match, not a deal. A generic pipeline — lead, qualified, proposal, won — describes the client side tolerably, but says nothing about whether you can fill the role. An agency can have a healthy-looking client pipeline and still miss the quarter because the candidate side is thin in exactly the niches the vacancies demand.

The practical answer is two linked pipelines:

• Client development: target account → conversation → terms agreed → live vacancy → placement → repeat business.
• Candidate flow: sourced → qualified → available → submitted → interviewing → placed.

When both are staged, then the cross-view becomes possible: which live vacancies have fewer than three submittable candidates, and which strong candidates have no live vacancy. Those two lists are the day's work, generated by the system rather than by memory.

What goes wrong when only the ATS exists?

The ATS is candidate-shaped, so agencies that run everything through it end up with client development as an oral tradition. Symptoms are consistent: business development happens only when a consultant's desk goes quiet; client records hold contact details but no history of terms, fees or hiring cadence; and when a consultant leaves, their client relationships leave with them because the record was never the system of record. That last one is an ownership problem as much as a data problem — the same pattern as growth that depends entirely on the founder, pushed down one level to the consultant.

What does a working setup look like, mechanically?

When a target client list is built — by sector, size and hiring signals such as job postings — then each account enters the client pipeline at "target" with a named owner. When outreach starts, then every touch is logged automatically from the mailbox, not typed in from memory. When terms are agreed, then the fee basis and rebate terms are recorded on the account, so the next consultant does not renegotiate history. When a vacancy goes live, then it links to a candidate shortlist, and the CRM shows coverage per vacancy daily. When a placement completes, then a dated follow-up task is created for the candidate's start, the rebate expiry, and the client's next likely hire — because in recruitment the second placement costs a fraction of the first.

Hygiene rules keep it honest: no stage without a next action and a date; anything untouched for 30 days flags for review, not deletion.

Where does speed fit?

Everywhere. Recruitment is the most speed-sensitive sub-vertical we work with — vacancies are often multi-agency races, and candidates accept the first credible offer. The CRM's job is to make speed structural: instant routing of new enquiries, same-day submittal targets visible per vacancy. The contact-rate rule of thumb — responsiveness falling away sharply within minutes, commonly cited as roughly 8x after five — bites harder here than anywhere. We cover that side separately in Speed in recruitment: first call wins.

What should the numbers show?

Per consultant and per desk: live vacancies, coverage ratio, submittals per week, interview-to-placement conversion, and repeat-business share. If the MD cannot see those without asking, the CRM is a filing cabinet. Recruitment shares this problem with training providers, whose pipeline runs on cohort calendars, and with marketing agencies, whose new-business systems decay whenever delivery gets busy — different businesses, same underlying failure: the pipeline exists, but nobody built the machine that maintains it.

---

Next step: the Growth System Audit — £450, seven days, credited against any build — maps where your growth system leaks and what to build first.