--- title: "Reason-Matched Save Offers — Retention Growth Tactic" description: "Ask why the subscriber is cancelling, then route them to the offer that answers that reason—price objections get right-sizing, dormancy gets a pause, and a generic one-size-fits-all offer answers nobody." canonical: "https://churnkey.co/growth/library/reason-matched-save-offers" category: "growth" related: - /growth/library/index.html.md - /growth/library/methodology.html.md - /feature/cancel-flows.html.md last_updated: "2026-06-09" --- # Reason-Matched Save Offers Ask why the subscriber is cancelling, then route them to the offer that answers that reason—price objections get right-sizing, dormancy gets a pause, and a generic one-size-fits-all offer answers nobody. - **Stage:** Retention - **Evidence grade:** strong (large, consistent correlation) - **Evidence:** Reason-routed offers outperform one-size-fits-all offers in Cancel Flows - **Trigger type:** Event - **Channels:** cancel modal ## What is it? A subscriber on the way out volunteers the single most valuable piece of targeting data an org will ever get: the reason. A structured cancel-reason question—one tap, fixed options—captures it, and the flow routes on it. "Too expensive" routes to a right-sizing offer. "Not using it right now" routes to a pause. "Missing a feature" routes to product help or the roadmap. "Switching tools" gets a clean, respectful exit. The premise is that cancellers are not one population, and a single offer treats them as if they were. A discount answers a price objection and nothing else; a pause answers a usage gap and nothing else. Matching the offer to the stated reason puts the right answer in front of each subscriber instead of the average answer in front of all of them. ## What the evidence shows Across the platform, Cancel Flows that route on the stated reason outperform single-offer flows. The pattern in the underlying data is the explanatory part: offer acceptance concentrates where the offer matches the reason—price offers convert price objectors, pauses convert the temporarily dormant, and each performs poorly against the other’s population. The direction is consistent across orgs; the magnitude is not, because it depends on each org’s reason mix. An org whose cancellers are mostly price-sensitive gains differently from one whose cancellers are mostly dormant. The honest read is that routing reliably beats not routing, and how much it beats it is a property of the audience. ## How it runs In production, the Cancel Flow opens with a structured reason question—a short list of options, answered in one tap, never a free-text field standing between the subscriber and the exit. The selected reason determines the next screen: a right-sizing offer, a pause, a product-help or roadmap path, or a direct route to confirmation for subscribers who are switching tools. Every reason has a route, and every route includes the exit. The reason data flows into analytics whether or not an offer is accepted, so the org learns its cancel-reason mix even from the subscribers it loses. Subscribers switching tools are not chased with a discount; an exit interview yields more there than a price cut does. ## 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 initiates cancellation and enters the Cancel Flow. **Surface:** Reason question on the first screen of the cancel modal, with the matched offer on the screen that follows. **Guardrails:** - Friction: the reason question is one tap from a fixed list—never a free-text field as a gate before the exit. - Coverage: every reason has a route, including a respectful fast path to cancel for subscribers who are done. - Analytics: reason data feeds reporting even when no offer is accepted, so the cancel-reason mix is measured on losses too. - Restraint: never route "switching tools" to a discount reflexively—an exit interview beats a price cut for that population. **Evidence:** Reason-routed offers outperform one-size-fits-all offers in Cancel Flows, measured on structured cancel-reason and save outcomes across hundreds of orgs. Offer acceptance concentrates where the offer matches the stated reason. The direction is consistent across orgs; the magnitude varies with each org’s reason mix. **How to run it:** 1. Define a short, fixed cancel-reason list that maps cleanly to the offers the org can actually honor. 2. Place the reason question as the first screen of the Cancel Flow, answerable in one tap. 3. Route each reason to its matched offer: price objections to right-sizing, dormancy to a pause, feature gaps to product help or the roadmap, tool-switchers to a clean exit. 4. Pipe every selected reason into analytics regardless of save outcome, and review the reason mix monthly. 5. Track acceptance rate per reason-offer pair and replace any pairing that underperforms the flow average. 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. - [Cancel Flows](/feature/cancel-flows.html.md) — The Churnkey feature this tactic maps to in production.