WHEN EVERY NEW LENDER
BROKE THE UI
A Loan Management System (LMS) builder that moves lender setup from code to configuration, so Application Engineers (AEs) can create a customizable dashboard for each lender with minimal or no developer help.
To set up a new lender. A team estimate, not tracked in analytics.
AEs configure lender dashboards with little or no developer help.
UI, Workflow, Task and Policy builders in one configuration system.
Every new lender meant a new build
A lender's dashboard used to be built in code. The old dashboard was driven by rigid configuration, so a lender who needed something different meant developer work.
Every lender went down the same path, and an AE who wanted a change to a dashboard had to ask a developer.
- Ticket
- Design
- Code
- QA
- Deploy
Months for a new lender, by the team's estimate.
So the question became: how can the people closest to the lender set it up themselves?
One dashboard, four builders
A lender's dashboard is not one screen. It is four builders working together, and each one answers a different question about an application.
01UI Builder
What do people see?
Shapes what people see and work in.
02Workflow Builder
Where does the application go next?
Manages where an application goes and how it moves.
03Task Builder
What has to be done first?
Decides which tasks must be completed before an application can move on.
04Policy Builder
Who can do or see what?
Decides who can complete those tasks, and who can view or edit specific information.
Role, Team, Timeline & Constraints
Product designer and problem owner, end to end. I defined the problem, designed the UX and UI, and worked through technical trade-offs with engineers.
A Product Manager, myself as the designer, and a group of developers.
5 to 6 months.
- The old dashboard was driven by rigid configuration, which limited how screens could be designed.
- The database structure decided what the interface could show, so some gaps had to be solved in the design itself, not in the data.
- Data arrives through an API that needs a trigger, so screens could not assume the information was always live.
LMS Builder
We built a modular, block-based system that allows product teams to configure the entire application lifecycle without touching React.
Ticket → Design → Code → QA → Deploy
Configure → Preview → Live
Four modules
Each one has its own tab on the left, with the decisions behind it.
PlaygroundSee all four working togetherChange a task, a stage, a permission or a tab, and watch the dashboard update live.