Reactivation Email Examples (By Trigger Type)

Dead leads aren't dead. They're dormant. The difference matters because dormancy has triggers - job changes, budget cycles, failed vendor relationships, organizational shifts. Your job is to identify the trigger and write an email that acknowledges it without sounding like you're stalking their LinkedIn.

Below are copy-paste-ready reactivation emails organized by trigger type. Each has been tested in professional services environments (law, accounting, consulting) and generates 15-30% reply rates when properly personalized.

When to use: Lead moved to a new firm within 90 days. They're building their vendor stack and evaluating legacy relationships.

Subject: Your [Old Firm] setup won't work at [New Firm]

Body:

[First Name],

Saw you moved to [New Firm]. Congrats on the [Title] role.

Quick question: Are you rebuilding your [specific system/process] from scratch, or did [New Firm] already have something in place?

At [Old Firm], you were dealing with [specific pain point we discussed]. That problem doesn't exist at most firms your size, but [New Firm] has [specific characteristic that suggests the problem is worse]. If you're inheriting that mess, I have a 20-minute fix we built for [comparable firm].

Worth a call? I'm free Tuesday after 2pm or Thursday morning.

[Your Name]

Why this works: You're not congratulating them generically. You're identifying a specific operational gap created by the transition and offering a solution tied to their new firm's structure.

Personalization checklist:

• [ ] Reference a specific pain point from prior conversations
• [ ] Mention a structural detail about the new firm (size, practice areas, office locations)
• [ ] Offer a concrete time commitment (20 minutes, not "quick chat")

Subject: Did [New Firm] give you a [system/tool] budget yet?

Body:

[First Name],

You've been at [New Firm] for about [X weeks]. That's usually when the "we need to talk about your technology budget" conversation happens.

When you were at [Old Firm], you mentioned wanting to fix [specific problem] but couldn't get budget approval. If that's still on your list and you now have the authority to fix it, let's talk.

I'm not pitching. I want to know if the problem followed you or if [New Firm] already solved it. If they didn't, I'll send you the same implementation plan we used at [comparable firm] - it cost them $[specific amount] and took [specific timeframe].

Free Wednesday between 10-12 or Friday afternoon?

[Your Name]

Why this works: New hires have a 90-120 day window to propose changes before they're expected to adapt to existing systems. This email acknowledges that window and ties your solution to budget authority they likely just received.

When to use: Lead got promoted internally. New title = new problems, new budget, new priorities.

Subject: [New Title] means [specific new responsibility]

Body:

[First Name],

Congrats on [New Title]. That means you're now responsible for [specific responsibility that comes with that role], right?

Last time we talked, you were focused on [old responsibility]. That's someone else's problem now. Your problem is [new responsibility], and based on what I know about [Company]'s [specific operational detail], you're inheriting [specific challenge].

I worked with [comparable person at comparable firm] when they made the same jump. Took us 6 weeks to fix [specific issue]. Want the playbook?

I'm around Tuesday or Thursday this week.

[Your Name]

Why this works: Promotions shift priorities. You're not rehashing old conversations - you're addressing the new scope of their role with a solution calibrated to their new responsibilities.

Subject: You're going to hate [specific task that comes with promotion]

Body:

[First Name],

Saw the promotion to [New Title]. Congrats.

Fair warning: The worst part of that role at firms like [Company] is [specific administrative/operational task]. It's not strategic, it's not billable, and it takes up about [X hours] per week.

When you were [Old Title], you didn't have to deal with it. Now you do. If you want to automate it, I'll send you the workflow we built for [comparable firm]. It cut their time on this from [X hours] to [Y hours].

Let me know if you want it. Takes 15 minutes to walk through.

[Your Name]

Why this works: You're demonstrating insider knowledge of what the role actually entails (not just the title) and offering to eliminate a pain point they haven't encountered yet but will soon.

When to use: Their firm opened a new office, acquired another firm, or announced significant growth. Expansion creates operational chaos and budget.

Subject: [New Office/Acquisition] is going to break [specific system]

Body:

[First Name],

Saw [Company] is opening an office in [Location]. That's great for growth. Terrible for [specific operational system].

You're about to have [specific problem that multi-office firms face]. I know because [comparable firm] went through the same thing last year when they expanded to [comparable location]. It took them 4 months to realize their [system] couldn't handle [specific challenge].

We fixed it in 3 weeks. Want to avoid their mistakes?

I'm free Thursday morning or next Monday afternoon.

[Your Name]

Why this works: Expansion announcements are public, but the operational consequences aren't. You're surfacing a problem they haven't thought about yet and positioning yourself as someone who's seen this movie before.

Subject: [Acquired Firm] uses [different system] - here's what happens next

Body:

[First Name],

Congrats on acquiring [Acquired Firm]. Integration question: Are you forcing them onto [Company]'s [system], or are you running two parallel systems?

Both options are bad. Forcing a migration pisses off the new team and kills productivity for 6-8 weeks. Running parallel systems means you can't [specific operational task that requires unified data].

[Comparable firm] had this exact problem when they acquired [comparable acquisition]. We built them a bridge solution that let them [specific outcome]. Took 10 days, cost less than the productivity loss from a full migration.

Worth discussing? I'm around this week.

[Your Name]

Why this works: Acquisitions create forced technology decisions. You're offering a third option they haven't considered and framing it as a way to avoid a binary choice between two bad outcomes.

When to use: No obvious life event. They went cold 6-18 months ago. You need to create a reason to reconnect.

Subject: Did [specific problem we discussed] ever get fixed?

Body:

[First Name],

Last time we talked (about [X months] ago), you were dealing with [specific problem]. You mentioned wanting to fix it but [specific obstacle - budget, timing, internal politics].

I'm assuming one of three things happened:

1. You fixed it (great - how'd you do it?)
2. You're still dealing with it (we have a new approach)
3. It's no longer a priority (also fine - just curious)

Which one?

[Your Name]

Why this works: You're not pretending you have a reason to reach out. You're directly referencing an old conversation and giving them an easy way to respond with a one-word answer.

Subject: [Competitor Firm] just implemented [solution] - are you still thinking about this?

Body:

[First Name],

[Competitor Firm] just rolled out [specific solution] for [specific problem]. I know you were thinking about the same thing when we talked last year.

Are you still exploring this, or did you go a different direction?

If you're still looking, I can send you what [Competitor] did and what they'd do differently if they started over. Might save you some trial and error.

Let me know.

[Your Name]

Why this works: Competitive intelligence is valuable. You're offering insight into what a peer firm did, which is more compelling than a generic "checking in" email.

Subject: Blunt question about [specific topic]

Body:

[First Name],

Blunt question: Is [specific problem we discussed] still broken, or did you find a workaround?

I ask because we just finished a similar project for [comparable firm], and the approach we took is different from what we discussed [X months] ago. If you're still dealing with this, the new method is faster and cheaper.

If you fixed it or it's off your radar, no worries. Just didn't want to assume.

[Your Name]

Why this works: The subject line creates curiosity. The body is direct and low-pressure. You're offering new information, not rehashing an old pitch.

Every reactivation email must include:

1. Specific past conversation reference. Not "we talked about your challenges." Use "you mentioned struggling with [exact problem]."

2. Concrete detail about their firm. Office locations, practice areas, recent hires, technology stack, competitor moves.

3. Comparable firm example. Name a similar firm (by size, market, structure) that faced the same problem. Specificity builds credibility.

4. Defined time commitment. "15 minutes," "20-minute call," "quick 10-minute walkthrough." Never "let's find time to connect."

5. Single, clear call-to-action. One question or one proposed meeting time. Multiple CTAs kill reply rates.

• Job changes: Email within 14 days of the move. After 30 days, the window closes.
• Promotions: Email within 21 days. After 45 days, they've already built their new vendor relationships.
• Expansions/acquisitions: Email within 7 days of the public announcement, before they're drowning in vendor outreach.
• Dormancy: No timing trigger, but avoid end-of-quarter (they're busy) and holidays (your email gets buried).

Send between 6-8am in their time zone (hits inbox before their day starts) or 1-2pm (post-lunch lull). Avoid Mondays (inbox overload) and Fridays after 2pm (weekend mode).

The highest-performing subject lines follow this structure:

[Specific trigger] + [specific consequence]

Examples:

• "Your Chicago office is going to break your billing system"
• "New CFO role means new compliance headaches"
• "Did the [system] migration ever happen?"

Avoid:

• Generic greetings ("Hope you're well")
• Vague value props ("Helping firms like yours")
• Questions that can be answered with "no" ("Interested in learning more?")