WorkWritingAboutContactLet's talk →
Fintech UXProduct ThinkingCollect App

Three UX Problems We Fixed in Collect

Real fixes from building a fintech app from zero.

Editorial diagram showing three Collect UX fixes: KYC upload, contextual calling, and paid-date filtering.

Collect taught me that trust is not one screen or one badge. It is built through visible states, preserved context, and filters that match how users actually reconcile money.

Fix 01

The onboarding flow nobody could finish

The original onboarding asked business owners to enter details in the app, then send identity documents over WhatsApp to a phone number. After that, they waited without a clear status or timeline.

For a financial product, that broke trust immediately. We were asking users to share sensitive documents through a channel that felt informal, untracked, and disconnected from the product.

The fix was to bring document capture and KYC status into the app. Users could upload documents directly, see when they were received, understand review status, and know what to do if something needed correction.

Collect UX synthesis board showing problem, design response, and trust gained across KYC, calls, and paid-date filtering.
Each fix converted an invisible or context-breaking moment into a visible product state.

Fix 02

The context switch costing collections

Collections managers often needed to call customers while looking at mandate details: amount, due date, payment history, and outstanding balance.

Before the fix, calling meant leaving the app, opening the dialer, typing or copying a number, making the call, and returning without the same mental context.

A simple call icon solved more than a tap count problem. It opened the dialer with the number prefilled while keeping the Collect context available in the background.

Fix 03

The filter we were missing

The instalment page originally focused on due dates. That made sense for collections, but it failed reconciliation.

At month-end, users needed a different question answered: of everything expected, what actually came in during this period? A due-date filter could not answer that cleanly.

Adding paid-date filtering gave users a reconciliation view without exporting data or manually cross-checking records. The same data became useful because the axis changed.