Build Your Week Around Your Energy, Not Your To-Do List

An EA I talked to, color codes her calendar every Sunday night. Every
block planned, every hour accounted for. She follows it like scripture.
And she still missed a deadline on a resolution case last spring,
because she had scheduled the financial statement review, the part of
the job that actually requires her full brain, for 4pm on a Thursday. By
4pm on a Thursday she has nothing left. She read the numbers, missed
what mattered, and did not catch it until the client called upset three
weeks later.

Her calendar was not the problem. Her calendar treated every hour
like it was interchangeable, and no hour in your day is interchangeable
with any other hour.

Here is the answer up front. Time management built around tasks alone
fails, because it assumes you have the same capacity for judgment at 9am
and at 4pm, and you do not. The fix is mapping when you actually have
the mental sharpness for real decisions, protecting those hours for
exactly that kind of work, and moving everything else, deliberately, to
the hours where your judgment is already spent anyway.

The Two-Week Audit
That Tells You the Truth

You cannot protect hours you have not identified. For two weeks,
track what you are doing in fifteen-minute blocks, and mark each one
twice. Once for what it was. Once for how you felt doing it: sharp, or
foggy.

Do this during a normal working stretch, not a slow week in July when
everything feels manageable. The pattern only shows up under real
load.

By day four, you will already see it. Most people find one
predictable stretch, often mid-morning, where their thinking is
genuinely clear, and one predictable stretch, often right after lunch or
late in the afternoon, where it is not. Read that again, because it is
the whole insight: the fog is predictable. It happens at roughly the
same time every day. Which means you can plan around it instead of being
surprised by it.

What Tax Pros Usually Find

The pattern is remarkably consistent across the practitioners I have
watched run this exercise.

Strategy work, the kind that decides an offer structure or an appeals
argument, only lands well in the sharp window. Attempted outside it, it
takes twice as long and the quality drops even when the person does not
notice the drop themselves.

Document chasing, scheduling, and returning routine calls score the
same regardless of … Continue reading

Claude Code for Tax Pros: Build the Tool, Not Just the Prompt

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

Boundaries, Scope Creep, and the Got-a-Minute Call

The call starts the same way every time. “Hey, got a minute? Quick question.” Forty minutes later you have given away a free consult, missed your next appointment, and the client has no idea any of it cost you anything at all. It never feels like a big deal in the moment. It is a big deal, repeated fifteen times a week, across an entire year.

The got-a-minute call is the most common form of scope creep in this profession, and it is rarely dishonest. Clients are not trying to take advantage of you (at least most of them aren’t). They genuinely do not know where the line is, because you have never drawn one. That is the part you can actually fix.

The Got-a-Minute Call Is Never Actually a Minute

A “quick question” is almost never quick, because the question that prompted the call is usually connected to something bigger, a notice, a life change, a decision the client is nervous about. You cannot answer it in sixty seconds without either giving a dangerously incomplete answer or doing real, unbilled work to give a real one. Most tax pros, being conscientious by nature, choose the second option every single time, and that choice is exactly what turns fifteen scattered interruptions into an unplanned second job every week. I know this first hand as I have done this many times myself.

Why You Keep Saying Yes

Here is what is actually happening. Saying no to a quick question feels like risking the relationship, so the instinct is to always say yes and absorb the cost yourself. I get it. I respect it. And I am telling you that the relationship was never actually at risk. What was at risk is your calendar, your family time, and the false idea that being endlessly available is the same thing as being a good practitioner. It is not. Being available on a predictable, scheduled basis is what actually serves a client well. Being interruptible at all hours mostly serves their anxiety, at your expense.

The Boundary Script That Does Not Damage the Relationship

You do not need to say no. You need a redirect that sounds warm and still protects your time. Something close to this works: “That is a real question, and I want to give you a real answer, not a rushed one. Let me grab you fifteen minutes on the calendar this week so I … Continue reading