“Our billing platform already retries failed payments.” If you’ve tried to make failed renewals a priority, you’ve probably heard this. It’s a fair point. Anyone asked for budget or engineering time will want to know how well the current process works and what you’d change.
Our previous post, Who really owns failed payments?, looked at why this problem often has no owner. This one is for the person who decides to take it on. Making the case comes down to four steps: find out what your current process still misses, work out what improving it would be worth, answer each team’s questions, and ask for a small next step.
Step 1: Find out how much your retries still miss
As one payments lead told us: “We all know we need to do this, but understanding what the numbers look like first would be super helpful.” So start with the numbers.
Say you attempted $1 million in renewals last month and $100,000 failed on the first try. If retries and customer reminders recovered $60,000, then $40,000 in revenue is still lost to failed payments. That shows what your billing platform already does for you and how much is left on the table.
To get that breakdown, pick a billing month where every renewal has had the full recovery window. If you allow 30 days, give the renewal billed on the last day of the month the same 30 days as the one billed on the first. Tie every retry or later payment back to the original renewal, so you can see what went through on the first try, what was recovered later and what was never recovered.
In practice, many teams can’t pull these numbers easily. Retries, reminders and card updates often sit in different systems, and few reports connect a recovered payment back to the renewal that failed. If that sounds familiar, Revaly can build this breakdown for you from your existing transaction data.
Then look at where that lost revenue comes from. If first-attempt declines rose after a change to how some renewals were processed, the problem starts before recovery. If first attempts held steady but fewer payments were recovered after a decline, look at recovery itself: when customers hear from you and how easily they can update their card.
Step 2: Work out what an improvement would be worth
Once you know the gap, the next question is what closing part of it would bring in. Be careful here. Some payments that go through on the first try would have been recovered by retries anyway, so look at total revenue, not just the recovery report.
Say you test a change to first-attempt approvals on two comparable groups, each with $1 million in renewals and the same recovery window.
##TABLE:tbl-approvals-test##
The recovery report alone would show recovered revenue falling by $12,000. But more payments went through on the first try, leaving less for retries to recover. Overall, the business brought in $8,000 more and cut revenue lost to failed payments by 20%.
That $8,000 is the number Finance can weigh against the cost of the change. Getting paid sooner can also mean fewer subscribers lose access while you wait for payment. If you estimate the future revenue from keeping them, start from the next billing period so you don’t count the same renewal twice.
Step 3: Answer each team’s questions
Each team will look at those numbers differently, so have an answer ready for each.
Finance will ask whether the gain is worth the cost. Compare the extra revenue with the cost of implementing and running the change. If you’re still estimating, show which renewals the change would affect and what you’re assuming about them.
Payments and Retention will want to know what changed for customers. Payments can show how much of the gain came from first-attempt approvals and how much from recovery. Retention can check whether fewer subscribers lost access after a failed renewal. Give both teams the same starting point: the share of attempted renewal revenue captured by the end of the recovery window, your Payment Success Rate.
Engineering will ask what you need from them. To size the problem, start with what Billing or Payments can pull from existing reports: renewal amounts, first-attempt outcomes and status at the end of recovery. Once the analysis points to a specific change, Engineering can say which systems it would touch and what a test would take. That also gives you something concrete for a vendor review, if it comes to that.
Step 4: Ask for a small next step
If you don’t have a baseline yet, ask for the analysis. In a planning meeting, that could sound like this:
I’d like Billing to pull one month of renewals and show how much was approved on the first attempt, how much was recovered after a decline, and how much was still lost. Finance can then help estimate how much of that lost revenue we could win back with better first-attempt approvals or a stronger recovery process. By [date], [owner] will use that analysis to recommend whether a test is worth running and what we should try first.
If the numbers already point to a specific change, ask for a limited test. Name who will run it and which renewals are in scope, and keep a comparable group on the current setup over the same recovery window. Agree up front on how much more revenue you’d need to see to expand the test. For changes to first-attempt approvals, include fraud and chargebacks in that review.
Whichever you ask for, leave the meeting with an owner and a date.
If you can’t easily pull these numbers yourself, talk to Revaly. We’ll use your existing renewal data to show what’s approved, recovered and still lost, so you walk into the planning meeting with the number in hand.

