I’ve spent 15+ years building things inside other people’s companies. This week I started building one of my own.

It’s called Aqen.ai. You bring the idea. Aqen brings everything else — legal, finance, marketing, ops, all of it coordinated across every business function. Like having a cofounder who’s built it all before.

I’m also setting up a holding company called Grazier Ventures — the structure that catches whatever I build. Aqen is the first thing in it! There will be more, because Aqen is also the tool I’ll use to build them.

(I’m continuing to advise founders, investors, and CTOs through TideHelm — the work I’ve been doing there since 2022.)

Now the thing I actually want to write about.

The pattern I couldn’t stop seeing

Every time I’ve been part of scaling a company — Weedmaps from 30 to 300+ engineers through IPO, ShopKeep through a $550M acquisition, BuildOps to unicorn — the hardest part was never just the product.

It was everything else around the product, too.

Formation. Finance. Hiring. Brand. GTM. Compliance. Vendor selection. The thousand decisions that don’t show up in your product roadmap but eat your calendar alive. What I’ve called the cognitive overhead tax — the mental background processes that leak founder attention in every direction at once.

For most of tech history, we accepted this tax as the price of building a company. You raised money partly to hire the people who could carry it for you — a COO, a CFO, a head of marketing, lawyers, agencies. The business wasn’t just the product. The business was also a company that had to get built alongside the product. That company required a team.

I’m not sure that’s true anymore.

What changed

The AI era isn’t about AI getting better at answering questions. It’s about AI getting good enough to coordinate. To decompose a goal into steps, sequence them by dependency, execute across every business function, and validate outcomes. To hold context across weeks of work without dropping it.

That’s not ‘an AI assistant.’ That’s a cofounder-shaped thing.

I’ve been writing about this for a while from the inside of someone else’s company. Polymorphic cultures where humans and AI agents collaborate. Minutes Added to Workforce as the honest framing for AI’s real value — capacity expansion, not cost reduction. Tokenmaxxing as the wrong way to measure it.

At some point the observation curdled into an obligation. If I actually believe what I’ve been writing, the honest move is to go build the thing.

Enjoying this? I write about AI implementation and engineering leadership every week.

The bet

Aqen.ai is a system for turning business intent into coordinated execution. You say what you want to build. Aqen figures out what needs to happen across legal, finance, marketing, ops, product, brand — and coordinates all of it.

Not advice. Not a chat window. Coordinated execution against your actual goals, with a shared memory that every teammate — human or AI — reads from and writes to.

Like having a cofounder who’s built it all before.

If it works, it changes who gets to start a company. It collapses the years of accumulated ‘how the world works’ that currently separate a technical builder with an idea from a functioning business. It makes the non-product surface area of starting a company small enough that one person with an idea can actually carry it.

That’s a bet worth making. So I’m making it.

Why also a holding company

If Aqen works, it changes who gets to start a company. But it also changes who gets to start many companies — across categories that have nothing to do with AI as a product.

Grazier Ventures is the structure I’m building around that second idea. Not every venture in it will be an AI company. The thesis isn’t ‘AI is the product.’ The thesis is ‘AI is the leverage that makes the product buildable by a small team.’

Some of what I build through Grazier Ventures will be infrastructure — like Aqen. Some of it will be consumer. Some of it might not look like a tech company at all. The throughline is that every one of them gets built using AI as the force multiplier, and most of them get built using Aqen specifically.

Aqen goes first. It has to. It’s the proof, and it’s the tool.

But it’s not the end of the list. It’s the beginning of one.

What this changes for this blog

Nothing, and everything.

I’m still writing every week. Still about AI implementation, engineering leadership, and what it actually takes to build at scale. Still cross-linking the ideas so they compound over time.

What changes is the vantage point. For the last decade I wrote as an operator — someone inside a company explaining what was working from the inside. For the next chapter I’m writing as a builder, in public, figuring it out in real time.

If you’ve been reading for a while, thank you. The last year of posts laid the groundwork for this one without naming it. Now you know what I was building toward.

If you’re new here, the Start Here page is the fastest path in.

If you’re building something too — or thinking about it — I’d love to hear from you. LinkedIn is the fastest way to reach me.

Let’s build!