DEV Community

Swipe Again for Swipe Again

Posted on

Churn Is a Lagging Indicator

By the time a churn report moves, the events that caused it are weeks old and mostly unfixable. The subscriber whose card failed on the 3rd, who never saw the email, whose retry schedule gave up on the 9th, appears in the metrics as a cancellation on the 30th — filed under decisions, explained as preference. Churn dashboards are autopsies. Useful, respectful, and far too late to help the patient.

The leading indicator sits one layer down: this week's failed payments, sorted by cause. That number moves the day the problem starts. An expiry wave from a two-year-old signup cohort, an issuer tightening its generic-decline posture, a payday cluster drifting with the calendar — all of it is visible in the failure stream while the subscribers involved still consider themselves subscribers.

Swipe Again is built on that ordering: watch the failures and the churn number becomes the receipt, not the alarm. The recovery flow treats every failed payment as tomorrow's churn arriving early with a return address. Businesses do not usually lose subscribers in the month they churn. They lose them in the month the billing broke and nobody read the signal while it was still cheap to answer.

Top comments (0)