Good, Better, Best: Package Pricing Instead of Hourly

Hourly billing punishes you for getting good at your job. The better and faster you get at reading a transcript, positioning a case, and closing a resolution, the fewer hours you need, and the less you get paid for the exact same result. Ten years of getting sharper at this work, and your own billing model is quietly cutting your income for it.

The fix is not to bill more hours. It is to stop selling hours entirely and start selling packages built around the outcome the client actually wants. (This applies to tax prep as well).

Why Hourly Billing Works Against You

An hourly rate ties your income to your inefficiency. A client who hires you specifically because you are experienced and fast is paying you less than a client who hires someone slower and greener, for the identical outcome (assuming you both charge the same rate per hour). That is backwards, and every tax pro who has ever felt strange sending an invoice for two hours of work that solved a real problem already knows it in their gut.

Packages fix this because they price the outcome, not the clock. The client is not buying your time. They are buying the levy released, the case resolved, the letters stopping and peace of mind (as well as sleeping better at night). Price against that, and your growing skill and speed become pure upside instead of a pay cut you give yourself every time you get better.

The Math That Proves It

Run the numbers on one real case type. A collections engagement that took you 20 hours a few years ago, billed at $250 an hour, put $5,000 on the invoice. (Example figures for illustration only. Individual results vary. No income or IRS outcome is guaranteed). You have since gotten better at the work. You read a transcript faster, you know the resolution path by the first meeting instead of the third, and the same case now takes you 8 hours. Same client, same result, same you, just sharper. At $250 an hour that invoice drops to $2,000. You got faster and your practice got poorer for it, to the tune of $3,000 on a single case.

Now run the same case through a flat package instead. Price the full representation tier at $4,500, in the middle of the Better range above. Eight hours of work at $4,500 comes to $562 an hour, more … Continue reading

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