Figuring out what a team workspace looks like when half the team isn’t human.
I joined when Helio was still in closed beta. Every interface a Helio user saw in the next four months, I designed and I built.
Founding Design EngineerSan FranciscoMay to Sep 2026
Running on demo data.
Roughly in order of how much of it is mine.
Across Helio's repeated changes of product direction, I kept exploring, through user interviews, functional prototypes and frontend implementation, how users understand multiple AI teammates, hand work over, and find their way back to work in progress.
0.6 turned a team of AI teammates into one personal AI. Connect your accounts and the first run scans them, writes you a brief with citations, and hands over tasks that say what they came from. You fill in nothing.
Credits were described as an allowance that drains. They are a balance you own, and every money surface had to be re-derived from that.
127 providers, one card system. An admin sets the workspace up once, then every teammate connects on its own grants, and each state has to say who the AI acts as and what to do when the org says no.
Eighteen automations nobody could find, no schedule printed anywhere, and a detail panel with no way out to a page. The shelf, the cadence, the page and the trigger model all got rebuilt.

Built the whole thing in Expo and ran it on a real device, then made the case for the responsive web app instead: one thing to maintain, drawer nav, touch chat, a phone type scale.