--- title: "First-Screen Save Offer — Retention Growth Tactic" description: "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." canonical: "https://churnkey.co/growth/library/first-screen-save-offer" category: "growth" related: - /growth/library/index.html.md - /growth/library/methodology.html.md - /feature/adaptive-offers.html.md last_updated: "2026-06-09" --- # 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. - **Stage:** Retention - **Evidence grade:** strong (large, consistent correlation) - **Evidence:** Offer-first flow order outperforms survey-first in cancel-flow tests - **Trigger type:** Event - **Channels:** cancel modal ## 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 it with the Churnkey MCP This tactic runs via the Churnkey MCP. Connect it to your favorite AI agent and it reads your own usage and billing data, then recommends and runs the plays most likely to move your LTV — starting with whether this one fits. **Trigger:** A subscriber clicks cancel and the Cancel Flow opens. **Surface:** The first screen of the cancel modal, ahead of the exit survey. **Guardrails:** - Survey placement: the exit survey still runs after the offer decision—never as a gate before the offer or before cancellation. - Offer selection: the chosen offer respects the org’s measured discount-effectiveness profile; discounts only where they demonstrably help that org. - One offer: never present more than one offer screen before accepting the cancellation. - Decline path: declining the offer leads to a working cancellation in at most two clicks, in line with click-to-cancel compliance. **Evidence:** Offer position and flow order materially move save rates in cancel-flow A/B tests across the platform, and offer-first order outperforms survey-first. The direction is strong and consistent across tested orgs; the magnitude is org-dependent and tracks how well the first-screen offer is matched per subscriber. **How to run it:** 1. Move the save offer to the first screen of the Cancel Flow, ahead of the exit survey. 2. Select the offer per subscriber—pause, right-size, or discount—from plan, usage, and the org’s measured offer performance. 3. Run the exit survey after the offer decision, on both the accept and decline paths. 4. Build the decline path so a working cancellation is reachable in at most two clicks from the offer screen. 5. A/B test offer-first against the prior flow order and track save rate alongside flow-abandonment rate per screen. Install the MCP server: ```bash npm install -g @churnkey/mcp ``` The full reference is in the [Churnkey MCP docs](https://docs.churnkey.co/data-integrations/mcp). ## Related - [Growth Tactics Library](/growth/library/index.html.md) — The full register of graded growth plays. - [How Tactics Are Graded](/growth/library/methodology.html.md) — The four-grade evidence ladder behind this grade. - [Adaptive Offers](/feature/adaptive-offers.html.md) — The Churnkey feature this tactic maps to in production.