Waystar
Three years inside one of healthcare's largest payment platforms, designing claims management and shaping applied AI as both product designer and product manager.
Healthcare payments run on software patients never see. For three years I worked where the volume is heaviest, the claim itself.
Waystar sits at the center of the healthcare payments ecosystem. The platform processes over 7.5 billion payment transactions a year across more than $2.4 trillion in gross claims, serving roughly 30,000 clients that represent over a million providers.
Claims management is the working heart of that platform. It's where revenue cycle teams submit, track, and resolve the claims their organizations depend on, and where errors compound fastest at scale.
The work itself lives behind the platform, inside client workflows and regulated data, so this page tells the story rather than showing the screens. I walk through the work in detail in conversation.
Approach
At this scale, small design decisions move billions in claims. The work was making complexity feel routine.
Product Manager
Applied AI
2026 – Present
Shaping how AI and agents move from promise to shipped capability inside the revenue cycle.
The problem is administrative burden across the revenue cycle. Denials are the most visible piece, hundreds of millions of them a year, but the same friction runs through eligibility, prior authorization, coding, and getting paid. Waystar's answer is AltitudeAI, the platform's AI capability set spanning denial prevention and reimbursement recovery. The team works across that arc, finding the places where generative and agentic AI can lift real, repetitive work off a revenue cycle team without asking them to trust a black box.
Building AI products in a regulated domain is a trust discipline. Every capability has to clear accuracy thresholds and earn adoption from the teams whose work it changes. It only holds up when the products are explainable and actionable, so the specialist can see why the system did what it did and act on it in a single move. The first test is whether the team trusts it enough to follow a recommendation. The real promise is whether they trust it to run the routine on its own, so they can stay on the cases that need judgment.
Senior Product Designer
Claims Management
2024 – 2026
Leading design for the workflows that move claims from submission to resolution.
Claims management is a volume product. Clients use it work through millions of claims a day, monitoring status, resolving rejections, attaching documentation, and chasing the denials that put revenue at risk. I owned design across those workflows, for daily users who measure the product in keystrokes.
The recurring design problem at that volume is triage. Ninety-five percent of claims should move without a human touching them. The craft is making the exceptions unmissable and the routine nearly invisible. That meant designing for scanning over reading, prioritization over lists, and workqueues that put the highest-risk claims first.
It also meant consistency at platform scale. Patterns established in claims echo across the suite, so every design decision carried a second question. Does this hold up everywhere the platform repeats it?
Scale
Company scale, from Waystar's public reporting.