Journal · 18 November 2025
How UK subscription teams misread monthly cohorts
British subscription products live on two calendars. One is behavioural: when someone actually used the thing. The other is administrative: when GoCardless collected, when the cooling-off window closed, when an invoice with VAT went out. A “monthly cohort” that buckets by signup month and then scores “active in month two” will swallow all three.
We see the same pattern in Lifecycle Intervals. A drop after day 30 is narrated as churn when it is often the first collection attempt. Failed payments then look like product rejection. They are sometimes that. They are often a bank holiday plus a retry rule.
A cleaner practice is to keep a payment cohort and a usage cohort as separate objects. Merge them in a memo, not in a single colour scale. If you only have room for one chart in a QBR, pick usage and footnote collections. Finance already has the collection chart.
Consumer-rights windows add a third wrinkle for teams selling to individuals. Cancellations inside a statutory period are not the same behaviour as quiet abandonment in month five. Lumping them teaches the wrong lesson about onboarding.