Failed payment recovery, built by a solo founder for solo founders.

The problem

Every SaaS leaks revenue every month and most founders never see the bill. Industry data from ProfitWell, Baremetrics, and Stripe all converge on the same numbers:

• 5% to 12% of monthly subscription revenue fails to charge
• 9% on average for mature SaaS, climbing as your MRR grows
• Stripe Smart Retries (the default) recovers about 38% of failed charges
• A dedicated dunning tool with email, SMS, WhatsApp, checkout recovery, and cancellation flows can push that to 60% to 80%

For a $10k MRR business, that gap is $5,000 to $8,000 per year sitting on the table, recoverable by tooling that runs in the background.

Why we built Rebounce

The dunning category was built for enterprise. Category leaders charge $129 to $249 per month minimum, and many take a percentage of recovered revenue on top. That math works for a $500k MRR business. For a $5k MRR indie SaaS, paying a quarter of recovered revenue back to the recovery tool defeats the point.

So most small SaaS founders default to Stripe's built-in retries and silently leak 60% of failed payments. The tools that would solve it cost more than the leak itself.

Rebounce starts at $3.50/month, never takes a cut of recovered revenue, and bundles channels (SMS, WhatsApp, checkout recovery, cancellation flows, win-back campaigns) that the $200/month incumbents do not include together at any price.

Who builds Rebounce

Arthur Sprengel — founder, solo developer, based in Brazil.

I built Rebounce because I needed it. After years working with subscription products I kept seeing the same pattern: small teams losing real money to failed payments because the tools that would fix it priced them out. The tooling was enterprise. The problem was universal.

I write the code, talk to customers, and ship product. There is no growth team and no support tier — if you email hello@rebounce.dev, I read it. You can also reach me on X.

How we are different

• Affordable. $3.50/mo at the entry tier; the most expensive plan is $39/mo with no MRR cap. No revenue share, ever.
• Multi-channel by default. Most dunning tools are email-only. Rebounce includes SMS (45% to 50% open rate) and WhatsApp (90%+ open rate) so customers actually see the message.
• 5-minute setup. Stripe Connect OAuth, no migration, no data import. Connect and Rebounce starts watching for failures.
• Pre-dunning included. Card expiry warnings 30 days before a card expires — prevent the failure entirely instead of recovering after.
• Built for founders. Plain pricing, no sales calls, no contract minimums, no procurement cycle.

Built on (transparency)

We use boring, well-understood infrastructure. No part of recovery depends on a single point of failure.

• Frontend: Next.js 14 (App Router) on Vercel
• Database: PostgreSQL on Supabase, with Row-Level Security per organization
• Payments: Stripe Connect OAuth (read + write to retry failed invoices)
• Workflows: Inngest for durable retry chains and email sequences (cancellable when a payment succeeds)
• Email: Resend for transactional and dunning email
• SMS / WhatsApp: Twilio with direct payment links
• Hosting: Vercel (US/global CDN)

Stripe OAuth tokens are encrypted at rest with AES-256-GCM. Payment update links are JWT-signed with 72-hour expiry. We never store card numbers. See our DPA and Privacy Policy for the full picture.

Where we are going

The roadmap is shaped by what customers ask for. Active areas:

• Better deflection: cancellation flows, win-back, downgrade paths
• More billing providers (Paddle is in active development)
• Smarter retry scheduling based on cohort decline patterns
• Per-customer recovery analytics

If you have a problem we could fix, tell us.

Contact

• Email: hello@rebounce.dev
• X (Twitter): @rebouncedev
• Data protection / GDPR / LGPD: see DPA