Work · Tech
The Studio's Command Center
The studio's own command center — and it talks back.
20+
workstreams, one surface
1
question: can I take this on?
Daily
dogfooded by the studio
The problem
Running a studio, a day job, and a product pipeline means twenty projects competing for the same Tuesday.
Every task tool answers 'what's on the list.' None of them answer 'do I have room' — so the list grows until something breaks.
What we built
- A master task surface with per-workstream color pills, a stat strip (overdue / today / in progress / done), and timeline and workstream views.
- Infrastructure most dashboards don't have: an email worker that catches inbound invites, a fleet-tick cron shared with the calendar fleet, and test-gated deploys.
- 'The Ask' — the assistant reads the whole board and generates a capacity verdict and a status digest: what's on fire, what can slip, whether the new thing fits.
- Dogfooded daily; the studio's own operating truth.
Node.jsCloudflare email workerCron fleet-tickAI capacity verdictsTest-gated CI
In the product
Command
TasksTimelineThe Ask3Overdue · needs eyes
7Due today
12Done this week
FleetShip calendar update — one app at a timetoday
BrandCard files to the printertomorrow
ProductWarehouse import — Q3 refreshthis week
Near-black ground with terracotta, amber, olive, and plum workstream pills — moody, warm, unmistakably ours.
Command
MessagesAssistantNew client wants a dashboard by mid-month. Can I take it?
Tight but yes — if the fleet update ships this week as planned. Two workstreams have slack; travel on the 9th is your real constraint. Want the digest?
Send it. And hold Thursday morning.
The assistant reads the whole board before it answers — a capacity verdict, not a vibe.