I design websites and digital products for teams that need more than a pretty comp. The work covers everything from marketing sites to the interfaces people actually use day to day: dashboards, account areas, booking and ordering flows, internal tools.

Because I also build, I design things that can be built. Components that repeat instead of one-off screens. States that account for empty, loading, and error. Type and spacing systems a developer can implement without guessing. That tends to save a round of revisions and a lot of Slack messages later.

I start with what the thing has to accomplish. Who's using it, what they're trying to get done, and where the current experience gets in the way. If there's a brand identity in place, I extend it into an interface language rather than decorating on top of it.

Discovery: goals, audiences, competitive context, content and feature requirements

Sitemap, user flows, and information architecture

Wireframes for key screens and states

Visual design across all core templates or product screens

Responsive design from mobile through desktop

Component library and design system: type scale, color, spacing, buttons, forms, cards

Interaction and motion notes

Prototype for testing or stakeholder review

Developer handoff: organized Figma file, specs, and a walkthrough call

Structured phases with a deliverable and an approval at each one. You see flows and wireframes before any visual design happens, so we're not debating color when the real question is structure.

For studios and agencies: I can work inside your file conventions, present alongside you, or stay white-labeled. For product teams: I'll work against your existing system and extend it rather than replacing it.