Range built on the same way of thinking.

I designed and shipped Contract Intelligence as it evolved across files, payer policies, claims, agents, reports, monitors, and reusable templates. The draw proved to be less about managing contracts and more about helping revenue-cycle and contracting teams use policy and contract data to answer consequential questions.

By the time I left, we were moving toward integrating OpenPolicy and Price Intelligence—including Pivot Table capabilities—into one consolidated Trek platform.

I established shared foundations, tokens, components, and product patterns aligned with Material UI. The system supported dense data tables, document workflows, navigation, authentication, permissions, and AI interactions across Trek’s products.

Adoption was substantial but never absolute. We refined the system iteratively while moving quickly to ship, using it to create consistency as the product changed.

I wrote product copy across onboarding, guidance, notifications, errors, empty states, and reengagement experiences. The work translated unfamiliar or sensitive moments into direct next steps while preserving the voice of each product.

At Anchor, onboarding turned a complex billing product into a sequence of concrete, time-bounded actions. At Salaryo—the product previously known as Cashmere—account language clarified loan status, repayment choices, upcoming payments, and a detailed transaction history. For Budgie, I designed a card flow that let people switch between insurance terminology and plain English while comparing plan costs.

As Options MD’s only product designer, I created the design system and worked directly with the cofounders to define the end-to-end flow. The mobile experience had to make eligibility, provider selection, and scheduling understandable in a sensitive behavioral-health context.

The work shows how I structure consequential choices: set expectations first, state clinical criteria plainly, then make provider availability easy to scan and act on.