Overview

Replacing customization with configuration in enterprise lending.

Biz2X is a B2B SaaS platform that enables financial institutions in India to launch and scale digital lending products. As the platform onboarded more banks, NBFCs, and fintechs, application journeys became increasingly fragmented due to client-specific customizations.

This case study covers the design of a configurable application navigation pattern—specifically the application stepper—that enabled scalable onboarding without redesigning flows for every new client.

The problem

When scale exposed the cracks.

Each financial institution had its own credit policy, evaluation logic, and application requirements. These differences were handled through hardcoded screens, one-off frontend logic, and custom flows per client.

This made onboarding slow, fragile, and expensive. From a user perspective, applicants navigated using only Back and Next, with no visibility into where they were, what came next, or how much effort remained.

An image illustrating the mechanism of the interaction states to be followed for any interactive element.

Design context

Designing inside a system already in motion.

I worked as a senior individual contributor, collaborating with PMs, engineers, and the sales team. I identified the absence of a scalable application structure early during onboarding and led the design of a reusable navigation pattern focused on application completion.

Key insight

Eligibility was the invariant.

Despite wide variation in product types, credit policies, and data requirements, every lending journey revolved around eligibility.

What changed was how eligibility was evaluated, what information was required before it, and how complex the journey became after it. This insight became the anchor for restructuring the application flow.

The approach

One journey, two navigation models.

The application journey was split into three phases: pre-eligibility, eligibility, and post-eligibility.

Pre-eligibility used a fixed linear stepper to maintain momentum and clarity. Post-eligibility used a hub-and-spoke navigation model to support complex, multi-entity, and multi-day tasks such as document uploads, co-applicants, and verifications.

Algorithm chart for a self-sustaining feed generation.

System design

Configuration as a design material.

A JSON configuration schema became the single source of truth for the application journey. It defined step order, grouping, skippability, and mandatory rules—allowing new client journeys to be launched without redesigning screens or interactions.

To preserve platform consistency, layout, spacing, components, and interactions were fixed. Clients could customize labels, colors, and typography.

Algorithm chart for a self-sustaining feed generation.

Outcome

Impact beyond UI.

Client onboarding time reduced by 60%, while application completion improved by .

New lending journeys could be configured by sales and engineering teams without any design involvement, significantly improving speed to market.

x

Reflection

Designing systems, not screens.

This project reinforced the importance of aligning navigation models with cognitive load and encoding business rules into scalable design systems. Good systems make good experiences repeatable.