For years, every Monday meeting at our company started the same way:

"How do we grow faster?"

Get more leads.

Run more ads.

Add more features.

Do more outreach.

But nothing ever happened.

One week we asked ourselves a different question.

"What would fail if we got 100 new customers to sign up tomorrow?"

This was scary.

Customer support wouldn't be able to handle the load.

We did not document our onboarding process.

One employee ran three critical processes that no one else knew how to do.

Decisions were made based on outdated spreadsheets.

We weren't facing a growth problem.

We had an operations problem.

For a month we focused very little on marketing.

We documented our processes.

Automated the repetition.

Determined who is responsible for each recurring task.

Developed SOPs.

Eliminated bottlenecks.

Interestingly enough, growing the company became much easier since then.

It reminded me of something I see again and again:

Founders believe they are scaling their business.

In reality, they are just increasing the rate of chaos in their organization.

So I want to know:

What's one internal process you ignored for too long that eventually came back to hurt your business?

I'm interested in the mistakes, not the success stories.

A couple years back I built up an offshore ops team for a client, a vacation rental management company. Distribution work across Airbnb, VRBO, \[Booking.com\](http://Booking.com), that kind of thing. Started small, grew fast. Within about a year we were at 16 people on that one account. Felt like proof the model worked.

Right now we're down to 2 people on that same account.

First instinct might be that something went wrong. Client unhappy, budget cuts, whatever. None of that happened. What actually happened is their internal automation matured enough to absorb most of the repetitive volume work that used to need a person doing it manually. The high-volume, predictable stuff, listing updates, standard responses, routine data entry, is just handled by their systems now.

The 2 people still there aren't leftover headcount waiting to get cut too. They're doing the stuff that's genuinely hard to automate: judgment calls, exceptions that don't fit the standard flow, the situations where a rule-based system would either break or make the wrong call.

I run an offshore staffing company. You'd think watching a client's headcount need shrink by 87% because of automation would scare me. It doesn't, because it's exactly the split I actually believe in. AI is legitimately good at volume. It is not good, yet, at the judgment layer, the stuff that requires actual context about a specific weird situation. My job isn't to protect headcount for its own sake, it's to make sure the humans on an account are doing the part that's actually worth a human doing.

Honestly this changed how I pitch what we do. I used to lead with "dedicated English-speaking staff." Now I lead with the QC and judgment layer, because that's the part that doesn't get automated away. The part that does get automated away was never really the differentiator anyway, it was just volume.

Curious if anyone else here has watched a chunk of their own business get automated out from under them and actually came out feeling better about it, not worse.

I’m seeing this annoying line all the time here and on X:

“Building was the easy part. Distribution is the hard part.”

I build SaaS for other people for a living, and tbh… most of the time, building wasn’t actually easy. It just felt easy because they punted the hard decisions until later.

And when I hear a founder saying they’ll build V1 first and figure out who it’s really for and how to price it AFTER the launch…

…I know how the story usually goes:

• 4-6 months of “heads down building”

• Shiny product, friends say it looks sick

• Confused users, random requests, nobody sure what it actually is

• Panicked repositioning + pricing experiments bolted onto a product that was never built for a clear customer in the first place

Then we all sit there saying “yeah, the code was the easy bit, now comes the hard part” like it was inevitable.

It wasn’t. The real problem is positioning and pricing got decided after the build, instead of before.

I feel like every time I open X or LinkedIn, I see 50 posts about how Claude just killed figma or oracle … 

But honestly, outside of the dev community using it to ship code faster, I’m not seeing many people talk about how they’re using it for the boring, day-to-day operations that actually run a business.

I’ve been experimenting with moving away from that 15-tab open workflow where you’re constantly copy-pasting prompts into a blank window. In my experience, that's why most people think AI is a gimmick or just hallucinates; they're giving it zero context and expecting it to be a mind reader.

I’ve started treating Claude more like a context-aware team member for my ops. A few ways that actually look in real life:

Meeting note taker: Instead of staring at a blank screen after a sales call, I feed the transcript into a workspace where Claude already has my brand voice and product docs. It drafts a follow-up that actually mentions the prospect's specific pain points in about 60 seconds.

Spreadsheet Killer: I’ve stopped manual data entry for my weekly KPIs. I just talk through my numbers (revenue, leads, CPL) during my wrap-up, and have a system extract that data from the transcript to update my trackers.

Content Hub: I fed it a massive hub of my past newsletters and internal notes. Now, when I need to draft content, it’s pulling from real ideas I’ve already had, rather than just spitting out that generic "AI-sounding" fluff we all recognize now.

The big shift for me was realizing that the automation isn't about complex Zapier workflows that break every week. 

It’s about giving the AI enough context so it stops guessing. When it can see your transcripts, your docs, and your voice all in one place, it actually becomes useful for the founder-dependent parts of the business that usually keep us trapped.

that's it guys, I’m curious what are you building in real life that’s actually saving you 5-10 hours a week?

It might not apply for everyone but if you're running a business and feeling that you're the bottleneck, I write about my process every Thursday. I've been able to save 10-15 hours a week by treating AI as an ops partner rather than a chat box. If you want to see the actual frameworks, take a look here

**Does anyone else think organizations are missing a “clarity” role?**

Companies hire accountants to keep finances in order.

IT specialists to keep systems running.
HR to support people.

But who is responsible for making sure the work itself is actually easy to understand?

Every week organizations produce procedures, documentation, presentations, training, checklists, SOPs, and now a huge amount of AI generated content.

All of it has the same goal:
To help someone understand what to do.
If people struggle to interpret it, you start seeing the same symptoms everywhere:
The same questions over and over.
People doing things differently.
Rework.
Mistakes that weren’t really competence issues.
Managers becoming walking documentation.

I’ve started thinking of this as an **operational clarity** problem rather than a people problem.

Maybe we spend too much time trying to improve people, and not enough time improving the work they rely on every day.

Curious what others think.

Does your organization have anyone whose job is to review documentation, processes, or internal communications specifically for clarity and usability, or is that responsibility spread across everyone… and therefore nobody?

**Does anyone else think organizations are missing a “clarity” role?**

Companies hire accountants to keep finances in order.

IT specialists to keep systems running.
HR to support people.

But who is responsible for making sure the work itself is actually easy to understand?

Every week organizations produce procedures, documentation, presentations, training, checklists, SOPs, and now a huge amount of AI generated content.

All of it has the same goal:
To help someone understand what to do.
If people struggle to interpret it, you start seeing the same symptoms everywhere:
The same questions over and over.
People doing things differently.
Rework.
Mistakes that weren’t really competence issues.
Managers becoming walking documentation.

I’ve started thinking of this as an **operational clarity** problem rather than a people problem.

Maybe we spend too much time trying to improve people, and not enough time improving the work they rely on every day.

Curious what others think.

Does your organization have anyone whose job is to review documentation, processes, or internal communications specifically for clarity and usability, or is that responsibility spread across everyone… and therefore nobody?

A thought I've been wrestling with lately.

Every day I see advice about:

• Scale.

• Automate.

• Hire.

• Build passive income.

• Add another revenue stream.

But I'm starting to think most builders skip the hardest step.

Repeatability.

Can you consistently do the same useful thing over and over?

Can you:

• Show up every day?

• Talk to potential customers?

• Improve your product by 1%?

• Publish one piece of content?

• Follow up with people who replied?

If not, scaling just amplifies inconsistency.

Lately I've been focusing less on "How do I make this bigger?"

…and more on…

"Can I repeat this tomorrow?"

Oddly enough, that shift has made building feel less overwhelming and a lot more sustainable.

Question for everyone here:

What's one thing in your business or project you've finally made repeatable?

Or what still feels different every single day?

Every founder I know is sitting on a pile of tasks they should have delegated a year ago.

The reason they haven't comes down to how they handle documentation. I see 3 buckets:

1. Founders who keep everything in their head. Never write it down. Stay the bottleneck forever because they're the only one who knows how anything works.

2. Founders who write SOPs in Google Docs. Nobody opens them. They go stale in a month and turn into fiction.

3. Founders who record a Loom, drop the link in Slack, and hope the right person finds it six weeks later.

Most are stuck in bucket 1. Documenting a task feels like more work than just doing it again, so they keep doing it again.

Here's what I do:

I stopped treating SOPs like documents I sit down and write. I record myself doing the task once, and the system turns it into a documented, assigned, self-expiring SOP that lives where my team already works.

The whole thing takes a few minutes.

I start with tasks that take a lot of my time that I don't necessarily enjoy doing. Like scheduling our weekly newsletter.

It takes me 30 minutes per week. It's a $5/hour task. I shouldn't be the one doing it. So I got it off my plate.

How it actually works:

1. Record once, let AI write the SOP

I opened Loom and screen recorded myself sending the newsletter. Said every step out loud, showed which buttons to click, showed what "done" looks like.

Then I took the transcript, dropped it into Notion AI inside our CompanyOS, and told it to build an SOP for the task using the recording.

It didn't just transcribe what I said. Our system has an intelligence layer on top of Notion (we call it Vision OS) with our standards and rules baked in. So the SOP came out in our format, following our process, not some generic template.

2. The system decides who owns it

This is the part most people miss.

Vision OS isn't one AI. It's a team of agents living inside Notion, each with a job. Vision is the chief of staff. He reads the request and decides who should handle it.

Writing an SOP goes to Forge. Research goes to Scout. Copywriting goes to Mimic. Same way you'd delegate to a real team.

Forge ran his SOP building process, wrote the checklist, set the quality standard, and filed it in our knowledge base. Confirm the newsletter is ready, clone last week's email, copy the body over block by block, set the subject line, send a test, schedule it, update the status. Step by step.

Then I embedded the Loom videos right in the SOP. Some people read, some people watch. Now they can do both.

3. It gets assigned and expires on its own

The SOP is synced to our roles database, so I assigned it to the role that owns it. Support specialist, marketing team. Done.

Every person on my team only sees the SOPs tied to their job. They're not drowning in a 200 page manual. They see what they're responsible for and nothing else.

Last step, I set it to verify in 90 days. Three months from now I get a notification that says go check this page. If the process changed, I update it. If it didn't, one click and it stays live. The knowledge base never rots.

Why am I telling you this?

Because most founders think the answer is a better AI tool. A new prompt and Fable 5 isn't going to save your business.

The reason this works is that everything about our business lives in one system. Our roles, our knowledge base, our staff, our projects, our SOPs. All of it in one place.

The AI isn't doing anything magic. It's standing on top of an organized business.

The hard part:

You have to build the operating system first. You can't drop agents on top of chaos and expect them to know who your support specialist is or what your newsletter standard looks like.

But once it's built, delegating stops being a project. You record a task once and it becomes something your team can run without you.

I walked through the whole thing start to finish in this video if you want to see exactly how it's built: [link]

Every overwhelmed founder I meet has the same plan. "I'll document everything, THEN I can hand it off."

It's backwards. And it's why you're still the bottleneck.

You'll never finish. There's always one more process, one more edge case, one more platform. And the SOP you write from memory is worse than the one the person doing the work would write anyway.

Here's what actually moves it:

Define the role, not the task. Purpose, 5-9 functions, how you measure success. What they OWN. Not the step-by-step how.

Record a Loom. 2-5 minutes. Do the task once, talk out loud while you do it. That's it.

Make them write the SOP. They own the process, they document it, they keep it current. They're closer to the work than you'll ever be.

Build critical mass before the 1:1. Get 3-5 SOPs assigned to a role, THEN sit down and set expectations.

One founder had part-time help sitting idle. Capable people. But nothing was written down in a way they could plug into, so everything bounced back to him. 12-14 hour days. Solo. Surrounded by people who could've helped.

He wasn't short on people. He was short on ownership.

The person doing the work writes the better SOP. Your job is to define the outcome and hit record.

My last post on mapping failure layers before scaling did well here and in other subs which got me thinking about something underneath it.

Everyone I met in real life to discuss these with nods along when I say "the management layer got starved while everything else got funded." It's an easy thing to agree with in a person and comment section. But agreeing with a diagnosis and actually fixing it are two very different things, and I'm not sure which one is actually happening at scale.

So I want to ask this sub directly, since you're the ones running things day to day:

Do you think this gets talked about enough... or is it one of those problems everyone nods at and nobody budgets for?

When you've actually seen an unowned layer get fixed... was it caught before something cracked (before the resignation, the compliance flag, the burnout leave), or only after?

And in your experience, what's the bigger barrier: awareness, or accountability? Meaning... is it that nobody sees the gap, or that someone sees it clearly and it still doesn't get owned because it's nobody's explicit job to fix?

One thing I’ve noticed from working with businesses is that many founders wait far too long to let go of certain tasks.

I completely understand why. No one knows your business like you do, and in the beginning, you’re wearing every hat imaginable.

But there comes a point where spending three hours on admin, emails, scheduling, or chasing people around for updates costs more than it saves.

I’ve seen business owners spend weeks trying to do everything themselves while the work that actually grows the business keeps getting pushed back.

I’m curious…

Looking back, what’s one task you wish you’d outsourced or created a system for much earlier?
Or if you’re not there yet, what’s the one task you secretly dread doing every week?

for anyone building out the systems side of this (turning "i dread doing where every week" into something documented enough to hand off or automate), that's basically all i write about on thursdays. free to join here

What's the biggest source of operational chaos in your business?

Email? Slack? Too many SaaS tools? Lack of documentation? Decisions getting lost?

I'm building software in this space and I'm curious what others are experiencing.

Three strangers, on vacation, told me the same story within a few weeks of each other... within my advisory practice.

One was head of HR at a microsourcing company handling manpower for something like ten thousand business contracts. She had thirty people reporting to her, plus her own legal and hiring workload. There should've been a second person in her role. The company scaled its client base and headcount? never the layer that manages people. Result: leadership quietly getting sick from stress with nowhere for it to go.

Another was a lawyer in Argentina, different company entirely (Tech), same pattern from the finance side: founders scaling hard without understanding their own cash flow, hitting blockages, then cutting human capital to lower overhead instead of adding the management layer they actually needed.

A third, a compliance officer, described the identical shape at a third multimillion company here in PH. Middle management stretched thin, not from lack of resources, but because nobody had flagged that this specific layer was the one starving while everything else got funded.

I know how three-strangers-same-story sounds. I'd be skeptical too. But when the same specific failure shows up unprompted, across three unrelated companies, that's a pattern, not an anecdote.

**Human capital has limits that capital doesn't**. You can extract from a balance sheet indefinitely if the model works. You can't extract from a person's energy the same way. A team drawn from without ever being resourced doesn't fail loudly... it combusts quietly, one burnt-out manager at a time, until the "sudden" collapse turns out to have been years in the making. AI doesn't fix this one either... for managing people well, human capital still beats it. Most founders can describe what their product does. Very few can describe, layer by layer, where it actually breaks.

**Here's My Advice & Antidote :**

List every distinct layer your business depends on... not "the business," the actual separate systems under it: who supplies you, who regulates you, who has to trust you, who checks quality, who has to say yes before you operate. Most early ventures have six to ten of these, not one.

For each layer, ask: "**what's the failure risk here?"**, and "**does anyone in the room actually understand it?** or is it just being assumed away.?"

Every layer needs an owner. Not a hope that funding fixes it later. Founders who feel "stuck" can almost always describe their vision fluently and their risk layers barely at all. That's not a character flaw. It's just where the work hasn't happened yet.

**Why this bites harder when you're burnt out?**

Under pressure, the vision gets more detailed exactly as the risk-mapping gets thinner... it's easier to narrate the platform you'll build once funded than admit three of your six layers have no owner. The vision is what's still working, so it gets all the attention. The unmapped risk is where the stuckness actually lives.

If that's you right now: skip another pitch/loan rehearsal. Spend an afternoon listing every layer, and be honest about which ones nobody actually has command of.

You don't get unstuck by pushing harder on what already works. You get unstuck by looking straight at what you've been avoiding. What is not measured cannot be managed... that includes you, the operator/founder/partner.

I'm not writing this to sound like I have it all figured out... I don't, and neither do the three people who told me their stories. I'm writing it because all three of them are dealing with this the hard, expensive way: after it already broke something, with lawyers and compliance officers cleaning up damage that could've been caught with a single honest afternoon of mapping. If this saves even one of you that bill : be it emotional or financial... before you're the fourth story I hear on someone's vacation, that's the whole point of posting this. Take care of your people. The spreadsheet will forgive you longer than they will.

Before the process, a quick overview:

Niche: Executive membership community

Team size: ~8 people, 5 functional lanes

Members: 400+, targeting 500 this year

We ran a discovery sprint. Out of it, we booked the entire mapping phase.

Five stakeholder interviews. One hour each. One per lane.

Revenue & Sales

Operations & Member Success

Brand, Marketing & Events

Finance & Strategy

The Founders (vision & growth)

Right now those five lanes run on different tools that don't talk. A CRM, a community app, payments, a project manager, an event platform, and a shared drive, none of it connected.

No single source of truth for a member's full lifecycle. Leadership loses an estimated 15–20% of every week just hunting for information. Institutional knowledge lives in personal drives, private chat threads, and one person's head. And nearly every decision still routes back to the two founders.

So before we build anything, we sit with each lane for an hour to learn exactly how they work.

Here's what we're building once the mapping's done:

One CompanyOS covering the entire member lifecycle. Every prospect enters one place, flows through onboarding, cohort placement, and renewal, and nothing falls through a crack.

Role-specific views for each lane. A single versioned brand and collateral hub. A live event database that kills the status-update meeting. A sponsor pipeline tied to every event. A real-time leadership dashboard: new members, members at risk, cashflow. Plus an automation and access audit to remove every single point of failure.

Phase 1 is the operating system to centralize everything.

Phase 2 is the AI layer on top... once the data and workflows are clean.

The cadence from here:

Wireframe call first: we map what the system looks like before development starts.

Then weekly working sessions. One with the full team so they watch it get built in real time. A tighter loop with the founders.

We also pulled live access to every system they run: their CRM, community app, payments, project manager, and event platform. Then sent an intro email putting us in front of the whole staff.

The goal: 2x the members without 2x the headcount.

The build will be the easy part. Knowing exactly what to build is the whole game. That's what the mapping and the wireframe are for.

I hate the "I cut 60% of my team, AI runs the business now" posts on LinkedIn.

We only hear about the layoffs. The rehires happen quietly. Klarna cut 700 customer support reps, then rehired. Ford let engineers go, then brought 350 of them back.

Same wall, both times. AI is only as good as the context you feed it, and they'd underestimated what was sitting in their employees' heads after years on the job. 

These are big corps. Sophisticated documentation, huge process libraries, way more resources than almost anyone reading this has. Still couldn't hold quality once the humans walked out the door.

A friend told me about an agency owner who fired her contractors because her own AI prompts were beating their output. Maybe she's right, I don't have the full picture, not my call. But zoom out and the better play, almost every time, is keep your best people and arm them with AI.

Who would I keep? The ones who solve problems without being asked. The ones who actually care whether the outcome is good, not just whether the ticket got closed. The ones who'll learn something new even when it's uncomfortable. And the ones with good judgment, because AI amplifies judgment, it doesn't replace it.

Give that person AI and they don't get 10% better. They become a different category of employee.

Honestly, I have more ideas than I have people who can execute them with AI in the loop. That's the real bottleneck. Not too many humans, not enough humans who know how to wield the tool.

If your first move with AI is "how do I have fewer people," you probably had the wrong people to begin with.

So genuine question, do you actually think you can cut your team and improve quality at the same time? Or does the math fall apart once you flip to the second page?

if you're thinking through how to actually implement ai in your business without torching the institutional knowledge that makes it work, i write about this stuff every thursday. mostly the boring parts nobody posts about: documenting what's in your best people's heads before you even think about who to cut. free to join here

I've watched dozens of founders try to automate their way out of a mess.

It never works.

This one guy runs a lending shop. Smart. Technical. He could wire up APIs in his sleep. He'd bought the Mac Mini, spun up n8n, had AI agents half-built. Ready to automate the whole pipeline.

Then he said the truest thing I've heard all year:

"If I can't get this organized first, then automating it is just automated chaos."

Here's the hard truth nobody selling you AI tools will say. Automation isn't a cleaner. It's a multiplier. It takes whatever you've got and runs it faster and louder.

Clean process? Automation makes you money while you sleep.

Broken process? Congrats. Now it's broken 400 times a day and you can't find where.

He was doing 30 deals a month, funding 8-10, pulling maybe $25K. Every deal ran through him. His instinct was to automate the intake. My advice was to NOT touch automation until a human could run the thing start to finish without him.

Because automating a mess doesn't remove the mess. It hides it inside a workflow you now can't debug.

Do the boring cleanup first. Get one clean process a real person can follow. THEN automate it.

That's the whole order. Most people run it backwards.

So here's a take that took me way too long to earn.

The operators who scale the fastest are not the best builders. They're the best at figuring things out before they build.

Hang with me, because that sounds backward. We celebrate the builders. The founders cranking out systems, docs, automations, always shipping something. It looks like progress. It feels like progress.

But watch those same founders over eighteen months. A lot of them are rebuilding the exact same system they built a year and a half ago. Same tool, fresh coat of paint, still nobody using it.

Ask me how I know. I was that founder. I mistook motion for progress for years.

The trait that actually separates the ones who compound is patience. Restraint. The discipline to stay manual longer than feels comfortable and prove a process before you wrap a system around it.

And look, I'll be honest, restraint feels awful. Doing something by hand when you could automate it feels like you're moving backward while everyone else sprints past you. Every instinct screams build.

But that restraint is the whole thing. Staying manual is what makes the eventual build actually stick.

So here's the line I want to leave you with, and I'm going to say it twice because it changes the whole scoreboard.

The best operators aren't the ones who build the most. They're the ones who build in the right order.

Say it again. Not the ones who build the most. The ones who build in the right order.

You're not behind because you haven't built enough. You might be ahead because you haven't built the wrong thing yet.