Why AI That Works Became The Operator’s Notebook

For about a year, this publication was called AI That Works.

The name made sense at the time. AI was exploding. Everyone was talking about prompts, agents, automation, and whatever model dropped that week. I was in the same boat, trying to figure out where this was going and how to actually use it for real work.

Then I read back through what I’d written.

And I noticed something.

I wasn’t really writing about AI.

Some articles were. Others were about software. Or marketing. Or building products. The topics jumped around, which is how my brain works anyway. But the thing underneath all of them was not the technology. It was one person trying to figure out how to build useful things on his own.

That’s the story. Not the tools. The operator.

I’ve spent more than 25 years in digital marketing. I led teams, ran large budgets, eventually became a VP. The standard career arc says you move further away from the actual work as you go. More meetings, less making.

I went the other way. I went back to building, back to writing code, back to learning things I probably should have learned twenty years ago.

That’s because I got hooked on a simple idea: one person can now build things that used to take a whole team. AI is part of that, but so is software, automation, distribution, and the plain fact of the internet. AI is just the newest tool on the bench.

Here’s what I’m not trying to do.

I’m not building a startup. I’m not raising money. I don’t want a hundred employees or a calendar full of meetings. What I want is smaller and, to me, more interesting: build profitable digital assets, make useful products, own my time, and prove that an independent operator can still build real businesses in 2026 without any of the usual machinery.

That’s what this publication is about now.

Some weeks I’ll write about AI. Some weeks software, or marketing, or business models, or something I learned the hard way after 25 years in the trenches. And some weeks I’ll just write about what it’s like to build in public while figuring it out as I go, including the parts that don’t work.

Because that’s what this is. A notebook. Field notes from someone doing the work, not commentary from someone watching it.

The Operator’s Notebook fits better because it names the person, not the technology. Tools change. Platforms change. Algorithms change every few months. The skill of building, shipping, learning, and adapting does not.

If you’re building something too, a business, a product, a publication, or just a way of working that’s more your own, I think you’ll find something useful here.

Welcome to The Operator’s Notebook.