• Your AI Crew
  • Posts
  • I went quiet for a reason. Here's what I learned.`

I went quiet for a reason. Here's what I learned.`

Two confidential projects, a real lesson in what "operating" actually means, and a newsletter that's about to become useful.

Last time this hit your inbox, it was called Your Chief A.I. Officer — a roundup of AI news. Then it went quiet. Not because it failed. Because I got pulled onto the real thing, and the real thing doesn't leave much room for writing about the news.

Here's where I've actually been.

Where I've been

Two confidential projects, both still running, both deep in the world of film and AI. I can't get into specifics — not the names, not the details. What I can tell you is what it's been like to actually do this work instead of just writing about it.

For the last stretch, my job hasn't been "keep up with AI." It's been: take traditional film and TV crews — people who've made things their whole careers, the same way I have — and get them running real production work through AI workflows, at the scale a real studio actually needs. Not a demo. Not a slide. The actual pipeline.

What I learned

A few things I didn't expect, in order of how much they changed how I think:

Cutting production costs by as much as 90% was never about a smarter tool. It was about directing. The tools were mostly the same tools everyone already has access to. The difference was someone giving them a standard, a brief, and a correction — the exact thing a director does with a crew of people. Nobody sells you that part. It's not a feature. It's a skill.

The hard part was never the technology. It was the translation. Getting an editor who's cut film for twenty years to trust a new step in their process isn't a tooling problem — it's a leadership problem. The teams that adopted fastest weren't the most technical ones. They were the ones led by someone who'd already earned their trust on a hundred other things first.

Where we go from here

I'm not writing AI news roundups again. There's enough of that, and none of it's what got me pulled onto a real feature and a real studio.

This is Your AI Crew now — a letter from someone actually running a company, and now a production pipeline, on a crew of AI agents, showing you the exact moves. Plain English. Do-it-today. No theory. Every Tuesday, one directed move that hands you an hour back. Every Thursday, a story from twenty years on film sets, or a look inside the crew I run things with.

You already know how to lead talented people — that's the entire prerequisite. AI is just a new crew. I'll show you how to direct it, starting now.

Your first move (so this isn't just an announcement)

One real example of what "directing" looks like. Take any pile of messy notes — a call you scribbled through, a few voice-memo dumps, half-formed ideas — paste them into Claude or ChatGPT, and give it this:

Turn these notes into a clean, client-ready brief.
Keep my voice — short, direct, no hype.
Structure it: the goal, the plan, what I need from them.
Then flag anything that's missing or unclear before I send it.

"Keep my voice" stops it sounding like a robot wrote it. "Flag what's missing" turns it from a typist into a teammate — it hands you back your own blind spots, circled. You didn't clean up notes. You directed a first pass and kept the judgment. That's the whole thing, in one rep.

Want the next rung? I will be launching “two” free courses soon — Operate It (direct your first AI teammate) and Build Your Crew (build a permanent one on your own machine). They pick up exactly where this leaves off. → I will drop a link in a future edition when the are up.

Hit reply and tell me: what have you been quietly building or working through this past year — the thing you haven't posted about? I read every one, and it tells me exactly what to send next.

You're getting this because you signed up at seatd.io. Forward it to one person who'd use it — that's how this grows.