I sent recruiter messages the lazy way: a templated paragraph with the role name swapped in. The reply rate was near zero, and fair enough — the messages sounded like they'd gone to a thousand people, because they had. The fix wasn't more volume; it was making each one clearly about the specific person.

Recruiterly is the tool I use to write that first message. You give it a candidate profile and your open role, and it returns a warm, specific LinkedIn or email message with a profile-aware hook and a role-fit reason, in a low-spam tone. The point is to start from the person, not the job description.

Why templated outreach fails

A template signals "I didn't look at you." Candidates, especially passive ones, can feel that instantly, and the message is deleted before the second line. The work that earns a reply is showing you read their profile and can name why this role fits them — and that work is exactly what templates skip.

The tool's job is to make that personalized draft cheap. It pulls the hook from the profile you paste and ties it to the role, so the message opens with the candidate's context instead of your opening. That single move changes whether the rest gets read.

What "low-spam tone" means here

Recruiting messages fail two ways: too generic, or too pushy. I set the tone to stay specific without being urgent, and Recruiterly gives both a LinkedIn and an email variant so the same outreach fits the channel. The role-fit reason is the spine — if it's weak, the message is weak, and the tool makes you see that instead of hiding it.

I still rewrite the hook when the profile is thin, because a generated line from three bullet points can ring hollow. But having a structured first draft beats a blank compose box, and the fit reason keeps me honest about whether I should message this person at all.

Honest limits

It drafts outreach; it doesn't source candidates or guarantee replies, and it won't know if someone's open to moves. The quality depends entirely on the profile you paste — a thin profile yields a thin message. Used carelessly it can still read as mass mail if you don't edit. Treat the output as a starting point that earns a reply only when you make it genuinely about the person.

How I keep it from reading as a blast

The discipline is editing the hook for every send, even when the draft is fine. A generated line that names a project from the profile reads personal; a generic "I came across your profile" reads like the other forty they got. I'll also cap volume — if I'm messaging more than a handful of people, the messages should differ for real reasons, not just swapped names. Recruiterly makes the draft cheap, but the personalization is still mine to do. The tool earns the open; the edit earns the reply.

FAQ

What input does it need?

A candidate profile and your open role. From those it writes a LinkedIn or email message with a profile-aware hook and a reason the role fits the person.

Does it give both channel versions?

Yes. It produces a LinkedIn variant and an email variant so the same outreach reads right on each platform, in a low-spam tone.

Will this get me more replies?

It improves the message by making it specific to the person, which helps, but it doesn't source candidates or promise responses. A thin profile still yields a weak message.

Is the output ready to send as-is?

It's a draft. Edit the hook, especially when the profile is brief, and confirm the role-fit reason is real before sending, so it doesn't read like a blast.