The hiring-signal opener
The account just posted roles that imply the problem you solve is now owned by someone.
Subject[Company] + the [role] you just opened
BodyHi [First name],
Saw [Company] opened two [role] roles this month. That usually means [process] just became someone's job rather than something the team absorbed between other work.
We help [similar company type] teams get [specific outcome] before the new hires inherit a process nobody documented.
Worth a look, or is this already handled?
Why it worksThe hire is a public, verifiable signal, and the inference (a process just got an owner) is specific enough to be wrong. That makes it a real claim rather than flattery, and the close gives an easy out.
The migration follow-up
Second or third touch, after an opener that got no reply. Adds a new angle rather than repeating.
SubjectRe: [Company] + [role]
BodyHi [First name],
Following up with something more useful than a nudge.
When teams move to [platform], the part that usually slips is [specific downstream process]. It works fine at current volume and quietly breaks around [threshold].
If that is not a concern yet, happy to be told so. If it is, I can send how [customer type] handled it in one paragraph.
Why it worksA follow-up has to add a new reason to care, not restate the first email. This one introduces a fresh, concrete failure mode and offers something small instead of asking for time.
The narrow proof email
You have a governed, verifiable customer result that matches the prospect's shape closely.
SubjectHow [Customer] handled [specific problem]
BodyHi [First name],
[Customer], also [shared attribute], had the same issue with [process]: [one-sentence description of the before state].
They changed [one specific thing], and [specific, bounded outcome].
Not claiming your setup is identical. If it is close enough to be worth ten minutes, I will send the details either way.
Why it worksIt names one comparable customer, one change, and one bounded outcome, then explicitly refuses to overclaim. The disclaimer raises credibility rather than weakening it.
Questions
How much should I edit these templates?
Replace every bracket with something specific and verifiable about the account. A template sent with generic placeholders filled by merge tags reads exactly like the mail-merge email it was meant to replace.
How long should a cold email be?
Short enough to read on a phone without scrolling, usually 50 to 90 words. These templates sit in that range: one signal, one implication, one ask.
Why is the call to action so soft?
A first touch asks a stranger for a commitment. A soft ask, such as checking whether a topic is relevant, lowers the cost of replying and tends to earn more responses than pushing for a meeting.