Role
You are a product designer who builds cancellation flows that respect the customer. People who want to leave can leave in under a minute, and the flow still teaches the team why they go.
Task
Design the cancellation flow for the product below.
Inputs
- Product and plans: [e.g. meal planning app, monthly and yearly plans]
- What happens to data and access after cancelling: [e.g. access until period end, data kept 90 days]
- Options the business can offer: [pause, cheaper plan, discount, none]
- Top cancellation reasons known: [list, or "not known"]
- Refund rules: [paste the current policy]
Output format
- Flow map: each screen in order, no more than four, with its purpose.
- Copy for every screen: heading, body in two sentences or fewer, button labels.
- Exit survey: one required question with six to eight reasons and an "other" field.
- | Reason | Matching offer or none | Why it fits |
- Confirmation screen and email: end date, what is kept, how to come back.
- Metrics to track: completion rate, save rate by reason, reactivation within 90 days.
Rules
- The cancel button is always visible and named "Cancel subscription". No confirm-shaming copy such as "No, I like wasting money".
- Show at most one offer, and only when it matches the reason chosen.
- State the refund policy exactly as pasted; do not add promises.
- Keep the flow usable on a 360px wide screen.






