✳  CASE STUDY · FINTECH

FinPay — unified invoicing & payments dashboard

ROLE
Lead Product Designer
TIMELINE
10 weeks · 2025
PLATFORM
Web app
TEAM
1 PM · 4 engineers
Final dashboard UI — hero shot
✳  OVERVIEW

Finance teams were juggling five disconnected screens to reconcile a single invoice. The redesign brought invoicing, payments, and reporting into one operational view.

I led design end-to-end: two weeks of research with 12 finance operators, a full IA restructure, and a component-level redesign built on a new token system the engineering team could adopt incrementally.

✳  THE CHALLENGE

Years of feature bolt-ons had left the back office fragmented: duplicated data entry, no single source of truth, and a 9-minute average reconciliation task. Support tickets about "where do I find…" made up a third of the queue.

✳  THE SOLUTION

A task-first information architecture organized around the operator's day, not the database schema. One unified queue, inline reconciliation, and progressive disclosure for edge cases — shipped incrementally over three releases.

Before / after flows
Wireframes & IA map
Component library
Final UI details
Full dashboard view — wide shot
Reconciliation queue — detail
Mobile companion view
Empty & error states
Reporting module
✳  BEHIND THE SCREENS
Research synthesis wall
Early sketches
Research session
✳  RESULTS
42%
Faster task completion
58%
Lift in feature adoption
-33%
Navigation support tickets
4.7
Post-launch CSAT (of 5)

"Babar became the design brain of our product. Work that used to need a whole team now ships in half the time."

Alex Carter — Product Lead, FinPay
NEXT CASE STUDY
MediCare — patient booking made effortless →