Guide
CRM for recruiting and executive search firms: candidates, clients, and placements
Recruiting and executive search firms have a three-sided relationship model — clients, candidates, and placements — that most CRM tools were not designed to handle. Here is how to make it work.
The original relationship business
Executive search is one of the oldest relationship businesses there is. Headhunters were managing professional networks and tracking placements long before "CRM" was a product category. That history shows: most recruiting and executive search firms have deeply held, highly personal relationship data. The problem is where it lives.
Elsa once interviewed a partner at an executive search firm in Stockholm who had tracked every placement, candidate referral, and client relationship across three color-coded Moleskine notebooks for eleven years. Organized. Immaculate. When asked what happened when a colleague needed the context, the partner paused. "They ask me," she said. That is not a system. That is a single point of failure wearing a very organized suit.
A standard CRM was designed around a two-sided model: a company that sells something, and prospects who might buy it. Recruiting and executive search have a fundamentally different structure. Understanding that structure is the first step to making a CRM actually work for a practice like this.
The three-sided model most CRMs ignore
Clients
The businesses that hire you. Relationships, decision-makers, fee agreements, mandates, and a history of placements and introductions. A client might engage you twice a year or once every five years. The relationship still needs to be warm when they call.
Candidates
The professionals you place. Not leads in the traditional sense — long-term relationship assets. The candidate you place as VP Sales today may become a CEO client who hires you in six years, or they refer a colleague who becomes a placement.
Mandates
Active search assignments. Like a deal — with a client, a brief, a timeline, and an outcome. But unlike a sales deal, a mandate involves managing a shortlist of real people with their own relationships, preferences, and competing conversations.
Generic CRM tools handle one of these well and muddle the other two. Most teams end up using their CRM for client tracking and keeping candidates in a separate spreadsheet or ATS that does not share context with the client side. The result: when a client calls about a new mandate, the firm knows everything about the client and nothing about which candidates in their network would be a good fit.
What needs to live on every candidate record
- Current and historical roles and companies. Not just the latest LinkedIn title. The full career history is what makes a candidate record valuable for matching against future mandates.
- Placement history. Which client, which role, what year, who was the relationship manager. This connects candidate and client records in a way that supports long-term relationship tracking.
- Relationship warmth. When was the last meaningful conversation — not just a profile visit. Candidates who have been quiet for two years need a different approach than ones you spoke to last month.
- Candidate preferences. Geography, sector, seniority level, compensation range if shared. Logged once and kept current as circumstances change.
- Referral source. Who introduced this candidate to your practice? The referral network is the hidden map of a mature executive search business.
What needs to live on every client record
- Mandate history. What you have placed, what you attempted and did not fill, and what declined. The complete commercial history, not just the latest engagement.
- Key stakeholders and their roles. Not just the day-to-day contact. The decision-maker, the budget holder, and any board members who have a view on the hire. These relationships outlast the individuals.
- Fee structure and terms. Logged on the client record so every partner has the context before a commercial conversation.
- Relationship health and ownership. Which partner owns the relationship, when it was last active, and whether the level of warmth is appropriate for the next outreach.
Long relationship cycles and staying relevant across years
Executive search relationships span decades. A candidate placed at 35 may become a client CEO at 50. A client at one company may move to a new organization and bring you with them. These are not edge cases — they are the growth engine of a mature practice.
The tracking problem is that most CRMs were designed around short transaction cycles. The "last activity" timestamp matters a lot in a SaaS sales pipeline. In executive search, a relationship that has been quiet for three years might still be one of the most valuable in your network — if you know who the person is now and what they have been doing since you last spoke.
The discipline that makes long cycles manageable is relationship intelligence : building a record that captures not just what happened but what the relationship means. Who introduced you? What does this person care about? Where are they in their career now? When is the natural next moment to be in touch?
Firms that do this well reach out at relevant moments — a promotion announcement, a sector move, a news event at their company — with something specific and personal. That context lives in notes, in activity timelines, and in the relationship metadata that only exists in a well-kept CRM. The same principles apply here as in boutique consulting : a small team managing many long-term professional relationships where the system needs to remember context that individuals cannot reliably hold in their heads.
When the candidate becomes the client
The most common gap in how recruiting firms use their CRM: they do not track the candidate-to-client conversion.
A candidate placed three years ago is now a head of department with hiring authority. They are a potential client. But if the CRM only tracked them as a candidate record inside the original placement deal, there is no pipeline for the new relationship. When they call with a mandate, the context of how the relationship started — who placed them, what the experience was like — is buried in an old record that nobody thought to check.
The fix is straightforward: when a candidate progresses beyond placement into a recurring relationship, they get a client company record in addition to their contact record. The activity history carries forward. The question "what do we know about this person as a future client" becomes answerable from the CRM. This is the same principle behind turning past clients into new revenue : systematic follow-through on relationships that already exist, rather than always starting from scratch.
Confidentiality and discretion in a CRM
Executive search involves confidential information on both sides. A candidate in conversation for a role cannot have that fact visible beyond the team working the search. A client exploring a leadership change often cannot publicize the mandate. A CRM that does not support discretion is a liability, not an asset.
Practical requirements: role-based access control so that only the relevant team members can see sensitive search activity; notes fields that support nuanced context without requiring structured data entry; the ability to log conversations without creating visible deal records in shared views.
This is less about exotic security features and more about thoughtful data architecture. A CRM where everything is visible to everyone by default is a poor fit for search work. A CRM where individual contact and deal records can have granular ownership and visibility settings is workable.
The buying committee management discipline is also relevant here: on both the client and the candidate side, the person you speak to day-to-day is rarely the only one who matters. A hiring manager, a board member with a view on culture fit, an internal champion who advocated for the search — all of these relationships affect mandate outcomes and client longevity.
A CRM setup that fits a recruiting practice
You do not need a recruiting-specific CRM to run a practice well. You need a clean mapping of your model onto the standard building blocks.
Companies = clients and candidate employers
Both current and previous employers for candidates. Each client organization gets its own company record with the full mandate and relationship history.
Contacts = candidates and client stakeholders
Tracked persistently across employer changes. The same contact can be a candidate in one deal and a stakeholder at a client company in another. The record travels with the person.
Deals = mandates and BD conversations
One deal per active search. One deal per potential new client mandate. Both pipelines coexist in the same system, linked by the same contact records.
Lists = candidate and client segments
Filter candidates by function, seniority, location, and availability. Filter clients by sector, tier, and last engagement date. Lists make the CRM searchable without manual digging.
The Feed and relationship recency features in a modern CRM are particularly useful in this setup: when a candidate or client relationship goes quiet, it surfaces. You can reach out at a relevant moment rather than waiting until someone calls you — or until they quietly move to a competitor that stayed in touch.
Who this is for
Executive search firms, retained and contingency recruiting firms, headhunting boutiques, and internal talent acquisition teams managing significant candidate networks alongside long-term client relationships. Also relevant for career transition firms and outplacement practices where deep individual relationships are tracked over time. If you are a solo recruiter or small team currently managing everything in a spreadsheet, this is where the system breaks and a CRM becomes worth the overhead.