Retention

Live in Churnkey

First-Screen Save Offer

Put the best save offer on the first screen of the Cancel Flow, not after the exit survey—every screen before the offer sheds the very subscribers the offer could save.

Personalized save offer with accept and decline actions, surrounded by the subscriber signals that selected it
Strong

Offer-first flow order outperforms survey-first in cancel-flow tests

cancel-flow A/B outcomes across orgs running offer-order tests

Consistent effect across multiple independent deployments.

How we grade evidence →

Event trigger · Edition 1 · June 2026


What is it?

A subscriber who has decided to cancel gives the flow seconds, not minutes. Each screen between the cancel button and the save offer is a toll, and the subscribers most likely to pay it by abandoning are the lightly-committed cancellers—exactly the population the offer could have saved. The survey-first flow spends its best audience learning why they left.

This tactic inverts the order: the best save offer renders on the first screen of the Cancel Flow, before any exit survey. And "best" is per-subscriber, not per-org—a pause for the seasonal user, a right-sized plan for the over-planned one, a discount only where discounts demonstrably work for that org. The survey still runs, but after the offer decision, where it costs nothing.

What the evidence shows

In cancel-flow A/B tests across the platform, offer position and flow order materially move save rates. Flows that lead with the offer outperform flows that lead with the survey, and the mechanism is visible in the funnel: survey-first flows lose a slice of cancellers at every pre-offer screen, and the lost slice skews toward the saveable.

The second finding is that the winning offer is not uniform. The same test data shows different subscribers responding to different saves—pause, right-size, or discount—and shows discount effectiveness varying sharply by org. The direction of the ordering effect is strong and consistent across tested orgs; the magnitude depends on the org’s mix of cancel reasons and how well the first-screen offer is matched to each subscriber.

How it runs

In production, the cancel click opens directly onto an offer screen selected for that subscriber from their plan, usage, and the org’s measured offer performance. One offer, one screen, one decision. A subscriber who accepts is saved without ever seeing a survey; a subscriber who declines moves on immediately—no second offer screen stands between them and the cancellation they asked for.

The survey runs after the offer decision, as a question on the way out rather than a gate on the way in. Compliance shapes the decline path as firmly as conversion shapes the accept path: from a declined offer, a working cancellation is at most two clicks away, which keeps the flow on the right side of click-to-cancel rules and on the right side of the subscriber.

Run this for your business

Want to run First-Screen Save Offer for your business? Connect the Churnkey MCP to your favorite AI agent. It reads your own usage and billing data and recommends the growth and retention plays most likely to move your LTV—starting with whether this one fits.

npm install -g @churnkey/mcp
Read the MCP docs →

This tactic maps to a Churnkey feature—the same play, running in production.

See it in action in Churnkey

Put the evidence to work.

The same dataset behind these tactics powers Churnkey's retention products. See what it finds in your subscription data.