What is different in recruitment sales
Every placement needs two yeses. The client must want the candidate, and the candidate must want the job. Either side can kill the deal at any moment, which makes recruitment the only industry where your product can decline to be sold. A CRM built for one-sided sales fights this reality unless you shape it deliberately.
The cycle is fast and fragile. A perm placement runs two to eight weeks from signed job order to accepted offer, with interviews as the visible heartbeat. Speed is the competitive weapon: the agency that submits three strong profiles in four days beats the one that submits five in two weeks. Your pipeline has to surface stalled candidates daily, not at the Friday review.
Decisions sit with a hiring manager, but HR controls process and fees, and at contingency agencies you compete against two rivals and the client's own job ad. Exclusivity, fee percentage and guarantee terms are deal data, not contract trivia.
An example twin pipeline
We build recruitment accounts around two pipelines. The first wins the business, the second delivers it.
| Client pipeline (BD) | Placement pipeline (delivery) |
|---|---|
| Intake call held | Candidate submitted |
| Terms sent | First interview held |
| Terms agreed | Final interview held |
| Job order received | Offer made |
| (won: job goes to delivery) | Offer accepted |
In the placement pipeline, one deal represents one candidate on one job, with the fee as the deal value. Won means the candidate started. Lost reasons carry double weight here: rejected by client, withdrew, counter-offer, took another role. That report teaches an agency more than any other. The stage discipline that makes this work is the same covered in stages and probabilities.
The fields and automations that matter
On the client side: fee percentage, exclusivity as a yes or no, guarantee period, and source of the client. On the placement side: role title, salary offered, notice period, and candidate consent date. Notice period is the sleeper field. It drives start date forecasting, and start dates drive when you actually invoice.
Three automations matter most. First, an interview follow-up: when a deal enters an interview stage, create a same-day debrief activity for both sides of the call. Second, a stall alarm: any placement deal without movement for five days gets flagged, because in recruitment a week of silence is usually a lost candidate. Third, the guarantee tracker: when a placement is won, create an activity at 30 and 80 days to check in before the guarantee period ends. Keep the total list short, in the spirit of automations that actually matter.
On integrations, the honest picture is this. Email and calendar sync carry most of the value, since recruitment lives in the inbox. LinkedIn does not integrate natively with Pipedrive, so sourcing tools or a disciplined copy-in habit bridge that gap. Job boards can push applicants into Leads through webforms or middleware. At the point where an agency needs parsing, matching and compliance workflows at volume, that is the signal to add a dedicated ATS and let Pipedrive keep the client side.
Common mistakes
The biggest structural mistake is one deal per job with candidates listed in notes. It looks tidy and measures nothing. You cannot see candidate conversion, cannot spot which recruiter's submissions survive interviews, and cannot report why candidates fall out. One deal per candidate per job fixes all three.
The second is mixing BD and delivery in one pipeline. The job order is a sale to a company. The placement is a process run on people. Different stages, different owners, different maths.
The third is ignoring candidate experience data. Lost reasons like withdrew and counter-offer are early warnings about salary benchmarks and process speed. Agencies that track them adjust in weeks instead of quarters.
The fourth is importing a decade of stale CVs into a new account. Migrate active relationships and let the archive die, the same advice we give in migrating from a legacy CRM.
Questions
Is Pipedrive a replacement for an ATS?
For agencies up to roughly fifteen recruiters, it can be. Candidates become persons, placements become deals, and the job pipeline models the process. Above that size, or with heavy compliance requirements, a dedicated ATS wins and Pipedrive handles the client side only.
How do we model one job with several candidates?
One deal per candidate per job is the model that keeps reporting honest. The job itself lives on the organisation or as a labelled deal in the client pipeline. It feels like duplication at first, but it is the only way stage conversion per candidate works.
What about GDPR and candidate data?
Candidate CVs and notes are personal data, and consent has an expiry. Use a consent date field, an automation that flags candidates approaching the limit, and Pipedrive's delete functions for the rest. A recruitment CRM without a deletion routine is a liability.
Can Pipedrive handle temp and contract staffing?
Perm and contract placements fit well. High-volume temp staffing with daily bookings does not. That is scheduling software territory. Many staffing firms run perm placements in Pipedrive and temp operations in a specialist tool.
How should we split BD and delivery work?
Two pipelines. Business development wins the client and the job order. Delivery runs candidates against the job. Different people often own each side, and separate pipelines let each report cleanly, with visibility rules if teams should not see each other's accounts.