Most candidate outreach sold as personalized has one personal sentence in it. The recruiter writes a line about something on the profile, a talk the candidate gave or a product they launched, then pastes four paragraphs about the role underneath. The candidate can see where the template starts within a few seconds, so the line that took the research buys nothing.

I’d put that effort somewhere else. Sort the role’s list into the few groups of people who would leave their current job for the same reason, and write one pitch per group with the hiring manager. The part about the individual then shrinks to one fact you could defend if they asked where it came from.

That keeps outreach personal at a few hundred names without anyone writing a few hundred separate messages. You connect with candidates later, when they write back, so the method ends with who answers them and how fast.

Why a personal first line fails at volume.

A first line about the candidate answers a question they weren’t asking. A passive candidate wants to know why this job would beat the one they have, and that answer changes from one background to the next.

Take a senior product designer role. A designer at a large company might move for more say over what ships. One at a ten-person startup might move for a bigger team and a manager who has done the job before. A paragraph about “a fast-growing team with a strong design culture” gives neither of them a reason to reply. Polishing the opening line above it changes nothing about that paragraph.

Volume makes it worse in two ways. Each template a candidate learns to recognize makes your company’s name easier to skip the next time it lands in their inbox. And when a few hundred messages get little back, silence hides which part failed: the reason or the person.

Sort the list by why each person would move.

Before anyone writes a message, go down the role’s list and ask of each name why this person would leave a job they’re probably content in. I’d expect most roles to come down to two to four answers, and each answer is a group.

The answers come out of the intake call. Ask the hiring manager what this job has that a strong candidate’s current job lacks, and push for an answer that differs by background: what it gives someone from a big company, and what it gives someone from a small one. A piece on the intake meeting lists questions that draw out what the role offers, and it helps to bring them, because a hiring manager asked only who they’re looking for will describe the job and skip the reasons.

For the designer role, each group gives something up by moving, and the job has to make up for it:

A name that fits no group deserves a second look before it stays on the list. Sometimes it’s a fourth group the brief missed, and sometimes the person was there only because their title matched the search.

Write one pitch per group, and have the hiring manager read it.

A group’s pitch is the paragraph a person in that group would need to read before they’d give you twenty minutes. It names what this role gives them that their current job lacks, and it says plainly what the move costs. They already know the cost, and a pitch that skips it reads like a sales email.

If the role pays less than a group earns now, the pay is part of what the move costs. Name the range in your opening message, and aim the group at candidates who’d accept that trade.

Then send the pitches to the hiring manager with one question about each: would you say this to a candidate from that group on a call? If the hiring manager winces at a line, rewrite it before a candidate reads it. While you have them, settle whose name goes on each group’s messages and who answers the replies. I’d put the hiring manager’s name on the group moving for the work itself, since that’s the person they’d be doing it for.

Add one fact per person that you could defend.

The individual part of the message is one sentence, and it shows the candidate why they belong in this group. Make it a checkable fact, one you could point to if they wrote back asking where it came from, such as how many people they manage now, or a product they’ve worked on since its first release.

A compliment can’t do that job. “Loved your talk on design systems” tells the candidate you watched something, and says nothing about why the role fits them.

Put the fact first, the group’s reason straight after it, and then a small ask. For the startup group, a first message might read: “You’ve led design at three early-stage companies, each time as the only designer. This role reports to a design lead who has built a team of six before, and you’d be the second senior hire under her. Would a twenty-minute call next week be useful, even if the answer turns out to be no?”

If you can’t find a fact like that in a couple of minutes, the profile is telling you something. Either the person belongs in another group or the list was padded, and both are cheaper to find out before the send than after it.

Plan what each follow-up adds before the first send.

A follow-up that repeats the first message asks the candidate to say no twice. Give each step something new, taken from the group’s pitch:

• a second reason the role suits this group, held back from the first message
• a few lines from the hiring manager in their own words, or a step sent under their name
• an answer to the doubt this group usually raises, whether that’s the pay or the office days
• a short last note saying you won’t write again about this role, and asking whether you can get in touch about a later one

For pacing, I’d send three or four emails over two to three weeks, with longer gaps toward the end. LinkedIn can carry one or two touches spaced further apart, and I’d keep the phone for roles where the timing is urgent or the candidate has already replied once. Each step should land during the candidate’s working day, wherever they are.

Have a person answer every reply the same day.

Candidates decide whether to talk when they write back, and I’d guard this step hardest. Whoever answers should have the group’s pitch and the fact about the person in front of them, and should answer within the working day, because a candidate who wrote back while curious can be lukewarm by the next morning.

• Interested: offer two times for a call, and say who they’ll speak to and for how long.
• Not now: ask when would suit them better, and get back in touch then with whatever has changed.
• A question: answer it in full, even when the answer is one they won’t like, such as the pay band or the days in the office.
• No: thank them, and ask what would make a move worth it for them.

Write down why people said no, against their group. The no answers are the best material you’ll get for the next version of that group’s pitch, and after a few dozen of them I’d expect the pattern to be plain.

Where Metaview fits in candidate outreach.

The groups and their pitches are built from conversations your team already has, on intake calls and recruiter screens. Metaview records those conversations, and Outreach sends the sequences a recruiter builds from them.

Metaview’s Notetaker records and transcribes recruiter screens and intake calls, joining each one as a visible participant, and each conversation comes back as structured notes. On those calls, Metaview captures every spoken word. Your next pitch for a group can then start from what candidates in that group said made them take the call, in their own words.

1

2

3

1. 1The screen’s first question asks what made the candidate take the call, and their reasons sit beneath it.
2. 2A follow-up question about the candidate’s current team, answered in short lines.
3. 3“3 senior; 3 mid; 1 junior”: a fact about the person you could check with them, the kind a first message can open on.

Before writing a group’s pitch, I’d ask Metaview Reports why past candidates from that background were looking, and what they gave as their salary expectations. Reports answers from your own data: the interviews your team has recorded.

1

2

1. 1The page’s own example: compensation ranges candidates have mentioned for a given role, the question to settle before a group’s pitch names a salary.
2. 2Gemma B. appears again for her screen with the hiring manager, below her “Recruiter Screen” at the top, so an answer belongs to a call as well as a person.

AI Sourcing helps build the list in the first place. From one plain-language prompt it searches past Metaview conversations, the web, and the applicant tracking system you’ve connected, and it shows the reasoning behind each candidate it brings back. I’d run one search per group, with the group’s reason written into the prompt. It leaves the choice with the recruiter, who assesses who fits before any sequence writes to them.

Metaview Outreach runs the sequences. A recruiter turns each group’s pitch into a sequence, with its steps and follow-ups, and prompts the AI to tailor each message from the candidate’s contact record and the role. Outreach then sends the steps as automated email and follows up on schedule, and it finds verified email addresses and phone numbers for candidates whose details are missing.

Mailbox delegation lets a recruiter send a sequence on behalf of a teammate, so a group’s messages can go out under the hiring manager’s name while the recruiter still runs them. The sequence performance view shows what is driving replies by role and by step, which is where I’d compare one group’s pitch with another’s.

Check the batch for one group before the sequence starts.

Before a group’s sequence starts, open its batch and read the names and their messages together once more, as the recruiter who will own it.

• Place any name that has no group, with the hiring manager, or take it off the list.
• Rewrite or cut any message whose fact you couldn’t defend if the candidate asked where it came from.
• Name the person who answers this group’s replies, and hold the sequence until someone is named.

A candidate can tell within a sentence whether a message was written for people like them, and a few lines later whether anyone looked at them in particular.