HeiGin UI
The design system behind the HeiGin CRM: production-derived components, copyable source, and a docs site.

Product designer and PM. Nine products from blank page to something real. Currently designing at Noon and shipping HeiGin.
The design system behind the HeiGin CRM: production-derived components, copyable source, and a docs site.
300 people were ready to pay before the platform existed. So I skipped Figma.

We built an HR platform. Two pilots told us they wanted a CRM.

I use Claude, Gemini, and Lovable as collaborators, not shortcuts. They compress research and prototyping. The judgement stays mine, and every AI-touched output gets reviewed against user reality.
I’d rather put a rough version in front of 20 users than polish an idea nobody has touched. Me&Dev launched as a basic MVP before it earned a redesign. HeiGin found its real product only after two pilots said “this isn’t the expensive problem.”
Static screens hide interaction problems. I prototype in HTML with real components (shadcn, Tailwind), which means the handoff is less of a translation and more of a merge. Engineers I’ve worked with confirm this.
Where there’s no playbook is where I’m most useful. PRDs, competitor teardowns, RBAC models, information architecture, the first visual system. Early-stage, real ownership, engineers in the room.
Product taxonomy and information architecture across grocery, fresh produce, ice cream, and electronics.
Ad-tech and productivity SaaS. Designed Attrimo, an SSP, and a productivity app for music artists.
Brand guidelines and marketing design.