An EA I know checks the same list every single morning before she
opens her inbox. Which resolution cases have an IRS response deadline
inside the next thirty days. She built that list by hand, in a
spreadsheet, and updates it herself, every day, because she got burned
once. A case sat quiet for six weeks, the deadline passed, and she spent
a Saturday writing a very uncomfortable letter to a very angry
client.
She does not need a better spreadsheet. She needs something that
checks the list for her and only bothers her when something is actually
wrong. That is the difference between chatting with AI and building a
tool with it, and almost nobody in this profession has made that jump
yet.
Here is the answer up front: Claude Code lets you describe a task in
plain English and get working software back, not just an answer to a
question. You are not learning to program. You are directing something
that already knows how, and the output is a tool that keeps running
after you close the laptop.
Most Tax Pros Are Stuck at “Ask It a Question”
If you use AI at all, you probably use it the way you’d use a very
well-read colleague. You ask something, it answers, you take the answer
and do the work yourself. That is genuinely useful. It is also the
ceiling of what a chat window can do.
A tool is different. A tool runs on its own schedule, checks
something specific, and only surfaces when a human needs to act. The
deadline monitor my EA friend eventually built does not answer
questions. It checks her case list every night at 7pm and sends her
exactly one message: which cases have a deadline inside thirty days, and
which of those have had no IRS contact logged in two weeks. Nothing
else. She reads three lines and knows if tonight is a work night.
That shift, from asking to building, is what Claude Code actually
does for a tax practice. You are not hiring a developer. You are telling
it what “done” looks like, and it writes the thing.
The Three-Question Test Before You Build Anything
Not every task deserves a tool. Before you spend an hour building
something, run it through three questions.
Does this happen every week or more. A one-time task is not worth
automating, no matter how annoying it is.
Does the … Continue reading
