About

The work should run. You should steer.

As a kid I wanted to be an architect. I thought that meant buildings. Turns out it means systems. I came up through design first — Photoshop, Final Cut, the whole creative stack, mostly self-taught — freelancing print and digital work before I ever called myself an operator. The craft never left; I just pointed it at how work flows instead of how it looks.

Building with Legos taught me the rest early: the best structures are modular. Composable. You don’t design monoliths — you design pieces that lock together cleanly, so the whole thing can be rebuilt or extended without tearing it down.

Airtable gave me the language for it — they called themselves the Lego kit for work. I spent three years there, ten straight quarters above quota, but what stuck wasn’t the number. It was sitting in on hundreds of customer calls and learning to hear exactly how a workflow breaks, and why the people inside it think it breaks. That ear is the muscle everything since has been built on.

Somewhere in there I stopped selling and became an architect — running enablement, then a sales-velocity initiative across a 26-person team in thirty cities — and I’ve since pointed the same instinct across media and advertising, SaaS and databases, and now finance and web3. Closer to ten years in the work than the six a tech resume shows. The job never changes: find where it breaks, name the constraint, build the piece that fixes it for good.

The connective tissue between “we need to move” and “here’s the machine that makes it repeatable.”

Novakirk is those pieces, applied to AI. Systems that run your operations the way you would: bounded, auditable, with a human at every gate that matters. The AI handles the labor. The operator keeps the judgment. That isn’t a constraint — it’s the architecture.

And if the system looks good while it runs — that’s by design.