Opening on the hire

The note references the posting and says one true thing about what the role will face. No pitch, no link, no product name, no "our platform". The signal is the reason to talk; the product comes after they answer.

The pattern

[Saw / noticed] you're [opening / hiring] [the role]. [One true thing about what that role faces in its first weeks]. [Soft offer to share, or nothing].

Under 200 characters for a connection-request note. Under 60 words for a first message after they accept.

Examples

First SDR:

Saw you're opening a first SDR role. The first 90 days usually go into list building before anyone sends an email. Happy to share what we see work at that stage if useful.

RevOps hire:

Noticed the RevOps opening. The first thing that role inherits is usually three tools that disagree on the pipeline number. Curious which one you trust today.

Repost:

Saw the SDR role is back up. While you look, happy to share what the role would spend its first month on; it is rarely what the JD says.

First Head of Sales (contact the founder):

Saw you're hiring a Head of Sales. The handoff from founder-led usually stalls on the list, not the pitch. Would like to compare notes if you're open to it.

What each example does

• Names the posting, so the note could not have gone to anyone else.
• Says one thing that is true of that role at that stage, which the buyer recognises because they wrote the JD.
• Ends with an offer to share or a question they can answer in one line. No calendar link, no deck.

Anti-patterns

Rewrite any draft that contains:

• the product name, a feature, a pricing word
• "we help companies like yours"
• a mention of the recruiter, or of having seen the post through a tool
• "congrats on the growth" (a hire is not growth; it is a problem)
• two people at the same company in the same week
• a note that would work for a fifth SDR hire and a first one alike