Rebuilding Bajaj Finserv's POS loan for the field
Bajaj Finserv
Year
2025
Duration
2 Months
A 30-minute, 11-stage Salesforce desktop tool was being used on mobile browsers by field agents at retail counters across India. Competitors closed the same loan in 11-12 minutes. I led the redesign for mobile web with scan-led inputs, progressive disclosure, in-flow recovery, and a tiered scheme recommendation that embedded business logic into the design itself. The redesigned journey was accepted by the MD of Bajaj Finserv. Application time dropped from 40 to under 20 minutes. Completion lifted from 60–70% on web to 75–85% on mobile
Contributors

Why this project?
A customer walks into an electronics store in Lucknow and asks for a phone on EMI. An agent steps in with a tablet while the dealer hovers and the queue grows behind them. In the next 20 minutes, the agent has to find the customer in the system, verify their KYC, scan documents, pick the right scheme, set up a UPI mandate, get the agreement signed, capture the invoice, and submit it for QC. Competitors do all of this in 12 minutes

The tool was built for desktop Salesforce. Used on mobile browsers by agents on their feet. The tool wasn't broken. It was designed for the wrong person
68%
Applications with at least one manual entry error
3x
Browser hops per application (camera, UPI, signature)
40 min
About the Users
FOS Agents (Primary)
Feet on Street agents run the entire flow, standing in retail stores and processing 10–15 applications a day. Most speak Hindi or regional languages, work on mid-range Android devices, and deal with patchy in-store networks
Customers (Secondary)
Customers touch the flow only at specific moments which are UPI QR scan, KYC via 3-in-1, loan review. They bring limited patience and varied digital literacy to the counter
Dealer (Stakeholder)
Dealers stand in the background but shape the agent's pace. They want the sale closed before the next customer walks in
















