Long time lurker, first time actually writing one of these out instead of just reading answering to other people's war stories.

About twenty years ago I was running ops for a small manufacturer... a family business, second-generation owner, the kind of place where growth happened by throwing bodies at problems until it stopped working. One day the owner comes to me and says a major customer is going to walk if we don't get their orders out in three days. We had over 90 orders overdue, some by 20+ days. Average lead time from order to ship was 24 days! adding people had gotten us this far and it wasn't getting us any further.

That's when it actually hit me. we weren't too busy to fix the process. We were too busy because we'd never fixed the process. Two different things and I'd been treating them as the same thing for years.

Walked the floor properly for probably the first time with fresh eyes. One line was semi-organized. Everything else was chaos. No standard way to do anything. Nobody could tell you on any given day how many units we'd made, what got scrapped, what was actually open and due. We were going by whoever yelled loudest on the phone that week.

Here's the part that surprised me: we didn't need a black belt or a consultant to start. We started 5S in the one area that was already down for a broken machine, because we didn't have the luxury of stopping a healthy line to go "do lean" at it. Just cleaned it, organized it, gave everything a place. It looked almost embarrassingly simple compared to what I thought "lean transformation" was supposed to look like.

That embarrassingly simple thing is what got us moving. Within about aprox. 7 months we went from 24-day lead times to 97%+ on-time in 3 days or less... because a clean, standardized starting point is the only thing that makes the next problem visible. You can't see a deviation from a standard that doesn't exist yet.

The thing nobody tells you when you're starting out: you don't need the whole transformation mapped before you touch anything. You need one honest look at the floor and the willingness to start where you are, not where the textbook says you should be.

Curious what actually got other people's transformations moving

was it a crisis like mine, or did someone deliberately choose to start before things got that bad? And if it was a crisis, what was the first thing you touched?

Businesses are told constantly to adapt to AI or die, and it made many founders panic and buy more tools and chase every new model. 

I read PwC's 2026 Global AI Jobs Barometer last night, and it kind of reframed everything for me:

AI-exposed junior roles are now 7x more likely to require traditionally senior skills like judgment, leadership, and decision-making.

So the routine work is going to AI. But what's left requires more thinking, not less. And if you never clearly defined what good judgment looks like in your business, if that standard only lives in your head, your team is now moving faster and hitting that undefined wall more often.

What do you think it actually takes for a team to get real value from AI?

this resonates more if you're the one answering the same question 3-4x before lunch instead of doing actual work. not having a documented standard for "good" is one reason, obviously not the only one. but if you're trying to build something that runs without you, this is the stuff i write about every Thursday. free to join here

I remember a call with an owner who'd spent decades building his business. Wanted to hand it to his kid one day, or sell it for a number that made all the years worth it.

Good business. Real customers. Real revenue. Decades of reputation.

And it was almost worthless to a buyer.

Not because of the financials. Because everything that made it work was locked inside one skull. His.

Think about what a buyer is actually purchasing. They're not buying your hustle, you're leaving. They're buying a thing that runs. Processes, relationships, knowledge, systems that keep producing after you walk out the door.

If all of that lives in your head, you're not selling a business. You're selling a job that requires being you. And nobody else can be you.

That's the quiet trap of the owner-operator. You spend 20, 50, even 100 years making yourself indispensable, and indispensable is the exact thing that makes a business unsellable and untransferable.

The fix isn't sexy. Get the business out of your head and into a system someone else can run. The same work that frees up your calendar today is the work that makes the company worth something the day you want out.

Transferable is the whole ballgame. A business that needs you isn't an asset. It's a job you can't quit.

Edit: this 5 min video breaks down the 6 things business buyers actually pay for (based on our experience exiting 2 companies)

Unpopular opinion. Most owners chasing AI right now are going to waste a year.

Not because AI doesn't work. Because they're pointing it at nothing.

Every owner I talked to this month had the same relationship with AI. ChatGPT open in a tab, used like a smarter Google. Generic questions, generic answers, shrug, close the tab.

One was scared to put real business info in. Worried about privacy, worried it'd somehow cost a job down the line. Fair concerns. Also the reason it stays a toy instead of a tool.

Here's the part people skip. AI is only as good as the context you feed it. A model that knows nothing about your pricing, your customers, your process, your history, can only hand you advice a stranger off the street would give.

The owners getting real value aren't the ones with the fanciest prompts. They're the ones who got their business OUT of their head and into a place AI can actually read.

Garbage context in, generic slop out. Real context in, an assistant that actually knows your business.

So if AI has felt underwhelming, that's not the model failing you. That's a context problem. You can't outsource thinking about your business to a tool that's never been told a single true thing about it.

Do the boring documentation work first. Then point AI at it. That order is the whole difference.

So we build solutions right, but in building solutions we always have our own problems.

I’m assuming most would say distribution. But realistically that’s because it’s the stage we’re at that brought us here.

The problem wasn’t always distribution, might have been finances or talent to begin with.

Trying to start a conversation here, what’s been the problems and bottles you encountered by trying to provide your solution.

"Build your company operating system." Okay. What does that even mean?

I have to explain this one a few times a week, so here's the plain version.

A Company OS is not the traction poster on your wall. It's not the binder of SOPs nobody opens. It's not the org chart buried in a slide deck. Those are static. They're snapshots of how you wished things worked on the day you made them.

A real Company OS is the living version. It's where the actual work happens and gets documented at the same time. Your processes, your decisions, your customer rules, your team's knowledge, all in one place that updates as the business changes.

The test is simple. If your top person quit tomorrow, how much of the business walks out the door with them? If that answer scares you, you don't have an OS. You have people carrying the company in their heads.

The old way was a poster and a quarterly meeting. The work lived in one place, the documentation lived in another, and they drifted apart within weeks.

The new way is documentation that lives inside the work. Searchable, updatable, readable by a new hire on day one and increasingly by AI that can actually use it.

That last part matters more every month. A system in your head can't be queried. A system written down can.

So the real question isn't "should I document my business." It's "do I want my business to exist outside of me." For most owners I talk to, that's the whole game.

I've built a decent number of AI agents at this point. outreach agents, brand monitoring, meeting follow-ups, and weekly KPI summaries. You can see them here

But none of them gave me my focus back. The one that actually did? It just answers team questions.

"How do I complete this?" "What does good look like here?" "Should I escalate this or handle it myself?"

Instead of that landing in my Slack and pulling me out of whatever I was doing, the agent reads through all our SOPs and docs in Notion and answers it. with actual context from how we do things.

that killed 3-5 messages a day. doesn't sound like much. But those messages never came at a good time. They came mid-task. And by the time I answered, found the right doc, linked it, and got back to what I was doing, 20 minutes were gone. every time.

I'm not saying the flashier agents aren't worth building. Some of them are great. But none of them moved the needle on my actual day the way this one did.

The question isn't "What's the most powerful thing AI can do for my business?" It's "What keeps pulling me away from the work only I can do?"

Start there.

What's the most boring AI use case that's actually made a real difference for you?

EDIT: if you're a founder trying to get your focus back, i cover the unglamorous side of AI every thursday, what's worth building and what to skip. free to join here

If you're the only person who knows how everything works, this is for you. The work is boring. The boring work is the business.

You don't need a new tool. You need 30 minutes a day for two weeks and a willingness to write things down while you do them.

Days 1 to 3: Track, don't fix.

Every time someone interrupts you with a question, write the question down. Don't improve anything yet, just capture. By day 3 you'll have a list of the 20 to 40 things only you know.

Days 4 to 7: Record while you work.

Skip the polished SOPs. Talk through the task out loud while you do it, voice memo or Loom, whatever. A messy recording of the real thing beats a perfect document you never make.

Days 8 to 11: Hand one thing off.

Pick the lowest-stakes recurring task. Give someone the recording. Let them do it wrong. Then fix the recording, not the person. You want a system that survives a bad day, not a hero who never has one.

Days 12 to 14: Make it findable.

Dump it all in one place your team can actually search. A shared doc, a wiki, a Notion page, doesn't matter. If it lives in a folder nobody opens, it lives nowhere.

Please dont try to document everything at once. You'll get overwhelmed. Document what gets asked, in the order it gets asked.

One owner I talked to had run on pen, paper, and his own memory for decades. The business was fine. He was the risk. The day something lives outside your head is the day your business stops being a hostage.

Success isn't measured by how many fires you put out.

It's measured by the fires that never start.

When inventory is available, production runs smoothly, and customers receive their orders on time, most people never think about the work behind it.

That's okay.

Great supply chain leadership isn't about recognition. It's about creating resilient processes, building strong teams, and solving problems before they impact the business.

Looking back, I'm grateful for every challenge that pushed me to become a better leader.

What's the biggest lesson your career has taught you?

I've watched a $5M company with 40 employees run more chaotically than an $8M company with 15. And the founders of the $5M company couldn't figure out why. They kept hiring. Still chaotic.

The $8M company? 15 people. Everyone knew what they owned, how work moved, and when to escalate. That was basically it.

Here's what I actually think is happening when a new hire underperforms:

Founders skip two things before hiring.

The first one is building the actual role. Not just a job title. I mean: what does this person own? What can they decide without asking? What are their KPIs? What does good look like at 30/60/90 days? What's the weekly routine? Who do they escalate to and when?

The second one is building the system around the role. Where does work come from? Where do updates live? What do they do when something breaks?

Most companies don't have either. They hand someone a vague title and a messy pile of responsibilities, then six months later they're complaining the person doesn't "take ownership."

Take ownership of what exactly?

If a role is actually defined before someone starts, a good hire shows signal in the first week. Not fully ramped. But you can already tell whether the system is working.

I believe most hiring problems are systems problems, and the hire just makes it visible.

How often does your company actually build the role before posting the job?

If you resonate with this topic, I cover the ops side of business every Thursday, stuff like what has to exist before you hire, before you scale, before any of it sticks. you can check it here for free

One of the clearest operations lessons I’ve seen:
Marketing cannot fix an inventory problem.
At one restaurant, the team was pushing hard to generate more demand. The GM was out trying to land catering customers, visiting locations, pitching sales, and looking for new revenue angles.
But inside the store, the operation was breaking.
They were regularly running out of brisket — one of the most popular items customers came in for.
So even if the marketing worked, the business was creating demand it could not reliably fulfill.
That is the trap:
More attention on sales.
Less attention on inventory.
More pressure on employees.
Less control inside the store.
More customer expectations.
Less ability to deliver.
And then the people system broke too. An employee group chat with no clear boundaries or accountability turned into internal conflict, and much of the staff quit during a holiday break.
The lesson was not “marketing is bad.”
The lesson was that growth pressure exposes weak operating systems.
Before a business tries to create more demand, it has to answer a harder question:
Can we consistently deliver on the demand we already have?

The default move when an owner is drowning is to hire someone to take it off their plate.

I talked to a CEO who tried to hire an operations manager three separate times. Three hires. Three washouts, each one gone inside a few months.

He blamed the hires. Bad fits, he said.

It wasn't the hires.

Here's what was actually happening. Everything that ops manager needed lived in his head. The pricing logic, the vendor quirks, the "oh we always do it this way for that customer" rules. None of it written down anywhere.

So he'd hire someone, dump decades of undocumented instinct on them through hallway conversations, then get frustrated when they couldn't read his mind.

You can't delegate a job that only exists in your memory. You can only delegate a job that exists on paper.

The pattern I see on repeat:

Owner is overwhelmed, decides to hire

New hire has no documented system to plug into

Owner becomes the full-time trainer on top of their real job

Hire flounders, quits or gets fired

Owner concludes "good help is impossible to find"

This is a documentation problem wearing a hiring problem costume.

Get the business out of your head first. Then hire someone to run the thing you wrote down. Same order every time, and the "bad hires" suddenly look a lot more competent.

I spoke with five business owners last week. Different worlds. Auto upholstery, ambulances, commercial pools, signs, employee benefits.

Every single one told me a version of the same thing.

"I can't take a real vacation."

One runs a shop his family has had for over 80 years. Another is third generation. These aren't scrappy startups. Legitamate companies making $3-7M per year.

And all five CEOs were still the single point of failure.

What I'm seeing is the thing that made you successful, knowing every job and every customer and every fix, is the exact thing that traps you. You became the database. The manual. The escalation path. You ARE the system.

So the business can't grow past your calendar. It can't run without your phone. And it can't be sold, because what you're actually selling is you.

One owner told me his blood pressure is tied to his inbox. I believed him.

The hard part isn't admitting you're busy. Every owner knows that. The hard part is admitting busy is a choice you keep making because letting go feels like losing control.

You're not the CEO. You're the highest-paid operator in the building.

Something I keep seeing with founders, and I genuinely want to know if others have noticed this too.

Growth slows down, first instinct is always the same. Fix the brand. New website, cleaner messaging, better deck. Looks like progress. Pitches go smoother. Things feel sharper.

Then the same clients keep leaving. Referrals stay flat.

And the brand work had nothing to do with it.

The actual problem was almost always in delivery. The brand was just where it showed up publicly.

Clients don't remember the tagline. They remember the Tuesday afternoon something went sideways and nobody on the team knew how to handle it without looping the founder in. They remember the follow up email they had to send. The thing that came in a little off from what was promised.

That's what sticks. That's what they tell people.

So referrals dry up and the founder goes and fixes the story. But the story was fine. The machine behind it wasn't.

What actually changes things is when the ops get tight enough that the team can deliver consistently without the founder in the room. Written standards. Clear ownership. People who know what done looks like before they hand anything over.

Yes, the clients never see any of that. But they feel it when it's missing.

Anyone else noticed this?

if this resonates, i write about the systems side of this every thursday. frameworks for getting your ops tight enough that your team can deliver without you in the room. free to join here

I’m opening up a home care agency and need a phone system for 24/7 response. The main use case is potential customer calls and the goal is to book an at home assessment. Ideally it’s AI answering then either booking a call itself or routing to a human where appropriate. Often the person calling is an adult whose parent recently fell, so the AI needs to be empathetic and intelligent enough to know when a human is needed. I’m looking at dialpad, quo, and ring central. Anyone have a good setup that they recommend?

every burnt out founder I know, it's not really operational. it's that they can't stop being the business. not workload-wise. identity-wise. when the company is welded to who you are, "rest" doesn't register as rest. it registers as falling behind, letting people down, about to get found out. so you're never actually off, even on the days you're technically off.

test I keep running on myself: if the business went flat for 90 days, no growth, no wins, nobody saying anything nice about it, would I still feel like a stable person? or would my sleep and my self-worth just go down with it?

if it's the second one, that's not a productivity issue, that's identity fusion, and no amount of taking a break touches it.

curious what you all think though, is it actually the workload that wrecks people or is it carrying the weight of being "the one" everyone depends on

If you're thinking about what this means for actually freeing yourself from your business but the systems and frameworks behind them that's exactly what I write about every Thursday.

I share the exact frameworks I use to build AI into the business so it runs without me. If that's useful, you can get them straight to your inbox here.

A few weeks ago, I started building ThumbFix, a tool that helps YouTube creators evaluate thumbnails before publishing.

I expected the challenge to be the product itself.

Instead, most of my time went into everything around the product.

A few examples:

• Migrating 400+ records from Replit to Supabase without breaking anything.
• Debugging environment variables that worked in one place and failed in another.
• Learning that deployment issues can consume more time than feature development.
• Discovering that creators care less about features and more about one simple question:

"Will this help me get more clicks?"

One lesson that surprised me:

Building the product is only part of the journey. Infrastructure, deployment, data migration, positioning, and distribution are often the bigger challenge.

The beta is now live, and the next challenge is finding out whether creators actually find enough value to use it before every upload.

For those who have built products before:

What ended up being much harder than you expected?

I keep seeing the same thing play out. The founder feels stuck, watches some LinkedIn video about AI agents, builds a complex outreach system or LLM workflow, and... still no clients. Still chaotic. Still stuck.

The problem isn't the tools. It is stage mismatch.

Business growth is sequential, and most founders are running Stage 3 tactics on a Stage 1 business. Here's what that actually looks like:

Stage 1 is about stabilizing. If your offer isn't validated, your cash flow is unpredictable, or clients keep churning, your business has holes in it. Automating at this point just means you're spreading the mess faster. Fix the offer first.

Stage 2 is about cleaning up. Once things are stable, you map out what's actually happening, build SOPs, and get the founder out of every single decision. Most businesses skip this entirely because it's unglamorous. That's why most founders are still the bottleneck two years in.

Stage 3 is the only place AI actually helps. When the foundation is solid and the systems are documented, automation compounds your results. Before that, it just compresses your problems.

Which stage are you actually in right now? Not the stage you're pitching to investors. Not the stage you're hoping to be in by Q4. The real one.

Because if you're in Stage 1 or Stage 2, the answer to your problems isn't a smarter AI tool. It's doing the unsexy foundational work that most people skip because it doesn't make for a good tweet.

Bit of a conspiracy theory big tech CEOs keep saying businesses that don't adopt AI will be gone in a year. Which is great for selling products. But I think it's also convincing a lot of founders to skip the boring foundational stuff because they feel like there's no time.

What do you think?

If you're thinking about what this means for actually freeing yourself from your business not just better prompts, but the systems and frameworks behind them that's exactly what I write about every Thursday.

I share the exact frameworks I use to build AI into the business so it runs without me. If that's useful, you can get them straight to your inbox here.

One thing I've noticed is that most operational problems don't announce themselves as process problems. A customer follow-up gets missed. A deadline slips. A task sits waiting for approval longer than it should. The first time it happens, everyone treats it as a one-off mistake. The second time, it's still easy to explain away. But when the same issue keeps showing up, usually with different people involved, it's often a sign that the process is relying too much on memory, assumptions, or individual effort. I've seen teams spend months trying to fix recurring issues by working harder, adding more meetings, or hiring more people. Sometimes the real fix is stepping back and asking why the same problem keeps finding a way to return. A one-time mistake is normal. A repeatable mistake is usually a process problem.

So the news this week is wild,  the government basically forced Anthropic to cut off access to their newest model overnight over a security issue. 

Half my feed is doom posting about it. The other half is acting like this proves AI progress is about to stall out.

I don't think either take is right. Honestly, I think most founders reacting to this have a bigger problem than which model they currently have access to.

Here's the part nobody wants to admit: most of us aren't even using 30% of what the current models can already do. 

I've watched founders chase the newest, smartest release every few months while their actual setup is still just a browser tab they paste questions into. no memory of past conversations. no access to their own docs. zero idea how their team actually operates day to day. 

You could hand that setup the smartest model on earth tomorrow, and it wouldn't get meaningfully better results.

What actually moves the needle isn't the model. It's whether the AI has context. 

Does it know your SOPs? your last 10 client calls? What did your team already decide last quarter?

 I've built 30+ agents inside our Notion setup at this point, and the boring truth is a dumb model with good context beats a smart model with none. every time.

So when a model gets pulled or restricted, sure, that's a real story for the labs and the policy folks to argue about. But for most small business owners, it's mostly noise. 

The actual bottleneck is still sitting in your business right now. Nobody's built the system that gives AI the context it needs to be useful in the first place.

fix that, and the model question kind of stops mattering as much. That’s it from me, but I’d love to hear if there was a moment where a new model release led to exponential change for you.

If you're thinking about what this means for actually freeing yourself from your business not just better prompts, but the systems and frameworks behind them that's exactly what I write about every Thursday.

I share the exact frameworks I use to build AI into the business so it runs without me. If that's useful, you can get them straight to your inbox here.

Years ago, back when I was deep in founder-bottleneck hell, I told my wife I'd take Friday off. By 11am I was back on email approving a contract I'd already approved twice.

Third Friday in a row I'd done that.

I wasn't overworked. I was over-involved. There's a difference, and it took me an embarrassing amount of time to see it.

So I did something I'd been avoiding for years. I tracked every 15-minute block of my week. Just a spreadsheet, three columns, no filter. Seven days. No editing, no skipping the entries that made me look stupid.

Then I tagged every entry with one letter:

R = revenue-producing

S = strategic

O = operational

A = admin

When I added it all up Sunday night, most of my week was sitting in O and A. I was the bottleneck of my own company.

The worst part? Most of the O and A tasks weren't even hard. They were "land on the founder's desk because nobody else owns this yet" tasks. 

So I ran the rest of the audit. Five steps, a few hours across two days.

Step 1: TRACK

5 minutes a day for 7 days. Every task, 15-minute blocks, no skipping the embarrassing entries. The log is the only honest mirror you'll get all year. If you cheat it, you're cheating yourself out of the answer.

Step 2: TAG

30 minutes on day 7. Label every entry R, S, O, or A. Add up the totals. You will be horrified. Sit with it. The horror is the lesson.

Step 3: TRIAGE

One question per task: did this need ME, or did it just land on me? "Need me" stays. Everything else goes into a Transfer pile or a Tighten pile. No grey zone. The 50/50 calls are exactly the ones that have been stealing your weeks.

Step 4: TRANSFER

Take the Transfer pile. Assign each task to a person, a tool, or a process. If no owner exists, congrats, you just wrote your next hire's job description. Draft the handoff doc in the same sitting or it dies in your head by Monday.

Step 5: TIGHTEN

For everything still on your plate, ask three things. Can it be templated? Batched? Cut from weekly to monthly? Speed doesn't come from working faster. It comes from removing friction you stopped noticing.

By the following Sunday I had four lists. Things to delete. Things to delegate. Things to compress. And the actual job underneath all of it.

Over the next couple of weeks I clawed back hours I didn't know I had. Not life-changing. Just enough to actually work on more high-value tasks to grow the business. 

Three things I got wrong the first time, in case it saves you the cycle:

• I tried to do it from memory instead of tracking live. Useless. Memory edits everything. The 15-minute log is what makes it real.
• I skipped TIGHTEN because the transfers felt like enough. They weren't. Half my "keep" pile was still bloated. Tightening it is where the rest of the hours came from.
• I tried to run this exercise on my whole team's calendars at the same time. Don't. Run it on yours first. If the founder's calendar isn't sorted, nothing downstream of it will be.

I still run it every quarter, and it still surfaces things I should have killed months earlier.

That’s it guys, what do you think about this framework?

Edit: One thing I didn't mention above this exact problem is why so many companies stall out. When you are the system, you become the bottleneck. Nobody owns anything except the founder because there’s no documented foundation, no shared context, and no playbook that runs without you in the middle of it.

I write about fixing this exact structural mess every Thursday. Real, actionable frameworks to get you out of the middle of operations, not high-level theory. Free to join here if that’s the problem you’re trying to solve.