Courier
I built the initial architecture and most of the early implementation of Courier's embeddable message designer. As the team grew, I continued developing its document conversions, editing behavior, and saving workflows.
Product engineer. AI interfaces & systems.
I build complex frontend products, from the initial architecture through release and ongoing development with a team. My work spans embeddable editors and shared UI platforms. Today I'm building FamilyBoon, a system for family documents and context across AI sessions.
Read the Courier case studyIndependent work01 / Ongoing
Family archive in use
App in development
Documents, context, and unfinished work beyond the chat.
Shared family memory / The work cycle
I use Boon to work with my family's documents and ongoing matters. Original files, matter notes, and saved work remain in the archive, independent of any chat. Conversations retrieve relevant sources, and I save replies and useful context back to the shared record.
I'm developing an app around these workflows. The broader direction is a family archive that can outlive its apps, preserving personal accounts and history for future readers.
Read the engineering story
I built the initial architecture and most of the early implementation of Courier's embeddable message designer. As the team grew, I continued developing its document conversions, editing behavior, and saving workflows.
I was a main contributor to Propel's public UI kit for data interfaces. My work covered chart components, a CSS Modules migration, theme foundations, and the Storybook and packaging setup used to maintain the library.
I built the original component library while developing the web version of Paw. It became RapidAPI's shared UI Toolkit; by the time I left, 13 projects used it as a dependency. I created its Storybook and integration documentation, and worked with the design team on the shared components and themes.
For teams still using Vue, I proposed a React-in-Vue adapter so they could adopt the toolkit while migrating to React.
Read the case studyThe family-owned record at the centre of FamilyBoon, and what it needs to carry between generations.
Context engineering for family documents, durable artifacts, and work that continues across AI sessions.
My background is in complex frontend products. These days, my work extends into AI tools, persistent context, and the reliability of agent-driven workflows. I’m interested in how the interface and the systems behind it work together.
I also build my own products. FamilyBoon grew out of managing my family’s documents and ongoing matters. My goal is to make software that takes more of that work off people’s hands, giving them time and attention back.