Cold outreach messages that get replies

Cold outreach gets replies when it reads like it was written for exactly one person and costs nothing to answer. The working anatomy has four parts: a subject line specific enough to earn the open, a first line built on one genuine detail of the candidate’s work, the role pitched in two sentences with the basics in plain sight, and an ask small enough to answer from a phone in ten seconds. Everything else you are tempted to include, the company story, the benefits list, the second paragraph about culture, lowers the odds of a reply. Vague messages do not get rejected; they get ignored.

Why does the subject line do most of the work?

Candidates with in-demand skills get recruiter messages every week, and most die unopened. The subject line is not a summary, it is the audition: its only job is to prove that a human wrote this for them. “Exciting opportunity” and “Quick question” announce a template before the message is even opened.

What survives is a subject that names something real about the candidate or the role. “Your zero-downtime migrations talk + a staff role in Rotterdam.” “Question about your move from agency to in-house.” Specific reads as effortful, and visible effort is the whole signal.

On LinkedIn the first line is effectively a second subject line, because it shows in the preview. Spending it on “I hope this message finds you well” wastes the most valuable real estate you have. Open with the detail; the greeting can be one word.

What counts as a genuine personal detail?

One detail that could not be pasted into a message to anyone else with the same job title. That is the entire test. “I was impressed by your background in software engineering” fails it; ten thousand people have that background, and most of them received the same sentence today.

Details that pass: a conference talk they gave, a pull request or side project, a blog post, an unusual career move (embedded to cloud, agency to product), something true about their current employer that makes a move plausible right now. Notice that these all come from their work, not their profile summary. If all you have after sourcing is a name and a title, the problem sits upstream of the message; candidates found in communities beyond LinkedIn arrive with context attached, which is exactly what makes the first line writable.

One detail is the right number. Zero is a template; three is surveillance.

How do you pitch the role in two sentences?

Sentence one says what the job actually is and what makes it concretely different: the problem, the team, the stage, the stack. Sentence two covers the practical frame: location and remote policy, seniority, and the salary range if you can share it. Naming the range ends wrong-fit conversations before they start, and a role whose basics are hidden looks like a role that cannot survive daylight. If the number is under market, concealing it only delays the problem; there is a more honest way to pitch a lower salary.

Then stop. The pitch is not there to close the candidate; it is there to make the ask reasonable. Every sentence past the second is you negotiating with yourself.

What is a low-friction ask?

The ask determines the cost of replying, and cost is what loses interested-but-busy people. “Send me your updated CV and your availability for a call this week” is homework assigned by a stranger. A low-friction ask is answerable in one line, ideally one word: “Worth a short call, or should I leave you alone?” “Open to hearing more? A no is a fine answer.”

Explicitly permitting the no is not weakness; it reads as confidence and lowers the social cost of engaging at all. Skip the booking link in the first message too: it presumes a yes you have not earned yet. Save it for your reply to their reply.

What does a good InMail look like in full?

Subject: your zero-downtime migrations talk + a staff role in Rotterdam

Hi Sanne,

Your PGConf talk on zero-downtime migrations settled an argument on our platform team (the partitioning section, in my favor, thank you).

I am hiring a staff engineer for a 40-person logistics scale-up in Rotterdam whose Postgres estate grew faster than its schema; you would own that problem end to end. Hybrid, two days on site, and the range up front: [X to Y].

Worth a 15-minute call? A no is a fine answer, and I will not chase you weekly.

Marta

Just over eighty words, four moves, each one earning the next. The opening detail proves the message is for her. The pitch is two sentences with the basics in daylight, the bracketed range filled in before sending. The ask costs one word to answer, and the no is pre-approved. There is nothing about the company’s founding story, no culture paragraph, no buzzword sign-off; all of that survives into the call, where it belongs.

Which patterns kill replies?

Most dead outreach dies of the same few wounds.

Pattern	Why it kills the reply	Do instead
“Exciting opportunity” subject	Announces a template before the open	Name something specific to them or the role
Flattery opener (“impressive profile”)	Reads as mail merge, because it is	Lead with the one genuine detail
The company essay	Three paragraphs nobody asked for, on a phone screen	Two sentences; the rest after a yes
Hidden basics	Missing location, level or range looks evasive	Put all three in sentence two
Homework ask	CV plus availability plus a form, from a stranger	One question, answerable in a word
Manufactured urgency (“we move fast!”)	Pressure without trust reads as spam	Let specificity carry the urgency

What happens after you hit send?

Two things, and both matter more than perfecting message one. First, most replies come from the second or third touch, so the sequence deserves as much craft as the opener; there is a separate playbook for follow-ups candidates actually answer. Second, the message is a promise about the process behind it. A personal, respectful opener followed by three weeks of silence after they reply does more damage than no outreach at all, which is why outreach and candidate experience are the same project wearing two hats.

Where does Recruitifly fit?

The grind in outreach is not writing one good message, it is writing the thirtieth without sliding back into templates. Recruitifly’s assistant, Fly, drafts outreach and follow-ups from the candidate’s profile and the job, in multiple languages, and stages every message as a proposal: you add or sharpen the personal detail, then approve each send. Nothing goes to a candidate unsupervised, which for first-touch messages to strangers is the only sensible default. We are in private beta; if your reply rates are stuck, talk to us and bring a real role.