Recruiting Agency Playbook: Running Candidate & Client Pipelines in a CRM
A practical playbook for how a recruiting agency structures pipelines, automates candidate follow-ups, and tracks placements in a CRM instead of spreadsheets and inboxes.
Last updated July 18, 2026
Why recruiting needs two pipelines, not one
A recruiting agency runs two separate sales motions at once: winning client companies who need roles filled, and moving candidates through those roles to placement. Treating both as a single generic "deals" pipeline collapses information a recruiter actually needs day to day, like which stage a candidate is in versus which stage the client relationship is in.
The fix is two linked pipelines in the same CRM: a client pipeline (prospect, active job order, filled, renewal) and a candidate pipeline (sourced, screened, submitted, interviewing, offer, placed). Candidate records link to the job order they're being considered for, so a recruiter opens one job order and sees every candidate in flight for it, at whatever stage each one is in.
Example
Imagine a 12-person agency working 40 open job orders at once. Without linked pipelines, a recruiter has to cross-reference a client spreadsheet against a candidate tracker to answer "who's still in play for this role?" With linked pipelines, that's one filtered view.
Structuring the candidate pipeline
The candidate pipeline should mirror the actual hiring funnel, not a generic sales funnel. A typical structure: Sourced, Screened, Submitted to Client, Client Interview, Offer Extended, Placed, and a separate Declined/Withdrawn state that captures why a candidate dropped out (rate mismatch, counter-offer, went dark).
That "reason lost" field matters more in recruiting than in most sales pipelines, because it's the fastest way to spot a systemic problem — if 30% of candidates are declining at the offer stage over a compensation gap, that's a signal to renegotiate rate with the client, not a one-off loss.
Example
A team like this might tag every declined candidate with a reason code. After a quarter, a recruiter reviewing the pipeline report notices "counter-offer" accounts for a disproportionate share of losses on one client's roles — a prompt to talk to that client about offer speed rather than sourcing more candidates.
Automating candidate follow-ups without going quiet
Candidates who don't hear back for a week assume they've been passed over, and good candidates take other offers while a recruiter is busy with other job orders. The fix is automated, staged follow-up: a scheduled check-in after submission, a status nudge if the client hasn't responded in a set number of business days, and an automatic re-engagement touch for candidates parked in a talent pool for future roles.
This only works if the automation reads as personal rather than mass-blasted — short, plain-text-style messages referencing the specific role, sent from the recruiter's own name, not a "no-reply" address. Automating the timing doesn't mean automating the tone.
Example
A recruiting team might set a rule: if a submitted candidate hasn't moved stage in 5 business days, the CRM creates a task for the recruiter to check in with the client, and separately queues a short status update to the candidate so they aren't left wondering.
Tracking time-to-fill and source quality
Time-to-fill — the span from job order opened to candidate placed — is the metric clients care about most, and it's only visible if every stage change is timestamped in the pipeline instead of buried in email threads. A CRM report that groups time-to-fill by client, by role type, or by recruiter shows where the pipeline is actually slow, whether that's sourcing, client response time, or interview scheduling.
Source tracking matters just as much: tagging each candidate with where they came from (referral, job board, sourced outreach, agency database) shows which channels actually produce placements versus which just produce volume.
Example
A typical agency might find that referral-sourced candidates close in half the time of job-board candidates, which justifies shifting budget toward a referral incentive program instead of another job board subscription.
Rolling this out to a recruiting team
Recruiters resist tools that feel like extra data entry on top of their actual job, which is talking to people. The rollout works better when the CRM captures activity automatically — logging emails and calls against the candidate or client record without a manual step — and when the pipeline stages match language recruiters already use, rather than importing a generic sales template.
Start with one job order
Migrate one active job order into the new pipeline first and run it end to end before moving the whole desk over. It surfaces stage-naming and workflow issues while the stakes are low.