---
name: candidate-outreach-inmail
source: https://app.decimal.ai/s/candidate-outreach-inmail@1/SKILL.md
source_sha256: 1dff0ad0f299
---

# Recruiter Cold Outreach (InMail / Email)

The first message a recruiter sends to a passive candidate who has never heard from them.
Base models default to a long, flattering, everything-about-us note: a generic opener ("I
came across your profile and was very impressed"), a paragraph of company boilerplate ("we're
a fast-growing, well-funded team backed by top-tier investors"), a pile of perks (comp,
equity, remote, unlimited PTO, great culture), and a vague or stacked ask. Passive candidates
skim that on a phone and ignore it. A cold outreach earns a reply by proving *this* message
was written for *this* person about *one* thing worth their attention.

Write every first-touch candidate outreach in these four moves.

## 1. Open with a specific role-to-candidate hook

The first line proves you know who they are and why you're reaching out to *them* for *this*
role. Reference a concrete detail from their background — a system they built, a domain they
work in, a technology on their profile, the kind of team they've led — and connect it to what
the role needs.

- Never open with generic flattery: "I came across your profile and was impressed", "Your
  background is amazing", "You have an incredible profile." These say nothing and mark the
  message as a blast. Cut them — start on the specific detail.
- One or two sentences. State the observation and the connection to the role, then move on.
- The hook is a *fit* claim, not a compliment: "you've scaled a payments system past X" →
  "this role owns exactly that problem," not "you seem very talented."

## 2. Give the role's ONE headline draw

Pick the SINGLE most compelling thing about *this opportunity for this candidate* and say it
plainly — the scope, the problem, the team, the growth, or the mission that would actually
make them consider a move.

- Choose one. If the role has five selling points, name the one that maps to what this
  candidate is likely to want given their background. Listing all five buries the one that
  matters and reads as a template.
- Frame it as what *they* get to do or own ("own the pricing platform from zero", "first
  infra hire, you set the architecture"), not a company brag ("we raised a Series B").

## 3. No company boilerplate, no perk-dump

Do not paste a paragraph about the company's funding, investors, growth rate, or awards, and
do not enumerate perks (comp band, equity, remote policy, PTO, snacks). A cold outreach is
not a job description. One concrete draw beats a bulleted list of benefits. If you're tempted
to write "we also offer…", stop — that belongs in a later conversation, not the first touch.

## 4. Close with ONE low-friction ask

End with a single, small, easy-to-answer request — an invitation to talk, not a task.

- Make it low-commitment: a yes/no question or a tiny time cost — "Open to a quick chat this
  week?", "Worth a 15-minute call to see if it's a fit?", "Mind if I send a few details?" A
  single reply should satisfy it.
- Never ask them to apply, fill out a form, or send a resume in the first message, and never
  stack asks ("reply with times, send your resume, and let me know your salary expectations").
  Each extra request is a reason to defer, and asking a passive candidate to *apply* assumes a
  decision they haven't made yet.

## Length

Keep the whole message under ~125 words. Short is the point — a passive candidate skims it in
seconds between meetings. If it runs long, the hook and the ask are the parts that survive;
cut everything else.

## Worked shape

Candidate: a staff engineer whose profile points to years spent building large-scale search
and ranking infrastructure at a consumer marketplace. Role: first platform hire at an
early-stage company, owning the core indexing and query system. A conforming message:

> Your work on the search infra at [their company] caught my eye — you've been living in
> exactly the latency-and-relevance problems this role is built around.
>
> We're hiring our first platform engineer to own the indexing and query stack top to bottom —
> you'd set the architecture rather than inherit someone else's.
>
> Open to a quick chat this week to see if it's a fit?

Notice: the opener names a specific detail from their background tied to the role, exactly one
headline draw (owning the system as first hire), no funding/perk paragraph, one small ask that
isn't "apply" — and it's well under 125 words.