I thought I’d finally hired help.
That was the feeling, early on. Type the brief, get the draft, move to the next thing. For about a week, it felt like I’d quietly added a person to the team without the overhead of actually doing so. No onboarding, payroll, or ramp-up period. Just output, on demand, whenever I needed it.
Then I noticed what my mornings had turned into. Re-pasting the brand voice guide into a new chat window. Re-explaining the client I’d already explained on Monday, again on Wednesday, again on Friday. Rewriting an output that sounded confident and said nothing close to what I actually needed it to say. The help I thought I’d hired turned out to need almost as much management as the work I was trying to hand off in the first place.
I wasn’t using the tool less than I expected. I was managing it more than I expected, and somewhere in there the math stopped working in my favor.
A 2026 workforce study puts a number on this feeling. Knowledge workers report that AI saves them roughly 11 hours a week. The same workers also report spending close to six and a half of those hours feeding the AI context, re-running prompts that missed the point, and cleaning up output they couldn’t ship as-is. The real weekly gain isn’t 11 hours. It’s closer to five. The researchers have a name for the gap: botsitting. Less a productivity tool, more a junior hire who needs constant supervision and never quite remembers what you told them yesterday.
If you’ve felt that gap and quietly assumed it was just you or simply the wrong tool, it’s worth slowing down to examine the real cause before you go shopping for a different platform. Many founders skip that question entirely and go straight to the upgrade.
That six-hour babysitting tax doesn’t land evenly across an organization. A team can absorb it. Someone owns the prompt library. Someone owns the style guide. The overhead gets distributed across more than one set of hands, and no single person feels the full weight of it.
A solo consultant or a boutique agency owner doesn’t have that luxury. Every re-explanation, correction, and re-upload (of a document the tool should already have) lands on the same person who was supposed to be getting hours back in the first place. There’s no second pair of hands to absorb the overflow. It just quietly accumulates in the part of the calendar that was supposed to be freed up.
To be fair to the tools, not every re-explanation is a waste. A genuinely new client, a new project with no precedent, a situation the AI has never encountered before is not botsitting. That’s onboarding, and it would take a new hire the same orientation. The pattern worth questioning is repetition. The same client. The same brand file. The same five minutes, lost again, to a tool that had already been told this once before, sometimes twice.
That repetition is where the real cost hides, and it’s worth naming precisely, because it rarely announces itself as a problem. It feels like normal friction. A small tax on an otherwise useful tool. Every manual touch that should have been a one-time setup instead of a weekly ritual is a Touch Tax, charged in minutes instead of dollars, which is part of why it never shows up anywhere that would prompt someone to fix it. It shows up in the eleven o’clock email you’re still answering by hand, and in a workflow you call automated that somehow still requires you, every single time, without exception. The tax doesn’t announce itself. It just keeps getting collected.
The instinct when a tool disappoints is to upgrade it. Try the newer model. Add a second platform that promises to handle what the first one missed. Surely the next version will finally understand the business the way you do.
The same research that surfaced the botsitting number also found the opposite of what most people expect when they go shopping for a fix: workers using multiple AI tools were over a third more likely to report frequent botsitting, not less. More tools didn’t reduce the babysitting…it multiplied it.
That tracks once you sit with it instead of taking the marketing at face value. Every new tool is another relationship that needs onboarding. Another place that needs the brand voice file, the client history, and the decision logic explained again from scratch, because none of these platforms talk to each other, and none of them inherit what the last one was taught. Add a second tool to fix what the first one couldn’t do, and the babysitting hasn’t gone down. It’s doubled because there are now two things to manage instead of one.
This is the part most AI-for-business content skips entirely, because a tool review is a much easier thing to write than this question is to answer honestly: what’s actually missing isn’t a smarter model. It’s something the tool has nowhere to reference, because it was never written down anywhere outside one person’s head to begin with. No model, however capable, can retrieve information that was never recorded.
Call it whatever feels accurate to you. Institutional knowledge. Decision logic. The specific, unglamorous judgment a founder has built over years of doing the work: knowing which client emails need a same-day response and which can wait, knowing which proposal language closes and which stalls, knowing the difference between a real fire and one that only feels like one. None of it is complicated. All of it is real. None of it written down anywhere a tool, a contractor, or a future hire could ever find it.
This is also why the well-known failure rate around AI adoption keeps surfacing again in coverage this year. The widely cited figure puts pilot failure above 90 percent, with the large majority of those failures traced not to the tool itself but to whether the organization was ready for it. A business running on memory, instinct, and “just ask me, I’ll tell you” doesn’t become AI-ready because a subscription was purchased. The tool needs something to work from. If the only place that information exists is inside one person’s head, the tool isn’t reasoning. It’s guessing, dressed up convincingly enough that the guess is easy to mistake for understanding.
None of this means the documentation has to happen all at once, or that it costs nothing to build. Writing down how you actually make decisions takes real time, and at an earlier stage, with lower volume and fewer repeat scenarios, it can be its own kind of premature work — systematizing something before there’s enough repetition to justify the effort. The point here isn’t that every founder needs a fully built knowledge base before touching another AI tool. The point is narrower and more useful than that: before reaching for the next platform, it’s worth asking what the current one is actually missing, and whether that gap is a tooling problem or a documentation one. Far more often than the tool reviews would suggest, it’s the second.
The instinct to reach for a better tool isn’t wrong, exactly. It’s just early. A tool can only remove your hands from the work once it’s been given what you currently carry in your head, and that has to happen before the tool gets blamed for not already knowing it. Skip that step and the upgrade just buys a more articulate, more expensive version of the same babysitting you were already doing. Asking why isn’t AI saving me time after the third platform switch is asking the same question a fourth time and expecting a different category of answer.
The businesses that are closing this gap aren’t the ones with the longest AI subscription list. They’re the ones who stopped long enough to ask what their AI had to work with before adding the next thing to the stack. That’s a smaller, less exciting question than “which tool should I try next?” It’s also the one that determines whether the next 11 hours promised on the label turn into five, or finally show up in full.
It rarely requires the dramatic overhaul it sounds like it should. The tool was never going to be the thing that changed the math. The decision to stop re-teaching it every Monday was.
If you’re not sure where that gap is currently costing you in your own business, the Profit Leak Scorecard is built to surface exactly that. Eight minutes, no guesswork, no new tool required to find out.
July 15, 2026
Be the first to comment