How to review cancellations and downgrades
Review cancellations and downgrades by customer. Measure recurring revenue lost, group the reasons customers gave, and choose where to follow up.
Free app. Runs on your Mac with the Claude or Codex plan you already have.
What it means to review cancellations and downgrades
When you review cancellations and downgrades, you trace each loss of paid subscription revenue to an account change and any reason the customer gave. The result shows who left, who stayed on a cheaper plan, what each change cost in monthly revenue, and what the founder can do about it.
A churn reasons report combines two records. The billing export tells you when paid service ended or shrank. A survey, support note, or exit email can explain why. Keep those records distinct throughout the cancellation analysis. A move to a cheaper tier is visible in billing, while a statement that the customer needed an integration requires evidence. Treat the review as a draft for a qualified finance reviewer to check before you rely on the figures or act on its proposals.
What it does for the business
- Decide which accounts merit personal outreachUse the size of each loss and the customer's own words to decide where a call is worth making. Assign the call to someone who knows the account and can speak to the issue the customer raised.
- Identify where billing needs attentionLosses linked to failed payments give the billing owner a starting list for checking reminders or payment update steps. The owner can trace the route a customer took and see where a failed payment turned into ended paid service.
- Make a better case for a product or pricing changeRanking themes by recurring revenue lost shows which reported issues carry the most financial weight in each currency. Read the comments before deciding whether to review a plan boundary, document a feature, or investigate a product problem.
- Improve the next round of feedbackThe share of lost revenue with no stated reason shows where your evidence stops. If the gap affects a decision, ask a short exit question and retain its link to the account so you can use the answer in your next review.
How to review cancellations and downgrades, step by step
Set the period and check the billing export
An export of surviving subscriptions leaves out the customers whose losses you need to explain.
What to do
- Choose a reporting window and one cutoff date. Use complete months for a regular review, or record a partial month so a reader knows which days it covers.
- Export subscriptions that ended as well as subscriptions that are still active. Look for an end date and check whether the export contains dated plan or recurring charge changes needed to identify downgrades.
- Confirm which fields carry account identity, dates, plan, amount, billing interval, and currency. Check whether the amount is in whole currency units or minor units such as cents.
- Gather exit survey responses, support notes, or emails that cover the same period. Match by customer ID where available, and check an email match against the event date when one customer has multiple subscriptions.
Why
A current subscription snapshot shows today's plans. Historical movements need evidence of what customers had before and when it changed. Checking units and dates also prevents errors in the size or month of a loss.
Measure the recurring revenue lost
Measure the recurring value of the account immediately before and after the change.
What to do
- Put recurring charges on a monthly basis before comparing them. A yearly subscription contributes its recurring yearly charge divided by twelve to monthly recurring revenue, commonly called MRR.
- Record the plan and MRR before and after each event. Treat ended paid service as a cancellation, reduced paid service as a downgrade, and a move to a free plan as a visible case that reaches zero paid MRR.
- Report the decrease as lost monthly recurring revenue in the billing currency. Show the annualized loss as lost annual recurring revenue, or ARR, and keep that run-rate measure separate from a forecast of cash collections.
- Reconcile opening recurring revenue and the period's movements to closing recurring revenue within each currency. Check excluded rows and resolve data or mapping problems that would leave a material customer out of the result.
Why
Revenue churn can be easy to miss when account counts look steady. A customer can stay on a cheaper plan or keep using the product after paid revenue ends. Keep these movements visible so finance can check the figures and account owners know who still uses the product.
Group the reasons customers gave
An account with no stated reason belongs in the totals where everyone can see it.
What to do
- Keep the original reason beside the account and read any feedback that matches the event. Store unmatched feedback separately so it cannot be mistaken for a specific customer's explanation.
- Use a small set of themes that point to different decisions. A budget cut, a missing feature, and a payment failure may all end a subscription and each calls for a different response.
- When a customer mentions several issues, assign the event to the reason emphasized in their words and record the other issue in a note. Keep a separate theme for no reason given.
- Look for involuntary churn, which is paid service lost through a billing failure, in billing status and reasons as well as survey feedback. Check how much lost revenue has a documented reason before presenting the theme totals.
Why
Assigning each event once keeps theme totals free of double counting. Feedback coverage matters because customers who answer exit questions may have different reasons from customers who leave quietly.
Choose a follow-up for each account and theme
Give an account priority when its loss is material and the customer's words point to a response you can deliver.
What to do
- Read the lost MRR and the reason together. Rank cases within the same currency and note whether the loss looks recoverable based on the information you have.
- Give each event one next action. Assign a billing fix for a failed payment, a call to understand an unclear issue, a win-back offer when you can address the reason, or no outreach when the business has closed.
- Draft a short win-back email that refers to the known issue and offers a concrete next step. Check that the team can deliver anything you mention before the account owner sends it.
- Choose one change to investigate for each of the costliest themes. Point to the accounts and comments behind the change so the owner can check that the pattern supports it.
Why
An account that canceled after a card failed may need help updating payment details. A larger account that finished its project may have no use for the product today. Record the recovery judgment so the owner can assess whether the follow-up is worth pursuing.
Check the review and hand it to the owner
A reviewer should be able to trace every loss and stated reason to the records behind it.
What to do
- Ask a qualified finance reviewer to trace the counts, amounts, and shares to the reconciled movement and theme tables. Check that currencies stay separate and that the same event is counted once.
- Check the stated reason against the source and read the no-reason group for any guesses presented as fact. Confirm that unavailable or unmatched feedback is visible in the limitations.
- Hand over the customer list, theme totals, proposed changes, and drafts together. Show the period, the meaning of lost MRR and ARR, and which decisions need the owner's approval.
Why
A review pass can catch a reason that came from the wrong customer, a figure copied from the wrong currency, or a follow-up that depends on a guess. The owner can then see the evidence behind each proposed change.
Common mistakes
- Using an active-only exportStart from an export that retains ended subscriptions and gives you the dates of paid service changes.
- Mixing recurring and one-time chargesUse comparable recurring amounts before and after each event so a setup fee or one-off credit cannot distort the run rate.
- Adding losses across currenciesKeep the figures in separate currency groups so each total has a clear meaning.
- Treating a survey response rate as revenue coverageMeasure how much lost recurring revenue is linked to documented reasons, because respondents can represent a different share of customers and revenue.
- Assigning price as the reason for any downgradeRecord the plan change and use the customer's actual explanation or leave the reason unreported.
What a good result looks like
- A stated window, an as-of date, and a subscription export that includes ended accounts.
- One row per loss event, with the month, customer, movement type, monthly loss, and currency.
- Source-backed reasons, visible unmatched feedback, and a separate theme for no reason given.
- Reconciled recurring revenue and theme totals by currency, with any material gaps explained.
- A follow-up for each event and evidence a founder can use to evaluate the proposed changes.
And then what? Using the result
- Assign the billing owner the payment-related cases and have them check the account status before contacting customers.
- Give the account owner the drafts for recoverable cases so they can check recent conversations and decide what to send.
- Take the costliest documented themes into your product or pricing meeting and choose which change to investigate first.
- Add a short cancellation survey or fix the link between survey responses and accounts when reason coverage limits the review.
- Repeat the review after the next complete period using the same boundaries so you can compare movement types and feedback coverage.
When to run it
- At a monthly subscription reviewA regular cutoff lets you compare losses over time and route account-level follow-ups while the reason is still fresh.
- After a pricing or packaging changeLook for documented comments about the new plans and read them alongside actual account movements. The timing alone cannot establish a cause.
- When the number of customers looks steady and recurring revenue fallsAccount counts can miss downgrades. Review the type and value of each movement before deciding where to investigate.
- Before choosing a retention projectCheck the cost and coverage of each theme and read the source comments before giving work to billing, product, or customer success.
Questions people ask
How do you review cancellations and downgrades?
Use a complete billing export to find the period's losses, measure recurring revenue before and after each event, then add documented reasons and choose a follow-up. Reconcile the figures and have a qualified finance reviewer check the draft and its sources before relying on it.
How do you calculate lost monthly recurring revenue?
Subtract the monthly recurring revenue after the movement from the monthly recurring revenue before it, using the same currency and billing basis. For an account that ends paid service, the after amount is zero. Keep annualized loss labeled as a run-rate figure.
Is a move to a free plan a cancellation or a downgrade?
Show a move to a free plan as its own case in the review. Paid recurring revenue went to zero and the customer still has an account. Both facts matter when you decide how to report the loss and whether to follow up.
What if customers do not give a cancellation reason?
Record those events as no reason given and keep their losses in the totals. You can still report account changes and prioritize follow-up. Show how much of the lost revenue has a documented reason before drawing conclusions from the themes.
How do you prioritize win-back outreach?
Use the size of the monthly loss and the evidence that you can address the customer's reason. Give the account owner a short draft and the supporting note. A practical remedy gives them a clear reason to reach out.
Can you combine loss totals from multiple currencies?
Report each currency on its own in this review. Show the currency with each amount and compare themes within that group so a reader can check the figures directly against the billing records.
More jobs in Finance
Review cancellations and downgrades, on your own Mac.Free app. Runs on your Mac with the Claude or Codex plan you already have. Your files stay on your computer.
Download for Mac