Loan Origination System for Gold Loan Product (0-1)

4 mins read

Contribution:

End-to-End

Team:

2 PMs, Head of Product, Business, Client(Bank)

Duration:

3 Months

Context

Aumnee is a technology company solving fintech problems through innovative SaaS solutions, empowering banks to manage the complete loan lifecycle.

As an expansion of Aumnee products suite, we were tasked with Building a Loan Origination System (LOS) to streamline the end-to-end gold loan journey.

I lead this 0-1 project as sole product designer - which includes collaborating with PMs, owning visual design, prototype.

Background: Why We Built This

In many banks and NBFCs, customer gold loan applications are still managed through a mix of spreadsheets, emails, and manual paperwork. Even when digital platforms exist, they’re often generic flows or outdated systems not tailored for gold loans.

This leads to:

  • Fragmented loan journeys across tools

  • Manual gold assessment and valuation logging

  • Delays in approval due to offline processes

  • No clear visibility into application status

Solution

We built a Gold Loan Origination System (LOS) to solve these problems — a dedicated platform that digitises and streamlines the entire loan journey, from creation to disbursement, with role-based access, rule-driven approvals, branch-level support and real-time visibility.

My Role

As the product designer, I was responsible for converting complex defined workflows into a smooth, role-based digital journey — ensuring speed, clarity, and accuracy for both field officers and internal approvers.

I kickstarted this project with understanding end-to-end workflow diagram created by the PM (see below image).

This visual became our north star — helping map the stages, edge cases, and dependencies.

I also created a role matrix to identify the responsibilities and goals of each user type. This helped validate our designs during review meetings.

Role matrix created by me to understand each type of roles

NOTE: Given the project's multiple modules, I’ll focus on just a couple to keep the case study short and concise. Happy to present more during a call.

How do we assist users in filling 250 inputs efficiently?

When a potential customer requests for the loan, the first step is collect customer data and input into the system. These details which are nearly 250 fields are being collected and entered into platform along with document collection and verification.

So the challenge was, "How to make this activity easier, less overwhelming and faster for the user?"

Why faster? Because speed matters here. Typically the TAT for the gold loan is 40-50mins. So the platform should be easy and quick for the user.

I was shared with different categories of data and the fields that needs to be collected from the customer. I ensured whether the proposed categories and order in which data is collected is logical and helps user understand faster and suggested changes wherever necessary.

I worked closely with the PM, who had gathered direct requirements from the client. Since I couldn’t speak to end users myself, I relied heavily on detailed conversations with the PM to understand:

  • How does the journey looks from the point customer comes to bank requesting loan to final disbursement

  • How does customer data is collected? (Through any physical form or verbal)

  • Why existing processes is causing bottlenecks

Objectives

  • Simplifying the data entry process for complex forms.

  • Ensure flexibility for different types of customers (e.g., individuals, businesses).

  • Provide clear sections to prevent users from feeling overwhelmed.

  • Make mandatory and optional fields visually distinct.

  • Support validations and document uploads inline to minimise context switching.

Initial Approach

Entering 250 fields manually can feel overwhelming for anyone.

  • A common way to make this easier is to break the process into smaller steps. However, in this case, that may not work well—because users often don’t know in advance which customer data they’ll have with them when customer visit the bank. So, it’s important to give them the flexibility to fill out the fields in any order that suits them.❌

Final Outcome

  • The form is broken down into well-defined collapsible sections. Each of customer data is grouped logically, and stacked one by one for user to fill faster.

  • One left side, I created checkbox with category to make easier for user to track his progress

  • Quick scroll is enabled to move top to bottom of the page quicker since it's a long page.

Challenges Addressed

  • High data volume: The form handles extensive data but segments it for better focus.

  • Data accuracy: Inline verification reduces manual errors and rework.

  • Flexibility: The form allows the user to save partial progress and fill sections in any order.

Some key design Highlights

Data accuracy: Inline verification reduces manual errors and rework.

Friction less OTP Verification

Application Tracking Dashboard for Bank Users

This dashboard was designed for banking staff to monitor, track, and manage loan applications at different stages of the loan lifecycle — from collateral & valuation to disbursement.

The goal was to provide clear, actionable, and scalable view because of large volume of applications, ensuring timely follow-up and transparency.

  • Each column gives specific info that’s important for tracking and taking action

  • The status tags are color coded to help users quickly understand what stage something is in or if it needs attention.

  • I also added filtering, sorting, and search to help users narrow things down fast. I decided to go Tabs at the top because it helps switch between stages smoothly without needing to go to another page.

Overall, the idea was to reduce visual clutter, make it fast to skim through rows, and support high efficiency for daily ops work.

Designing a dedupe module

As part of loan processing, to ensure that the applicant does not have multiple or fraudulent identities, and to get a clearer picture of their creditworthiness, a process called Dedupe (short for de-duplication).

How it works

  • The system checks incoming customer data against internal records.Uses match algorithms to flag duplicates.

  • Matches are categorised (Partial match, Complete match) and shown to the operations or credit team for review.

  • Bank can choose merge if they found close match, or else create a new ID.

Final design

Home page

For the dashboard, I wanted to use it to surface key information tailored to each user based on their role, and evaluate whether it could be helpful and informative.

Since there were primarily two distinct personas involved, we needed to design two different home screens depending on the user’s role:

  • Branch Manager – Needs to view rich analytics related to overall products, loan performance, AUM, disbursal rates, and more.

  • Branch Ops – Information related for day-to-day operations. They need to see dashboard metrics such as task counts and a recent history of assigned tasks.

Designing a Clear & Traceable Audit Log Timeline

We wanted to help internal users track every action of users for each applications. In fintech, especially in loan processing, maintaining traceability is super important for compliance and internal reviews, so the goal here was clarity and transparency.

I structured the log as a vertical timeline to show a clear chronological flow.

  • Each action is grouped with its timestamp, the person responsible, and relevant icons to make scanning faster.

  • For example, uploads are shown with an upward arrow and linked to filenames, while edits show old vs. new values with strike-through and arrows to visually communicate what changed—this helps users catch important updates at a glance.

  • I also added a “Show less” toggle for long updates to keep the view from feeling overwhelming. The “Filter by” and “Export” options give power users more control, especially when they need to extract logs for audits or reports.

The focus was on building a trustworthy, human-readable timeline that doesn’t feel like a wall of text. It’s meant to make ops teams feel confident about what happened, when, and by whom.

Outcome

We launched the product with the client and it is currently being used by banks everyday and has become lots of positive feedbacks due to its reliability and effectiveness.

Learnings and Highlights

1.My biggest project yet

This was the largest project I’ve shipped as the solo designer. It came with a lot of responsibilities and tight timelines. It was definitely challenging, but with the right feedback at the right time, I was able to navigate through and deliver successfully.

2.Faster turnaround, higher approval

After incorporating major feedback in the first round with 40% changes, I was able to deliver the second iteration with just 5% changes and a turnaround time of 1 week. This not only sped up the process but also improved stakeholder alignment and approval significantly.

3.Balancing quality and delivery

I learned how to manage my time better and work more efficiently. There were moments when I couldn’t deliver pixel-perfect designs, but this project taught me that sometimes timely delivery matters more than quality of designs—especially when the stakes are high.

Still here? This project was a massive in scope, and I'm leaving few more out. I'd be delighted to talk about it in more detail.

Other Projects

Redefining User Management & Task Assignment in Loan Origination

Read Case study

Designing a no-code tool for banking users to manage lending policies easier

Read Case study