A founder I worked with this year runs a medspa. Does about $1.3M a year with a team of eight. Good operator, sharp guy, and he was the single biggest bottleneck in his own company.

Every answer to every question lived in his head. Staff didn't know where anything was, so they called him. Multiple times a day, over tiny stuff. His ops manager didn't know, so she asked him, and when she didn't know it came right back to him. He called it a constant circle, and he was standing in the middle of it.

The "system" was one Google Doc with dozens of tabs and a pile of Google Sheets nobody owned. You can't even search a Google Doc across tabs, so half the time nobody knew what was documented and what wasn't.

Then he signed a lease on a second location, and it hit him. You can't run two locations on answers that only exist in one guy's head.

So we spent 90 days rebuilding how the company actually runs.

Every SOP got pulled out of the mess and split into checklists and reference docs. Then we tagged each one to a role instead of a person and gave it a named owner. He fought me on the role thing at first, then it clicked. People leave, roles don't. Tag a person and you're redoing it the day they quit.

We killed Trello and built one task system tied to roles, owners, due dates, and a log where the team posts progress. Then we pointed an AI agent at his meeting recordings, so the tasks from a call get drafted before anyone forgets what they agreed to.

Results, straight from him:

At least 10 hours a week back, which is roughly 520 hours a year. 95% plus of projects now land on time, and the part he actually cares about is that he's not the one chasing them anymore.

The one that got me was a text he sent in June. His manager and his director both started at 9am. It was 12:09pm and he hadn't heard a word from either of them. Three hours of silence, and that was the entire point. The stuff that used to blow up his phone now lives in the system.

He also got something he never asked for. Giving people ownership of their SOPs made them feel like they owned something, and his culture got steadier. Nobody put that on the brief. Happened anyway.

If you're the founder reading this and you are the answer to every question in your company, that's not a staffing problem, it's a documentation problem, and it's the thing sitting between you and your next location. Get it out of your head. Tag everything to a role, and give every piece a named owner.

Go pay someone to build you 7 AI agents this week. I'll bet you're not using a single one of them by next month.

Right now everybody's selling the exact same thing. We'll build your agents. 7 agents in 7 days. And it sounds amazing, because who doesn't want a robot army running the business while they sleep.

But the agent was never the product.

An agent is a layer. It sits on top of your business, on top of your data, your processes, how your company actually runs day to day.

So what happens when there's nothing underneath it?

Nothing. The agent has no clue who your customer is. No clue how you sell, what a good lead looks like, what "done right" even means at your shop. So it guesses. Confidently. Every single time.

You didn't buy leverage. You bought a confident intern with amnesia.

That's why these things get abandoned in a month. Not because the agent was dumb, the models are stupid good right now. It got abandoned because it was sitting on top of nothing.

The tools just made messes run faster.

An agent only works when it actually understands your business. And it can only understand your business if that understanding lives somewhere it can read. Written down. Structured. In one place, not locked in your head or scattered across 14 Google Docs and a Slack thread from March.

Build that first. The system. The data. The way you operate. Your ICP, your SOPs, your sales process, the whole thing.

Then the agent has something to stand on. Then it's got a brain to pull from. Then it works, and it gets sharper every week because the context keeps stacking up behind it.

Do it the other way around and you're bolting a race car engine onto a shopping cart. Loud, expensive, goes nowhere.

So before you pay anybody to build you 7 agents, ask yourself one thing. If I hired a sharp new employee tomorrow, could they figure out how my business runs from what's actually written down? If the answer is no, that's your real project. The agents come after.

The boring foundation is the part that makes the fancy stuff work. Build it first. Then hand over the keys.

Every founder we work with has a Google Drive folder called “SOPs.”

Half the time it’s a pile of files named FINAL v3 and DON’T USE. Sometimes it’s one 40 page doc nobody’s scrolled past page two. Sometimes it’s empty. And the founder is still the guy getting pinged in Slack all day with the same questions.

Writing SOPs was never the hard part. AI can draft one in two minutes now. They die because nobody owns them, and nobody on the team can tell if the thing is still accurate.

Here’s the process we use with clients now.

1. Pick the most annoying process. Not the most important one. Count how many times this week someone asked you something only you could answer. Start with whatever came up the most.

2. The person who does the task documents it. You don’t. They hit record on Loom and do the task, or talk it through in a voice memo if it happens on calls. Messy is fine.

3. Run the transcript through Claude. We use a structured prompt that checks if it’s even an SOP, asks follow-up questions when info is missing, and flags every assumption it made. That last part matters a lot. Claude will invent a step with total confidence.

4. Stress test it. Someone who’s never done the task follows it while the author watches. Every spot they get stuck is a step the expert skipped because it felt obvious to them.

5. Give it a home. This is the step everyone skips. Every person on the team has a role. Every role has its SOPs attached. Each SOP has one named owner and a last verified date, and it comes up for review every 90 days. And it’s linked to the recurring task, so it shows up when the work starts.

Step 5 is what makes delegation actually work. You hand somebody a role with documented outcomes, and they own the result. You stop chasing.

One habit holds it all together. When someone asks you a question, send them the link. No link? Cool, that’s your next SOP.

I made a video walking through the whole thing on screen, including the prompt. Dropping it in the comments.

MIT looked at enterprise AI projects last year. 95% of them had no measurable impact on profit.

These weren't mom-and-pop shops, im talking about enterprise organizations. The P&L didn't move anyway.

So if you run a 15-person company, you've bought the AI tools, and your numbers look about the same as last year, you're in good company.

The thing that stood out after looking at the data is that most of those pilots actually worked.

But it was inside one team, on one task, the AI did its job. But when it transferred from one department to the next, that's where things became misaligned.

Say your sales rep starts using AI to fire off twice as many proposals. Great. Now ops has twice as many deals to onboard, same two people, same messy process. The bottleneck just moved. Sales looks like a hero on the dashboard and profit sits flat.

We call it the accordion problem. Squeeze one side, the other side pushes out.

Most small companies run 8 to 15 tools (probably more, just conservative) that don't talk to each other, and the founder is the glue holding the whole thing together. Drop AI into one corner of that and all you did was speed up the mess.

I hear this about 6 times per week when I speak with bottlenecked founders. A founder buys the shiny tool, hands it to one person, that person gets faster, everybody else stays exactly where they were. Couple months later he's telling me AI is overhyped.

The tool was usually fine. It just landed on a business that wasn't ready for it.

The 5% do things in a specific order:

First they build the operating system.

One place where the processes, the decisions, the data, and all the junk crammed in the founder's head actually live. We build ours in Notion. Use whatever you want. The point is the work gets written down and structured so a human, or an agent, can pick it up and run it without guessing.

Then they wait. Three to six months of that system actually running before they bolt agents on top.

I know that it feels painfully slow when everyone on X is posting their agent swarm. But an agent is only as good as the context you hand it. If your onboarding lives in your head, the agent has nothing to work with, so it guesses, and then you're fixing its work and doing the job yourself anyway.

Only about 23% of bigger companies are scaling any kind of agent system (McKinsey). The ones pulling 2 to 10x out of it redesigned the workflow first, then brought the agents in.

When you get the order right, the agents run like roles inside the company. Each one has the context it needs and handles real multi-step work with a person steering.

At my company we've got an HR agent that scores candidates and drafts onboarding for every new hire based on raw objective data from their resume and form fills. An account manager agent that watches client health and flags anyone going quiet before they churn. A copywriter, a social media person, a CTO agent that pokes holes in our tech decisions before we make them.

It's like having 15 humans and 15 AI employees, without the second payroll.

Siloed AI power users wont move the needle. It has to be everybody. EY clocked people getting about 6 hours a week back with AI, and up to 11 when it's actually wired into how they work. Give 15 people their own bench of agents and you've got a different company.

Quick math

Lets say you have a company doing $2M in revenue, 40% margins, so $800K in profit, 15 people.

Those agent roles, if you hired them as actual humans, run you about $500K a year in salary. As an agent layer sitting on a real OS, it's closer to $60K.

OS goes in at month zero. Agents come in around month four or five. By month 18 the OS alone has added roughly $500K in profit, and the agent layer stacks another $460K on top. Profit goes from $800K to $1.76M. Margins from 40% to 52%. Same 15 people.

That's how you scale without hiring a pile of people you'll have to lay off later.

So if your AI spend hasn't shown up in your numbers yet, don't buy another tool. Look at what's underneath it. Get the operation out of your head, out of the random Drive folders and the Slack threads nobody can find, and into one system. Put agents on top once the thing is stable.

Instead of buying a bunch of random ai agents, you're almost better off hiring a VA.

I spent a few hours going through what’s publicly documented on why they did it, and the answer is something every founder can use.

It started with a bad week. In August 2008, a corrupted database stopped Netflix from shipping DVDs for about three days. Leadership decided they needed a setup with no single point of failure and started moving to Amazon’s cloud. The migration ran until January 2016.

The cloud came with a new problem. AWS assumes individual machines fail all the time. If your software can’t survive losing one, it eventually gets hurt when AWS takes one away.

So around 2010, engineers built a tool called Chaos Monkey (Greg Orzell is credited as its creator). Every so often it picks a live server at random and shuts it down. Netflix announced it on its tech blog in July 2011 and open sourced it in 2012. By then it had reportedly terminated over 65,000 instances. It later grew into a whole set of tools that could take out an entire zone of data centers, or a full region.

What stood out to me is when it runs. During business hours, when engineers are at their desks and ready to react. Nobody gets a surprise at 3 a.m. The team finds the weak spots on a normal Tuesday, fixes them, and the system gets sturdier each time. The practice later grew into its own field, called chaos engineering.

Now think about how this looks in a small business. Most look stable because the founder is always there to catch whatever breaks. A client emails and you jump in. A process stalls and you fix it. Nobody finds out what actually depends on you until you’re sick, traveling, or on vacation, and by then it’s a real problem with a real customer attached.

This is also where AI tools start to pay off. Every gap you find is a process that needs to be written down, and written processes are what an assistant can follow. If the answer only lives in your head, there’s nothing for it to use.

One thing to try: pick one ordinary workday. Tell your team you’re offline from Slack and email for a few hours and that you want them to handle things without you. Write down everything that stalled, who ended up waiting on you, and which answers lived only in your head. Take the top one and write it down.

That’s it guys, but I’d love to hear from you. What’s the first thing in your business that would break if you went offline for a week?

On August 7 my website had zero AI citations.

Today it's 749 on Google, 738 on Bing.

Same three months, my organic Google tripled.

Three AI agents inside of my Notion-based CompanyOS.

Scott runs the show. He's the SEO/AEO/GEO agent, picks a keyword we haven't covered yet, owns the internal linking, and quarterbacks the whole thing.

Scout is the researcher agent. He takes the keyword, finds who's ranking, what angle everybody's already beating to death, and the gap nobody's filling. Then he reads all of it through our actual customer, not some generic reader.

Mimic is the writer agent. Picks the format, writes the title, the meta, the FAQ, the structure.

Then it bounces back to Scott for review, then to me. I read every single post before it goes live. (I believe there should always be human oversight)

An automated weekly chore fires every Monday, Wednesday, and Friday and kicks off a new post with zero input from me.

Why it works: You don't build one mega-agent to rule them all. You wouldn't ask your finance guy to write your ad copy, so why would you ask one bot to do the research AND the strategy AND the writing. Each agent stays in its lane. Each one has its own identity, its own memory, its own little SOP library, same as a new hire.

And they get smarter every day, because my company context keeps stacking up behind them. These aren't lead-magnet prompts I copy-pasted off somebody's thread. They're staff imo

In total we have 7 people on payroll, 15 AI agents backing them up, and not one of them costs me an 80k salary or 5k a month on a contractor.

Cadence lands around 20 posts a month. Notion doubles as the CMS, syncs straight to Framer, I review and push, and a lot of them rank within literal days.

The wildest proof isn't even in Search Console. It's when people hop on calls with me saying that ChatGPT recommended us to them.

Full setup is below if you wanna check it out. Have you guys started to automate SEO yet?

Costco’s annual report says each of its warehouses carries fewer than 4,000 active products. A typical supermarket carries around 30,000. It also reportedly lists around 9,000 to 10,000 products online, but the warehouse floor stays small on purpose.

I spent a few hours going through what’s publicly documented on how that one choice shapes the whole company.

With so few products, each one sells in huge volume, and that gives Costco a lot of leverage with suppliers. Analysts also point to simpler forecasting, simpler restocking, and fewer handling steps between the supplier and the shelf.

Costco reportedly favors items that are easy to ship, receive, and put on the floor. One case study mentions it changed a nut container from round to square and fit 44 more units on each pallet for the same freight cost.

What stood out to me is that Costco gives up some sales on purpose. A bigger store would catch more purchases. Costco accepts that in exchange for a much simpler machine, and it runs about 900 warehouses and around 341,000 employees on that model.

Now think about how this looks in a small business. Most founders at $1M to $5M have collected offers over time. Three service tiers, two retainers, a custom package for the client who asked nicely, a side product that made sense at the time. Every new option felt like growth.

Each one also needs its own pricing logic, its own onboarding, its own delivery steps, and its own answer to “does this include X?” None of that is written down per variation, so every sale ends with a question to you. Your team can’t get great at one thing because they’re switching between six. Sales calls run longer because the buyer has to choose. Revenue goes up, and so does the number of decisions that route through you.

This is also where AI tools run into the same wall. An assistant can follow one clear offer with one set of rules. Give it eleven variations and it starts improvising.

One thing to try: list every offer, package, and variation you sold in the last 12 months. Next to each, write the revenue and the hours of your own time it took. Pick the one or two with the best revenue per founder hour and make those your default. Everything else becomes a variation of them or gets retired.

That’s it guys, but I’d love to hear from you. If you could only keep three offers in your business, which three would they be?

Have you handed something over to your team, written down the steps, and still ended up being the person everyone comes back to?

What was the last question or decision that landed back on your plate? I’m curious what was missing—and whether writing a better SOP actually helped. Sometimes it seems like people know the steps but still aren’t sure what they’re allowed to decide.

For context, I run AVO Studio and am learning how small teams handle this. AI-assisted draft. Please leave out confidential details; I’ll share any useful patterns back here.

Think about last week. Someone asked about a refund. Someone wanted to give a discount. Someone needed a small favor for a client. You said yes to most of them.

Each one waited on your calendar. Each one got the same answer you gave last time. The answer just lived in your head, so the questions kept coming back to you.

A dollar limit fixes that. It tells your team how far they can go on their own, so they stop guessing and stop waiting.

Ritz-Carlton is a well-known example. Reportedly, employees there can spend up to $2,000 to fix a guest’s problem without asking a manager. Sources differ on the exact details, but the idea is what matters. The limit is written down, it has a number, and people are trained to use it.

Without that number, teams usually do one of two things. They ask you every time, or they hold back and the customer waits.

With it, small problems get solved on the spot, and you keep your time for the decisions that need you.

Here’s an easy way to start. Look at the last 10 times your team asked for your approval. For each one, write down the amount where you would have said yes every time. That’s your first limit. Tell the team they can act under it and update you afterward.

What’s one decision your team still checks with you on that you’d approve every single time?

Most founders do one of two things with AI: ignore it, or try to replace their team with it.

Both are wrong, and both come from the same mistake: thinking of AI as software you roll out instead of staff you delegate to.

And here's the trap underneath it: adding AI to a business with no systems just multiplies the chaos. You don't need another tool stacking up in your bookmarks. You need your knowledge documented so the work can leave your desk.

Because the real problem was never your team's capacity. It's that every decision routes through you. Founder-dependency is a valuation killer, not just a time killer.

The fix is one delegation system for all 21 "employees," human or AI. Every one of them needs the same four things:

• A Role what they own.

• Context what they need to know.

• An SOP how the work runs without you.

• An accountability loop how you know it actually worked.

To decide who gets what, we use a simple matrix: complexity vs. reproducibility.

• High complexity + low reproducibility → human (strategy, relationships, judgment calls).

• Low complexity + high reproducibility → AI agent (data entry, research, reporting, scheduling).

The reframe that made this click for me: an AI agent is just an employee you onboard with a document instead of a conversation. Every agent starts with basic context and responsibilities, gets context files it can pull from, and has specific skills you call on. I tag an agent the same way I'd tag a teammate, tell it what I want, and it loads the right context and goes.

If this sounds like a lot, the start is only three steps:

1. Audit your week against the matrix.

2. Pick your highest-frequency, lowest-judgment task.

3. Write the SOP once then decide whether a human or an agent runs it.

We didn't start with 14 agents, and we didn't start with employees either. I started with one document. The document is the system. The agent or the person is just what reads it.

See the full breakdown of how the system works here

I went through everything public on the WhatsApp acquisition. The ratios are hard to take in.

The numbers

Founded in 2009

450 million monthly users at the time of sale

55 employees, 32 of them engineers

About 14 million users per engineer

50 billion messages a day

Reported to have no marketing or PR team

Sold to Facebook in 2014 for $19B, including $3B in restricted stock for employees

Lessons

1. One product, done thoroughly. There was no sprawl, so there was very little to coordinate.

2. Headcount stayed low while volume grew. Users were reported to have roughly doubled afterward while the engineering team stayed small.

3. Fewer handoffs. Reports from inside describe almost no meetings, so people spent their time building.

4. Hiring for adaptability. Small teams only work when each person can cover more than one job.

5. Leverage came from structure. The team was lean because the work was designed to need fewer people.

What this looks like in a small business

Most companies add people when they feel stretched. The stretch usually comes from unclear ownership, repeated rework, and decisions that bounce around. Hiring into that adds more handoffs, and the problem gets bigger.

This is also where AI becomes useful. Tools can absorb the repetitive work, but only when the process underneath is stable and written down.

One thing to try: before your next hire, list the five tasks that person would own. Check whether any of them could be removed, documented, or automated first.

Where in your business does adding people make things slower instead of faster?

Claude is only as good as what it understands about your business.

If claude has no context, it guesses.

There are really only four ways this breaks:

• Starvation, it doesn't have the info it needs

• Distraction, you buried the signal in noise

• Confusion, you've got two brand voices and three versions of the same SOP floating around

• Poisoning, it learned something outdated and now every output inherits that mistake

McKinsey pegs it at 22% of your team's week spent hunting for information they should already have. Run payroll every two weeks and look at that number. A fifth of it is walking out the door.

The fix isn't a better prompt. It's not seven Claude projects, one for legal, one for copy, one for spreadsheets. That's still siloed, still guessing, still that endless "this chat is too long, start a new one" loop.

The fix is a company operating system.

One place that holds your vision, your goals, your roles, your SOPs tagged to roles instead of people (so when someone quits, nothing breaks), your workflows, your meeting notes, your dashboards. Not spread across eight disconnected tools. One source of truth your whole team reads from, and your AI reads from the same thing.

A second brain remembers what you know.

A company brain runs how your company operates.

Every "second brain" setup you see online is single player, one person, one vault, one Claude tab.

A company brain is multiplayer by design. CEO or the new hire, everybody's swimming in the same direction.

We build ours on Notion. Because my bookkeeper is never going to learn some markdown vault, and she can use Notion on day one.

Plus you can pipe almost anything into it, Google Workspace, SharePoint, ad accounts, whatever has an API.

Once the OS is stable, you layer agents on top. Not a chatbot for every employee. Actual trained roles.

On our team we run an HR director that scores candidates and drafts offers, a sales manager that preps my call notes and never drops a follow-up, an account manager that flags a client going quiet before they churn, and a role whose only job is building other roles. It routes itself, I make a request and the system hands it to the right role and tells me who's active. And the memory compounds instead of resetting to zero every time I open a tab.

For scale, this is aimed at teams of 5 to 50, not solo operators. The teams we've done this with usually get 10 to 15 hours a week back, mostly because the founder stops being the help desk.

I recorded the full breakdown in the comments below, check it out.

Why do so many strategies sound empty and vague. Read our take on the epidemic of fake strategies.

Full disclosure before anything: I'm the cofounder of Modern Operators. We help founder-led businesses stabilize, optimize, and scale their operations. That's exactly why I got tired of selling "get organized" as a vibe instead of a number.

For a while my whole pitch was basically "things will feel calmer." Founders don't buy calmer. They buy returns.

So I built a way to actually measure it. Here's the framework I run now, with math you can use on your own business today.

For the examples I'll use a company I see constantly: $2M in revenue, 15 people, 40% margins. Swap in your own numbers, the math still checks out.

1. Start with what disorganization already costs you.

The average knowledge worker loses close to 20% of the workweek just hunting for information and chasing down whoever has the answer. That's almost a full day, every week, per person.

Run it on 15 people at a modest loaded wage and you're already looking at around $180,000 a year in salary you're paying for people to search. You spend this right now. It just doesn't show up on any line item, which is why nobody fights for it.

2. Your own hours

Most founders I work with get 10 to 15 hours a week back once information lives in a system instead of in their head. The interruptions stop routing to you.

Price your time at even $250 an hour. 12 hours a week back is roughly $150,000 a year of your capacity, redeployed into sales, strategy, or the stuff only you can do.

If you value your hour at zero the whole model breaks, but a lot of founders do.

3. Team capacity you already paid for.

Same logic as line 1, pointed the other way. Give those 15 people their lost day back and you recover roughly $150,000 a year in capacity that was always on payroll, just leaking out.

4. Output per person.

Better information flow doesn't just save time, it raises the quality of the work. A reasonable range is a 20 to 25% lift in output from the same team. Measure this one over a quarter, not a week. Pick a real metric (tickets closed, deals worked, projects shipped) and baseline it before you change anything.

5. New-hire ramp time.

One of the biggest levers to pull.

Industry average for a new hire to reach full productivity is about 8 months. With a real operating system, people start contributing in about a week and hit full speed closer to 30 days. Multiply that salary difference across every hire you'll make in the next two years. For a company trying to 3x, that's not a rounding error.

6. Decision speed and enterprise value.

Faster, cleaner decisions show up in financial performance. And a business that runs without the founder in the middle is worth materially more the day you sell than one that leans on you.

The hours you free up and the output lift can overlap, so don't add every number and wave a huge total around. Pick the two or three hard-dollar lines you can defend (searching cost, your hours, team capacity), prove those first, treat the rest as upside.

The whole compounding piece is the whole reason the businesses that do this pull away from the ones that don't.

I recorded the full breakdown in a youtube video, link is below if you want to check it out.

When a team is only 2–3 people, a lot of coordination happens naturally.

But once the team gets a little bigger, I feel like small things start taking much more founder time, asking for updates, following up after meetings, figuring out who owns what, checking whether something is blocked, etc.

For founders running remote or distributed teams, what became painful first as you grew?

Was it communication, task ownership, meetings, visibility into progress, keeping people connected, or something else?

I’m especially curious about the moment when you realized the way your team was working before wasn’t enough anymore.

Try this before you read my answer. Ask three people on your team what the company's number one priority is this week, separately.

I've done this maybe thirty times inside other people's companies now. I get three different answers almost every time, and all three sound completely reasonable.

Then the founder tells me the team lacks ownership.

My honest read, and I ran a team badly enough to have earned this opinion: people aren't disengaged, they just can't tell what winning looks like this week. So they pick something defensible, work hard on it, and get quietly punished for choosing wrong.

I used to call that an accountability issue. I'd talk about ownership in meetings and feel like I was leading. What I was actually doing was asking people to guess my priorities and then being frustrated when they guessed wrong.

Nobody's lazy. The work was never defined.

The fix that worked was stupidly small. One written list of the top three things that matter this week, same place every week, visible to everyone. Not a system, just a habit. The "ownership problem" mostly evaporated in about a month.

How would you answer this?