I work in code from day one — you review live URLs, not static files. Four phases, roughly six weeks, weekly deploys the whole way through.
I study what already exists before designing what comes next.
Content hierarchy and information architecture, in writing.
Flows and states built as working pages, not static mocks.
Production code — components, tokens, motion, accessibility.
Edge cases closed, docs written, support window after ship.
Every project is different, but the rhythm is usually the same: get clear, move fast, build properly, then tighten until the work feels ready for the real world.
Before any design happens, I need the real problem — which is rarely what the brief says. I audit the existing product, talk to whoever owns the outcome, and we agree in writing on what done looks like.
Typical outputs
I design in the browser, not in Figma. You get clickable flows built with real components at real widths — because a static comp hides every problem that only shows up when content changes or the viewport shrinks.
Typical outputs
Design and code move as one. I ship production-ready components weekly — not prototypes you hand to someone else. Every Friday ends with something live you can review on a real URL.
Typical outputs
The part that decides whether the work outlives the engagement. Performance pass, accessibility audit, edge cases closed, and documentation written so the next person doesn't reverse-engineer my reasoning.
Typical outputs
Timelines flex with scope — a single flow is faster than a design system, a marketing site shorter than a product surface.
I keep the stack flexible, but these are the tools I use most often across design, build, and delivery.
I like fast progress — a mix of async updates, focused calls, shared files, and tight feedback loops. I can plug into your existing workflow or run a lightweight structure on my side.
One call at the start to find the real constraint and agree on what done looks like.
One channel for everything — questions, updates, feedback. No context split across tools.
What shipped, what's next, what I need from you. Written, async, never a meeting.
You review the actual URL, not a screenshot. Comment on the real thing whenever suits you.
Docs, a walkthrough, and reasoning behind the non-obvious calls — so it survives me.
I stay available after launch. Questions, tweaks, edge cases — I don't disappear on day one.
How we stay aligned.I don't vanish for two weeks and come back with a big reveal.
A short call to scope the work, or see how I engage.