Cold Email for Recruiters

Two audiences, two sequences

Recruiters email two different audiences: candidates and hiring managers. They need separate lists, separate copy and separate metrics. Mixing them produces generic emails that fit neither.

A candidate cares about the role, the location, the compensation range and why you thought of them. A hiring manager cares about time-to-fill, relevant placements and the difficulty of the role. Neither cares about your agency's history.

Candidate outreach

The first line should show why you are writing to this person: their current role, a skill, a project or a public profile. Then name the opportunity in one sentence: title, company stage, location and a salary range if you have one.

Keep it short and make it easy to say no. A candidate who is not looking should be able to reply "not now" without a follow-up argument. If they are interested, the next step is a short call, not a request for their CV in the first email.

• Name the role and location.
• Give one reason for the contact.
• Include a salary range where possible.
• Ask whether it is worth a conversation.
• Respect a no and suppress the contact. A candidate who is not looking today may be the right person next year, and a gracious reply is what keeps that door open.

Client outreach

For hiring managers, lead with a relevant placement or a specific observation about the role. "You have been hiring a senior backend engineer for a while; we placed two in similar teams last quarter" is more useful than "we are a recruitment partner".

Offer a small next step: a shortlist of two profiles, a market note or a 15-minute call. A client who is not hiring yet can still be a future client if the outreach is respectful.

Compliance and data care

Recruitment involves personal data, and the rules vary by country. Do not send a candidate's CV or contact details to a client without permission. Do not scrape personal profiles and mass-email them without a lawful basis and a working opt-out.

Keep the data minimal and delete it when it is no longer needed. When a candidate asks to be removed, suppress them across roles, not just the current campaign. The unsubscribe requirements apply to candidates as well as clients.

A worked example

A recruiter specialising in fintech operations writes to a candidate: "You have been running payment operations at a Series B company for two years. I am hiring a head of operations for a fintech in Manchester, base around the range you would expect for the scope. Worth a 15-minute conversation?"

The email names the role, the location, the reason for the contact and the next step. It does not ask for a CV or a salary history in the first message.

Volume and quality

Recruiters are often tempted by large candidate databases. Volume without relevance produces low reply rates and complaints. A smaller list of people who match the role, contacted with a specific message, performs better and protects the domain.

Warm the inboxes, verify the addresses and keep role addresses separate. Candidate personal emails are common; segment them and check the domain matches a real person. The list building guide applies to candidate sourcing too.

Metrics

Track replies, conversations, CVs received and placements. A campaign that produces many replies but few qualified candidates may be targeting the wrong seniority. A low reply rate with a high placement rate may be fine for a niche role, so judge the channel by placements rather than by the loudest metric and review the mix every month with the hiring team.

Do not use opens as the main signal. Use replies and outcomes, as why opens mislead explains. Track time-to-reply as well: a recruiter who answers within the hour wins candidates that a slower competitor loses.

The short version

Name the role, the reason and the range. Keep candidate and client sequences separate, respect a no and protect personal data. Relevance beats database size in recruitment outreach.