Win-Back Offer

Recover a lapsed customer by naming what changed since they left and crediting the relationship they already built.

Pro moderate Funnel-Stage Offers

What it adds

The builder pulls prior purchase history and product change records from your source files to construct a return offer that addresses the specific reason a former customer left and acknowledges their previous tenure. It converts on relevance and dignity: the message proves you know what they had, admits what was missing, and shows what is different now, rather than treating them as a fresh lead. The conversion event is a reinstated purchase or subscription from a previously churned customer.

What your builder is told to do

The actual instructions, in order.

1
Inspect the source files and segment lapsed customers by exit reason and time since departure; a customer who left over price needs a different message than one who left over a missing capability.
2
For each segment, identify what genuinely changed since they left using only documented changes — if nothing relevant changed for a segment, do not contact it.
3
Open by acknowledging the specific thing they used to have, then state plainly what is different now, with no apology theater and no pretending the departure did not happen.
4
Credit their history concretely: preserved settings, restored data, prior tenure counted toward status, or a returning-customer rate — whichever the source files can actually support.
5
Make return frictionless: reactivate the previous configuration in one action rather than requiring a fresh setup, and show what will be restored before they commit.
6
Send at most two messages per segment spaced across a short window, the second adding a single new fact rather than repeating the first with more urgency.
7
Define layout: mobile presents the changed capability and a single reactivate button above the fold; tablet adds a compact then-versus-now comparison; desktop shows the restored-account preview alongside the comparison in one view.
8
Suppress anyone who cancelled with a hard exit reason, track returns by original exit reason, and route reinstated customers into an onboarding refresh rather than the standard new-customer path.

Edge cases it handles

The things an agent skips when you only say "build a win-back offer".

A former customer's data has been purged: state honestly what cannot be restored before they pay.
The customer left due to a problem that still exists: exclude them from the campaign entirely.
The prior plan no longer exists: map to the closest current plan and disclose the differences.
A returning customer's old price is below current pricing: decide and disclose whether legacy pricing is honored.
Contact details are stale: verify deliverability before sending and remove hard bounces.

Definition of done

Your builder is required to check every one of these before reporting the work finished.

Lapsed customers are segmented by documented exit reason and recency.
Every message cites a real, documented change since the customer's departure.
Tenure or history credit is concrete and supported by the source files.
Reactivation restores prior configuration in one action, with restoration scope shown first.
Mobile, tablet, and desktop each present the changed capability and return action clearly.
Segments with no relevant change and hard-exit customers are suppressed.
The builder names the source files supplying history and change logs, and lists unresolved restoration assumptions.

Related offer files

Funnel-Stage Offers

Lead Magnet

Turn anonymous cold traffic into named subscribers by trading one narrowly useful asset for an email address in seconds.

Funnel-Stage Offers

Cart Recovery Offer

Close an abandoned checkout by returning the shopper to their exact cart and resolving the friction that stopped them.

Funnel-Stage Offers

Activation Offer

Push a signed-up-but-idle user to their first real result by removing every step standing between them and one visible win.

How it works

1

Copy the link

Grab the Markdown blueprint URL for this offer type.
2

Give it to your builder

Paste it into Claude Code, Cursor, Codex, or whatever AI builder is already working in your app.
3

It maps, then builds

Your agent reads the blueprint first, then builds the offer into your app around the product, audience, and stack.

Works with your stack

These blueprints are written to adapt. They tell the agent to detect your framework, match your existing design system, and use your source files instead of guessing the offer.

Need it tighter than that? Customize the offer file and tell it exactly which source docs and stack to use.