Here's the most common AI adoption pattern in small business right now: the owner — or the one person who took to the tools — starts using AI for drafts, quotes, emails, and content. Personal output roughly triples. And the business ships at exactly the speed it did before.
Nate B Jones named this failure mode in a recent piece: one person on the team gets fast while review, approval, and handoff steps stay manual. The pipeline doesn't move. Just the person.
If that matches what you're seeing, the problem isn't that AI doesn't work. It's that AI accelerated a step that was never your constraint.
Why Individual Speed Doesn't Compound
Every workflow is a chain of steps where work gets done and steps where work waits. The waiting steps — approvals, reviews, handoffs, re-entry into another system — are where the time actually goes.
Watch what happens when AI lands on one creation step. A quote that took four hours to prepare now takes twenty minutes. Total cycle time drops from six hours to two hours and twenty minutes, because the two-hour approval wait is untouched. Fine. But now run three people's output through the same funnel and every fast draft queues up on the same approver's desk. You've made the waiting step more loaded, not less.
That's the pattern to internalize: speeding up a non-constraint step makes the constraint more visible, not less binding. The pipeline moves at the speed of its slowest handoff.
Find Your Three Slowest Handoffs
Draw the workflow for one revenue stream — say, inquiry → estimate → approval → job scheduled → done → invoice → paid. Boxes and arrows; paper is fine.
At each arrow (not each box), write the typical WAIT time in hours. Not the work time — the time the work sits before someone picks it up.
The three biggest numbers are your automation list for the next 30 days. Not the boxes. The arrows.
Common winners in a 10-person business, in rough order of impact:
- Estimate → approval. The quote is ready; it waits for the owner to review and send.
- Job done → invoice. The work finished Tuesday; the invoice goes out Friday.
- Invoice → payment follow-up. Nobody chases until the account is 30 days late.
- Lead → first response. The form fills; the reply waits until someone checks the inbox.
Two Causes, Two Fixes
Every slow handoff is one of two problems, and the fix differs:
1. The missing draft. The step is slow because a human has to produce something — an approval summary, a comparison, a follow-up email, a description of what was done. Fix: have AI generate the review-ready artifact automatically when the prior step completes. The approval request arrives with the job details, pricing, and risk notes already attached.
2. The missing decision. The artifact exists, but the human has to reconstruct the context before they can decide. Fix: pre-decision rules. Written thresholds — auto-approve quotes under a set amount for existing customers, refunds under a set amount — turn judgment calls into confirmations. If you can't write the rule down, that's a sign the decision genuinely needs you. Leave those in your queue and automate the rest.
Both fixes point at the same goal: the human gate becomes a yes/no, not a rewrite. A gate where the approver re-does the work is a second creation step. A gate where they confirm a complete draft is a decision.
Measure Wait, Not Work
If you only measure work time, you'll conclude AI failed. Track one number per handoff: hours elapsed between "previous step done" and "next step started." Time the arrows.
Two weeks of those numbers will redirect most of your AI effort — usually away from wherever you're currently spending it.
What Not to Do
Don't add more speed to the fast step. A faster draft machine in front of a manual approval gate doesn't clear the gate; it deepens the queue. If one person's AI output is piling up at someone else's desk, the automation target is the desk.
And don't automate the handoff you enjoy — automate the one with the biggest wait number. Enthusiasm picks the creation step. The math picks the handoff.
The Monday Version
- Pick one revenue stream. Draw it — boxes and arrows.
- Write wait time (in hours) at every arrow.
- Circle the three biggest numbers.
- For each, ask: missing draft or missing decision?
- Assign AI to the drafts. Write down the rules for the decisions.
One page, half an hour, and your next month of AI work pointed at the steps that were actually costing you the days.
Looking for templates? The Boring Automation Pack includes automation templates and approval-gate patterns built for small businesses — the pieces that turn a review step into a yes/no.
Top comments (0)