[OSS GAP] Subscription Dunning #payments #subscription #recovery #smb
Pain: SaaS teams want a narrow failed-payment recovery workflow instead of paying for a full billing platform just to send retry emails. ”## Summary Replace the custom 2-step cancel/feedback modals with Churnkey’s SDK for intelligent cancel flows (surveys, targeted discount offers, A/B testing) and failed payment re” — github-issues (https://github.com/Kilo-Org/cloud/pull/1799)
Why now: Small teams in 2026 are cutting tool spend and refusing extra platform debt. Chargebee, Recurly, ProfitWell Retain are strong products, but they are packaged for bigger companies than small SaaS and other small teams. That makes a smaller, self-hosted wedge in subscription dunning unusually easy to explain.
Tiny wedge: Failed payment webhooks for small SaaS and other small teams without Chargebee-style pricing and platform weight.
Why this wins: Replaces recurring Chargebee spend with a boring self-hosted alternative for small SaaS and other small teams.
Scope cut: Skip full billing engine and revenue recognition in v1.
Stack: Node.js + Express + PostgreSQL + Redis + background worker + Web Components + REST API + webhooks.