DEV Community

Swipe Again for Swipe Again

Posted on

The Scoreboard Is Not the Work, but It Decides Whether the Work Counts

Every subscription business keeps two ledgers, whether it admits it or not. One is the work ledger: failures noticed, retries scheduled, emails sent, cards updated. The other is the scoreboard ledger: money that was owed, money that arrived, money that never will. Teams love the first ledger because it is full of activity. Finance trusts only the second, because activity that does not end in collected revenue is just motion.

That is the honest frame for revenue recovery software that is judged on collected renewals, not activity counts. Its job is not to generate attempts, messages, or dashboards. Its job is to turn a specific pile of failed renewals into paid ones, at a cost — in money, issuer goodwill, and customer patience — that leaves the business better off than doing nothing. Anything softer than that standard lets a tool look busy while the leak continues underneath it.

Begin an evaluation with the pile itself. How large is last month's failed-payment pool, really? Not the gross exposure number that makes a sales deck dramatic, but the workable pool: failures on cards and accounts where recovery is genuinely possible, separated from the closed accounts, the fraud cases, and the people who cancelled on purpose. A serious tool helps you draw that line. A unserious one prefers the bigger number, because a percentage of a bigger number always looks like more value.

Then follow one failure all the way through. A renewal fails on Monday. When is the first retry, and what decided that timing? When does the subscriber hear about it, in what words, and what exactly are they asked to do? If their card was replaced, does the system notice a new credential, or does it keep presenting the old one? If they pay by another route entirely, does the case close as recovered, or does the machinery keep writing to someone who has already fixed the problem? That last failure — pestering the recovered — is the one customers remember.

Cost deserves the same unsentimental treatment. A percentage-of-recovery price means the meter runs hardest in your best months, and the total is unknowable until the quarter ends. A flat price can be compared, budgeted, and judged: did collected revenue beat the fee by a margin worth the effort? Whichever model you choose, do the arithmetic on your own pool, with your own recovery rate, not on the worked example in a brochure where every assumption leans the vendor's way.

There is a timing question too, and it is easy to miss. Recovery that lands in week one is worth more than the same dollars landing in week five, because a subscriber recovered quickly never starts shopping for your replacement. Ask how long cases stay open, what the schedule looks like across that window, and when the system declares a case honestly finished. A long, vague tail of attempts is not thoroughness; it is a queue nobody is managing.

None of this requires a large finance team. It requires refusing to grade recovery work by how much of it happened. Count the pool honestly, trace single cases end to end, price the models on your own numbers, and check the scoreboard monthly against the work ledger. When the two agree, you have a system. When only the activity ledger looks healthy, you have a very energetic leak.

Start small if you need to: one month, one failure report, one afternoon. The businesses that get good at this are not the ones that bought the most features. They are the ones that decided, early, that recovered revenue is a number you verify — never a story you are told.


Published by Swipe Again — failed payment recovery at a flat $179/mo.

Top comments (0)