Paytient app screens: home, rewards, spending summary, transactions, notifications, card details, payments and settings
Work

Building the design foundation behind 1M users

Taking Paytient from a small MVP to a mature, full-featured product.

Summary

  • ServicesProduct design, Design systems, User research
  • IndustriesHealthcare, Fintech
  • DateNov 2021 - Jun 2025

I joined Paytient as its first full-time product designer, when the product was a basic MVP, and spent nearly four years turning it into a full-featured, mobile-first platform. I built the design system, ran user research, took the product through a company rebrand, and helped grow the design team from 2 to 5 people.

Results

  • 100k → 1M

    Eligible users

  • x6

    Monthly card payments

  • ↓35%

    Time to full onboarding

  • ↑63%

    Onboarding completion rate

Paytient's visual language: type, colour palette, photography, icons and the mobile app home screen

Timeline

  • Late 2021Joined as employee #33. The product was a basic MVP with minimal branding and generic UX.
  • Early 2022Designed and implemented Paytient's first design system.
  • Mid 2022Ran the first foundational user research and led the first in-person product offsite.
  • Late 2022Supported a company-wide rebrand and updated the design system and every product visual to match.
  • 2023 - 2025Grew the design team from 2 to 5, expanded the design system, and launched new features and products.

The challenge

When I joined, the product had basic functionality and a sparse design language and brand identity. Paytient is a Health Payment Account (HPA) that employers or health plans give to their members, so they can pay for care over time without interest or fees. Three things needed doing at once:

  • Expand the product's features while consolidating its visual language.

  • Build a scalable, well-documented, mobile-first design system.

  • Set up design workflows that would make scaling and collaboration easier.

That was a lot for one product designer. The only other person sharing the work was a UI designer and front-end developer, and he left a few months later.

Design system

I'd built design systems at RMS and knok Healthcare, so I knew we needed one to grow in a structured way, on both the design and the implementation side. I also knew a growing system is laborious to manage, because any change can break existing designs. We settled on three principles to keep it manageable:

  • Mobile-first

    Paytient is a mobile-first product, so the system follows the same rule. Clear rules for how mobile designs adjust to larger viewports cut a lot of design and development complexity.

  • Purposeful minimalism

    We kept the system lightweight to limit design debt, adding only the styles, components and patterns we needed. Before adding anything new, we asked how many other places it would be useful and whether an existing component could do the job.

  • Consistency before style

    We kept one visual language that followed Paytient's brand and matched the coded components.

Paytient Design System 2.0 pages: logo, cards, buttons, icons, typography, colors, inputs, notifications, tabs, dropdowns and navigation
Paytient Design System 2.0

Working with engineering

Front-end engineers built a repository of coded components that matched the system's components and patterns. They also helped us set practical naming conventions for design tokens: margins, corner radius, font sizes and colors. Consistent token names kept design and code closer together, removed ambiguity, and made the system easier to maintain.

Paytient home screen on tablet, phone and desktop
The home screen's responsive behavior

Product goals

With the foundation in place, we could finally expand the product. Our goals came from business needs and customer feedback. Priorities shifted over time, but three stayed constant:

  • Increase onboarding completion

    Simplify the flow and build trust with members earlier.

  • Increase card utilization

    Turn the home screen into a hub that explains how the product works, announces new features and reminds members about pending items.

  • Reduce delinquency

    Surface early payment and past-due options throughout the app so members repay on time.

The onboarding flow

We personalized the key steps of the onboarding to welcome members in and help them trust Paytient earlier, which raised engagement and cut drop-off. Between 2021 and 2025, completion went from 53.7% to 87.4%, and the average time to finish fell from 3.6 to 2.35 minutes.

Onboarding splash screens: pay for care your way, interest-free payment plans, no credit check to apply, and take care today

We ran A/B tests to find out what would raise completion and get more members to submit their Ability to repay details. We tested a more personalized welcome screen, and split identity verification into more steps with clearer copy. We rewrote the income and expenses questions so members knew it wasn't a credit check, and improved the illustrations on the login screen.

Five onboarding experiments in Figma, each comparing the current screens with proposed changes: welcome screen, identity verification, ability to repay, application intro and splash screen
Onboarding experiments

We added biometric login, so returning members get back into the app with Face ID or a fingerprint instead of typing a password every time. To keep accounts secure, we also added multi-factor authentication.

Onboarding screens: set your password, use Face ID to sign in, a personalized welcome, and enable notifications
Product deck slide on the launched onboarding, with the repayment plan step removed: validate phone or email, create login, welcome, assess ability to pay, and sign agreements and policies
Summary of onboarding improvements from a late 2024 product deck

The home screen

The home screen was our main lever for getting members to use their Paytient card more. I turned it into a hub that explains how Paytient works, announces new features and reminds members about anything pending.

Dev-ready home screen states, from ineligible and not ready to spend through active, failed payment, past due and cancelled card, each with its delinquency, eligibility, onboarding and card status
Home screen variations by eligibility, identity verification, new features and past-due payments.

I added a summary card that shows what a member spent in the last 90 days, with a link to a full breakdown, and a to-do list that collects pending items in one place. I also reworked “Where to use Paytient” to show examples of eligible care.

Paytient home screen with the account summary card, Paytient card, to-do list and Where to use Paytient, flanked by the summary card’s add payment method and past-due states

Transactions and payments

Every Paytient transaction has a repayment plan behind it, so members need to see what they spent, what they still owe and whether they're on track. This area is also where we worked on our third goal, reducing delinquency.

Members are more likely to repay on time when paying is easy and the next step is obvious, so we focused on three things:

  • Setting up a repayment plan takes a few steps and lets members choose how many payments to make.
  • Members can pay any transaction in full at any time, or make an extra payment to get ahead.
  • When an installment is past due, the transaction shows a clear button to pay it and get back on schedule.
Setting a repayment plan: choose a plan or pay in full, pick a payment method and number of payments, and confirmation that the plan is saved
Transaction details on schedule, past due and paid, and the repayment plan timeline

We also added the Paytient summary, which shows a member's transactions in a chart split by type, with clear infographics of their health spending over time.

Transactions screen with no transactions yet, a list with a transaction waiting for a repayment plan, the filter sheet, and the Paytient summary with spending by category and top merchants

Expanding to desktop

What started as a lightweight library for the mobile-first product soon had to cover new products. The biggest was the Paytient Operations Portal (POP), a desktop-only management dashboard with different requirements. I created a separate library for POP. Most styles and components still came from the core system, and POP added desktop components like tables, advanced filters and metric cards.

Paytient Operations Portal styles and components: type, blue and fuchsia colors, metric cards and a filtered table
Paytient Operations Portal employees page at three widths: full sidebar, collapsed icon sidebar, and the sidebar expanded over the content
The POP, short for Paytient Operations Portal

How we worked

Paytient's development process was an adaptation of Scrum, and we adapted the design process from that to fit how design work actually runs. Design sprints overlapped with development sprints, so we could share certain ceremonies, and we kept adjusting the process to serve the team.

User research

We ran in-person and remote research throughout. Two in-person rounds with real members, in New Orleans (June 2022) and Columbia, Missouri (October 2022), were open conversations about how people used Paytient day to day, what got in their way, and which features mattered. Watching their reactions as they used the product let us test larger features and app redesigns in a real setting and uncover needs we hadn't spotted.

For targeted feedback on specific features, we used UserTesting.com and Maze. Participants completed tasks or moved through prototypes while we collected quantitative and qualitative data. It was faster and cheaper, and it reached more people, though we had to explain the product well to testers who had never seen it. We iterated quickly and caught pain points before launch.

Growing the team

As Paytient scaled, I helped recruit and onboard new designers, taking the team from 2 to 5. I established the documentation and processes that let them contribute to the product, encouraged open, constructive feedback between designers, and made sure everyone felt comfortable sharing ideas. That moved us from one solo designer to a team working together.

Outcomes

  • The design system let us iterate quickly and kept the experience consistent as Paytient grew.
  • Agile workflows and documentation helped new team members get up to speed and supported cross-functional work.
  • The refreshed identity made Paytient feel like a trusted, modern option in healthcare fintech.

What users said

★★★★★

"Account was very easy to setup and website is simple to navigate."

Cristopher, Feb 2024

★★★★★

"Setting up the card was a breeze, and I was impressed by how quickly I could access funds for my healthcare needs."

Andrea, Sep 2024

★★★★★

"Easy to setup and easy to use."

Milton, Jan 2025

★★★★★

"Super easy! And easy to navigate the app!"

Christine, Mar 2025