🎛 Operate

The fleet's real numbers, live: signups, end-use rate, revenue, ad and AI spend, email health, per-app performance. Below them, one task ledger — yours and the machine's in a single list, where an AI classifier decides per task whether it can be delegated and grows the button to do it. Daily analysis digs file their own findings as tasks; stale machine nags self-archive; your items are never touched.

Above the day-to-day, initiative boards hold the big structural moves — each with its own subtask mini-board, drag-to-reorder, and subtasks that mirror into the task ledger so checking off in either place checks both.

Every count is a beacon-verified event from a real session or a real account — landing views that actually rendered, signups that actually exist, purchases that actually charged. The journey funnel runs landing → signup → mid-use → completion → offer → purchase per app and across the fleet, with comparison mode for period-over-period deltas.

Click any stage and see the humans: the users in it, their session replays bounded to the window you're looking at, their emails one click from a full dossier. Analytics that ends in a person, not a chart.

Products, prices, and copy are managed centrally per app — Stripe processes the payment, but the catalog is yours, so a price change is one edit, not a deploy. Everything seeds as a draft; nothing is buyable until flipped live.

A purchase grants an entitlement the app reads at its premium gates — comp one to a tester in two clicks — and fires the full chain: funnel Purchase event, revenue in analytics, and a server-side Purchase to the ad platform carrying the real order value.

A master agent sits over the whole operation — ask it why signups dipped and it reads the spend, the funnels, and the logs before answering, then files the fix as a task. Daily digs analyze the fleet on schedule and surface what a growth team would have found in standup.

Around it: scheduled automations (CRO report → improvement build, on cadence), custom domains provisioned from settings, team roles down to a designers-only portal, and a code mirror that lets outside collaborators push app code through guarded, versioned, staging-aware rails.