Paul Wentzell UX
Home
About
Paul Wentzell UX

Enterprise complexity deserves great user experiences.

I build both.

Making products is what I love — and I mean all of it. The messy research, the wrong turns, the moment something finally clicks, and the satisfaction of watching something you designed actually ship.


I've spent 10+ years designing enterprise systems for financial platforms, insurance, compliance, and IoT — the kind of products where complexity is the job, not 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. I design in the language engineers work in — Blazor, AG Grid, design tokens, component specs — and I stay in through implementation until what shipped matches what I designed.

Enterprise complexity deserves great user experiences. I build both.

Making products is what I love — and I mean all of it. The messy research, the wrong turns, the moment something finally clicks, and the satisfaction of watching something you designed actually ship.


I've spent 10+ years designing enterprise systems for financial platforms, insurance, compliance, and IoT — the kind of products where complexity is the job, not 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. I design in the language engineers work in — Blazor, AG Grid, design tokens, component specs — and I stay in through implementation until what shipped matches what I designed.


I also build with AI. I used Claude Code and the Figma Plugin API to generate an entire enterprise design system in three days. That's not a party trick — it's where the craft is going, and I'm already there.


Research-led. Engineering-fluent. Always learning.

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. I've spent my career in those environments because that's where the hard problems are.

Most designers know one stack, one domain, one way a company works. I've designed across fintech, insurance, industrial automation, aviation, HR technology, and regulatory compliance. Every engagement is a new domain, a new set of constraints, a new team that needs to trust the work quickly. That's sharpened how I research, how I frame problems, and how I hand things off in a way that actually holds.

12+

12+

10+

10+

10+

6

6

7

7

YEARS IN

ENTERPRISE UX

YEARS IN

ENTERPRISE UX

ENTERPRISE

ENGAGEMENTS

ENTERPRISE

ENGAGEMENTS

INDUSTRIES

SERVED

INDUSTRIES

SERVED

FRAMEWORKS

MASTERED

FRAMEWORKS

MASTERED

INDUSTRIES

INDUSTRIES

HOW I WORK

Fintech

Insurance

Industrial Automation

Aviation

HR Staffing & Compensation

Regulatory Compliance

HOW I WORK

I use AI as a working tool, not a shortcut. I completed MIT xPRO's Designing and Building AI Products and Services to understand how these systems actually work — not just 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's always been — fewer gaps between intent and implementation.

SKILLS & TOOLS

UX Research

Interaction Design

Design Systems

Component Architecture

Accessibility (WCAG AA)

Figma

Figma MCP

Tokens Studio

Miro

Axure

DevOps

Claude

Copilot

GitHub

FRAMEWORKS I'VE DESIGNED FOR

SKILLS & TOOLS

HOW I WORK

SKILLS & TOOLS

.NET Blazor

Angular

React

AG Grid

Google Material

AWS Cloud Native

Prime NG

RIGHT NOW

Looking for a senior or staff UX role in fintech, compliance, or enterprise SaaS — somewhere with a real design system problem and room to shape how the team works.

Making products is what I love — and I mean all of it. The messy research, the wrong turns, the moment something finally clicks, and the satisfaction of watching something you designed actually ship.


I've spent 10+ years designing enterprise systems for financial platforms, insurance, compliance, and IoT — the kind of products where complexity is the job, not 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. I design in the language engineers work in — Blazor, AG Grid, design tokens, component specs — and I stay in through implementation until what shipped matches what I designed.

Enterprise complexity deserves great user experiences. I build both.