Leadership-change opener — 4 variants.
Four templates for the four exec roles where the leadership-change signal yields most: CRO, VP Engineering / CTO, CHRO, CFO. Each variant has a fill-in template, the worked example we sent, and the timing window it assumes. Read alongside the leadership-change playbook — the timing arc is the whole game.
New CRO — sales transformation
The CRO inherits an existing GTM org with existing tools, existing reps, existing pipeline. Their first 90 days are diagnostic. The opener that works is the one that helps them see a pattern they're already trying to articulate.
The {{source}} last month — the line about "{{public_quote}}" 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 {{n_others}} CROs I've worked with who started from the same place: {{pattern}}. The ones who fixed it first ran the rest of the transformation with way less politics later.
{{fork_question}}
If useful, I'll send the {{artifact}} — no deck, just the doc.
— [your_first_name]
{{n_others}} should be 2-5; "we've helped 50 CROs" reads as templated.
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
New VP Eng / CTO — engineering rebuild
VP Eng / CTO transitions follow a structural pattern: the new exec is making org-chart and platform-vs-product decisions in the first quarter. The opener that lands is the one that names the actual structural decision.
Saw the {{source}} about {{public_quote}} at {{company}} — specifically the structural decision around it. That kind of decision usually lands in the first quarter for new VPs and the org-chart implication runs for a year.
The recurring pattern from {{n_others}} VPs we've helped through the same shape: {{pattern}}. By month 4 it's structural and hard to claw back.
{{fork_question}}
Either way I'd be curious — and if you want the {{artifact}}, it's 1 page.
— [your_first_name]
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
New CHRO — people-ops scaling
The highest-yield variant in our leadership-change template family. CHROs at the Series A → B inflection are making people-ops decisions in real time, often without the budget authority they need; that combination of pressure and openness makes the right opener land harder than any other exec role.
The {{source}} appearance — the bit about "{{public_quote}}" was the most specific thing I've heard a new CHRO say in months.
The pattern that derails this for new CHROs at the same shape: {{pattern}}. The fix is usually {{specific_pitfall}} that nobody scopes until the month-3 manager survey reveals it.
Is the {{specific_topic}} 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 "{{artifact}}" doc from {{n_others}} other CHROs we've worked with — happy to send.
— [your_first_name]
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
New CFO — finance-ops rebuild
The CFO variant has the smallest field — fewer CFOs hired per quarter, so less inbox competition. The trade is that the bar for credibility is higher; CFOs are pattern-matchers and they spot template-shaped emails fastest.
The {{source}} mentioned {{public_quote}} — usually means {{specific_pitfall}} is on the desk inside the first 90 days. The first close after a CFO transition tends to surface it.
The technical pattern from {{n_others}} growth-stage CFOs we've worked through the same shape: {{pattern}}. Most teams build a manual workaround in month 2 and regret it by month 5.
{{fork_question}}
Happy to send the {{artifact}} we wrote for one of the others — covers the {{n_edge}} edge cases. 1 page.
— [your_first_name]
The Q1 earnings prep memo mentioned ASC 606 cleanup as a Q2 priority — usually means the revenue-recognition migration off the existing spreadsheet model is on the desk inside the first 90 days. The first close after a CFO transition tends to surface it.
The technical pattern from 4 growth-stage CFOs we've worked through the same shape: the manual ASC 606 spreadsheet built for 40 contracts breaks somewhere around 120, and the audit team starts asking the right questions at year 3. Most teams build a manual workaround in month 2 and regret it by month 5.
Are you planning to handle this in-platform via the NetSuite revenue module, or has the FP&A team scoped a third-party rev-rec tool?
Happy to send the rev-rec migration spec we wrote for one of the others — covers the 8 audit-attention edge cases. 1 page.
— Tash
How to use these.
Notes from running these templates across customer campaigns.
Pick the variant by exec role, not by personal preference. The CRO variant doesn't work for CHROs (the operating tempo is different) and vice versa. Each variant is tuned for the role's specific 30/60/90 rhythm.
The timing window is non-negotiable. Sending the CHRO variant in week 1 will return week-1 reply rates regardless of how good the email is. The variants assume you're sending in the documented window — usually weeks 5–8. See the timing arc in the playbook.
Skip if you can't quote the exec. The {{public_quote}} field is the single most important variable. If the exec hasn't said anything publicly that's specific enough to quote, skip the signal and use a different anchor on the account.
Build the artifact before you send. Line 4 promises a 1-page doc. If you don't have it ready when they reply, the reply dies. Build the doc per ICP segment so you can deliver same-day.
The template is the easy part. The public quote per exec is the hard part.
Mama's exec-move signal pulls the start date, the LinkedIn posts, the press interviews, and the previous-role context per exec — so when you sit down to fill {{public_quote}}, the right line is already in the brief.