A customer left one SaaS product: explain what the retention report measures

Start by deciding whether the report follows a product, a plan, a customer account or the whole business. A customer can leave one product and continue buying another. That is meaningful for the product owner, but its effect on company-wide retention differs from a customer ending every paid relationship. Keep both views where they answer different management questions.

ChartMogul's retention documentation describes settings that change how departures from a filtered plan are counted. The same underlying switch can therefore appear differently depending on the report configuration. Save the filter and departure treatment with the export rather than relying on a chart title that says only retention.

For each departure, identify the prior product, destination product if any, effective date and recurring value before and after. Distinguish a voluntary product exit from a business-led migration or catalog rename. Link replacement subscriptions to the continuing customer identity so the analysis does not mistake a technical record change for a new relationship.

Ask the account owner to confirm unclear cases and retain the commercial evidence. A customer buying another product months later may represent a genuine return rather than a continuous switch. Apply the stated reporting rule consistently and preserve timing differences instead of connecting records simply to improve retention.

Consider a hypothetical customer paying $300 for Product A and $700 for Product B. It cancels A but keeps B unchanged. Product A loses its $300, while the company retains the customer with $700 of recurring value. Calling the event complete customer churn would obscure the continuing relationship; ignoring the loss because the customer remains would obscure the product's contraction.

Present the product loss, retained account value and total change in separate columns. Where a customer moves between products, also identify any price or quantity change. This makes the report useful to both product and finance teams without requiring them to agree that only one perspective is legitimate.

Define whether the report follows customers who belonged to the product group at the opening date or dynamically selects current members. A current-members-only selection can omit customers who left, making historical retention appear stronger. Preserve the opening population and evaluate its subsequent outcomes under the chosen method.

Check how bundles and multiple subscriptions enter the calculation. If the business allocates customer value among products for management analysis, retain that allocation rule and its version. Changing the allocation while reviewing churn can shift apparent product performance without any commercial event. Reconcile the product totals to the appropriate whole-business measure.

Use the product view to investigate adoption, replacement and pricing questions. Use the customer view to understand the broader relationship and retention risk. A migration to a successor product may be planned progress, while an unplanned exit with no replacement may need follow-up. Label the event using evidence rather than treating every departure as success or failure.

Keep the customer-level movement map with the report and explain any configuration change in later periods. If leadership sees different retention rates in product and finance dashboards, show the population and switch treatment that produce each result. A transparent reconciliation is more useful than forcing distinct questions into a single percentage.