Cancellation Save Offer

Intercept a cancellation in progress by diagnosing the actual reason and answering only that reason with a matched remedy.

Pro simple Funnel-Stage Offers

What it adds

The builder constructs a short cancellation flow from your source files that asks one diagnostic question and then branches to a remedy matched to the answer — pause for cost, support for confusion, downgrade for fit, immediate exit for anything else. It converts by respecting the decision: a single relevant response outperforms a wall of retention offers, and offering the wrong remedy confirms the customer's decision to leave. The conversion event is a retained subscription via pause, downgrade, or resolution, with clean exits handled honestly.

What your builder is told to do

The actual instructions, in order.

1
Inspect the source files and enumerate the cancellation reasons your product can actually address, plus the ones it cannot; only the addressable ones get a remedy branch.
2
Ask exactly one diagnostic question with distinct, non-overlapping options and an explicit "none of these" that leads straight to cancellation.
3
Build one remedy per reason: a pause with a set resume date for temporary situations, a lower tier for cost, a targeted support or setup path for confusion, and immediate cancellation for fit or completion.
4
Present each remedy in a single screen with the accept action and a plainly-worded continue-to-cancel link of equal legibility — a hidden exit produces chargebacks and public complaints.
5
Cap the flow at two screens total; every additional interstitial converts a neutral cancellation into an angry one.
6
Define layout: mobile shows one question or one remedy per screen with full-width controls and no modal stacking; tablet keeps the remedy and exit link visible together without scrolling; desktop constrains width so the exit link is never pushed far from the accept button.
7
On confirmed cancellation, state the exact access end date, what happens to their data, and how to return, then send a written confirmation.
8
Record reason, remedy shown, and outcome for every session, and suppress the save flow for customers who have already declined a save within a defined period.

Edge cases it handles

The things an agent skips when you only say "build a cancellation save offer".

The customer selects a reason your product cannot fix: cancel immediately without presenting an unrelated discount.
The customer has cancelled and been saved before: skip the save flow and proceed directly to cancellation.
Cancellation is requested mid-billing-period: state clearly whether access continues to period end.
A pause is accepted: schedule the resume charge and notify before it posts.
The account has outstanding data or exports: offer retrieval before access ends.

Definition of done

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

One diagnostic question is asked with mutually exclusive options and a direct exit choice.
Each remedy branch maps to a reason the source files confirm is addressable.
A visible, equally legible continue-to-cancel path exists on every screen.
The flow is at most two screens on mobile, tablet, and desktop alike.
Confirmed cancellations display access end date and data handling, plus written confirmation.
Reason, remedy, and outcome are recorded, with repeat-save suppression enforced.
The builder reports which source files defined pause, downgrade, and support capabilities, and which reasons remain unmapped.

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

Affiliate Launch Kit

Equip partners with dated assets, tracked links, and a run-of-show so they can promote a launch window without improvising.

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.

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.