Your AI Makes More Work Than Your Business Can Absorb

Share
Cover banner: Your AI Makes More Work Than Your Business Can Absorb

Every guide to using AI in a small business ends at the same finish line: produce more, automate more, reclaim hours. You follow the advice and plug in the tools. Drafts, leads and replies start pouring out. Somehow your week gets heavier. For a small business, producing more with AI is the wrong first goal. What limits you is a human step further down the line, which in a small shop is you, and extra output just piles up in front of it. The top-ranking guides argue the opposite. They say automating widely and freeing up hours is the whole point of adopting AI.

Find the one step all your work has to pass through, feed it only as much as it can clear, and widen it before you widen anything else.

Your week never jammed at the production step

Follow one piece of work through a five-person business and count the hands it passes through. A new-patient inquiry reaches a physio clinic. Someone drafts a reply. The owner checks it because it mentions pricing. The patient books, and a clinician treats them. AI can draft that reply in seconds. It can't make the owner read faster, and it can't add an hour to the clinician's diary.

Picture your own business with AI switched on at the top of that chain. The front desk now produces follow-up emails for every lapsed patient, recall texts, several versions of the new website copy, a fresh batch of social posts and a weekly newsletter draft. Every one of them still goes to the owner's inbox for a yes or no. This Monday's pile is taller than last Monday's. By Thursday the owner is approving things half-read just to clear the queue. That's exactly when a wrong price or a clumsy clinical claim goes out under the clinic's name.

That cost never makes it into the pitch. Extra output at the top doesn't disappear. It waits at the one step that didn't get faster, and while it waits, speed and judgment both decay. Speed drops, because the queue gets longer. Judgment drops too, because a tired approver approves worse.

Ethan Mollick, the Wharton professor who studies how AI changes work, summed up the mechanism in a post this July.

“A real issue with AI adoption is that organizations are built around a narrow expected range of human productivity in a role. Too little output is a problem, yes, but way too much can sometimes be as bad since approvals, staffing models & coordination systems cannot absorb it.”
Ethan Mollick, Wharton School, in a post on X, July 2026.

Read that as an owner. Your business is built around what one person can do in a role: the receptionist, the account manager, you. Your approval habits, your staffing and your Friday check-in all assume that range. When AI output blows past it, those systems don't stretch. They choke.

The real bottleneck is a human decision or approval step with a fixed capacity, and AI does not expand it. You can't fix that by producing faster. You fix it by feeding that step only what it can clear, and by making the step itself wider.

I work inside this problem every day. I run this site as a one-person, AI-assisted content operation that publishes daily, and I built the whole pipeline around one fact: I'm the only reviewer. Every stat and quote gets checked against a real source before anything goes live, and I'm the one who checks. The drafting side is sized to what I can verify. The editor and verification gates in my command center exist so drafts can't reach me faster than I can check them properly. The PR outreach desk I built drafts pitches and never sends one, because sending is my job, done at my pace. The drafting tools could produce far more than that. The business wouldn't be any better for it.

Larger organizations are hitting the same wall at scale. Software teams adopted AI more widely than almost any other trade, and the payoff still looks small.

About 10%
Adoption of AI coding tools passed 90%, yet the organizational productivity gain came to only around 10%. Almost everyone uses the tools, and the lift is small.
Source: 2026 developer-tools research covered by DX.

For you, that gap separates paying for AI from profiting from it. Everyone uses it, the lift is small, and the reason is the same one hitting your clinic or your agency: the work still has to pass through review steps built for human speed.

GoDaddy's guide to AI tools for small businesses, published August 28, 2026, promises AI can "free up several hours every week." It lays out a tidy sequence: pick a pain point, adopt a tool, measure, scale. Jotform and RingCentral publish guides built on the same idea of producing more and automating more. None of that is wrong on its own terms. It just aims at the wrong step.

"Pick a pain point" sounds like bottleneck thinking. In practice, owners pick the pain they feel most sharply, which is the blank page. When writing feels slow, they automate writing. When replying feels slow, they automate replies. What actually hurts is that everything written or replied to still waits on one person, and no tool on the market sells a wider version of that person.

There's a commercial reason the advice leans this way. A tool that fills a screen with drafts in under a minute makes a great demo. Widening the owner's approval step is a people decision: who gets trusted with what, under which rules. Nobody can sell you that as a subscription. Nobody advertises it either.

"Freed-up hours" has a measurement problem too. Hours saved on drafting show up nowhere if the drafts then wait in a queue. The time only moved. Before you count any of it, check whether your AI time savings are real or just moved to someone else's desk, which in a small business is your own.

This is the capacity side of a problem I've already written about from the quality side. AI output that looks polished but shifts the real work onto whoever receives it is one failure. Today's failure can happen even when every draft is good: there are simply more of them than the person signing off can handle.

Some of your work is limited by production. If nobody has to approve it and the only delay was the typing, AI helps directly. Internal meeting notes and transcripts fit here. I built a live meeting transcriber for my own calls and use it daily. The test is simple. If a piece of work has to pass a human decision before it reaches a customer, production speed isn't your limit, and speeding it up just moves the jam.

QuestionFlooding the bottleneckFeeding the bottleneck
The goalProduce as much as AI can generateProduce what the approval step can clear this week
Where the pile sitsIn the owner's inbox, growingEarlier in the process, where holding drafts is free
Decision qualityDrops as the approver skims to catch upHolds, because the approver sees a normal load
What you expand firstProductionThe human step: delegate approvals, add a reviewer
What you measureOutputs created, hours "saved"Time from drafted to approved, and what reaches customers

A comparison framework for owners, not measured data.

Mollick and Lütke describe the same jam from opposite ends

Mollick's second point explains why the jam isn't anyone's fault. He wrote this in another July 2026 post on X:

"When workers gain productivity from AI, the rest of the bottlenecks in the system can eat up any gain. This is just a legacy consequence of human intelligence being the only kind we ever had until now, and so our current organizations are built around its limits and advantages."
Ethan Mollick, Wharton School, on X, July 2026.

Your business wasn't designed badly. It was designed for people, which was the only option anyone had. Every handoff, sign-off and meeting in it assumes work arrives at human speed. Plug a machine into one step and every other step is still running at the old pace.

Tobi Lütke, Shopify's CEO, came at it from the other direction. On The Knowledge Project podcast, released September 15, 2026, and covered by Matt G. Southern in Search Engine Journal on September 21, he argued that the old problem, people not producing enough, has flipped.

“The failure case now of lazy work is not lack of output.”
Tobi Lütke, CEO of Shopify, on The Knowledge Project podcast (released September 15, 2026), as reported by Matt G. Southern in Search Engine Journal, September 21, 2026.

Lütke's point is that the failure has flipped: lazy work now shows up as too much output, not too little. He also made the point that matters most for a small business. A machine can't take responsibility for work. A person does. By his own estimate in that interview, an internal Shopify AI agent called River generates up to roughly half of the company's pull requests. Pull requests are the proposed code changes engineers review before release. Even at that scale, a human still answers for what goes live.

Translate that to a ten-person agency. AI can write the client report, the ad copy and the strategy memo. The name on the email to the client is still yours. Responsibility doesn't spread out as output grows. It falls on fewer people relative to the volume of work. In a small shop, those few people are you and maybe one senior hire.

I've lived the demand-side version of this. I once booked a London ADHD clinic solid for three straight months. At that point the clinic's limit wasn't inquiries. It was specialist time, the one resource every patient had to pass through. The fix that worked was widening that step: they hired more specialists and outsourced the overflow. More marketing on top of a full diary would only have made the wait longer. AI output behaves the same way. Past the point where the human step is full, adding more just grows the queue.

Size AI to the step everyone waits on, then widen that step

The fix is organizational, not technical. You can start it on Monday. It's also the difference between owning a stack of tools and building an AI system that fits how your business actually runs. A tool speeds up one step. A system decides how much work reaches the next one.

Feed the bottleneck, then widen it
1Name the step. Ask: what has to wait for one specific person before it can reach a customer? Write that person's name down.
2Count what that step clears in a normal week. Tally approvals by hand for one week, with no AI surge in the mix.
3Cap AI inflow at that rate. Batch drafts into one daily slot and hold the rest back until there's room for them.
4Widen the step. Hand low-risk approvals to a trusted person with written rules, or add a second reviewer.
5Raise production only after the queue stays short, then run the count again.
Run it in this order. Widening production before step 4 just refills the queue.

Step one takes ten minutes. In most shops under ten people, the answer is the owner. Sometimes it's a single senior clinician, the one account lead every client asks for by name, or the bookkeeper who signs off every quote. Whoever it is, their hours are fixed. Everything else in your business is really a question of how much work reaches them.

Step two stops you from guessing. Write a tally on a sticky note: every time you approve, edit or send back something a team member or a tool produced, add a mark. At the end of the week you'll know what your approval step can actually handle. That number is your ceiling, and it tells you how much AI output your business can absorb.

Step three feels backward, because you're deliberately turning a fast tool down. Drafts that haven't reached you yet don't cost you a minute. They don't nag, age or go stale in your inbox. Keep them there, feed the approval step one batch at a time, and every item gets a real read.

Step four is where the real gain is. In the physio clinic, the practice manager could approve recall texts and routine follow-ups against a one-page rulebook: no pricing changes, no clinical claims, no new offers. Anything that breaks a rule comes back to the owner. The owner's queue shrinks to the decisions that need the owner's judgment. An agency can do the same by naming a second reviewer for social posts and routine client updates, and keeping strategy and pricing with the principal.

If an agency runs your marketing, ask them this before they add more AI output: "Who approves what you produce, and how many items can that person clear in a week?" If they can't answer, don't pay for the extra volume they're pitching. It ends up in your inbox or goes out unchecked.

Track the queue at your bottleneck, not the pile AI produced

The number AI tools love to report is how much they made: drafts generated, posts written, emails queued. That number is the vanity metric of this whole trend. It measures the top of the process, where work was never stuck. A business can double that number and book nobody new.

Measure at the bottleneck. Check it every week for the first month after any change, then every month once the queue stays steady. The first month tells you whether the cap and the delegation are working. After that you're watching for creep, the slow drift back toward flooding as someone switches on another tool.

What to check at your bottleneck
✓Queue age. How long the oldest item has waited for sign-off.
✓Turnaround: the time from "draft ready" to "approved and sent."
✓Send-back rate: how often the approver rejects or rewrites what arrives.
✓Approver hours: the time the owner spends reviewing each week, going up or down.
✓Outcomes after approval: bookings, replies, signed quotes, revenue.
Skip the count of AI outputs. It measures the step that was never stuck.

Two of these tell you the most. A growing queue age means you're flooding, however good each draft is. A rising send-back rate means the approver is rejecting what reaches them, which points back to the quality problem, not the capacity one. Watch the pair together. If turnaround falls while the send-back rate holds steady, you've fed the bottleneck properly. If turnaround falls because the send-back rate dropped to zero, you might just be rubber-stamping.

Watch owner hours too. When delegation works, the owner spends less time reviewing and the approvals left are harder, the ones that need judgment. If the owner's review hours climb every month after AI arrives, the tools are taking time from the one person you can least spare, whatever the dashboard says.

The last check is the only one your bank balance cares about. Bookings, signed quotes and paid invoices come after the bottleneck. If AI output climbs and those stay flat, the extra work never made it through, or it went through half-checked. Either way, it didn't earn you anything.

Frequently Asked Questions

How do I know if AI is creating a bottleneck in my business?

Look at what's waiting for you. If drafts, replies or quotes sit unapproved longer than they did before you added AI, the tool sped up the wrong step. Another sign is that you approve things faster but read them less carefully. Count the items waiting for your sign-off every Monday for a month. If the pile keeps growing, you have your answer.

Should I stop using AI if my team can't keep up with the output?

No. Turn the volume down to what your approval step clears in a normal week, and hold the rest back where unused drafts don't cost you anything. Then widen that step by delegating approvals or adding a reviewer. Once the queue stays short, raise production again. The tool is fine; the flow rate is the problem.

Who should approve AI work if I'm the owner and I'm already too busy?

Someone you already trust with customers, working from written rules you set. Start with low-risk work like routine follow-ups and social posts, and keep anything involving pricing, clinical or legal claims, or new offers for yourself. Give them a short checklist of what must be true before something goes out. Spot-check a sample each week until you trust the rules.

Every competitor you have can rent the same firehose tomorrow. The approval step behind it is the one part they can't copy, and it's the part almost nobody is widening. If you want a second pair of eyes on where your own bottleneck sits, book a call with me and we'll find it together. If AI handed you more finished work tomorrow than you could read, who in your business would have to say yes to all of it?

Free, No Commitment

Find out exactly where your AI visibility is leaking. In 30 minutes.

No pitch. No fluff. A straight diagnostic on your specific situation and the single highest-leverage fix to make right now.