PayPlan: a configurable lending platform built for scale

PayPlan: a configurable lending platform built for scale

A centralized loan system that shares data smoothly across products, configures to any lender, and unifies applications, underwriting, payments, and reporting in one place.

Client

Business Warrior

Role

Product Designer

TIMELINE

Ongoing | 0->1

SCOPE

Design System · UX/UI

cover_image

Core dashboard, lender configuration, and reporting

Overview

PayPlan is a configurable lending platform that lets non-technical operators launch and run financing programs without engineering. I owned the product from a blank canvas to software processing real loans at scale.

What I owned

Founding design across a 0→1 build: product definition, research, end-to-end UX, and UI across 100+ screens, plus the token-based design system, documentation, and developer handoff.

SCOPE
0

+

Screens designed

0

+

Lender configurations

0

M+

Loans processed

01 — Background & Problem

Lending built on fragmented, disconnected systems

Lenders had no centralized loan system. Data sat in silos across products, nothing was configurable to loan type or underwriting, and the stack couldn’t flex or scale as programs grew. Every new lender or loan type meant custom work that should have been reusable.

Without a centralized, configurable system, lenders couldn’t scale; every new program rebuilt what should have been shared.

problem_image

The fragmented status quo before PayPlan

02 — Goals

What the platform had to do

1.

Be white-labeled for any lender.

2.

Stay fully configurable for multiple loan types and their unique data needs.

3.

Support quick release and deployment so new programs scale efficiently.

The Work

Final designs

The payoff: fast, flexible surfaces that could be configured without redesigning from scratch.

final_designs_hero

Configurable lender dashboard and workflow system

final_design_1

final_design_2

03 — Design Process

From evidence to a system

Four phases: stake, study, layout, prove.

“We were saying yes to lenders faster than we could actually build them.”

Research & discovery — interviews and support evidence distilled to the insight that framed the work.

Research & Discovery

Product Designer

process_user_flows

User Flows

Product Designer

process_wireframes

Wireframing

Product Designer

process_iteration

Iteration

Product Designer

04 — Design System

A token-based system built for flexibility

To support multiple lenders, loan types, and white-label deployments, I designed a token-based design system that prioritized flexibility, consistency, and speed.

Color

Type

Aa Aa Aa

Spacing

Data types

Users, portfolio screens, payment cards, messages, and payments

Users, portfolio screens, payment cards, messages, and payments

Data types

Users, portfolio screens, payment cards, messages, and payments

Users, portfolio screens, payment cards, messages, and payments

Data types

Users, portfolio screens, payment cards, messages, and payments

Users, portfolio screens, payment cards, messages, and payments

Models

Reusable decisions without losing lender flexibility

Reusable decisions without losing lender flexibility

module1_image_1

module1_image_2

Patterns & System Logic

Product Designer

The system aligned design and engineering around shared primitives, enabling rapid iteration across 100+ screens and cutting developer handoff time by 40%.

05 — Architecture & Scale

From a product to a platform

PayPlan was built as a modular system: applications, payments, and reporting are independent yet share one unified data model. That structure is what lets the product reconfigure itself per client instead of being rebuilt for each one.

architecture_diagram

Configurable feature flags

Turn capabilities on per lender without core code

Turn capabilities on per lender without core code

Configurable feature flags

Turn capabilities on per lender without core code

Turn capabilities on per lender without core code

Configurable feature flags

Turn capabilities on per lender without core code

Turn capabilities on per lender without core code

architecture_diagram

06 — Core Product Modules

Four modules, one data model

Every visual captioned; image count varies by module.

Portfolio Management & Reporting

A single dashboard gave lenders portfolio health at a glance, replacing exported spreadsheets.

module1_image_1

module1_image_2

Underwriting

Risk signals surfaced inline, cutting decision time and removing manual re-checks.

module2_image_1

module2_image_2

module2_image_3

module2_image_4

Loan Applications

One adaptive intake reshaped itself to each lender’s rules, lifting completion.

module4_image_1

module4_image_2

module4_image_3

Collections & Customer Portal

Automated collections and a self-serve portal cut manual follow-up and reduced missed payments.

module3_image_1

module3_image_2

08 — Results
0

+

Screens designed

0

+

Lender configurations

0

M+

Loans processed

09 — Reflection

Thinking in systems

The hardest call was choosing configuration over open-ended customization: less freedom per lender, but a platform that stays reliable and ships fast at scale. Designing PayPlan taught me that the strongest systems decide what to leave out as much as what they include.

Next Project

Rivet — Design system at scale

Have a complex product that needs clarity?

Founding designer crafting clear, reliable product experiences from early definition to shipped software.

Available for new projects

© 2026 Austin Griblin. All rights reserved.

Founding designer crafting clear, reliable product experiences from early definition to shipped software.

©2026 Austin Griblin.

All rights reserved.

Founding designer crafting clear, reliable product experiences from early definition to shipped software.

© 2026 Austin Griblin. All rights reserved.