The 6-Hour Tax: Why AI Costs You More Than It Saves

Hal, can I confess something on the air? My favorite kind of sentence. So I bought the AI subscription to get my life back, and last Saturday, I worked. You love Saturdays.

I love Saturdays, and that's the whole point. So let me get this straight. The robot gave your time back. And then quietly booked my weekend.

That's not an assistant. That's a roommate who eats your food and puts an empty box back in the cabinet. Right. And here's the part that really got me, though.

Somebody finally put a number on that. Okay. AI hands the average operator about 11 hours a week. 11 hours.

That's a full vacation day every single week. But then it takes about six of them right back. Takes them back like a free trial that started charging your card. Worse, because nobody put that on the box.

11 hours, asterisk. Six hours, asterisk. And today, we name it, we prove it, and we figure out how to stop paying it. I'm Kim.

I'm Hal. And this is Small Business Big AI. The podcast for operators building real businesses in an AI-shaped economy. Where we don't chase the shiny object.

We build the thing underneath it. So I want to start in a place where this actually happens. Which is not a keynote. No, not a keynote, not on stage, and not even in a headline.

On a Tuesday morning. Exactly, on a Tuesday. So your coffee's already cold because something blew up at 8.40 a.

m. You open the thing that the AI drafted for you, maybe the proposal, the email, the summary, and, you know, it's not bad. It's 80% there. Yeah, and that 80% is the trap because now you're fixing the 20.

You're retyping the prompt, feeding it the context it should have already had. The context you gave it last Tuesday. Yeah, and 20 minutes later, you've got something good, and this little voice goes, you know, I could have really written that myself. And you're not even sure you saved time.

You just moved where the time went. Yeah, you just moved it. And Hal, here's the cruelest part. You can't even complain.

Right, because on paper, you have the help now. Yeah, so you swallow it and the resentment just sits there, quiet, under your to-do list. It came back wearing purple jeans and a productivity badge. Yeah, it came back wearing those purple jeans and a productivity badge, yes.

And for a year, operators have described that exact feeling to me, almost word for word. I'm busier than I was before I got the help. Which sounds insane out loud. You've added a thing that does the work.

How are you more tired? And that right there, Hal, that's the right question, right? How are you busier with help than you were without it? I mean, I want to say somebody finally measured it.

So the Glean Work AI Index, which is out this month, June 2026. Okay, give me the numbers. Okay, well, 11 hours a week given back and six and a half hours a week spent supervising the thing, like checking it, correcting it, reprompting, cleaning up after it. Six and a half hours out of the 11.

So I'm netting four? Yeah, four and a half on a good week. and the six even has a name for it now. I'm afraid to ask.

Yeah, it's called bot-sitting. Bot-sitting. I hate how perfect that is. I know, right?

That's the six-hour tax. And here's the line that really matters. The heaviest bot-sitters are four more likely to be quietly job hunting. Okay, that tracks because the person doing all the checking is never the careless one.

No, never. The tax falls on your conscientious person, the one who refuses to send something sloppy under your name. You know, the one who still cares. So your best people are absorbing the cost.

Just silently. they've become the quality control department for every tool everyone else is excited about. And one day, they're tired enough to update the resume. And that right there, that's the real bill.

Not the six hours. The person updating their resume. Okay, so let me be the operator listening to this with one eyebrow up. Please raise that eyebrow.

Because I can feel the consultant answer coming. You need to redesign your workflows. I know. And that phrase makes me tired.

You are talking to a four-person shop owner. The owner is answering the phones approving quotes chasing receivables and doing payroll at the kitchen table She does not have a transformation office She has 47 tabs open and a customer on hold And that is the real objection. Good, because if the answer to AI made me busier is go re-architect your business, then we have just given her another thing to feel behind on. Agreed.

So tell me why this is not that. Well, because I do not want her to re-architect the business. Okay. I want her to stop paying rent on the same six hours every week.

That is different. Very different. So let's name the thing plainly before we fight about the fix. So the 11 hours, Hal, now they are real.

The six and a half are also real. The gap between them, that's a tax. And you're paying it every single week. Whether or not it shows up on a line item, that's what makes it sneaky.

It's corrosive and invisible at the same time. And here's the diagnosis that nobody wants. Most operators are using AI like an employee that they've never onboarded. Oof.

You hand it work. It gives you a draft. You fix the draft. And then next week, you fix the same thing again.

Because nothing stuck. Right. Nothing stuck. Now, think about a real hire.

So, month one, you check everything. Okay. Then month three, they really know your standards. Then month six, they're handling it because every correction became training.

The supervision goes down because the human goes up. Exactly. But now let's look at the AI. In most businesses, it starts at month one every single morning.

The corrections never compound. So you're onboarding the same intern forever. That's the intern who never learns. And that's the line right there.

The intern who never learns. You didn't automate the work. You hired an intern who never learns. Say that one slower because it stings.

You didn't automate the work. You hired an intern who never learns. And the insult is the repetition. Same fix every week.

And when the same correction repeats, you start blaming the tool. But really, Hal, the tool isn't always the problem. The problem is the workflow has nowhere for learning to live. So the business has no memory.

Oh, the business, it has memory. It's just trapped in your head or in my head or in the office manager's head. Maybe it's trapped in a Slack thread from March or in a spreadsheet that nobody wants to open. In the inbox of one person who knows how everything is supposed to sound.

Yeah, that sacred inbox. Every business has one. And usually it's belonging to the person who can never afford to take a vacation. And then we act shocked when AI lacks context.

Right. It can't use what the business never wrote down. So when we say the AI is missing context, sometimes what we really mean is the company never turned its own judgment into something you could hand to someone. That's not a tool problem.

No, that's not a tool problem. That is architecture. There's that word again. Right.

There it is. Architecture. quick breath here and an honest one if that six-hour tax just described your week you're exactly who we build this show for so follow small business big ai on your favorite podcast app no hype no shiny object chase just the structure underneath the noise every week okay back at it All right. So what's the cause everyone reaches for first?

Oh, the AI just isn't good enough yet. Wait for the next model. And that's the expensive mistake. So you sit on your hands waiting for a tool to fix a problem that the tool didn't create.

Okay. So how is what you're saying different than any other consultant with the binder? Because re-architecting isn't a project. It's not a transformation initiative.

It's not six months, a binder, and an offsite. It's one decision made one time about one workflow. One workflow. Right, one.

So instead of asking, how can AI help me with this thing I already do, which is the exact question that creates the tax. You ask something else. Right, you ask instead, if AI had existed the day I built this, how would I have shaped it in the first place? Paint it for me because designed around AI still sounds abstract.

Right So let look at it this way Say a client quote Now the old way customer send a request Someone reads it digs through old emails asks three clarifying questions copies it into the AI The AI drafts it. Someone checks it, adjusts the pricing, sends it. Then someone has to remember to follow up. I'm exhausted already.

Right. So now the AI native version is the request hits a structured intake. The system grabs the facts that matter, checks the customer history, drafts the quote against your standards, flags the exceptions, won't send anything over a threshold without you, and schedules the follow-up on its own. And the human's still there.

Right. The human's even more there, Hal, but not copying and pasting, making the judgment call. So the AI takes the low judgment labor. Right.

So that the human gets the high judgment moments. That's the whole game. But if you don't design it, AI just manufactures more low judgment checking. And the human becomes the guardrail.

And that's exhausting because a person was never supposed to be the system's only guardrail. The guardrails belong in the workflow. Parameters. Parameters.

Define that in plain English. Okay, it's something we've talked about a lot here on the podcast. A parameter is a decision that you make before the work starts so that you do not have to remake it every time the work shows up. So the AI doesn't need freedom.

It needs lanes. Hey, you know, that's quite beautifully said, honey. I have my moments. Yeah, you do.

And here's where the small operator actually has an advantage. Actually beats the giant. How? They are closer to the work.

They've got the process. Yeah, and you've got proximity. You know where the weird exceptions hide. You know which customer needs a gentler tone.

You know the phrases that can never go out under your name. The big company has process. The small business has proximity. Yes, and proximity, that becomes power the second you turn it into structure.

I mean, if you leave it trapped in your body, then it's just pressure, but built into the workflow, and it's an asset. Which means a lot of six-hour tax is really the owner being the operating system. The owner as the operating system. That's a t-shirt.

Right. And how it does not scale. Might look good on a t-shirt, but it doesn't scale. Not if you want to grow.

Not if you want your people to take a real vacation. Not if you want AI to help instead of hover. Now, here's the whole thing in one sentence. Architecture isn't a department.

It's a decision. Say it once more. I think that's the episode. Right.

So architecture isn't a department that you don't have. It's a decision you already get to make. The four-person shop and the 400-person company make the same move. They pick one workflow, design it as if AI was already part of it.

The scale is different. The decision is identical. All right, bring it home. I got cold coffee, the 80% draft, and six-hour tax.

What do I do this week? Well, three moves and you start with exactly one. Of course I do. So move one is you find the memory.

That means you ask the uncomfortable question. Where does this business actually keep what it knows? And the honest answer is going to sting. A little.

because the answer is usually, well, in my head, in her inbox, in old texts, and in the way we just know. The way we just know is the most expensive line in small business. Very expensive because if the AI can't reach the standard, it can't apply the standard. So you, the human, stay the bridge forever.

Move two. Okay, move two is you pick the workflow marked by the sentence, I could have just done it myself. There it is again. Hey, yeah, that sentence, it is a flare.

It's marking the exact spot where you bolted AI on instead of redesigning around it. So, So don't pick the impressive one. Right. Don't pick the impressive one.

Pick the one that keeps irritating you. I mean, proposals, customer replies, meeting summaries, quote follow-ups, the thing that you keep redoing. And then ask the better question. Yes.

If AI had existed when I built this, how would this workflow be shaped? Not where can I add AI. Yeah, never start there. That question creates bolt I want you to start with the shape of the work Move three So move three is build a context asset Explain that like I'm tired and slightly cynical.

Oh, yeah, okay. So a living document that tells the AI how your business thinks. Not a prompt library. No, not just prompts, because prompts are instructions for one task.

Context is memory for the business. What goes in it? Well, what goes in it is your tone, your pricing rules, your approval thresholds, your customer promises, and things like what you never say, what you always check, examples of great work, even examples of bad work, and really kind of the weird edge cases. So the tool stops guessing your business.

Exactly. The tool stops guessing. And this is where operators need to understand something. The AI tool is not your advantage.

Your context is. Because everyone can buy the same tool. Right. They can buy the same tool this afternoon.

Same subscription, same model, same shiny interface. But what they can't buy is your standards, your customer history, your way of making the trade-off, and your lived judgment. Unless you never capture it. And then it's not an asset.

It's just pressure on a very few exhausted people. So here's the real stakes, kind of without the scary music. Everybody is going to have the AI. That race, hell, is already over.

The winners in this next season won't be the ones with the most AI. They'll be the ones with the best architecture around it. Stop being the memory. Build the memory.

And that right there is how you stop renting your hours back from a tool and start building a real technology-enabled superpower. That's right. So here's your one assignment this week. Now, don't redesign your business.

Just name your six-hour tax out loud. Where are you babysitting instead of building? or like we said, bot sitting. And then I want you to pick the one workflow that you'll redesign as if AI had already been there.

One workflow. That's the whole homework. Right, the whole homework, just one. And I genuinely, listen to me, I genuinely want to know which one you pick.

So tell us, because somebody else out there who's listening is starting at the exact same workflow, wondering where to start. Here's the question I sit with. If you stepped away for two weeks, would your business still know how to sound like you? Or does it all live in one sacred inbox?

And that question, That is the difference between a job and an asset. And if this conversation names something you've been feeling, share it with one operator who's got the tools, got the pressure, and still can't figure it out why the week still feels heavier. And that's how a show becomes a movement. One operator handing it to the next.

And one personal note before we go, because I don't just talk about this. I am actually living it. So on August the 3rd, I am opening the Lewis Howard Insurance Group. It is built AI native from day one.

Practicing what you preach. Every word of it. And if you want to protect what you've built, come to our 2026 Property Protection Briefing. It's all at AskLewisHoward.

com. That's A-S-K-LewisHoward.com. And that's it for today's episode of Small Business Big AI.

If this is your first time here, welcome. Be sure to follow Small Business Big AI so you're notified of the next episode. We're not chasing shiny objects. We're building the structure underneath it.

So until next time, keep embracing change, keep innovating, and remember, the future of your business is bigger than you think. And the steps you take today will shape the legacy you build tomorrow. Keep building your technology-enabled superpower. Now, I'm Kim.

I'm Hal. And this has been Small Business Big AI. We'll see you in the next episode. Thank you.

Thank you.