How to cold email a prospect who just changed jobs

A job change is the closest thing to a free pass that cold outreach gets. The buyer is rewriting their stack in their head, their predecessor's vendor loyalties don't bind them, and they're under pressure to show wins in the first ninety days. And yet most reps blow it by sending the same "Congrats on the new role!" email that lands in the inbox of every new VP within forty-eight hours of the LinkedIn announcement.

The job-change trigger is valuable precisely because it's so widely used. Which means the bar for getting a reply is now much higher than it was three years ago. Here's how to clear it.

Time the email to the buyer's actual calendar, not the announcement date

The reflex is to fire the email the day the LinkedIn update appears. That's the worst window. The new hire is drowning in welcome notes, internal intros, and the polite-but-empty congratulations flood from every SDR with a Sales Navigator seat.

Two windows work better.

The first is roughly day 14 to day 30. The honeymoon noise has died down, the buyer has started forming an opinion about what's broken, and they haven't yet committed publicly to a plan. They're receptive to outside perspective because they're actively shopping for it.

The second window is day 60 to day 90. This is when most new executives are expected to present a plan to their CEO or board. If your product touches anything in that plan, you have leverage the previous vendor doesn't. The incumbent is associated with the prior regime; you're associated with the new one.

The dead zone is week one. Skip it.

Lead with what changed, not with congratulations

The structural problem with most job-change emails is that the opening line is about the prospect's career and the rest is about your product. The buyer reads the first sentence, registers it as flattery, and braces for the pitch.

Invert it. Open with a specific observation about the company they just joined, or the function they now own, and let the role change sit in the background as context.

Compare these two openings to a newly hired VP of Revenue Operations at a mid-market SaaS company:

Weak: "Congrats on the new role at Acme! I saw you joined as VP RevOps last month and wanted to reach out. At [vendor], we help RevOps leaders…"

Stronger: "Acme's last two earnings calls flagged sales cycle length as the drag on net new ARR. Most VPs of RevOps walking into that brief inherit a forecasting process built around stage probability, not deal-level signals, and rebuild it in the first quarter. Worth a conversation on what your predecessor left you with?"

The second version signals three things in under sixty words: you read the public filings, you understand the job they were hired to do, and you have an opinion. That's a different category of email from the congratulations flood.

Mine the gap between the old role and the new one

The most underused research lever is the contrast between where the buyer came from and where they are now. A buyer who moved from a 5,000-person enterprise to a 400-person Series C is making a deliberate bet on speed over scale. A buyer who moved laterally from a competitor brings opinions about your category that you can name explicitly.

A few patterns worth looking for:

• Up-market move. The buyer is now responsible for more complex problems than their last role exposed them to. They're hungry for frameworks and reference architectures, not feature lists.
• Down-market move. They're used to bigger budgets and more headcount. They're going to be frustrated by tools that assume they have a 15-person ops team. Lead with how the product works with a small team.
• Functional pivot. A marketing leader who became Chief Customer Officer, for example, sees the world through a different lens than their title peers. Reference the pivot directly. "Most CCOs come up through support; you came up through demand gen, which usually means…"
• Competitor migration. They know your category. Skip the education and go straight to the comparison they're already making in their head.

This research takes ten minutes per prospect. It separates the email from the templated congratulations flood entirely.

Make the ask proportional to the relationship (which is zero)

A new hire's calendar is the most defended object in their life right now. Asking for a 30-minute discovery call in the first email is asking them to spend a meaningful percentage of their available time on a vendor they've never heard of.

Better asks, roughly in order of friction:

1. A specific question they can answer in two sentences. ("Did your predecessor standardise on [tool], or is the team still on a mix?")
2. A piece of content that maps directly to their first 90 days. Not a generic ebook. A teardown of how three companies in their exact situation solved the exact problem they were hired for.
3. A 15-minute call with a named expert (a CS leader, a solutions architect), not a sales rep. The implicit promise is that the call is consultative, not transactional.
4. The full demo. Reserve this for replies, not first touches.

The point is to make the first reply cheap. Once they've responded once, the second ask can be larger.

A worked example

Imagine a new VP of Sales at a Series B fintech, hired six weeks ago from a larger competitor. Public signals: the company just raised a Series B with growth efficiency cited in the press release, the previous VP left after fourteen months, and the careers page shows eight open AE roles.

A defensible first email:

Subject: the eight AE reqs

Saw the Series B announcement and the eight open AE seats on the careers page. Most VPs walking into a hiring sprint right after a round inherit a ramp plan built for a smaller team, which is usually the first thing that breaks at this stage.

You ran a 40-rep org at [previous company], so you've seen what works at scale. Curious whether you're planning to port that playbook over or rebuild for the smaller motion.

Happy to share what we've seen work at the Series B-to-C transition specifically. Two-sentence reply is fine, or 15 minutes next week.

No congratulations. A specific observation. A reference to the move that signals research. A low-friction ask. That's the bar in 2026.

The takeaway

• Skip week one. Send between day 14 and day 30, or between day 60 and day 90, when the buyer is actually planning rather than onboarding.
• Open with an observation about the company or the role, not with congratulations. Treat the job change as context, not the headline.
• Mine the contrast between the old role and the new one. Up-market, down-market, functional pivot, and competitor moves each call for different framing.
• Keep the first ask cheap. A two-sentence question or a piece of content tied to their first 90 days will out-convert a 30-minute demo request every time.