gross churn and net churn swapped in the board report: expansion included in the wrong calculation

TL;DR

Gross churn cannot be improved by expansion, that is the entire point of it, so when a board report shows gross churn moving with expansion deals, the two calculations have been crossed somewhere in the model. Gross churn counts only lost revenue from churn and contraction against the starting base, net churn subtracts expansion as well. Find where expansion entered the gross figure, fix the model, restate the board series, and lock the definitions where the next analyst cannot quietly re-cross them.

gross churn and net churn swapped in the board report: expansion included in the wrong calculation

Use this when

• Gross and net churn in the board report are equal, or gross moves when only expansion changed
• Finance figures for the same period do not match the boards gross number
• A report refactor or a new analyst rebuilt the churn model recently

Not for this skill when

• Both metrics were rebuilt correctly and the board is comparing different periods or bases
• Expansion is tiny this period, so gross and net legitimately sit close together

Steps

1. Write the two definitions out in full with the exact components and base period each uses, from your finance teams agreed standard, and keep them in front of you for the whole investigation. Most swaps survive because people argue from the metric names instead of the component lists, and names feel obvious until they are not. Verify: both definitions are documented component by component
2. Recompute both metrics by hand for one recent month from billing records, listing starting recurring revenue, churned revenue, contraction, and expansion per account, and summing each metric strictly by the written definitions. This hand built month is the arbiter for everything the model claims. Verify: the hand built gross and net figures for the test month are recorded
3. Compare the models outputs component by component, not just the final rates. Where the model gross equals your hand net, or its components show expansion inside the gross sum, read the model code at that exact component and find the crossed term, a reused intermediate measure is the usual culprit, where a net revenue change variable feeds both calculations. Verify: the crossed component in the model is located
4. Fix the model so gross and net are built from named, separate component measures with no shared intermediate that mixes expansion in, and rename ambiguous measures so expansion carrying ones cannot be mistaken for loss only ones by the next person editing the file. Verify: the corrected model reproduces the hand built month for both metrics exactly
5. Rebuild the full board series and check the relationship that must always hold, net churn is less than or equal to gross churn for every period, and gross never improves in a month where losses were flat and only expansion grew. Flag and investigate any historical period that still violates the relationship. Verify: every period in the rebuilt series satisfies the relationship between the two metrics
6. Restate to the board with a clear note on which periods changed and why, publish the definitions in the board pack appendix, and add an automated check in the reporting pipeline that fails when net exceeds gross, so a future swap stops the pack instead of reaching directors. Verify: the board pack carries the definitions and the pipeline check is active

Why it happens

Gross and net churn differ by exactly one component, expansion, and reporting models often compute a single revenue change measure and reuse it in both places for convenience. The reuse swaps the metrics results while keeping both numbers plausible, so nobody questions them until finance, working from definitions, produces a different gross figure. Plausibility is what makes this error durable, only the invariant between the two metrics betrays it reliably.

Compatibility: Board and finance reporting models over Stripe or Chargebee revenue data, with agreed gross and net churn definitions, in current BI and warehouse tooling.

Variants and edge cases

gross churn net churn swapped board report

['The direct phrasing. The invariant that net can never exceed gross is your fastest detector, check it across all periods first.']

expansion included in gross churn calculation

['The component variant. Shared intermediate measures are where swaps breed, separate and rename them as part of the fix.']

board churn numbers do not match finance

['The credibility variant. Bring the hand built month and the definitions page, boards accept arithmetic they can follow and distrust assertions.']

Edge cases to work through before you close the incident:

• Cohort based and period based churn are different again. Confirm the board definitions specify which, or the swap fix will expose a second quiet disagreement.
• Annual and monthly bases must never mix inside one series. If the refactor standardised the base as a side effect, call that out separately in the restatement.
• Multi-currency revenue needs a stated conversion rule in the definitions. Expansion in one currency can otherwise appear to move gross in another.

Provenance

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

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

Thread query: gross churn and net churn swapped in the board report: expansion included in the wrong calculation

TL;DR: Gross churn cannot be improved by expansion, that is the entire point of it, so when a board report shows gross churn moving with expansion deals, the two calculations have been crossed somewhere in the model. Gross churn counts only lost revenue from churn and contraction against the starting base, net churn subtracts expansion as well. Find where expansion entered the gross figure, fix the model, restate the board series, and lock the definitions where the next analyst cannot quietly re-cross them.