The tax you can't see on a timesheet
Before every coaching call with a client, I do the same thing. I check with my bookkeeping team. Where are the books at? What's still open? Any issues I should know about before I sit down?
It takes five minutes. Sometimes ten. It feels like preparation — like due diligence before a client meeting. And in a sense it is.
But here's the thing I didn't see for years: that conversation isn't the work. It's the cost of getting current on context that already exists somewhere in my practice — in the bookkeeper's head, in their workpapers, in a Slack message from Tuesday. I'm just paying the price to move it into mine.
That's a coordination tax. And every CAS practice pays it dozens of times a day.
Every handoff is a coordination event
Every handoff in your CAS practice workflow is a coordination event. Bookkeeper briefs the accountant on where the file stands. Accountant briefs the partner before a client meeting. Partner checks with the tax specialist on a question that came up last week. Someone writes up notes so the next person can pick up a task they've never touched. Someone else re-reads an email thread to reconstruct context they had on Friday and lost over the weekend.
None of this shows up on a timesheet as overhead. It shows up as "client work" or "team communication" or "meeting prep." In a 5-person firm, it doesn't even look like coordination — it looks like teamwork. Good management. Staying on top of things.
But it's a tax. And it compounds.
Why CAS practices pay more coordination overhead than almost anyone
Here's what makes CAS different from a tech company with a coordination problem. A product team coordinates around one product. Your team coordinates around 30, 50, maybe 100 clients — each with different status, different open items, different history, different quirks. The context-switching isn't just between people. It's between people and clients, constantly.
Every "where are we with the Smith file?" is a tax payment. Multiply that by your client count and your team size, and the invisible tax becomes the single largest non-billable cost in your practice.
I'd estimate — conservatively — that my team spends 10 to 15 hours per week on coordination events. Not doing the work. Moving context around so someone else can do the work. That's a quarter of our productive capacity, gone — not to client service, but to the friction of being a team that serves multiple clients.
The context already exists — it's just trapped
The frustrating part is that the information isn't missing. My bookkeeper knows where the books stand. The accountant knows the client mentioned a new equipment purchase. I remember the client's risk tolerance from the last advisory meeting. The tax specialist has notes on a filing question from two weeks ago.
All of that context exists in the practice. It's just distributed — across heads, email threads, Slack messages, workpaper notes, and half-remembered conversations. The coordination tax is the cost of reassembling it every time someone else needs it. We're not creating information. We're just moving it from person to person, over and over, because there's no other way to access it.
Or there wasn't.
AI doesn't need to be briefed
This is where context engineering stops being a concept and becomes an operational advantage. If your practice builds structured, machine-readable context — client profiles with current status, standardized workpapers that AI can read, handoff notes in a format that persists — then the pre-meeting briefing changes completely.
Instead of calling my bookkeeper, I get a 30-second AI summary: here's where the books stand, here are the three open items, here's what changed since your last meeting with this client. The bookkeeper's time is freed. My time is freed. The context was always there — it just needed to be accessible without a human intermediary.
And unlike a verbal briefing, AI context doesn't degrade. It doesn't forget Tuesday's update by Thursday. It accumulates — every note, every resolved issue makes the next briefing more complete. The coordination tax doesn't just drop. It drops further every month as the context layer deepens.
The real cost of waiting
This isn't a technology problem. The AI to do this exists today. The barrier is the same one that holds back every rebuild — it requires building the structured context first. Writing the client profiles. Standardizing the handoff notes. Creating the machine-readable layer that AI can work with.
That's context engineering, and I know it feels like overhead when you're already buried. But consider what you're currently paying instead — every hour your team spends briefing each other is an hour they're not spending on client work, and every verbal handoff is a chance for context to get lost. You're already paying the tax. The question is whether you keep paying it, or invest in eliminating it.
Next time you catch yourself asking "where are we with this client?" — notice the tax. Then ask whether that answer could have been waiting for you before you needed to ask.
I built a structured version of this audit to walk you through your week and identify every coordination event — every briefing, every status check, every context handoff — then calculate what it's costing your practice in real dollars. The Coordination Tax Audit is available free below for subscribers. Run it once. Share it with your team. Let the number speak.