If you were shopping for dunning software back in 2021, Churn Buster was probably on your shortlist. It was the pragmatic, Stripe-friendly choice. Focused on involuntary churn, transparent about how it worked, and not tied to any particular billing platform.
Then in 2022, Recurly acquired it.
A lot of SaaS operators I've spoken to since still aren't sure what that meant for them as customers, or whether Churn Buster is still the right call if they're running on Stripe and have no intention of migrating billing systems. This post walks through what we know, what likely changed, and why some teams are now actively looking for independent dunning tools again.
What actually happened
In 2022, Recurly, the subscription billing platform, reportedly acquired Churn Buster. Recurly framed it as a way to strengthen its retention capabilities for subscription businesses. Churn Buster had spent years building email sequences, payment recovery flows, and analytics specifically for failed payments. On paper, it was a natural fit.
For existing Churn Buster customers, nothing broke overnight. The product kept running, sequences kept firing, and Stripe integrations kept working. But the center of gravity shifted. Churn Buster was now part of a billing suite, not an independent product.
That's the detail that matters most.
Why the shift matters for Stripe-first teams
Most Churn Buster customers were, and still are, Stripe users. They picked Churn Buster precisely because they did not want to migrate billing. Stripe handled their subscriptions, invoicing, and payment methods, and Churn Buster bolted on to recover the ones that failed.
When a dunning tool gets acquired by a billing platform, the long term product strategy usually tilts in one direction. The acquiring company has an incentive to deepen integration with its own stack. Customers who use the acquirer's full suite get the best experience. Customers who use a competing platform often sit in a holding pattern.
We're not saying Churn Buster got worse for Stripe users. We're saying the roadmap is no longer driven purely by what Stripe users need. It's driven by what Recurly customers need, with Stripe support maintained as a legacy capability.
If you're a Stripe-first SaaS team, that's a subtle but real change in how you should think about the tool.
What likely changed under the hood
A few things tend to shift after this kind of acquisition, based on how similar deals in the SaaS space have played out:
- Pricing alignment. Independent tools often start cheap to win standalone customers. Once absorbed into a larger platform, pricing tends to drift upward to match the parent company's enterprise posture.
- Sales motion. Self-serve sign ups get deprioritized. The sales team starts routing prospects into demos and annual contracts, because that's where the acquirer makes its money.
- Feature prioritization. New features ship faster for the acquirer's native billing users. Stripe integrations get maintained but rarely get new capabilities first.
- Support SLAs. Standalone support often gets folded into the broader customer success org, which can mean longer response times for smaller accounts.
None of this is malicious. It's just gravity. When a tool becomes a feature of a bigger platform, it has to serve the bigger platform's goals.
Why some teams are looking for independent alternatives again
Over the last eighteen months, we've noticed a pattern in conversations with founders. Teams that picked Churn Buster three or four years ago are starting to ask the same question: "Is there still an independent dunning tool built for Stripe, with transparent pricing, that isn't going to get bought and pivoted?"
The reasons come up consistently:
- They don't want to be a second-class user on someone else's billing platform
- They want pricing they can predict without talking to a sales team
- They want the product team focused on one thing: recovering failed payments on Stripe
- They want to avoid lock-in to a full billing suite they'll never use
Involuntary churn still costs SaaS companies around 9% of MRR on average. About 40% of failed payments come from expired cards, and the rest from insufficient funds, 3DS2 challenges, fraud blocks, and issuer declines. Recovering even half of that is meaningful revenue. Teams want a tool whose only job is that recovery, nothing else.
What to look for in an independent dunning tool
If you're reevaluating your stack, here's what actually matters for a Stripe-first SaaS team:
Native Stripe integration that stays current. Stripe ships new APIs and webhook events regularly. Your dunning tool needs to keep up without waiting in a feature backlog behind a full billing platform.
Email plus SMS. Email-only recovery tops out around 50% of recoverable payments. Adding SMS typically lifts that by another 15 to 25 percentage points because SMS open rates are dramatically higher. If your tool only sends emails, you're leaving money on the table.
Pre-authenticated payment links. Customers shouldn't have to log in, find their billing page, and re-enter a card. A one-click update link converts significantly better.
Transparent, flat-fee pricing. Percentage-of-recovered pricing can look fair, but it scales with your success in ways that punish growth. Flat fees are easier to forecast.
A real ROI dashboard. You need to see recovered revenue, recovery rate, and cost per recovery in real time. Not in a monthly PDF.
GDPR-aligned opt-outs. If you sell into the UK or EU, you need proper opt-out handling for both email and SMS, and an auditable trail.
Where Rekko fits
We built Rekko because we kept hearing the same frustrations from Stripe-first founders. They wanted something focused, predictable, and independent. Not a feature inside someone else's billing platform.
Rekko is flat-fee dunning software for Stripe. Email plus SMS sequences, pre-authenticated payment update links, a real-time ROI dashboard, and GDPR-compliant opt-out management. Setup takes about five minutes because we connect directly to Stripe via OAuth and read failed invoices from webhooks.
We're not trying to become a billing platform. We're not going to ask you to migrate anything. The only thing we care about is recovering the payments Stripe tried and couldn't. That's the whole product.
If you're a current Churn Buster customer and the post-acquisition direction doesn't match where your business is going, it's worth a look. We also have comparison pages for Churn Buster, Churnkey, Recurly, and Stunning if you want to see how the options stack up.
The honest trade-off
To be fair, Churn Buster under Recurly is still a capable product. If you're already using Recurly for billing, it probably makes sense to use their native retention features. The integration story is cleaner when the tools are built by the same company.
The question is whether you're a Recurly customer or a Stripe customer. If you're the latter, you probably want a tool whose entire product roadmap is aimed at your stack.
That's the gap independent tools like Rekko fill. Not better than Recurly at being Recurly, but better at being focused, predictable, and Stripe-native.
Try Rekko free
If you want to see what flat-fee, Stripe-first dunning looks like, you can try Rekko without committing anything.
- Email plus SMS sequences
- 5-minute Stripe connection
- Pre-authenticated payment links
- Real-time ROI dashboard
- Flat monthly pricing, no percentage of recovered revenue
Start your 14-day free trial. No credit card required. See our pricing for full details.