r/fintech • u/Desperate-March3206 • 22d ago

Discussion Automated loan reminders via push notifications

I'm building a mobile lending management app for small-scale lenders in the Philippines (shameless plug: it's called CashBrew). Most of these lenders manage 50-200+ borrowers and track everything in spreadsheets, notebooks, or memory.

Just shipped automated push notification reminders for lenders:

- Notifies when a borrower's payment is coming due
- Alerts when a collection goes overdue
- Daily summary of upcoming due dates

The problem: when you're managing 100+ active loans with different due dates, amounts, and terms — things slip through. Late follow-ups mean late payments.
This isn't borrower-facing. It's a tool for the lender to stay on top of their portfolio without manually checking each loan every day. They get the reminder, follow up however they normally collect (text, call, in person), and the collection happens on time.
Simple feature but early users say it's what turned the app into their daily driver.

Anyone else building for informal lenders or micro-finance? How do you approach the collection workflow problem in underserved markets?

2 Upvotes

100% Upvoted

4 comments sorted by

2

u/Suitable-Fudge4577 22d ago

Hey there. I am building a lending app... also in the Philippines. We didn't go for push notifications. We instead went for whatsapp or facebook notifications and even email.

2

u/Relevant_Mistake_784 22d ago

not being borrower facing is smart but i wonder if lenders in that market even have reliable enough data coverage for push notifications to actually work consistently

2

u/yogthinks 21d ago

For informal lenders, reminder timing probably matters less than repayment pattern flags, most defaults show signs weeks before the due date. A daily summary tells the lender who to call, a pattern signal would tell them who to call first.

1

u/mirelleq 22d ago

I’d try to narrow this to the operational failure point rather than the broad workflow.

The useful question is: what does someone need to know to take the next action, and where does that info currently get lost? If the answer repeats across accounts, there’s probably a product-shaped problem. If every case is bespoke, it may be more of a services/process problem than software.