Touch. Speak. Ambient.
Today the operator and the client share an interface they click through. Tomorrow they speak to an agent they trust; the agent renders the surface only when they need to see it. Eventually the engagement lives on-chain and follows the operator to whatever device they pick up.
You touch.
Portal, dossier, tracker, change requests, Concierge text. You log in, click, fill, save. Predictable, observable — every step a row you can read.
You speak.
Voice-first. You trust the agent to act; it builds the surface only when you need to see it — a route map, an invoice, what changed. The interface becomes on-demand, not omnipresent.
It lives with you.
Engagements live on-chain — portable, verifiable, yours. The agent runs on whatever device you pick up. The studio follows you, not the other way around.
Why friction is the through-line
Every stage on this roadmap is the same studio doing the same thing — diagnosing first, building from a structured intake, holding the state. What changes between stages is how much of the system the operator has to touch to get value out of it.
Stage 01 — Today
The portal is live. The Concierge answers questions about the engagement using real data. Milestones, change requests, and the dossier are auditable rows the operator and the client both see. This is the baseline. See it on the home page →
Stage 02 — Next
Voice-first interaction layered on top of the same engagement schema. The agent picks up a phone call, a voice memo, or a passing question, decides what action to take, and surfaces a UI only when the operator needs to confirm or read something concrete. The interface stops being a place you go and starts being something the agent brings to you when needed.
Stage 03 — Ahead
Engagements live on-chain — meaning the operator's contract, milestones, change-request history, and deliverable manifest are portable, verifiable artifacts they own, not records trapped in our database. The agent runs on whatever device the operator picks up: phone, wearable, in-car display, kitchen counter. The studio follows the operator, not the other way around.
What we will not do
We will not build stage 02 or stage 03 ahead of customer demand. Both are real on the roadmap because both are technically tractable today; neither ships until a paying operator asks for them. The discipline that got us here ships there.