Last verified: 2026-09-07

Waste

Why is AI making my week busier, not shorter?

Picture a CPA in September, deep in extension season. A client emails to ask if she should change her next estimated tax payment. He has AI write the reply, reads the first two lines, and sends it. Nine minutes, for a job that used to take an hour.

The speed is real. But speed lets you cut more corners than you used to, and every corner you cut comes back later as work. The busy week you can’t explain is last month’s shortcuts, coming due.

The nine-minute email that cost an afternoon

Two weeks later, the client calls. The reply used last year’s income, and it didn’t know what she had told him in March: she sold her rental property.

He spends forty minutes on the phone, none of it billable. He goes back through her file and writes a corrected letter, then a third, because she wants her attorney copied. The fifty minutes he saved cost him an afternoon. And now she reads everything he sends twice.

He did nothing unusual. He did what everyone does in a full week. AI made the writing faster. It did not make the checking faster, and the checking is what got skipped.

Four shortcuts every practice has

The unchecked AI draft is the newest one. The older ones work the same way.

The process that lives in your head. You know what to check before an engagement letter goes out. Whoever covers for you knows most of it. The step they don’t know shows up when a client gets the wrong terms.

The client folder nobody else can follow. Files named “final,” “final2,” and “use this one,” spread across email and two drives. Finding the file takes twenty minutes, and finding it still doesn’t tell you whether it’s the version you approved.

The tool you bought and never set up. You bought it to fix a recurring problem, and the setup is half done. You pay the subscription and keep doing the job by hand.

The AI draft that goes out unread. This is the one that multiplies. A draft that took an hour now takes four minutes, so you write more of them and read each one less. The checking piles up for later.

Why you don’t notice the cost

Shortcuts that bill you later

A shortcut saves time today and sends a bill later. The bill never says what it’s for. It arrives as a bad afternoon, or a forty-minute call, and it looks like an ordinary busy day. So the bills keep coming, and you blame the week.

Some busy weeks have other causes: more clients, or a new tool you’re still learning. Repeated corrections and repeated searching are different. That is work you can prevent.

Find the one that repeats

Before you change anything, keep a simple log for one week. Every time you redo something, hunt for a file, explain a process again, or do by hand what a tool was bought for, write it down. What happened, and roughly how long it took.

You will be surprised where the hours went; everyone is. At the end of the week, look for the item that shows up most often. That is the one to fix. Just one.

While you’re at it, time an AI draft honestly. Count the checking and any correction after it went out, not just the writing. Four minutes is only fast if the total is small.

Fix it, then leave it alone for two weeks

If it’s AI drafts: decide what must be checked before anything goes out. Read the whole draft and check the facts it rests on against the file. For the CPA, that means: is the client’s information current, and did the draft account for the rental sale? If something is missing, fix that first. Nothing with your name on it goes out unread.

If it’s the process in your head: write it down during the next real job. One page. The steps, and the points where someone needs your judgment. Then have whoever covers for you try it. Their questions show you what’s missing.

If it’s the folders: pick one place for approved versions. Name files so the client, the document, and the date are obvious. Start with active work. Tell anyone who shares the files where the approved copy lives. Leave the old files where they are.

If it’s the tool: block an afternoon to finish the setup. Try it on one recurring task, then decide: keep it or cancel it. If you cancel, save any records you need first.

Run the change for two weeks and see whether the same problem comes back. Adjust it before you take on the next one. Change one thing at a time, and know how to put it back.

Where I come in

In software, where I spent thirty years, this has a name: technical debt. Every shortcut in the code sends a bill later, and the teams that last pay it down a little every week instead of all at once in a crisis. Your practice needs the one-page version of that habit. Finding the corner you cut most is where I start with every engagement. Then we build the small routine that checks it before it reaches a client.