
A hardware company's first app
A guided flame-sensor diagnostic for field technicians, live in both app stores with the hardware launch.

An AI CRM, shipped solo in five days
A live AI-assisted CRM with a design-to-code loop that holds. Real APIs, open to click through.

Five tools into one
A disconnected underwriting stack consolidated into one workspace. 25% faster turnaround.

A system, built in three days
Twenty components and seven handoff documents, authored with Figma MCP and AI in three days.

Subscription complexity made legible
A subscription and activation model nobody had mapped, made readable and validated against real users.

12 teams, one source of truth
A speed brief, reframed as a structural fix. Twelve investigation teams aligned on one workspace.

First designer to acquisition
Three compensation products built from scratch with no system to inherit, validated by acquisition.

Paper out of oil analysis
A hand-filled aircraft checklist rebuilt as a validated app. Errors caught at the aircraft, not the lab.
Making products is what I love, all of it: the messy research, the wrong turns, the moment something finally clicks, and the satisfaction of watching something you designed actually ship.
12+ years designing enterprise systems for financial platforms, insurance, compliance, and IoT, the kind of products where complexity is the job rather than the problem to avoid. Trading dashboards, investigation workflows, diagnostic tools, design systems. Data-dense, high-stakes environments where clarity isn't a nice-to-have.
What I've learned is that the gap between a great design and a great product is almost always the handoff, so I close it. The design lives in the language engineers work in, Blazor, AG Grid, design tokens, and component specs, and I stay in through implementation until what shipped matches what I designed.
WHAT I DO
Enterprise complexity is the job I want. Financial platforms, compliance tools, IoT dashboards, insurance systems, products where the data is dense, the stakes are real, and design decisions have consequences past the next sprint. My career has been in those environments because that's where the hard problems are.
Most designers know one stack and one domain. My work has spanned fintech, insurance, industrial automation, aviation, HR technology, and regulatory compliance, and every engagement brings a new domain, new constraints, and a team that has to trust the work quickly. That has sharpened how I research, frame problems, and hand things off in a way that holds.
6
7
Fintech
Insurance
Industrial Automation
Aviation
HR Staffing & Compensation
AI is a working tool here, not a shortcut. The MIT xPRO course Designing and Building AI Products and Services grounded how these systems actually work, beyond how to prompt them. Day to day that means Claude for synthesis and structured thinking, GitHub Copilot for rapid prototyping, and Figma MCP to keep design and development closer together. The goal is the same as it has always been: fewer gaps between intent and implementation.

UX Research
Interaction Design
Design Systems
Responsive Design
Component Architecture
Accessibility (WCAG AA)
Figma
Figma MCP
Tokens Studio
Miro
Axure
DevOps
Claude
Copilot
GitHub
DESIGNED FOR
.NET Blazor
Angular
React
AG Grid
Google Material
AWS Cloud Native
Prime NG
RIGHT NOW
Open to senior and principal UX roles and contract work in fintech, compliance, insurance, or enterprise SaaS, Boston or remote.
Looking for a real design-system problem and room to shape how the team works. Find me on LinkedIn.
