Action first
Payment state and the primary action stay visible without requiring horizontal navigation.
Designing the mobile payee experience at Built
- Role
- Lead Product Designer
- Team
-
- Product Manager
- Engineering Manager
- Customer Support
- Marketing
- Timeline
- 1 month
- Platform
- Responsive web
Problem
The product had been designed primarily for desktop, but most payees were accessing Built from their phones. Inconsistent patterns added friction to the steps required to receive a payment.
Solution
I redesigned the full payee journey for mobile, creating responsive, accessible, and reusable patterns across payments, bank accounts, and lien waivers.
Result
The redesign created a simpler path to getting paid and established a stronger foundation for a scalable design system.
The problem
A desktop product met a mobile reality
Built’s payment product served two sides of a transaction: payers, who sent payments, and payees, who received them.
The payee experience was especially important because payees needed to complete several critical steps before getting paid: accept a payment, add a bank account, and sign lien waivers.
While the existing experience worked on desktop, most payees were accessing Built from their phones. The desktop-first interface didn’t translate well to smaller screens, and the absence of a mature design system meant patterns and components varied across the journey.
For someone who simply wanted to receive their money, the product introduced friction at exactly the wrong moment.
My role
Design the journey, not a collection of screens
I redesigned the entire payee experience for mobile, working through every screen and state in the existing web flow rather than addressing individual screens one at a time.
My goal was to create a consistent experience that worked across screen sizes while improving usability and accessibility.
Accept a payment
Add and manage bank accounts
Review and sign lien waivers
Understand payment details and status
Reconsidering the hierarchy for a smaller screen
Mobile was not a scaled-down desktop table. It needed a new content model that surfaced the next action without losing the payment context.
%201.png)
Context preserved
Amount, project, invoice, due date, company, and requirements remain scannable in a compact card.
Details on demand
Secondary information is progressively disclosed so each payment remains easy to scan.
Core flow
One clear path to accepting a payment
The redesign connected the steps required to receive money into one coherent mobile flow, with consistent navigation, form patterns, validation, and status messaging from start to finish.
- Keep the next required action prominent.
- Break longer tasks into manageable steps.
- Make progress, errors, and completion states unambiguous.
System thinking
Reusable patterns across the whole experience
I audited the existing payee journey and rebuilt the screens using reusable patterns for navigation, forms, inputs, buttons, status messaging, and responsive layouts.
Rather than optimizing individual screens in isolation, I treated each decision as part of a shared product language—one that could stay consistent as payees moved between payments, banking, and documentation.
Navigation
A predictable structure kept users oriented while they moved through required tasks.
Forms and inputs
Repeatable field, validation, and action patterns reduced relearning between flows.
Status messaging
Consistent language and visual treatment clarified what was done and what remained.
Responsive patterns
Make complex controls feel native to mobile
Dense desktop controls became focused mobile interactions. Filters moved into a bottom sheet that preserved context, supported comfortable touch targets, and kept the receivables list available beneath it.
Accessibility
Designed in from the beginning
Accessibility was part of the redesign from the start. I improved typography, hierarchy, spacing, touch targets, form patterns, and contrast so the experience remained clear and usable on smaller screens.
These were not finishing touches. They shaped the responsive patterns and component decisions that the broader product could build on.
The outcome
Built to help payees get paid
The redesign created a responsive, accessible payee experience across the full payment journey and introduced consistent UI patterns that could be reused as the product evolved.
It also established a stronger foundation for a design system, helping the team move away from designing individual screens toward building with repeatable components and patterns.
For payees, the result was a simpler experience focused on what mattered most: completing the required steps and getting paid.