Stack-change opener — 4 variants.
Four templates for the four ways a tech stack changes: a tool gets dropped, a tool gets added, a tool gets swapped for a competitor, or the org runs a full migration. Each variant has a fill-in template, the worked example we sent, and reply-rate context from the campaign.
Drop — tool removed
The buyer's team removed a tool from their stack and hasn't added anything to replace it yet. You have a 30-day window where they're acutely feeling the gap and haven't committed to a successor.
Noticed {{company}} stopped running {{old_tool}} {{detection_window}} — saw it in our tech detection.
Most teams that drop {{old_tool}} end up with {{role_pain}} inside a month. Painful gap to manage manually while the team evaluates the next step.
{{our_one_liner}} — meant for exactly this in-between window.
{{specific_ask}}
— [your_first_name]
Noticed Northbeam stopped running Apollo in the last two weeks — saw it in our tech detection.
Most teams that drop Apollo end up with reps losing the per-account context they used to anchor first touches, inside a month. Painful gap to manage manually while the team evaluates the next step.
We're the research layer that fills the gap — briefs auto-write into whatever sequencer you land on, so the reps don't lose the muscle memory.
Want me to send the 4-line summary of what the integration looks like?
— Asif
Add — tool added
The buyer added a new tool to the stack. The buying impulse for an adjacent or complementary product is highest in the 3 weeks after adoption, while they're still tuning the new setup.
Saw {{company}} spun up {{new_tool}} {{detection_window}} — solid pick for the stage you're at.
The one piece {{new_tool}} doesn't do alone is {{role_pain}} — most teams realize that in week 3 and either build it in-house or bolt on a layer for it.
{{our_one_liner}} — plugs into {{new_tool}} directly, no extra workflow.
{{specific_ask}}
— [your_first_name]
Saw Lattice spun up Outreach in the last 9 days — solid pick for the stage you're at.
The one piece Outreach doesn't do alone is the per-account research layer that makes the first email actually personalized — most teams realize that in week 3 and either build it in-house or bolt on a layer for it.
We're that layer — Outreach-native, briefs auto-push into every sequence step, no extra rep workflow.
Want me to send a 4-line summary of how the Outreach integration works?
— Asif
Swap — competitor replaced
The buyer removed one tool and added a direct competitor in the same window. Highest-reply-rate variant in our data — the buyer is in active evaluation mode and the swap proves they'll switch when something's worth switching for.
Noticed {{company}} swapped {{old_tool}} for {{new_tool}} {{detection_window}} — saw the migration in our tech detection.
Every team I've watched make that specific switch loses two things in the first month: {{role_pain}}. {{new_tool}} is great at what it does, not at what {{old_tool}} did.
{{our_one_liner}} — fills the specific gap that opens when you make this swap.
{{specific_ask}}
— [your_first_name]
Noticed Northbeam swapped Apollo for Outreach in the last two weeks — saw the migration in our tech detection.
Every team I've watched make that specific switch loses two things in the first month: the prospecting data that lived inside Apollo, and the per-account context reps used to anchor their first touches. Outreach is a great sequencer, not a research surface.
We're the research layer that fills the gap — Outreach-native, briefs auto-push into every sequence step.
Want me to send the 4-line summary of what the integration looks like in your Outreach instance?
— Asif
Migration — full lift
The buyer is mid-migration of a whole stack category (e.g. moving off Salesforce to HubSpot, or moving warehouses). Longer window than the other three — migrations take 60–120 days — but stronger signal: they're actively committing budget and rep-hours.
Saw {{company}} kicked off the {{old_tool}} → {{new_tool}} migration {{detection_window}} — that's a serious lift, congrats on getting it scoped.
The piece that usually gets left for "phase 2" and then never happens is {{role_pain}}. We've watched it become the biggest regret 4 months post-cutover, three times running.
{{our_one_liner}} — meant to be scoped in during the migration, not bolted on after.
{{specific_ask}}
— [your_first_name]
Saw Acme kicked off the Salesforce → HubSpot migration last month — that's a serious lift, congrats on getting it scoped.
The piece that usually gets left for "phase 2" and then never happens is the per-account research data that used to live in Salesforce reports. We've watched it become the biggest regret 4 months post-cutover, three times running.
We're the briefs-per-account layer that plugs straight into HubSpot — meant to be scoped in during the migration, not bolted on after.
Worth a 15-minute look at how to scope it into your phase 1?
— Asif
How to use these
Three rules from running these across 9 campaigns:
Pick one variant per account, not all four. If you can't tell which variant applies, the signal isn't strong enough to anchor a cold email on. Wait for the next signal.
Rewrite {{role_pain}} per role, not per company. The pain a Director of SDR Ops feels from an Apollo drop is different from the pain a Head of Sales feels. Same signal, two different consequences. The template gives you the structure — the role-specific consequence is the only part you actually have to think about.
The "specific ask" sentence is more important than the variant choice. A bad ask kills a good template; a good ask saves a mediocre one. We're publishing a separate CTA playbook soon — for now, default to "want me to send the 4-line summary?" — it works.
Want stack-change signals fired into your inbox the day they happen?
Connect a CRM. Mama detects drops, adds, swaps, and migrations across every account in your list — and drafts the right variant for each, weekly.