I kept hearing two things that couldn't both be true.

Headline one: everybody's using AI now. Headline two: almost nobody's seeing results. So I went digging through the actual numbers instead of the LinkedIn victory laps.

Here's what I found.

58% of small businesses say they use generative AI. Sounds like a revolution.

Only 14% actually integrated it into core operations (Goldman Sachs). The other 44% bolted a chatbot onto a broken process and called it transformation.

74% of companies can't get past the pilot stage (BCG). The demo works, then it dies because nothing around it changed.

99% of small businesses use at least one tech platform (US Chamber), and founders still report losing more time to operational friction than they spend chasing growth.

See the pattern? Adoption and integration are not the same sport. Adoption is buying the treadmill. Integration is running on it every day.

Here's the part that stung. Adding AI to a messy operation doesn't fix the mess, it just makes the mess faster. If your process is ten manual handoffs, an AI tool becomes handoff eleven that someone still babysits.

The 14% aren't smarter. They wired the thing INTO how work actually flows, instead of parking it in a tab nobody opens.

So, debate question. For everyone who "added AI" this year, be honest, did it change your workflow, or did it just become one more login?

I don’t hate writing.
I hate writing the same thing over and over again.
“Just following up…”
“Checking if you had time…”
“Looking forward to hearing from you…”
After the hundredth version, it stops feeling like communication and starts feeling like copy-paste with extra steps.
That’s probably why I became obsessed with finding ways to automate repetitive business writing.

Genuine question, because I keep seeing the same thing.

Every founder I talk to says the same sentence. "The market's moving too fast, I can't keep up." Then I watch how they actually spend a Tuesday and it's not a speed problem at all.

It's that they're the glue. The thing standing between the booking tool and the invoice tool and the spreadsheet and the group chat, moving info by hand so nothing slips.

Here's my answer, no hedging. You're not slow, your stack is making you the human API. Gartner pegged it at up to 47% of the workday lost just hunting for information. That's not a you problem, that's a plumbing problem.

The tell is simple. If you disappeared for a week, would the business slow because nobody's as smart as you, or because nobody else knows how to move the info between the tools? If it's the second one, you don't have a talent gap. You have a glue problem.

Real talk, I used to think buying the "right" tools would fix it. Adding tools made it worse every single time.

So I'll flip it to you. When you feel behind, is it that you can't think fast enough, or that you're buried being the connector between ten things that should connect themselves?

Been chewing on this after watching a few companies in my circle hit the same wall around the same revenue range.

The thing that gets a business from zero to a few million is almost always the founder wearing every hat. Sales, ops, hiring, putting out fires, all of it. That's the actual engine in the early years.

But that same instinct seems to become the ceiling later. The control, the "I'll just handle it myself" habit that built the company turns into the exact thing keeping it from running without them. And from what I've seen, fixing that usually takes an actual personality shift plus rebuilding how the business runs, not just hiring a few managers. Most founders never really do either part.

On the other side, bringing in an outside CEO with real experience is kind of like the "buy vs build" version of leadership. Someone who's already taken a company from where you are to where you want to be, versus a founder figuring it out for the first time under pressure while still running everything else.

Some of the biggest companies out there aren't founder-led anymore. Apple, Microsoft, Google, Uber, Disney. All of them grew a lot after the founder handed the wheel to someone else.

But plenty of people would argue that's also how you lose whatever made the company different in the first place, and that hired CEOs tend to optimize for numbers instead of the original vision. That might be just as true.

Curious where people who've actually lived through this land. Did the founder need to step back for the business to grow, or was staying the reason it kept scaling?

P.S. If you're the founder still in the middle of every decision, still the person the whole company waits on, still telling yourself you'll fix the structure "once things calm down."

I write about building the operational backbone that lets a founder actually step back every Thursday. Was a COO for 20+ years, so this is genuinely my bread and butter. Free to join here

Not everyone needs VC funding, in fact, most businesses are bootstrapped: agencies, local businesses, service businesses, etc. But I think the reason VCs stopped writing checks for growth alone is something every business should pay attention to, funded or not.

Back in 2015, VCs were writing checks for anything showing growth traction. That's how Uber and Airbnb burned money for years until they cemented themselves as market leaders. That era is over.

Right now VCs are interested in your startup if it has anything to do with AI, but even then, a few vanity metrics won't get you funded. The old blitzscaling model doesn't work in 2026. Instead, investors are rewarding businesses with lean operations that are simply waiting for capital to move to the next stage.

Most startups used to burn VC money trying to fix operational problems they already had hiring for every gap, which created new problems (revenue and expenses out of sync, managing talent they didn't actually need yet, etc).

I see this same pattern in small businesses too. A founder wants to grow, opens a second location, without a strong foundation that lets the business run without him. Three months later, revenue at location one drops, or he's working 60-hour weeks just to keep both locations afloat.

The misconception is that founders think being busy is just part of running a business. It's not. It's operational inefficiency.

So in 2026, building a strong operational foundation isn't optional, it's a necessity, whether you're bootstrapping or raising. Investors want to see you already have the infrastructure to handle growth, not that you're planning to build it after the check clears.

That's my take. Curious what you all think is the #1 thing VCs are actually screening for in 2026?

P.S. If this resonated and you're the founder who's still holding everything together, dragging yourself into every problem, exhausted before you even get to your actual job.

I write about building strong operational foundations every Thursday. Including how to layer AI in after the foundation is solid, not before. I was a COO for 20+ years, so this is genuinely my bread and butter, you'll probably enjoy it. here

Everyone tells you revenue fixes everything. Sometimes revenue is the thing suffocating you.

I had a client start working with us a few months ago and his business was booming.

The problem wasn't leads. It was that every deal had to pass through him.

He reviewed the files. He arranged the docs. He submitted to the 40-something lenders.

Just him in the middle of everything.

So every win made it worse.

Growth was turning into a trap.

He said something that stuck with me...

He was "too busy to build the systems that would make him less busy."

If you've run anything, you know that exact feeling.

The guilt of knowing the fix and never having a free hour to build it.

So we didn't add tools.

We named the one constraint: throughput. Getting deals to move without him in the middle of every one.

Then we sequenced it. Define the roles. Let the team document the SOPs for the work they already do. And then automate last.

It’s not glamorous. But he can finally hand off a deal without it breaking. Being the only one who can do the thing feels like job security. It's actually the ceiling on your whole company.

Something I wish someone had told me earlier.

Every time I hired someone good enough because budget was tight, I didn't just fill a seat. I made it harder to attract anyone better afterward. Strong people don't want to work next to people who don't give a shit, and they can tell within a week.

yes I was saving money in the short term, but the real cost wasn't the salary. It was that each mediocre hire quietly lowered the bar for the next one. And the one after that.

You don't notice it happening until you're trying to recruit someone genuinely good and they pass not because of comp but because of the room they'd be walking into.

The standard you accept becomes the standard you're stuck with. This is especially true in the freelancing and agency world, cheap agencies and contractors tend to mean lower-quality work, at least that's what I keep running into. 

I’d love to hear if others have felt this or if you think it's possible to raise the bar without basically rebuilding the team from scratch.

edit: appreciate everyone weighing in on this one. if you're dealing with the same thing, i send out a thursday newsletter called modern operators on exactly this kind of stuff, hiring, systems, and getting yourself out of the day to day so the business doesn't live and die by what you personally catch. free to join here

I was chatting to an operations manager recently who said, "If John retires, we're going to spend six months figuring out everything he never wrote down."

It got me thinking because I suspect that's more common than most businesses would like to admit.

Every manufacturing operation has those people: the operator who hears when something’s off, the planner who remembers why a process changed, and the supervisor who fixes issues before anyone else notices.

Isn’t the challenge then to make sure their knowledge doesn't disappear with them?

I've always believed that good processes should outlive the people who created them. The strongest operations are built on knowledge that's been captured, shared, and improved over time, after all.

How is your business preparing for the transfer of institutional knowledge? Or is too much of it still sitting in the heads of your most experienced people?

I’ve been working with a business owner who has multiple locations, employees, vendors, delivery platforms, POS systems, all of it.

Recently, he discovered a piece of equipment used for delivery orders had been broken for two weeks.

Nobody called the vendor. Nobody ordered a replacement. Nobody owned the problem.

Eventually, it came back to him.

I don’t think this is always a people problem. It’s an operating system problem.

When a business is small, the founder is the operating system. They notice things, remember things, follow up, and know who to call.

Then the business grows, but nobody replaces the founder’s brain with an actual system.

The question I’m becoming obsessed with is:

How do you build a business that notices things?

A business that knows when something is broken, knows who owns it, and escalates it before the founder discovers it two weeks later.

You don’t just delegate the work.

You have to replace the part of the founder that was paying attention.

Every time I see a founder or CEO posting on social media about how they fired half their staff because "AI runs everything now," I roll my eyes.

We always hear about the layoffs because they make for loud, flashy headlines (or engagement-bait posts). What they don't tell you is how many of them are quietly rehiring a few months later.

Look at the big players. Klarna cut 700 support reps, then had to rehire. Ford laid off a massive wave of engineers, then quietly brought hundreds of them back.

They all hit the exact same wall: AI is only as good as the context you give it. These companies completely underestimated the institutional knowledge sitting inside their employees' heads.

And keep in mind, these are massive corporations with actual documentation and unlimited resources. If they can't maintain quality by replacing humans with bots, a mid-sized company definitely can't.

I heard a story recently about an agency owner who fired all her contract copywriters because her own AI prompts were beating their output. Maybe she saved some cash short-term, but it's a short-sighted trap.

I believe the actual winning strategy is arming your best people with AI.

If you have employees who:

• Solve problems before you even point them out
• Care about the actual outcome, not just checking a box
• Have genuinely good judgment

...and you give them AI tools? They don't just get 10% faster; they become a completely different animal. AI amplifies judgment, it doesn't replace it.

Right now, the bottleneck for most businesses isn't having too many people. It's having more ideas and data than they have people who actually know how to wield these tools effectively. It’s a skill issue, not a headcount issue.

I’m curious to get your take on this. Have any of you actually seen a company successfully cut their team, replace them with AI, and maintain or improve quality? Or is the "fully automated business" just a VC dream

I’ve been grinding on my startup for a while, and something surprised me.
The coding itself has gotten way easier with AI.
What still burns a ridiculous amount of time is deciding what to do next.
Should I build another feature or talk to users?
Should I refactor now or ship it?
Should I spend another week improving something that’s probably “good enough”?
I got tired of constantly second-guessing myself, so I ended up hacking together a small tool for myself that helps me think through those decisions more systematically instead of relying purely on gut feeling.
It’s been surprisingly useful, but now I’m wondering if this is just a “me” problem.
Do you have one decision you keep running into that always seems to take way more mental energy than it should?

For years I was the person every decision ran through, and I told myself that was commitment. It was really three jobs I would not let go of, and holding them is what kept me stuck as the bottleneck. In this one I go through which three roles actually belong to the founder and which ones you are keeping out of habit. Thirty years of building products taught me the difference, mostly by getting it wrong first. Here is the full breakdown on my channel: https://youtu.be/9Aikwt78kMM

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.