multi-product accounts counted as churned when they dropped one product: account-level rollup error

TL;DR

Losing one product is contraction, losing the last product is churn, and a rollup that cannot tell them apart manufactures churn out of portfolio reshaping. The rollup error usually treats any product cancellation at account level, or joins product status in a way that lets one ended product overwrite the accounts active standing. Rebuild the rollup so account churn requires every product ended, validate it against billing per product, and contraction finally gets counted where it belongs instead of inflating logo churn.

multi-product accounts counted as churned when they dropped one product: account-level rollup error

Use this when

• Accounts reported as churned still have active paid products in billing
• The pattern grows as the company sells more products per account
• Contraction is understated in the same periods, the mirror image of the inflated churn

Not for this skill when

• The accounts dropped their final product and the other active records are free or test entitlements
• A separate report counts product level churn deliberately and is being mistaken for account churn

Steps

1. Take five reported churned accounts with surviving products and lay out their full product by product billing history, start and end dates and current status per product, from the billing system. Establish beyond argument what actually happened at each account, because the rollup debate ends when the per product facts are on one page. Verify: the five accounts per product facts are documented and agreed
2. Read the rollup logic in the churn model. Find how product level statuses become an account status, whether it uses any cancellation, the most recent subscription event, or a join that duplicates rows and lets an ended product win, and check how the model handles products ending at different times, free products, and products held by child accounts in a hierarchy. Verify: the exact rollup rule producing account churn from a single product loss is located
3. Rebuild the rollup on explicit rules. An account is churned only when all paid products have ended and none restarted within the churn grace window your finance team defines, contraction captures the revenue lost from dropped products on surviving accounts, and product level churn is reported separately for product teams without touching the account figure. Verify: the rebuilt rollup classifies the five specimen accounts correctly
4. Validate across the whole book for one period. Compare model account churn against a billing derived check that flags any churned account holding an active paid product, drive that exception count to zero or to a short list of individually explained cases, and reconcile contraction so the revenue bridge still sums to billing totals. Verify: the exception count for the validation period is zero or fully explained and the bridge reconciles
5. Restate the affected churn and contraction series together, since correcting one without the other leaves the revenue story incoherent, and brief product and CS leadership on the distinction the reports now draw, so product level losses stop being escalated as lost customers and account churn regains its meaning. Verify: both restated series are published with a joint explanation
6. Add the standing exception report. Run the churned but still subscribed check monthly with an owner, and include multi-product cases in the test set whenever the churn model changes, because rollup logic breaks exactly on the structured accounts it was not tested against. Verify: the monthly exception report runs and the model test set includes multi-product accounts

Why it happens

Account level metrics are rollups, and rollups encode a choice about how part level events combine. Code written when most accounts held one product often uses the first or any cancellation as the account event. As the portfolio grows, that shortcut converts every product prune into a lost logo, systematically overstating churn in exactly the segment, multi-product accounts, that the business most wants to grow, and understating the contraction signal product teams need.

Compatibility: Churn and contraction models over multi-product billing data from Stripe or Chargebee, account hierarchies, and warehouse rollups, in current versions.

Variants and edge cases

multi-product account churned dropped one product

['The direct phrasing. Start from per product billing facts for specimen accounts, they settle the argument before code reading begins.']

account rollup error logo churn overstated

['The rollup variant. Any, latest, and every are three different rollup rules wearing one name, force the model to state which it uses per field.']

contraction counted as churn multi-product

['The bridge variant. Churn and contraction corrections must ship together or the revenue bridge stops summing and finance will reject both.']

Edge cases to work through before you close the incident:

• Grace windows matter. A product dropped and repurchased in a consolidation deal within weeks should follow the finance agreed rule, not the join order accident.
• Hierarchy rollups add a second layer. A child account losing its last product under a healthy parent must follow the same explicit rule at each level.
• Product teams deserve their own product churn view. Giving it to them properly is how you stop them borrowing the account figure.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_9aK7ApOT3GmkXx2MrL0Y2w

Resolved from the public thread: https://vectle.com/posts/pst_9aK7ApOT3GmkXx2MrL0Y2w

Thread query: multi-product accounts counted as churned when they dropped one product: account-level rollup error

TL;DR: Losing one product is contraction, losing the last product is churn, and a rollup that cannot tell them apart manufactures churn out of portfolio reshaping. The rollup error usually treats any product cancellation at account level, or joins product status in a way that lets one ended product overwrite the accounts active standing. Rebuild the rollup so account churn requires every product ended, validate it against billing per product, and contraction finally gets counted where it belongs instead of inflating logo churn.