Recurly occupies an interesting position in the billing world: more dunning machinery than most platforms ship, real account-updater integrations, a configuration surface with genuine depth. Teams choose it partly for that sophistication. Then a pattern repeats that Recurly's own consultants could probably recite: the implementation partner configures the dunning campaigns during onboarding, everyone nods at the defaults dressed as decisions, and the configuration is never seriously revisited — not because the team is lazy, but because a configurable system gives no alarm when its configuration has quietly stopped matching the business.
Configurations rot in specific directions
The retry cadence set for a young subscriber base stays in place when the base ages into annual plans, where a failed charge deserves a longer, more patient window than a monthly plan's. The email templates written for a product's first hundred customers keep sending at the hundred-thousandth, in a voice the company no longer uses anywhere else. The cancellation-for-nonpayment rule chosen to keep the books clean starts amputating accounts that a longer grace period would have recovered whole. None of these are bugs. They are the predictable half-life of settings chosen under different facts, which is why mature Recurly shops treat dunning configuration as a quarterly review item rather than an onboarding artifact.
The data Recurly gives you, and the question it cannot answer
Recurly's reporting will show recovered revenue and dunning performance with reasonable clarity. What it will not cleanly separate is which lever produced a given recovery — the platform's retry, the account updater's silent refresh, the email that finally reached the subscriber — because from the platform's chair those are all "dunning worked." From your chair the distinction is the entire improvement program: levers you cannot tell apart cannot be tuned apart. The workaround is unglamorous — periodic exports, manual tagging of what happened immediately before each recovery — but a quarter of that data will tell you more about your next configuration change than a year of dashboard totals. An operator's review of failed payment recovery on Recurly goes station by station through where the platform's machinery ends and an operator's judgment has to begin.
When the answer is a second system
There is an honest point in a Recurly shop's growth where the recovery problem outgrows what configuration alone can express: coordination with the gateway's own retry logic, save offers at the cancellation moment, recovery reporting that separates the levers by design. That point is recognizable — the configuration reviews start producing smaller gains, and the failure file's composition (more authentication declines, more platform-collision cases) stops matching what the built-in tools were shaped for. Naming that point, when you reach it, is cheaper than a year of tuning a system past its design center.
The review agenda, if you want one
A useful quarterly pass over a Recurly dunning setup asks five questions, in order. Has the plan mix changed enough to make the retry windows wrong? Has the decline mix changed — in particular, is the authentication-required share creeping up in a way the current email-first flow handles badly? Do the templates still sound like the company, and do they still name the product the way subscribers know it? Are recoveries being attributed to levers anywhere, even roughly, or is every improvement discussion still anecdote against anecdote? And has the business crossed into territory — a second platform, a storefront pipe — where a single-platform recovery view no longer describes the whole failure file? Five questions, one export, an hour. The configuration almost always confesses something.
Configurable is a compliment to a platform and a responsibility for its operator. The shops that get Recurly's worth revisit the settings on a schedule. The rest are running a 2023 opinion about their customers, at scale, every night.
Platform operations notes from Swipe Again, for subscription businesses on serious billing stacks.
Top comments (0)