Hi r/NoCodeSaaS,  
I’ve been researching how collections and payment recovery workflows are managed operationally across fintech, lending and AR systems.

One pattern I kept noticing was how fragmented the workflow can become across reminders, retries, payment tracking and reconciliation — especially once scale increases.

To understand the space better, I built a small realtime orchestration prototype that explores:

• multi-channel reminders (WhatsApp/SMS/email)  
• retry workflows  
• payment links  
• realtime payment reconciliation via webhooks  
• operational recovery timelines  
• automatic cancellation of retries after payment

The goal wasn’t to build a polished product, but to better understand how modern collections systems actually operate and where the operational pain points are.

I recorded a short workflow demo below and would genuinely love feedback from people working in:

* collections/recovery operations
* fintech lending
* AR automation
* subscription billing
* payment operations

A few things I’m especially curious about:

1. How are reminder/recovery workflows typically managed today at scale?
2. Are teams still switching across multiple tools for reminders, reconciliation and payment visibility?
3. How operationally useful is realtime payment reconciliation in practice?
4. What are the biggest pain points in collections/recovery workflows today?
5. Do modern collections platforms already solve this well, or are workflows still fragmented internally?

Would really appreciate honest feedback — especially from operators actually dealing with these workflows day-to-day.

Researching modern collections/recovery workflows — built a realtime orchestration prototype around reminders, retries, payment links and reconciliation. Curious how teams currently handle this operationally.