Lendly. 4 months turning complex lending operations into one clear workspace.

4 months
From structure to final UI
5+ core areas
Leads · Deals · Clients · Tasks · Analytics
1 connected system
UX · Visual identity · UI system
Lendly overview dashboard with performance chart and recent leads

Overview

A B2B platform that connects client information, deal activity, and the tasks needed to move work forward.

Lendly is a financial CRM for loan professionals managing leads, deals, contacts, and client activity.

The challenge

A CRM needs to support both a broad view of the pipeline and detailed work on an individual deal.

The design challenge was to connect those levels: help users review ongoing activity, open the relevant record, and understand what needs their attention next.

A loan professional reviewing the Lendly overview at her desk

What I owned

I designed the product’s information architecture, user flows, and interface, including dashboards, data tables, client profiles, deal views, and task management. My role also included the visual identity and reusable Figma component system.

How I approached it

I designed the analytics dashboard, lead management views, tables, and filters.

These screens organize information at different levels of detail. The overview presents performance and activity, while record-level views provide the context needed to work on a specific client or deal.

My Leads table with contacts, loan purpose, amount and status

Key decisions

Keeping deal context close to daily tasks

Deal views bring together client information, recent activity, documents, and tasks. I designed the relationship between these sections so that the interface could support ongoing work within the context of a deal. Task views distinguish upcoming work from its history, while the activity feed provides a record of updates.

Consistent patterns for a data-heavy product

Lendly uses recurring interface elements across tables, profiles, dashboards, and forms. I created a design system covering typography, navigation, inputs, buttons, tags, cards, and interaction states. Shared patterns provided a consistent foundation for both the existing screens and future product work.

Deal view with recent activity, upcoming tasks and task history
Notifications panel with lead updates, replies and shared files

Outcome

  1. 01Information architecture and user flows.
  2. 02Dashboards, lead management, client profiles, and deal interfaces.
  3. 03Task, activity, table, and filter designs.
  4. 04Visual identity and a reusable Figma design system.

More projects.

Building or improving a custom CRM? Let’s look at the workflow connecting your clients, deals, and daily tasks.