Lending Platform Design System
A commercial lending origination and servicing platform — serving both government programs and commercial markets — had no design system. Multiple teams (product, engineering, marketing, sales) all needed mockups fast, and they all needed to look like one product when they landed.
Without a system, a small team couldn't keep up. Building one was the single highest-leverage move available.
The design system as connective tissue
A lending platform is deceptively complex: government programs and commercial workflows each carry their own forms, branching logic, and compliance shapes. The design system picked up the mockup backlog, standardized the look across teams, and freed everyone to think about the hard UX problems instead of redrawing the same input field for the third time that week.
For a stretch it carried an entire in-house design shop — product mockups, marketing assets, sales-deck support — all from the same tokens, so the brand stayed consistent without anyone hand-touching every file.
From design system to component library
A design system makes the design half fast. But engineering was still rebuilding components from scratch every time. The next step was a real component library — design and engineering on one source of truth.
From that point, replacing legacy screens stopped being a rewrite and became a genuine refactor. Whole sections of the product modernized in weeks rather than quarters, and the experience took a step change each time another surface got swapped over.
Two pieces worth calling out
A new data table. Built from the ground up — filters, saved custom views, column resizing, per-user display settings. Borrowers, loan officers, and admins all live inside it, so the impact of one component spread further than any other.
The borrower portal. A multi-quarter effort that took the borrower experience from a digitized-paper application — long, intimidating, abandoned mid-flow — to a focused, task-based portal. Conversion went up across every institution running on the platform.
Why it matters
A design system, then a component library, then the specific components and flows users actually feel — done in that order, on a small team, alongside everything else.
Foundations let small teams ship like big ones. That's the lever, and it's the first thing we build into a client engagement.