The expensive part of design isn't the design. It's everything after the ambiguous states nobody specified, the interaction that turns out to be impossible, the three days of back-and-forth in Slack because the Figma file answered one question and raised four.

I spent close to three years as a software engineer, building and maintaining a POS platform running across hundreds of retail stores, before moving into product design. I know what a component actually costs to build. I design accordingly, and I hand off files your engineers can implement without a translation layer.

Product design — Interface design for web and mobile, from flows to final screens. Every state accounted for: empty, loading, error, edge case. Not just the happy path.

Design systems — Tokens, components, and rules that hold up as the product grows. Structured to map cleanly onto whatever framework your team is already using.

UX research & usability testing — Testing when there's a real question worth answering. On a previous project I found a 21.1% misclick rate on a core feature and resolved it with contextual coach marks, that kind of finding is what this is for, not research theatre.

Prototyping — High-fidelity interactive prototypes when a static mock won't settle the argument. Motion and interaction specified properly, so nobody's guessing at timing or easing.

Engineering-ready handoff — Specs written by someone who's read the ticket from the other side. Component logic, responsive behaviour, states, and the reasoning behind decisions your team will otherwise have to reverse-engineer.

Marketing & brand surfaces — Landing pages, social assets, and launch material designed inside the same system, so the marketing site and the product stop looking like different companies.

Continuous iteration — Weekly cycles. You get work you can review and act on, not a status update.

We set priorities at the start of each week. I work in cycles and share progress at the end of each one. Async updates in whichever tool your team already uses, plus a call when a decision needs a conversation rather than a thread. I'm available to your engineers directly during implementation, most handoff problems take five minutes to resolve if you can just ask.

Roughly 25 hours a week. One retainer client at a time, so you're not sharing my attention.

Seed to Series A teams with engineers and no in-house designer. Teams whose product has outgrown whatever it was designed with a year ago. Founders who need someone to own design end to end rather than take tickets.

Teams who want an agency, a dedicated squad, or three concepts to pick between. I go deep on one direction and iterate. If you want options to vote on, I'm the wrong hire.

Two-month minimum. Month one is usually the most intensive, that's when the foundations get set.