UX RESEARCHFINTECH0 → 112 WEEKS

Trust Over Revenue

I don't defend the design. I defend the solution. Two conflicts from a fintech build that processed ₹1.5Cr in its first month.

Platform

Merchant Payments. An intercity network where stall owners and their proxy staff settle daily payments. High volume, tight cash cycles, zero patience for friction. One designer (me), 1 PM, 2 devs, 12 weeks.

Constraint

A decade of burned trust. Merchants had tried and abandoned platform after platform. Every screen had to earn instant reliability without touching their daily cash routine.

Features

Cash Flow Tracker: settlement timelines and earnings in real time. Proxy Controls: hard operational bounds for delegated staff. Compliance Locker: verification and approval logs in plain sight. Identity Hub: a status report that unblocks payments, not a settings page.

Crack

Adoption was never blocked by missing features. It was blocked by uncertainty: cash settlements, approval delays, cryptic errors. Trust was the growth lever.

Approach

Twice in this build, someone challenged the design. Both times I refused to defend it. I prototyped the alternatives and defended the solution instead. Both fights are below.

Signal

₹1.5Cr processed in month one. Operational stability, speed, and clarity beat the feature checklist.

CASE 01

The banner everyone wanted.

Early wireframes. The PM wanted a big transactional banner pushing payments at the exact moment users were most unsure. I didn't argue taste. I prototyped both directions with AI tools and let the evidence testify: guidance close to the action reduced hesitation, the banner added pressure. The banner lost.

CASE 02

The form nobody asked to remove.

The safe move was a standard Edit Profile form. Correct pattern, wrong solution. The owner never logs in; their staff does, mid-rush, trying to unblock a payment, not browse settings. So the profile became a status report: spot the expired document, fix it, keep the money moving. Nobody asked me to remove the form. The solution did.

Impact

200+Merchants Onboarded

70%Enterprise Adoption

90%KYC Completion Rate

PAPER TRAIL

Every flow, every dead end, every revision. The full working file, unedited.

EXHIBITS

OUTCOME

₹1.5Cr processed in month one.

The web app grew into a native mobile app, meeting merchants where they work. One widget settled ₹1.2Cr in five weeks with zero "where is my money?" tickets.

LEARNINGS

The design lost twice.Both times the shipped thing was better than the defended thing. That's the job.

Clarity beats reassurance.Merchants didn't want promises. They wanted to see where the money was, every hour of the day.

Evidence ends arguments.A quick prototype of both directions closed debates that opinions kept open.

TRADEOFFS

Simplified on purpose.Advanced capabilities were cut from phase one to protect clarity and speed.

Web shipped first.The native app waited until the platform had earned trust on the counter, not before.

Opinionated defaults.Proxy staff got hard bounds, not settings. Fewer choices, fewer errors.

WHAT's NEXT

Reopen the docket.The capabilities simplified in phase one return as the platform scales.

Follow the behavior.Merchant habits will outgrow phase one. The design has to follow them, not the roadmap.

Predict, don't react.Settlement clarity earned adoption. The next win is flagging issues before merchants ever see them.

You just scrolled through 4,200px of design.

Clearly, you care about detail. That’s exactly how I build products. If you value craft, polish, and execution, let's build together.

a friendly wager

Beat me at tic-tac-toe and there will be no salary negotiations.

You're X. Make your move.

LinkedIn→GitHub→Resume→