A new role cold email is a first-contact message to a person who has recently started a job or been promoted, sent inside their first 90 days, when they have a mandate to change things and no attachment to the tools they inherited. It is the best-converting trigger in most B2B sets, with 6 to 14% positive replies reported on verified lists, and the one most dependent on a fresh address: the person moved, so the finder's database address for them is the old company's.
A new leader arrives with a plan they were hired to execute and a budget nobody has spent yet. They are expected to change something, so a vendor email is not an interruption; it is input. By month four the plan is set, the vendors are chosen and the email becomes ordinary.
The second reason is that they are reviewing everything. Inherited tools, inherited data, inherited lists. If what you sell replaces or cleans up something they inherited, the first quarter is the only time the review is open.
The third reason is practical: a new contact at a known company is a new row in your database with no history of ignoring you. The database maintenance loop surfaces these for free: an address that goes from valid to invalid is usually a move, and the move is the trigger.
| Source | What it tells you | Address freshness |
|---|---|---|
| LinkedIn job change notifications | Name, new title, new company, start month | Address not included; find and verify |
| Your own bounces | A valid address went invalid: the person moved | Find the new company, then the new address |
| Press and company news pages | Senior appointments, usually with a quote on priorities | Address not included |
| Database "job change" alerts | Batch of moves by filter | Database address often lags the move by months; verify |
| Signature changes in reply threads | New title in a known contact's signature | Address usually already valid |
Every source except the last needs the address found and then verified. The person moved, which is exactly the case where a finder's stored address is wrong.
Subject: {first_name}, first quarter at {company}
Hi {first_name},
Congratulations on the {new_title} role. The first 90 days usually come with a review of {inherited_area}, and that is the part we help with.
{sender_company} gives {customer_type} {outcome} without a long implementation. {similar_company} brought us in during their new {function} leader's first quarter and had {result} by the end of it.
If {inherited_area} is on your list, I can show it in 15 minutes. If it is not, say so and I will leave you to the quarter.
{sender_name}
{sender_title}, {sender_company}
If this is not relevant, reply "no" and I will not write again.
{inherited_area} The thing they inherited that you fix: the CRM data, the outbound stack, the list{function} Their function: sales, marketing, RevOps{result} One measurable result from a comparable first quarterSubject: The bigger remit
{first_name}, congratulations on the move to {new_title}.
A wider remit usually means {inherited_area} becomes your problem, if it was not already. We take that off the plate for {customer_type}; {similar_company} saw {result} within {timeframe}.
Would a short call help, or a two-line summary to read when there is time?
{sender_name}
If this is not relevant, reply "no" and I will not write again.
{timeframe} How long the result took, in weeks or monthsSubject: Your note on {stated_priority}
Hi {first_name},
Read your post about {stated_priority} at {company}. One thing that tends to slow that down is {problem}, and it is usually invisible until month three.
We fix it for teams like {similar_company}: {outcome}, in place by {timeframe}, no change to the rest of the stack.
Open to a 15-minute conversation about whether it applies?
{sender_name}
If this is not relevant, reply "no" and I will not write again.
{stated_priority} A priority they named publicly, quoted in their words{problem} The obstacle to that priority you removeA database that shows the person at the new company may still hold the old address. Find the pattern at the new domain, generate the candidate, and confirm it with a single check or a bulk job before sending.
Pattern-inferred addresses at catch-all domains look valid to a finder. Route catch-all results to LinkedIn or a warm, low-volume sequence instead of the cold send.
The inbox of a new leader holds fifty congratulations. One clause, then the mandate. No images, one link, plain text.
Job-change lists are small and high value; do not let a cold domain's reputation decide whether the email lands.
LinkedIn alerts for your target titles, your own valid-to-invalid transitions, appointment news. Record start month; the clock runs from it.
New domain pattern plus verification. Expect a higher invalid share than usual on this list because every record is a mover.
Record which inherited area they confirmed as a priority. It predicts the next quarter's deals better than the reply itself.
Trigger, stage and role templates
When the new hire follows a raise
Pattern inference, database finders and why movers break both
Getting from a job-change notification to an address
The maintenance loop that surfaces moves from your own bounces
When the new role is the top one
Days 20 to 60 in the role. Earlier, they are still orienting. Later, the first-quarter plan is set and vendor choices are made. The window is short, so the list has to be built weekly and verified the same day.
LinkedIn job-change alerts for your target titles, appointment announcements, database job-change filters, and your own bounce data: a business address that goes from valid to invalid is usually a move. Find the new company, then the new address.
Because every contact on the list has just moved, and finders and databases often still hold the old address. Generate the candidate at the new domain and verify it before sending; treat catch-all results as unconfirmed.
Only if the connection is the point, for example a tool they used there that you integrate with. Otherwise the email is about the new mandate; the old job is their past, and reminding them of it reads as surveillance.
Teams report 6 to 14% positive replies on verified job-change lists, the highest of the trigger templates. The rate falls quickly after day 60 in the role, so timing drives the result more than copy.
Verify the job-change list, keep confirmed-valid addresses, and send inside the window. 100 free checks a month, unknowns refunded.
Ayoub built BounceZero's 5-stage validation pipeline, its dedicated BGP-announced IP infrastructure, and the Patroni HA PostgreSQL cluster behind every verification. Previously built high-volume email delivery infrastructure. Trained at 1337 Benguerir (École 42 network, 2019). Open-source: bgp_analyzer.
Templates by trigger and stage, each with the deliverability rules that apply
A funding round cold email template with two variants and merge fields
A hiring trigger cold email template that uses open roles as the signal
A technology change cold email template for tech-stack triggers
A competitor user cold email template
An after-event cold email template for conferences, webinars and trade shows
A first follow-up email template for when a cold email gets no response
Continue through related topics