The cold email after a leadership change.
Leadership-change signals reward patience like no other category. Send week 1, get archived. Send week 4–10, get a meeting. The timing arc that separates the over-eager from the right-on-time, three worked examples by exec role, and the single discipline that turns the second-most-overused signal in outbound into one of the highest-yielding.
What counts as a leadership-change signal.
Not all "leadership changes" deserve outbound. The signal you want is a person with new budget authority moving into a category where you can credibly help. A new CMO who's about to rebuild the martech stack is a high-yield signal for a CDP vendor. A VP Engineering promoted internally without budget movement is a much weaker one for the same vendor.
The four sub-types that actually move
- External VP+ hires. Highest signal weight. New executive walks in with a mandate, a 90-day plan, and usually a list of vendors they want to evaluate from their previous role. The window is 4–10 weeks post-start, after the assessment phase but before vendor decisions are locked.
- External C-suite hires (CRO, CMO, CHRO, CFO, CTO). Same dynamic as VP hires but with broader budget. The category overhauls these drive last 6–12 months. Worth tracking for months, not weeks.
- Internal promotions to a new scope. Softer but valid signal — when an internal hire is given a new function (e.g., promoted from Director of Marketing to VP Growth covering new categories), they're often more receptive than an external hire because they don't have the "I have my preferred vendors" bias.
- Departures of the previous owner. Often missed. The 4-6 weeks after the previous decision-maker leaves but before the replacement starts is a structural opening — the team is operating without a champion for existing tools, and entrenched relationships are weakest.
The timing arc is the whole game.
Most playbooks treat timing as a footnote. For leadership-change signals, timing isn't a footnote — it's the entire thesis. The arc below is from ~ 220 campaigns where we have permission to cite the data. Reply rates by send-week, against the same role / same category / same ICP fit.
The single most counterintuitive lesson in outbound is buried in this chart. The fastest senders — the ones who fire on day 2 — get worse reply rates than ICP baseline. Patience is a competitive advantage when the field is racing to be first.
The implication: most leadership-change outbound is sent at exactly the wrong time. The day-of and week-1 sends pile into an inbox the exec hasn't even sorted yet. The week-7 sends land when the exec is actively forming opinions about what their stack should look like. Same email, same ICP — the timing alone changes reply rate by an order of magnitude.
Why most of these openers fail.
Four patterns that appear in roughly 80% of the leadership-change outbound corpus we've audited.
- "Congrats on the new role!" as the opener. The exec received 200+ of these in week 1. Even from people they actually know. Yours is indistinguishable in the wash.
- Sent too early — usually day-of. Sales-tech vendors get LinkedIn notifications and fire same-day to look fast. The exec hasn't had a 1:1 with their team yet; vendor pitches register as noise.
- Pitching against the previous decision-maker's choices. "Now that [previous CRO] is gone, you're probably reconsidering the sequencer choice." Reads as opportunistic. The new exec hasn't decided anything; the framing assumes they have.
- No reference to the actual context the exec is walking into. Generic "as you build your team" boilerplate. The exec wrote a real reason for joining; reference it.
The 4-line frame, timing-aware.
Same structural skeleton as the funding-round playbook, but with timing as the gating variable. The frame only works if you send in weeks 5–8. Sending the same email in week 1 will underperform regardless of how good the lines are.
most teams at this point or the pattern we've seen. Positions you as someone who's been at this exact crossroads before.
Three rules specific to this signal type:
- Send Tuesday–Thursday morning during the window. Monday inboxes are still full from the weekend; Friday emails land at the wrong cognitive moment for vendor evaluation.
- Reference what they said publicly — not what someone else said about them. The exec's own LinkedIn post or interview is the credible source. Press-release blurbs read as templated because they were templated.
- Never use the previous exec's name in line 1. Triangulating off the predecessor reads as politically tone-deaf in the new exec's first 90 days.
Three worked examples by role.
Same frame, three different exec roles, three different industries. All sent in weeks 5–8 of the new role. Reply rates are real — names anonymized, patterns intact.
Example 1 · New CRO at a Series C SaaS company
The Forum interview last month — the line about "Crestbound needs buying-cycle visibility before we touch the sequencer stack" stuck with me. Most CROs land somewhere on that question in their first 60 days; you said it on day 12.
The pattern at the next 3 CROs I've worked with who started from the same place: pipeline visibility outpaces the sequencer rebuild by about a quarter. The ones who fixed the visibility first ran the sequencer migration with way less politics later.
Curious — is the visibility piece staying as a Q3 priority, or did it move once the team gave you the actual pipeline picture?
If useful, I'll send the 2-page write-up of how the other 3 sequenced it — no deck, just the doc.
James
Example 2 · New VP Engineering at a Series B fintech
Saw the LinkedIn post about the platform-team build at Loftbank — specifically the "we're separating platform engineering from product engineering" decision. That decision usually lands in the first quarter for new VPs and the org-chart implication runs for a year.
The recurring pattern from 4 fintech VPs we've helped through the same split: the platform-team's first 90 days get eaten by incident-response work that should be auto-resolved. By month 4 it's structural and hard to claw back.
Are you planning to staff platform with senior IC hires day 1, or building the team behind the product roadmap and hoping incident load stays manageable?
Either way I'd be curious — and if you want the playbook on how the 4 sequenced platform hiring vs incident load, it's a 1-pager I'll send.
Nina
Example 3 · New CHRO at a Series A SaaS company
The All-In podcast appearance — the bit about "Northpath needs to hire 30 people in the next quarter without breaking the perf-management cadence" was the most specific thing I've heard a new CHRO say in months.
The pattern that derails this for new CHROs at the Series A → B inflection: the existing perf cycle was built for 40 people, and the manager-1:1 cadence breaks at around 70. The fix is usually 6 weeks of work that nobody scopes until the month-3 manager survey reveals it.
Is the perf cycle one of the things you're auditing in the first 90 days, or is it queued behind the comp work most CHROs do first?
If useful, I have a 1-page "what breaks at 70" doc from 5 other Series A CHROs we've worked with — happy to send.
Elena
The receipts test.
Every leadership-change email going out should pass: is there a phrase in line 1 the exec themselves would recognize as their own? If no, rewrite. If yes, the timing window is the next gate.
When not to use this signal.
Four situations where the leadership-change signal is the wrong anchor:
- It's a Senior Director or Director-level hire. The reply-rate math falls off sharply below VP. Skip and wait for the VP+ replacement when it comes.
- The exec joined a company that's not in your ICP. A new CRO at a company you couldn't sell to before is still a company you can't sell to. The signal doesn't override the fit problem.
- You're outside the week 4–10 window. Sending earlier means competing with 200 welcome notes. Sending later means competing with already-formed vendor shortlists. Wait for the next signal on the same account if you missed the window.
- The exec has no public statement about their plans. Without a quotable line about what they're building, your email defaults to "congrats" boilerplate. Skip the signal — use a different one on the same account.