WIN-BACK EMAIL SEQUENCES

Jake McMahon — ProductQuant

8+ years B2B SaaS · Behavioural Psychology + Big Data (Masters)

Cancelled accounts come back when the message matches the reason they left.

Your current win-back emails treat every cancelled account the same. This sprint builds reason-segmented sequences with specific offers, timing, and copy for each cancellation segment.

Start the Sprint → See what’s included ↓

At least 4 segmented sequences with timing and copy — or full refund.

WHAT YOU HAVE AT THE END

Cancellation taxonomy Every reason categorised and mapped to a win-back strategy

4–6 sequences built Different sequence per cancellation reason, 3–4 emails each

Timing framework When to send each email post-cancellation, per segment

Re-activation offers Specific offer per segment — discounts, feature unlocks, concierge

ESP implementation guide Ready to load into your email platform

Fixed price · Guaranteed delivery

We build emails that bring customers back.

You get a set of targeted email sequences. Each one addresses a specific reason someone cancelled, so your message actually fits.

CUSTOMER SUPPORT

A customer says, "It's too expensive."

They get an email with a limited-time discount or a cheaper plan option. This directly answers their reason for leaving, making them more likely to reconsider.

PRODUCT TEAM

A user tells you, "I couldn't figure it out."

They receive a simple guide and an offer for a free onboarding call. This removes the frustration that caused them to cancel and shows you want to help.

SALES CALL

A prospect asks, "Does it do [specific feature]?"

If they cancelled because it didn't, they now get an email announcing that feature is live. This shows you listened and solved their problem.

WEEKLY REPORTING

Your report shows many 'lack of use' cancellations.

Those users get a re-engagement sequence with tips and a reminder of their unused benefits. It wakes up dormant accounts before they're lost for good.

DELIVERY

Guaranteed

Ready-to-send sequences delivered. Cancellation taxonomy, segmented emails, timing, and ESP implementation guide — all included.

GUARANTEE

4 sequences

At least 4 sequences designed to recover cancelled accounts — segmented by why they left — or full refund.

FIXED PRICE

One Price

One price. Everything included. Cancellation taxonomy, sequences, timing framework, re-activation offers, and implementation guide.

--- *Note: This section is clean regarding price, as the price is not in the hero. The description is fine.*

THE WIN-BACK EMAILS YOU HAVE NOW AREN’T WORKING

One generic email, then silence

“We send one ‘we miss you’ email and that’s it. If they don’t come back from that, we never contact them again.”

Head of Growth — B2B SaaS, $4M ARR

Same message to every churned account

“Our win-back rate is low because every churned account gets the same message. The person who left over price gets the same email as the person who left because they outgrew us. Of course it doesn’t work.”

VP Marketing — Series B

Cancellation reasons are a black box

“We don’t even know why most accounts cancelled. We have a cancellation survey but the data is messy and nobody has structured it into anything we can act on. So we just send the same email to everyone.”

Product Manager — B2B SaaS

Winnable accounts mixed in with the rest

“The accounts we could win back are mixed in with the ones we can’t. Someone who cancelled because of a bug we fixed is sitting in the same list as someone who shut down their company. We treat them identically.”

Lifecycle Marketing Lead — $6M ARR

WHAT THIS TYPICALLY REVEALS

Your churned accounts are recoverable. You’re just sending them the wrong message.

Price-sensitive churners respond to completely different messaging than feature-gap churners.

Offering a discount to someone who left because a feature was missing insults them. Offering a new feature to someone who left over price wastes their time. The reason they left determines the only message that works.

Timing matters more than you think — and the window is shorter than expected.

An email sent 3 days after cancellation performs very differently from one sent at 30 days. The optimal timing varies by cancellation reason, account value, and how long they were a customer before leaving.

High-value accounts that churned recently are recoverable at a much higher rate than the average.

When you segment by account value and recency, the top tier often has a significantly higher win-back rate than your overall average. But those accounts are buried in the same list as accounts that will never return.

A structured re-activation offer beats a generic discount every time.

Some segments respond to a temporary price reduction. Others respond to a concierge onboarding call. Others respond to hearing that the feature they needed has shipped. The offer has to match the reason they left — not your default incentive.

WHY THIS IS DIFFERENT

Generic win-back emails fail because they treat every cancelled account as the same problem. They’re not.

A founder who cancelled because they ran out of budget is a completely different recovery target than a team lead who cancelled because a competitor offered a feature you didn’t have. Sending both the same “come back, we miss you” email is why your win-back rate is low.

This sprint starts by building a cancellation reason taxonomy from your actual data — cancellation surveys, support tickets, Stripe metadata, whatever you have. Then it builds a separate email sequence for each reason, with timing and offers matched to the specific situation. Your lifecycle team loads the sequences into your ESP and the segmentation runs automatically from that point forward.

TIMELINE

Segmented sequences loaded and ready to send.

DAYS 1–3

Taxonomy + Segmentation

Cancellation surveys, support tickets, and Stripe data reviewed. Cancellation reasons categorised into actionable segments. Account value tiers mapped. Winnable vs. unwinnable accounts separated.

→

DAYS 4–7

Sequences + Copy

4–6 win-back sequences written. 3–4 emails per sequence. Timing framework built for each segment. Re-activation offers designed per cancellation reason.

→

DAYS 8–10

Review + Handover

All sequences reviewed and refined. ESP implementation guide completed. Walkthrough session with your lifecycle or growth team. Everything handed over — ready to load and send.

Cancelled accounts start receiving their first win-back message

WHAT YOU GET

Four to six sequences. Each one written for the specific reason they left.

Days 1–3 · Taxonomy

Cancellation Reason Taxonomy

Every cancellation reason your product generates, categorised into segments that map to different win-back strategies. Built from your actual cancellation data — surveys, support tickets, Stripe reasons, and CRM notes.

Cancellation reasons grouped into actionable segments
Account value tiers mapped to each segment
Stop spending recovery budget on accounts that were never coming back
Data gaps identified — what to start collecting for better segmentation

Days 4–7 · Sequences

4–6 Segmented Win-Back Sequences

A separate email sequence for each cancellation reason segment. 3–4 emails per sequence, written specifically for the situation that caused the cancellation. Not templates — actual copy your team can send.

Unique sequence per cancellation segment — price, competitor, feature gap, etc.
Subject lines, preview text, and full body copy for every email
Escalation logic within each sequence — when to increase the offer
Tone and messaging matched to cancellation context

Days 4–7 · Timing

Timing Framework

When to send each email post-cancellation, per segment. Built around the psychology of each cancellation reason — not a one-size-fits-all drip schedule.

Send timing for each email in each sequence
Reasoning behind each interval — why day 3 vs. day 7 for that segment
Suppression rules — when to stop sending and why
Re-entry criteria if an account re-cancels after returning

Days 4–7 · Offers

Re-Activation Offer Strategy Per Segment

The specific offer that matches each cancellation reason. Discounts for price-sensitive churners. Feature announcements for gap churners. Concierge calls for high-value accounts. Each offer designed around what actually motivates return.

Offer type per segment — discount, trial extension, feature unlock, concierge
Offer escalation — what to try first, what to escalate to
Know exactly what each win-back offer costs you vs. the revenue it recovers
Urgency that feels real, not manufactured — because the offer actually expires

Days 8–10 · Implementation

ESP Implementation Guide

Everything your lifecycle team needs to load the sequences into your email platform and start sending. Segmentation rules, trigger conditions, and sequence logic documented for your specific ESP.

Segmentation rules for your ESP — how to route accounts into the right sequence
Trigger conditions — what fires each sequence and when
Exit conditions — what pulls an account out of the sequence
Measurement plan — what to track to know if it’s working

On the revenue sitting in your cancelled accounts: segmented sequences target the specific reasons accounts leave, moving recoverable accounts out of your generic list and into a tailored win-back flow. This turns cancelled revenue into recovered MRR.

FIT CHECK

You’re losing accounts every month. Some are recoverable — if the message matches the reason.

GOOD FIT

B2B SaaS with meaningful monthly cancellations and some cancellation data

Cancelled accounts available · reason data exists or can be inferred

The situation

You have accounts cancelling every month and your current win-back effort is either non-existent or a single generic email. You have some data on why accounts leave — cancellation surveys, support tickets, or at minimum Stripe cancellation reasons. You know there’s recoverable revenue in that list but you haven’t built the system to go after it.

What you leave with

A segmented win-back system that runs automatically from your ESP
Different messaging for different cancellation reasons — not one email for everyone
Re-activation offers matched to the psychology of each segment

Cancelled accounts start returning at a measurably higher rate — recovered MRR from accounts you’ve already lost.

NOT A FIT

Very low churn volume, no cancellation data, or churn isn’t the constraint

Wrong stage or wrong problem

When this sprint doesn’t apply

If you have very low churn volume, the impact of segmented sequences may be limited. If you have zero cancellation data — no surveys, no tickets, no reason codes — there’s nothing to segment on yet. And if your problem is acquisition rather than retention, win-back emails won’t move the number that matters.

Better starting points

Churn Prediction

Identify which accounts will churn before they cancel — so you can prevent it.

Churn Prevention Emails

Intervene before cancellation with behaviour-triggered email sequences.

Chameleon Flows

In-app interventions that reach at-risk users where they already are.

What this sprint doesn’t cover

The Win-Back Email sprint delivers the taxonomy, sequences, copy, and implementation guide. Your team loads them into the ESP and manages the sends.

Setting up the ESP automation — the guide tells your team exactly how, but we don’t log into your platform
Fixing the underlying churn causes — the sequences recover accounts, they don’t fix why accounts leave
Ongoing sequence optimisation — we deliver the measurement plan, your team iterates

To prevent churn before it happens → Churn Prediction

Jake McMahon — ProductQuant

Jake McMahon

8+ years building retention, activation, and growth programs inside B2B SaaS · Behavioural Psychology + Big Data (Masters)

I write these sequences myself. The taxonomy, the segmentation logic, the email copy, the timing — all of it. Your cancelled accounts are not a homogeneous group. Someone who left because of price has different economics than someone who left because a feature was missing. Someone who churned after 2 months is a different recovery target than someone who churned after 18 months. The sequences I build reflect those differences.

The psychology background matters here more than in most sprints. Win-back emails are persuasion under constraint — you’re asking someone who already decided to leave to reverse that decision. The message, the timing, and the offer all have to align with their specific reason for leaving. Generic “we miss you” emails fail because they ignore the decision that was already made.

I won’t do this:

Write generic win-back copy that could apply to any SaaS product
Recommend blanket discounts without understanding the cancellation reason
Deliver sequences without a timing framework backed by segment-specific logic
Skip the taxonomy and jump straight to writing emails

What if our cancellation data is messy?

Most cancellation data is messy. Free-text survey responses, inconsistent reason codes, support tickets that mention cancellation in passing. The taxonomy phase exists specifically to impose structure on whatever you have. If the data is very sparse, we supplement with Stripe metadata, usage patterns before cancellation, and support conversation analysis. You don’t need clean data to start — you need enough signal to segment.

Teams Jake has worked with

PRICING

One price. Cancelled accounts start coming back this month.

$1,997

one-time · fixed price

10-day sprint

Cancellation reason taxonomy built from your actual data
4–6 segmented win-back sequences, 3–4 emails each
Timing framework per segment — when to send each email post-cancellation
Full email copy — subject lines, preview text, and body
Re-activation offer strategy per cancellation segment
ESP implementation guide for your specific platform
Measurement plan — what to track and what “working” looks like
Everything stays with your team permanently

At least 4 segmented sequences with timing and copy — or full refund. No conditions.

Book a 30-minute call →

At least 4 sequences designed to recover cancelled accounts — segmented by why they left — or full refund. If your cancellation data can’t support meaningful segmentation, we tell you in the first 3 days and scope what’s possible. The deliverable either exists or it doesn’t.

Questions.

Or book a call →

What if we don’t have a cancellation survey? +

Cancellation surveys are one input, not the only one. We also use Stripe cancellation reason codes, support ticket analysis, usage patterns before cancellation, and account metadata. If you have any signal at all about why accounts leave — even rough signal — we can build a taxonomy from it. If you have genuinely zero data on cancellation reasons, the sprint starts by recommending what to collect and how, then builds sequences from whatever segmentation is possible from account value and tenure alone.

How is this different from hiring a copywriter to write win-back emails? +

A copywriter writes emails. This sprint builds a system. The difference is the taxonomy and segmentation logic that sits underneath the copy. Which accounts get which sequence, when each email fires, what offer matches each cancellation reason, and when to stop sending. The copy matters — but the segmentation is what turns a low win-back rate into something meaningfully higher. A good email sent to the wrong segment still fails.

Do you set up the sequences in our ESP? +

The sprint delivers an implementation guide specific to your ESP — Customer.io, HubSpot, Intercom, Braze, Klaviyo, or whatever you use. The guide includes segmentation rules, trigger conditions, sequence logic, and exit conditions. Your lifecycle or growth team loads the sequences. If your team needs hands-on help with ESP setup, we can scope that separately, but most teams with an existing ESP can load from the guide in a few hours.

Can this work without churn prediction? +

Yes. Win-back sequences work from cancellation data — accounts that have already left. Churn prediction works upstream, identifying accounts likely to leave before they cancel. They’re complementary but independent. If you pair them, you get prevention emails before cancellation and win-back emails after. But the win-back sprint stands alone — all it needs is cancelled accounts and some signal about why they left.

What’s the guarantee? +

At least 4 segmented win-back sequences with timing and copy — or full refund. If your data can’t support that level of segmentation, we surface that in the first 3 days during the taxonomy phase and scope what is deliverable. We don’t reach day 10 and hand over something that doesn’t meet the brief.