When a company announces layoffs, most people see disaster. Your prospect just got fired or lost their job. Why would they take your email seriously?

Because layoffs create one of the most predictable buying triggers in B2B - and most of your competitors won't know how to use it.

Here's what actually happens: people who get laid off become decision-makers at new companies faster than anyone else. They're motivated. They're actively job hunting. They're meeting people. And within 60-90 days, many of them land somewhere - often in roles with hiring authority or influence over vendor decisions. That's your window.

The mistake most people make is trying to email them during the shock period (day 1-14). They're not thinking about work solutions. They're updating their LinkedIn, fielding recruiter calls, and maybe drinking. Wait for the signal that they've landed somewhere new, then move.

Timing: The 30-60 Day Window After They Land Somewhere

You need to know when they actually got hired, not when the layoff happened. Layoff announcements are public, but job transitions aren't - at least not immediately.

Here's how you find the signal:

Once you see the update, wait 14 days before emailing. They're still onboarding. Day 14-60 is your sweet spot - they're settled enough to engage, but early enough to influence priorities in their new role.

The Email Structure That Works

Your subject line needs to acknowledge the transition without being weird about it. You're not saying "congrats on getting laid off" - you're being direct about knowing they're in a new role.

Subject line example:

"Saw you just moved to [Company] - quick thought on [department/function]"

Or:

"New role at [Company]? One thing I'd audit first"

Don't use "congratulations" or exclamation points. It feels tone-deaf. These people just got fired. They're proving themselves at a new job. Stay businesslike.

The Opening: Show You Did Your Homework on Their New Situation

Your first line should reference something specific about their new company or role - not about them personally or the layoff.

Bad opener:

"Hey [Name], I saw you just joined [Company]. Congrats on the new role!"

Good opener:

"[Name] - I noticed [Company] brought on 3 new people in your department in the last month. That kind of growth usually means one thing: they're auditing their [vendor/process/tool] stack to scale."

The second one works because you're:

Then your hook is: you've seen this exact scenario before, and there's usually one thing newer teams miss.

The Core Message: What Problem Can You Solve Faster?

People in new roles want to make an impact in their first 90 days. They want to find quick wins. Your job is to position yourself as someone who helps them do that.

Generic example (adjust to your service):

"The issue we usually see with newly scaled teams: they inherit vendor relationships from the old team, but nobody's questioned whether those are actually the best fit for how they're operating now. Different priorities, different tools needed."

Then: "What's your current [department/process] setup looking like after the transition?"

This works because it's not a pitch. It's insight wrapped in a question. You're positioning yourself as someone who understands the pain that comes with onboarding into a new company - and you've helped people solve it before.

The CTA: Make the First Step Stupidly Easy

Don't ask for a call. Ask for a conversation about one specific thing.

Bad CTA:

"Would love to jump on a call and talk about how we can help."

Good CTA:

"Quick question: are you still running [old system] or did the new team want to revisit that coming in?"

If they respond yes, the next email can ask for a call. But your first email is just asking for information. It's conversational. It lowers the barrier to response.

Sequence Strategy: Multi-Touch Across 10 Days

One email gets maybe 2-3% open rate if you nail the subject line. You need a sequence. Here's what works:

Email 1 (Day 0): The opener we outlined above. Insight + question.

Email 2 (Day 3): No response? Send a one-liner follow-up. Don't repeat yourself. Just add new information: "One more thing I meant to mention - saw [Company] is expanding in [region/vertical]. That usually affects [relevant process/vendor] strategy."

Email 3 (Day 7): Final touch. Short. "Last one from me - just wanted to make sure this landed. Let me know if any of this is relevant to what you're building over there."

Stop at 3. If they haven't engaged by day 7, they're not interested right now. Move on.

Pro tip: If they do respond with "not right now" or "we're good", don't pitch. Just ask: "Got it. When do you usually revisit [vendor/process] decisions?" Keep the relationship warm. They'll remember you asked good questions.

List Building: Where to Find Recent Movers

This is the hard part. You need a data source that shows recent job changes fast enough to be useful (within 30 days ideally).

The best approach: combine 2-3 sources. No single tool catches everyone, and timing matters. You want the newest data possible.

Expectations: What Your Numbers Should Look Like

Layoff trigger emails should outperform your baseline cold email by 15-25% on open rate (because the subject line references something specific they just experienced). That puts you at roughly 18-28% open rate if your baseline is good.

Reply rate is typically 3-6% if your opening insight is actually valuable and not generic. That's higher than regular cold email because you're reaching people in a moment where they're actively problem-solving.

Close rate depends entirely on your product, but these conversations tend to move faster - newly hired people have more authority and more motivation to implement changes quickly.

The Gap Between Knowing This and Running It at Scale

In theory, this is straightforward: find people who got laid off, wait for them to land, send a smart email. In practice, it requires constant list maintenance (tracking 50+ people across multiple data sources), sequence management (making sure follow-ups go out on time without spamming), and copywriting that actually reflects your service instead of sounding generic.

If you're doing this yourself, you're managing the data pipeline, testing subject lines, handling replies manually, and trying not to miss your 30-60 day window. That math doesn't scale much past a handful of conversations per month.

If you want this to run reliably at 5-10+ meetings per month - where data, sequences, copy, and replies are all handled - that's where having a system built for it matters. We've spent the last few years building this specific trigger into our cold email infrastructure because the window is tight and the potential is real. That's what takes the framework you just read and turns it into a sustainable pipeline.

Related Guides