DEV Community

Swipe Again for Swipe Again

Posted on

An Audit You Run on a Quiet Afternoon, Before the Quarter Runs You

Most retention problems are not discovered in a crisis. They are discovered in an audit — or, more precisely, they were discoverable in an audit months before the crisis, sitting in plain sight in systems nobody had walked end to end since they were set up. The welcome email still promises a feature that moved tiers. The card-update page still fails a basic check on a small phone screen. The grace period in the billing settings says one thing and the help article says another. None of these is dramatic. Together, they are the difference between a renewal system that catches people and one that quietly lets them fall.

An audit earns its keep by being walkable: one person, one afternoon, following the subscriber's actual path rather than the org chart's idea of it. Start where a new subscriber starts. Read the onboarding messages as a stranger. Then become a subscriber in trouble: let a test payment fail, and live through everything that follows — every email, every retry, every page — with a notebook open. The gaps announce themselves in that walk with a clarity no dashboard reproduces, because the dashboard reports each step in isolation and the subscriber experiences them as one continuous story, including the seams.

The checklist discipline behind running a thirty-point retention audit across the whole subscriber journey adds the part memory cannot: coverage of the unglamorous back half. Payment-method expiry warnings, sent early enough to act on. The exact hour access changes after a final failure, and whether support's macros describe that hour correctly. What happens to a paused subscriber's data, a cancelled subscriber's winback eligibility, an annual plan's renewal notice in a holiday week. These are the places systems drift, because nobody owns the whole journey and every individual setting looked reasonable on the day it was changed.

Bring one more instrument on the walk: a real subscriber's confusion, borrowed honestly. Support tickets from the last quarter, read before setting out, tell the auditor where subscribers actually stumbled rather than where the team imagines they might. Search those tickets for the billing words — card, charged, cancelled, access, refund — and note every place a subscriber describes an experience the internal documentation describes differently. Each mismatch is an audit finding before the walk even begins, and it directs attention to the seams between what the system does and what the business believes it does, which is where nearly every item on the eventual list will be found.

Score honestly, and resist the urge to fix during the walk. The audit's product is a list, ordered by how many subscribers each defect can touch, not by how embarrassing it is. A broken link in the second dunning email outranks a misspelled help article by an order of magnitude in lost revenue, however much more the misspelling stings. Fixes then proceed in that order, and — this is the step most often skipped — the same walk is repeated after the fixes ship, because a change to one step regularly disturbs the next, and only the end-to-end pass sees it.

Run it quarterly and the audit changes character. The first pass finds archaeology. Later passes find drift: small, recent, cheap to correct. That is the steady state worth wanting — a business whose renewal journey is re-read, by a human, often enough that no subscriber ever meets a version of it that nobody has walked since spring. Retention, in the end, is mostly that: the discipline of noticing, on a schedule, before the numbers have to notice for you.

Swipe Again (swipeagain.com) is flat-fee failed payment recovery for subscription businesses — $179/mo, no percentage of recovered revenue, no sales call required.

Top comments (0)