The Studio Cockpit — the app that runs this studio

Why build it at all

I sell a specific claim: AI should be invisible — built into how you already work, not bolted on as a chatbot. That's an easy thing to say and a hard thing to prove, and I'd rather demonstrate than argue.

So the studio runs on software I built for it. Not a demo, not a prototype kept alive for screenshots — the actual thing I open every morning to see what the business needs from me today.

What it does

Flow is dictation. Hold a key, talk, release, and the words appear at the cursor in whatever app I'm in, cleaned up — filler words gone, punctuation right, my proper nouns spelled the way I spell them. It runs on models on the machine, so it's under two seconds and nothing is sent anywhere. There's a well-known tool that does this for about twelve dollars a month. This took a day.

The Factory is the part I find most interesting to explain. Client sites get built from inside the app — templates, tasks, deploys, all of it. The production line and the sales demo are the same object, which means every improvement to how I work is also a thing I can show.

The Bus is the honest centerpiece. The app and my AI coding sessions have a shared mailbox. When something in the interface feels wrong, I pin a note on it. That note reaches a session, which fixes it, which reports back — often overnight. In the morning I look at what changed and click approve, or I don't.

The business view is unglamorous and does the most work: pipeline, billing, finance, and the current week in one screen.

The design decision that matters

Every one of those loops could have been fully automatic. None of them are.

The Bus can fix a problem, deploy nothing, and wait. The Factory can prepare a site and stop. Flow puts words on screen and never sends them. The pattern is the same everywhere: the machine does the work, the human keeps the throttle. One approval click, always mine, always required.

That isn't caution for its own sake. It's the thing that makes this shippable into someone else's business. An owner will happily let software do the typing, the drafting, the chasing, and the reconciling. What they won't do — correctly — is let it act in their name without looking first. Build the approval step in from the beginning and the trust question stops being a question.

What it proves

Three things, and they're the same three I'd want proved to me:

It's real. This isn't a pitch deck; it's the software the studio runs on, and it has the rough edges of something used daily rather than something staged.

It's fast to build. A native Mac app with local speech, a build system, and a two-way link to AI sessions, solo, in days. That speed is the reason a custom-built tool now competes with renting a generic one — the maths changed.

It's the same work I'd do for you. Small jobs, done quietly, inside the workflow that already exists, with a human holding the approve button. The only difference is whose business it's shaped around.