A small team building a desktop AI company.
We think the wedge in agentic AI is not capability — it is hiding the wiring and showing the work. This page explains the bets we are making and the principles we keep coming back to.
Why a desktop app?
Most AI products today are either single-agent chat (great UX, no real coordination) or developer agent frameworks (real coordination, no UX). We think there is a third shape: a desktop app where a non-technical user runs a hierarchy of AI employees the way they would manage a small team — by DMing people and letting managers route work.
Desktop is the right surface because the work is local: the App Builder writes files into a folder the user can see, the filesystem and shell are real, and nothing about a chat thread with an employee needs to be cloud-synced to be useful.
The validation question
“Did running an AI company feel like managing a small team without learning agent infrastructure?”
Not “is any one employee useful?” — that bar is met by every other chat app. The bar we care about is whether the coordination model feels natural to a non-technical user the tenth time they open the app.
Principles
