Ten years taking founders from blank canvas to shipped product: strategy, flows, UI, design systems, and handoff that developers actually want to build. Solo. Remote. End-to-end.
{{ item.summary }}
{{ item.quoteShort }}
{{ t.quote }}
I'm a senior product designer who works the way a founder needs one to: solo, remote, and across the entire arc, from the strategy conversation, through flows and wireframes, into polished UI, a real design system, and a handoff your engineers can actually build from.
For a decade I've done this for international clients across SaaS, AI product interfaces, dashboards, web apps, and iOS. I care less about making screens look nice and more about whether the product earns trust, because that's the part that decides if it ships and survives.
I take on only a few founders at a time. That's the point: depth over volume.
A few founders at a time, end-to-end. Remote, worldwide.
{{ active.summary }}
{{ active.overview }}
{{ active.problem }}
{{ active.approach }}
{{ procText }}
{{ active.outcome }}
A walk through what the prototype was built from, and the polished screens that shipped.
A complete flow for the Client role, mapped before a single screen got drawn. The Assistant and Admin roles followed the same method, each given its own world rather than being squeezed into a shared template.
The low-fi screens the clickable prototype was built from. These went through several revision rounds with the founder and real users before any visual design started.
~200 polished screens across the three roles, built on the client's brand guidelines. A selection of the screens that did the heaviest lifting in the product.
The polished admin experience that shipped, designed in parallel for web and mobile.
The desk-based admin panel for project leaders managing enterprise accounts.
The on-the-go and on-site companion, so the same insights were one tap away from anywhere on the job.
The artifacts behind the product. From flows to wireframes to the polished screens that shipped.
A complete flow for each role, mapped before a single screen got drawn, buyer and seller given their own paths rather than being squeezed into a shared template.
Pen-and-paper sketches for every screen, drawn fast and revised faster. These were the structural foundation the prototype was built from.
~80 polished iOS screens across both roles, designed in Sketch on the client's brand system. A selection of the screens that did the heaviest lifting in the product.
The artifacts behind the foundation: flows and wireframes. Drop in the images and these fill out.
Complete flows mapped in Overflow for the two main jobs the app had to do well. Each one drawn out so every navigation path was deliberate, not improvised.
Low-fidelity wireframes for every screen, drawn in Sketch and wired into a clickable prototype for testing. A few of those wireframes are shown here.
{{ active.quote }}
That kind of three-role complexity, or a different tangle you need someone to sit with end-to-end. Tell me where you are and I'll tell you how I'd help. Replies within 24 hours.