The first piece made the operational case for structure inside a flat organization. The second piece argued that structure only works when leadership has the trust to let go. The third piece showed the ROI — that healthy culture, built on clear structure and real trust, outperforms the S&P 500 by roughly 2,000% in cumulative returns over time.

This last piece is about the question every leader I work with eventually asks: where does AI fit into all of this?

The short answer is that AI belongs in service of culture, not in place of it. It’s a supporting role, not a replacement. And the reason most companies get the AI rollout wrong has very little to do with the technology — and almost everything to do with how leadership communicates it.

Culture Is a Financial Moat: The ROI of Healthy Work Culture

This is the third piece in a series. The first made the operational case for structure inside a flat organization — that good fences make good neighbors and that explicit scaffolding is what enables culture, not what undermines it. The second made the leadership case — that structure only works when leaders, especially founders, are willing to make the leap of faith that lets trust become a system of evidence rather than an act of faith.

This third piece is the one founders ask for first and then quietly never come back to: the business case. The ROI. The numbers that prove healthy culture isn't a soft investment — it's one of the most durable financial assets a company can build.

Healthy culture is a moat. Most companies don't see it that way until they look at the numbers.

In the last piece, I made the operational case for structure inside a flat organization. Clear roles. Mapped decision rights. Visible operating cadences. The argument was that good fences make good neighbors — that structure isn't the enemy of culture, it's the precondition for it.

But there's a part of that argument I deliberately left for a second piece, because it doesn't fit cleanly inside an operational frame.

Structure only works if leadership actually trusts the people inside it.

Without trust, even the cleanest org design becomes a more elegant form of micromanagement. You can map every role, document every decision right, run flawless operating cadences — and still squeeze the life out of the team if the founder or CEO can't bring themselves to let go.

For founders especially, that letting-go is the hardest part of the job. It's also the most strategic one.

There's a misconception that's been quietly costing growing companies for years. It usually surfaces around the time a startup hits 30–50 people. Leadership has worked hard to build a flat, collaborative culture, and they get nervous about anything that smells like “process” or “structure.” They worry that defining roles, building operating cadences, or writing things down will somehow undermine the culture they've built.

So they hold off. They keep doing what worked at 10 people. And then engagement starts slipping, execution gets sloppier, and the team that used to feel agile starts feeling chaotic. Leadership diagnoses it as culture drift and tries to solve it with more all-hands meetings, more values posters, or louder “we're a flat org” messaging.

The actual problem is upstream. The team doesn't need more flatness. They need clarity.

There’s a moment every growing company hits. Revenue is climbing, the team is expanding, and the CEO is busier than ever — yet somehow everything feels harder. Decisions stall. Hiring is reactive. Compliance is a someday problem. The founder is in every meeting because nothing moves without them.

Kindness isn't soft. It's a system. And the leaders who build the system show up on the P&L in ways nobody is tracking carefully enough.

The most common mistake I see people make with AI is starting with the tool.

They sign up for ChatGPT or Claude or Copilot, stare at the blinking cursor, and try to think of something to do. A few half-useful prompts later, they decide AI is overhyped and go back to their day.

That's a tooling mindset. And it's the wrong way in.

If you actually want AI to make a dent in your work, you have to start with your role, not with the model. Here's the framework I use, and how it plays out for some of the most common operational roles I work with.

Operations is the goalkeeper position — nobody notices the saves until one gets missed. How AI sharpened my goalkeeper instincts, and why sharing those wins with your team is the real MVP move.

A few different countries have started saying the quiet part out loud: AI is going to replace large portions of the workforce, and they're not going to pretend otherwise.

The rest of the business world is paying attention. Boardrooms are running the numbers. Consultants are pitching "AI workforce optimization" decks that are really just headcount-reduction plans with a new label. And the conversation has clearly moved from "if" to "when."

There's an assumption baked into a lot of early-stage thinking right now: that the operations function — the people who keep the company running — is the next obvious target for AI replacement. Founders are looking at their org chart, seeing the cost of an experienced operator, and quietly wondering if they can skip the hire and let AI cover it.

I understand the temptation. The tooling is impressive. The economics look good on paper. And there's no shortage of voices on LinkedIn telling founders that "ops is the first to go."

It isn't. And the companies finding that out the hard way are already starting to reverse course.

This is the piece I want every founder scaling past early stage to read before they make a workforce decision they'll spend a year unwinding.

The companies that cut hardest in the name of AI are quietly rehiring. Here's what the data says — and how operations leaders can make the case for building over cutting.

There's a version of the AI conversation I'm tired of.

The one where AI is either coming for everyone's job, or it's a magic button that does the work for you. Both takes miss what's actually happening — at least in mine.

AI isn't doing my job. It's making me more efficient at the parts of my job that were never the point in the first place. And the time it's giving back is showing me something uncomfortable: I had quietly turned strategic thinking into repetitive duty. AI is the thing that pulled me out of it.