I've sat inside 60+ agencies at this point.

And pretty much every one of them has a Google Drive folder called "SOPs" or "Processes" or "Playbooks" that nobody has opened in several weeks or months.

They spend months documenting everything. Loom videos. Notion pages. Process maps that look beautiful in a screenshot and useless in practice.

But why then the founder is still the one who knows how things actually work or still the person the team defaults to when something breaks…?

Here's what I've been thinking about a lot recently.

There are two ways an agency can be structured. We show both to every client we work with.

The founder sits at the base, holding all the weight. Operations stacked on top. Delivery above that. People at the very top. It looks like a pyramid and the founder is the load-bearing wall. Pull them out and the whole stack collapses.

That is the business of almost every agency founder we talk to between $500K and $3M.

The founder moves to the top, they’re the architect and owner, not load-bearer.

Between them and the day-to-day sits a layer that doesn't exist in most agencies at this stage: data, AI, and systems. That layer connects to people, delivery, and operations below it. Everything talks to everything else. The founder sets direction. The machine handles execution.

That middle layer - data, AI, and systems is where your documentation lives. But it's alive. It's queryable. It updates. It thinks with you.

A data layer is your delivery model, your client data, your process documentation, your decision frameworks... all connected, all searchable, all feeding into how work actually gets done.

It updates when your processes change. It answers questions with context from your actual clients. And it doesn't rot in a Google Drive folder after three weeks.

We've been installing this for our clients using tools like OpenClaw and Obsidian built on top of existing project management systems.

Your team doesn't need to remember where the SOP lives. They ask a question and the system answers it - with context from your actual clients, your actual processes, your actual pricing.

When a process changes (and they always do), you update it in one place and it propagates everywhere. The easiest part is that the bot will update the documentation, you just need to give a command to do so.

New hires don't need a two-week onboarding where someone walks them through 47 Loom videos. The knowledge system trains them as they work.

And the founder or seniors... they stops being the institutional memory of the business.

I had this conversation last week with an agency founder running $80K MRR, 65% margins, team of four. Beautiful numbers on paper. His words: "Delivery is not systemised enough. Not enough SOPs, not enough processes."

So his instinct was to document everything.

He's identified the gap. What he's about to fill it with will be ignored in a month.

What he actually needs is a proper infrastructure. A system where knowledge, processes, and client data all connect and talk to each other.

We, as founders, resist this because building infrastructure feels slow. Writing an SOP feels productive. You can knock one out in an afternoon and feel like you've made progress.

Building a system where your knowledge, processes, and client data all connect and talk to each other... that takes longer. But it's the thing that actually lets you step away.

That layer is data, AI, and systems.

___

P.S. If you're stuck in the Dependency Model and want to figure out what the Leverage Model looks like for your specific agency - you can:

1. Apply for a 1:1 Founder Dependency Audit - we diagnose it together.

2. Run the diagnostic yourself - ops, AI, dependency - here.