02 · NETSOL Technologies

Enterprise finance, simplified

Designing clear workflows for an automotive-finance platform that connects lenders, dealerships, and customers in one ecosystem.

Role
Senior Product Designer
Focus
UX strategy & end-to-end design
Period
2025—Present
Type
Enterprise B2B

NDA-safe workflow model

DealershipApplication & documentsLenderDecision & statusCustomer

One shared finance process, shaped into role-specific views and clear handoffs.

Context

Enterprise clarity is built from careful decisions, not decoration.

I work on an enterprise automotive-finance platform that brings dealerships, lenders, and end customers into a unified digital ecosystem. Leasing and finance products carry dense rules, operational dependencies, and specialist terminology, so each role needs a clear view of the same underlying process.

The work includes application and finance workflows, status visibility, document-handling moments, and customer-facing interactions—described here at a level that respects confidentiality.

My contribution

I lead UX strategy and end-to-end product design, translating complex operational requirements into journeys, interaction models, prototypes, and implementation-ready interfaces. I design multi-role workflows in which different users access the same process from different perspectives.

  • Map end-to-end journeys, user roles, decisions, and edge cases across the financing lifecycle.
  • Define information architecture and simplify information-heavy screens into clear steps and status cues.
  • Turn requirements into interaction flows, detailed Figma prototypes, and reusable patterns.
  • Partner with product, engineering, and stakeholders from requirements through validation, handoff, and delivery.

Working approach

I begin by making the operational model visible: who acts, what information they need, what decisions they make, and where the workflow can fail. From there, I shape the hierarchy and interaction model before moving into detailed interface design and handoff.

Specific screens and operational details remain confidential. This case study reflects the scope and design approach.

Value

A shared model for users, product, and engineering.

The result is a clearer path from complicated requirements to buildable product behavior, supported by reusable patterns that help multiple applications feel more consistent.