DEV Community

Swipe Again
Swipe Again

Posted on

Choose Recovery Software by the Cases It Closes, Not the Emails It Sends

Recovery software is usually sold on activity. Dashboards show emails sent, retries attempted, sequences launched, touches per case. Activity is easy to count and flattering to report, which is exactly why a buyer should be suspicious of it. A system can generate a great deal of motion around a failed payment while recovering very little of the money, and the gap between motion and money is where most evaluations quietly fail.

Start instead with closures, and ask how a case is allowed to end. A recovered case should mean one specific thing: the money that failed was collected, by an identifiable route — a timed retry, a customer card update, a platform account updater — counted once. A lost case should mean the attempts were spent sensibly and the file was closed, not that the sequence ran out of templates. And the awkward middle cases need names too: a subscription cancelled mid-recovery is a loss, honestly recorded; a paused subscription is parked, neither a win nor a loss, until it resumes or ends. Software that cannot describe its own endings this precisely will produce reports you cannot trust, however handsome the dashboard is.

Next, ask what happens before an attempt. The cheapest recovered dollar is the one collected because the system checked first: the card had already been updated through the merchant's own pages, a replacement charge for the same subscription had already succeeded, or the bank's updater had quietly refreshed the credentials. Checking live state before retrying prevents double charges, prevents pestering customers who already fixed the problem, and concentrates the attempt budget on cases that are actually still open. If a vendor's story jumps straight from failure to retry, the checking layer is missing, and you will feel its absence in support tickets before you see it in reports.

Timing deserves the same scepticism. Ask not how many retries the system makes, but when. A schedule aimed at paydays, spaced to let soft declines change, and capped before persistence becomes harassment will beat a longer, denser schedule on both recovery and goodwill. Attempts are a budget, and the calendar is how the budget gets spent well.

Finally, price the thing in a way that keeps its incentives pointed at your customers rather than your failures. A percentage of recovered revenue grows when your failure problem grows; a flat price does not care whether the win came from a retry, an update, or a failure prevented before it entered the queue. Buyers who care about prevention — and every buyer should, eventually — will notice which pricing model makes prevention somebody's job.

The comparison that follows from all of this is refreshingly short: how cases close, what gets checked before attempts, when retries land, how counting is done, and what the bill looks like in a bad month. Payment recovery software priced flat and judged on closed cases states one system's answers to those five questions on a single page, which is the right shape for the decision.

Software in this category earns its keep in a narrow, honourable way: money that was already earned, quietly collected instead of quietly lost, with the customer relationship intact at the end of it. Judge it on closures and counting, and the activity charts can go back to being what they should have been all along — supporting detail, not the headline.

Swipe Again charges a flat $179 a month on exactly those terms: declines read before attempts are spent, live state checked before every retry, timing aimed at paydays, and a guarantee judged on total recovery across the first 30 days — recover $179 or the next month is free.

Top comments (0)