How to Use Claude to Personalize Candidate Outreach at Scale (2026 Guide)
Claude can write hundreds of candidates a first message that reads like you researched each one.
Published
Written by
Chris Pisarski
Reviewed by
Manmohit Grewal
Read time
14
minutes

Claude can write hundreds of candidates a first message that reads like you researched each one.
A good opener connects what the person has worked on to why your role fits, in your own words. A weak one quotes their profile back, like "I saw your post on X" or "Congrats on 4 years at Y". Recruiters our team talks to call that table stakes, and candidates read it as a template.
One data call returns each candidate's roles with dates, profile text and up to ten recent posts. Claude reads it against your role brief, works out the connection no field holds, writes it in your voice and checks every draft. The hard part is restraint: skipping what's personal, not repeating what candidates wrote about themselves, and holding a candidate when there's nothing worth saying.
Our team tested this on a staff-level AI evaluation role with six real candidates. With a plain "mention one real thing about them" prompt, all six openers led with a line lifted from the profile or a post. With the steps below, Claude wrote five openers and held one candidate the brief's time-in-role rule ruled out. All five first drafts failed the quoting-back check, and all five passed after rewrites.
There are three ways to set it up:
Claude Code with the Crustdata MCP server, for a first test on a real shortlist.
Claude Cowork, without code: attach the brief and prompts to a chat.
The Claude API, when outreach is a feature of recruiting software you build.
What you'll need:
Claude Code, Claude Cowork or an Anthropic API key
A Crustdata account, which comes with free credits for new self-serve users
A shortlist of candidates with their professional profile URLs
A role brief, and three of your own openers that got replies
At a glance | |
|---|---|
What it does | Writes one opener per candidate that ties their work to your role |
Data per candidate | Roles with dates, profile text, education and up to 10 recent posts, from one person enrich call |
What Claude does | Works out the connection, skips personal signals, writes in your voice and checks each draft |
Cost | 6 credits per candidate at list rate with posts, 1 credit without |
Our test | 6 candidates, 5 openers, 1 held, every final draft past an 8-point check |
What does personalized candidate outreach mean?
Personalized recruiting outreach is a first message built from what this person has actually worked on.
The test is whether the message could only have gone to them. Naming their employer, title or school fails that test, because a template does the same. A recruiter at an agency put it to our team plainly: "I actually used to be totally against personalization because it was so bad for so long where it's like, hey, I noticed you went to Boston College."
What does this guide cover?
This guide covers the first message, from role brief to pre-send check, in five steps. Emails and follow-up sequences are in our Claude guide to candidate enrichment and outreach.
How does Claude personalize outreach for each candidate?
Claude reads each candidate's data against your brief, writes one opener and checks it before you see it.
Part | Who does it | What it produces |
|---|---|---|
Role brief | You | Must-haves, disqualifiers, what you can say about the client |
Candidate data | Crustdata | Roles with dates, profile text, education, recent posts |
The angle | Claude | One connection with the fields it rests on, or HOLD or THIN |
The opener | Claude | Two or three paraphrased sentences in your voice |
The check | Claude, then you | Pass or fail on 8 checks, then your approval |
Which candidate signals are worth using in a recruiting message?
Use signals about the person's work that connect to your role, and put them in your own words.
Signal | Where it comes from | Use it when | Skip it when |
|---|---|---|---|
What they've built in their current role | Role description, profile summary | It matches the work your role owns | It's a number or phrase you'd quote back |
A recent post about their work | Recent posts | It's under a year old and on the role's topic | It's the only hook and you'd have to name it |
A project, talk or open-source work | Profile summary, posts | It shows the skill your role needs | You can't tell what it is from the profile |
A job move | Role dates | It explains your timing | They're under your time-in-role rule |
A hobby they posted publicly | Recent posts | It's a light second detail next to the work | It would carry the message alone |
A shared past employer or school | Past roles, education | The overlap is real and you're in-house | It's the whole hook, or it reveals your client |
Should I mention a candidate's recent post?
Use what the post shows about their work, and leave the post itself unnamed.
"I saw your post on rubric checks" tells the candidate you read their feed. "You've been working out how to check an agent's tool calls" tells them you understood their work. Same post, different message. Posts carry a date_posted field, so drop anything older than about a year before Claude reads them.
Should I mention a recent job move?
Use a move to time your message, not as the hook.
"Congrats on the new role" reads as a template. If someone is under your time-in-role rule, hold them. A search filter on the current role's start date can drop them before Claude reads anything. Our test shortlist wasn't filtered that way, so Claude held the one candidate who was five months into a role, against a nine-month rule.
Should I mention a project, talk or open-source work?
Yes, when it shows the skill the role needs.
An in-house recruiter told our team they wanted Claude to write things like "notice that you were working on this project" for engineering roles. Same rule as posts: describe what it does in your words, without reciting its name or numbers.
Can I mention a candidate's hobby?
Yes, if they posted it publicly, as a light second detail that supports the work angle.
A published hobby can show you read past the headline, but it can't carry the message. In our test, Claude allowed one candidate's post about running a model on their home GPU as a second detail, then cut it from the final draft because the first draft gave the hobby as much weight as the work.
Does a shared past employer or school help?
Only when the overlap is real, and only when you can say it without exposing your client.
A school alone is table stakes. A shared employer works when the years and work overlap, and you don't imply people know each other. If you're recruiting for a client, leave it out. Naming who the hiring manager worked with gives the client away.
Which signals feel creepy, and why should you skip them?
Skip anything about their private life, and anything that sounds like you watched them:
Family, health and home life. None of it relates to the job, even when public.
Who they reacted to or commented on. It reads as watching their activity.
Posts older than about a year. They read as digging, and may no longer be true.
Guesses about job hunting. A layoff post or short tenure doesn't mean they're looking. If they said publicly they're open to a move, mention it once, lightly.
Watching language. "I noticed you've been..." or "I've been following your..." makes even fair signals feel tracked.
What's the test for creepy versus fair?
Ask three questions about every detail:
Did they publish it themselves, in public?
Does it connect to this role, or support a detail that does?
Would they expect a stranger hiring for this job to bring it up?
If any answer is no, leave it out.
Isn't naming their employer or title enough?
No, a template can do that, and readers know it. A recruiter at a talent agency objected to exactly this in Claude's first drafts: they didn't want "the obvious table stakes of like, I saw that you're working at this".
Can't I just paste profiles into Claude?
You can for five candidates, but pasting caps you at what you can copy by hand.
Claude can't open a profile on its own. One person enrich call returns everything this guide uses for up to 25 profile URLs at a time.
Which fields does Claude read?
Claude reads these sections:
Section | What Claude uses it for |
|---|---|
| Headline and summary, for what they say they work on |
| Current and past roles with start and end dates, and role descriptions |
| Schools and degrees, rarely used as a hook |
| Up to 10 of their most recent posts, newest first, with |
| A stable ID, so you can skip anyone you've already enriched |
The social_posts section is a beta add-on that has to be enabled on your account. Without it, the section is left out of the response (person enrich reference).
How recent does a post have to be?
Use posts from the last 12 months, checked against date_posted.
Indexed posts are refreshed every 1 to 45 days (data updates). For your top candidates, the live posts endpoint retrieves a person's recent posts at the moment you call it. Live retrieval is on enterprise plans or the live add-on.
What if a candidate never posts?
Write from their roles and profile text, which carry most openers anyway.
In our test, Candidate A below had no posts, and Claude built their opener from the role description and summary. When neither connects to your role, Claude marks the profile THIN.
Step 1: How do I write the role brief Claude personalizes against?
Write the brief you'd hand a new sourcer, plus what the opener can sell and say.
Requirements alone give Claude nothing to connect to. It also needs the selling points and the limits on what you can say about the client. Our team's brief for the test:
Claude caught a mistake in our first version: the sell line mentioned the hiring manager's background, which the may-say line banned. Fix contradictions like that before the first batch.
The brief splits the work between filters, data and Claude:
Brief line | Goes to |
|---|---|
Location, years of experience, title, excluded employers | Search filters |
Has built evaluation infrastructure for LLM systems | The search query, then Claude checks it |
Roles with dates, profile text, posts | Person data |
Time-in-role rule | Search filter on the current role's start date |
The connection, whether it's fair, how to say it, whether the profile is too thin | Claude only |
Step 2: How do I pull each candidate's posts and work history?
Enrich only your shortlist, with the sections Claude reads. In Claude Code with the Crustdata MCP server, ask in plain English:
The same call as a direct API request:
curl --request POST \ --url https://api.crustdata.com/person/enrich \ --header 'authorization: Bearer YOUR_API_KEY' \ --header 'content-type: application/json' \ --header 'x-api-version: 2025-11-01' \ --data '{ "professional_network_profile_urls": ["<profile URL 1>", "<profile URL 2>"], "fields": ["basic_profile", "experience", "education", "social_posts"] }'
curl --request POST \ --url https://api.crustdata.com/person/enrich \ --header 'authorization: Bearer YOUR_API_KEY' \ --header 'content-type: application/json' \ --header 'x-api-version: 2025-11-01' \ --data '{ "professional_network_profile_urls": ["<profile URL 1>", "<profile URL 2>"], "fields": ["basic_profile", "experience", "education", "social_posts"] }'
curl --request POST \ --url https://api.crustdata.com/person/enrich \ --header 'authorization: Bearer YOUR_API_KEY' \ --header 'content-type: application/json' \ --header 'x-api-version: 2025-11-01' \ --data '{ "professional_network_profile_urls": ["<profile URL 1>", "<profile URL 2>"], "fields": ["basic_profile", "experience", "education", "social_posts"] }'
Keep fields explicit. Without it, the call returns only basic_profile and social_handles, with no roles or posts (person enrich reference).
Step 3: How do I get Claude to work out the angle for each candidate?
Ask Claude for the connection between their work and your role, with the fields it rests on.
The angle is the one thing a recruiter who had done the homework would bring up. Our test sent one prompt in three parts. The opening line and first part:
In our test, the angles were about how each person works. For one candidate, it was that they "won't trust an agent's numbers until code has checked them". For another, that they already hold agent releases until they pass evaluation, and grade every step of the run. Neither repeats the profile's wording.
Claude also flagged must-haves it couldn't confirm, on-call experience for all five and backend language for two, to ask about on the call.
Step 4: How do I have Claude write one opener per candidate?
Have Claude write two or three sentences in your voice that paraphrase the angle. The second part of the prompt:
Claude copies your three past openers for voice. In our test, four of five first drafts still failed the voice check, and every rewrite passed. Pick short openers that got replies.
Should I personalize every message or only my top candidates?
Give your top tier the full research angle, and send the rest a lighter version.
Recruiters our team talks to do the same, since tailoring every message takes too long. A talent-agency recruiter described tiering a batch, where tier A candidates "have that very customized, unique personalization, and then the rest of the people can be a little bit more of a blanket".
Step 5: How do I check each draft before it goes out?
Have Claude run eight checks on every draft and rewrite until each passes. The third part of the prompt:
In our test, every first draft failed check 2, and most failed at least two more:
Check failed on the first draft | Drafts, of 5 |
|---|---|
Reads as quoting the profile back | 5 |
Uses something from the skip list | 5 |
Doesn't sound like the recruiter's examples | 4 |
Flattery or a mic-drop line | 4 |
A fact that isn't traceable or no longer true | 3 |
Reads the resume back | 3 |
All five finals passed all eight. Check 5 catches what a talent-agency recruiter called "mic droppy" lines in Claude's first drafts.
Read your top tier yourself before sending. One recruiter's unedited ChatGPT message drew a blunt reply in an r/recruitinghell thread: "What happened to review before you send??"
What does Claude do when a profile is too thin?
Claude marks the candidate THIN, and you send your standard note.
A forced connection reads worse than an honest template. A one-line headline with no role descriptions or posts gives Claude nothing true to connect, so don't let it invent one.
How do I personalize 40 candidates in one batch?
Tier the shortlist, pull posts for tier A only, then run Steps 3 to 5 over everyone:
Tier the list. Mark your top 8 to 10 as tier A.
Enrich in two calls. Tier A with
social_posts, everyone else without, since posts are the expensive section.Run the three prompts over the batch. Ask for one table: name, angle, opener, checks passed, and any HOLD or THIN.
Read every personal line in one list. Repeats and quoting-back jump out side by side.
Read tier A yourself, then approve. Hand approved openers to your sequencing tool, with your opt-out rules in place.
What do three personalized openers look like?
Three candidates from our test, with names, employers and identifying detail changed.
Candidate A | Candidate B | Candidate C | |
|---|---|---|---|
Now | Lead software engineer at a large bank, about 3.5 years | Senior software engineer at an industrial software company, almost 4 years | Software engineer at a robotics company, 5 months |
Work that matters | Built an internal question-answering agent that checks its numbers in code before showing them. Open-sourced a project with the same checks for tool-calling agents | Profile describes LLM evaluation tooling and the backend under it: workers, failure recovery, telemetry | Built an evaluation platform for AI agents at their previous startup |
Posts | None | A July post saying they're exploring their next role. A May post about a model on their home GPU that drifted on multi-step tool calls | All more than a year old |
Claude's angle | Won't trust an agent's numbers until code has checked them | Evaluation tooling plus the backend that keeps AI systems up, in one person | HOLD: 5 months in role, under the 9-month rule |
Claude skipped | The dollar figures and document counts in their summary | The home GPU post in the final draft, and older posts | Everything, until the hold lifts |
Candidate A. The first draft opened on a dollar figure from the summary and named two projects in a row, failing the quoting-back, skip-list and voice checks. The final:
"You don't let an agent's numbers stand until code has checked them, at work or in what you publish. A Series B team building AI agents for insurance claims needs that habit turned into the gate every agent release passes, on real claims data. Open to a 15-minute call?"
Candidate B. The first draft paraphrased the home GPU post closely and said "since you're exploring your next role" as if the July post were still true, failing six of eight checks. The final keeps the work angle, drops the hobby and softens the timing:
"You've built LLM evaluation tooling and the backend that keeps AI systems up underneath it: workers, recovery, telemetry. A Series B team running AI agents on 40 insurance claims workflows needs both in one person, to own the gate every agent release passes on real claims data. If you're still exploring a move, worth a chat?"
Candidate C. No opener. Claude noted the evaluation platform as the angle if the tenure rule is ever waived.
With the plain prompt, Claude opened Candidate A's message with the name of their open-source project, and wrote Candidate C an opener naming their previous employer, with the tenure rule noted underneath.
How do I connect it to Claude?
Claude Code, Claude Cowork and the Claude API use the same data and prompts.
Option A: Claude Code with the Crustdata MCP server
Add the MCP server in your terminal, then run /mcp in Claude Code and sign in (MCP server docs):
claude mcp add --transportclaude mcp add --transportclaude mcp add --transportThen save Steps 3 to 5 as a skill, which Claude loads when the task matches or you run with /candidate-openers. Put it at .claude/skills/candidate-openers/SKILL.md:
--- name: candidate-openers description: Write personalized first messages for a shortlist. Use when the user wants outreach openers for candidates. --- 1. Read the role brief in roles/<role>/brief.md. Flag any line that contradicts another. 2. Enrich roles/<role>/shortlist.csv with basic_profile, experience, education. Add social_posts for tier A only. Save to roles/<role>
--- name: candidate-openers description: Write personalized first messages for a shortlist. Use when the user wants outreach openers for candidates. --- 1. Read the role brief in roles/<role>/brief.md. Flag any line that contradicts another. 2. Enrich roles/<role>/shortlist.csv with basic_profile, experience, education. Add social_posts for tier A only. Save to roles/<role>
--- name: candidate-openers description: Write personalized first messages for a shortlist. Use when the user wants outreach openers for candidates. --- 1. Read the role brief in roles/<role>/brief.md. Flag any line that contradicts another. 2. Enrich roles/<role>/shortlist.csv with basic_profile, experience, education. Add social_posts for tier A only. Save to roles/<role>
Option B: Claude Cowork, for recruiters who don't write code
Add Crustdata as a custom connector: in Claude, open Customize, then Connectors, click Add, then Add custom connector, and use https://install.crustdata.com/mcp. On a Team or Enterprise plan, an Owner adds the connector for the organization first, and members then connect it (Anthropic's connector guide).
Keep each role's brief, your three openers and the prompts in one folder, attach them at the start of each chat, paste your shortlist and ask for the batch table.
Option C: the Claude API inside your own recruiting tool
Your backend calls person enrich, then sends the brief, records and three prompts to the Claude API, per candidate or per batch. Store each angle, opener and check result with the candidate, so a recruiter can see why a message says what it says.
How much does it cost to personalize outreach per candidate?
Person enrich costs 1 credit for the base profile plus 5 for posts, so 6 per candidate at list rate.
Posts are a flat 5 credits however many come back, and nothing when a person has none (person enrich reference). Crustdata credits cost $0.30 to $0.01 per credit, lower depending on plan. Three points on that range:
Batch | Credits at list rate | At $0.30 a credit | At $0.17 a credit | At $0.01 a credit |
|---|---|---|---|---|
1 candidate with posts | 6 | $1.80 | $1.02 | $0.06 |
1 candidate without posts | 1 | $0.30 | $0.17 | $0.01 |
40 candidates, posts for 8 in tier A | 80 | $24.00 | $13.60 | $0.80 |
The 40-candidate row is 40 base profiles plus 8 post add-ons, a ceiling, since a tier A candidate with no posts costs 1. Claude usage is billed separately by your Claude plan or API.
How can I cut the bill?
Request posts for tier A only, and never enrich the same person twice:
Limit posts to tier A. Posts are five of the six credits.
Keep a seen-list for every role. Store each
crustdata_person_id, and skip anyone you've already enriched for this role.Check your own rates for free. The
/account/endpointscall lists what each endpoint costs on your plan (pricing).
Where do I start this week?
Take one open role and five candidates you'd message anyway, and run the loop by hand in Claude Code:
Write the brief, with the may-say line and three openers that got replies.
Enrich the five with all four sections.
Run the three prompts, and compare each first draft with its final.
Send the ones you'd sign, and save the skill once the openers sound like you.
Start on a free Crustdata account or book a demo at crustdata.com.
FAQ
Do candidates notice when outreach was written by AI?
Often, when AI writes the same pattern for everyone. In an r/recruiting thread on AI outreach, the top reply is "It's slop and people can tell". Another commenter says in-demand candidates "will clearly see the pattern". The quoting-back check and your own openers as the voice keep drafts from sounding alike.
What is hyper-personalization in recruiting?
Hyper-personalization goes past merge fields and company news to a detail only this person would recognize, the angle from Step 3. A partner at a search firm described the alternative to our team: "We can just send a template with the first name."
