Last week I was on a Zoom call with a client, and we both had note-taking agents in the meeting — quietly transcribing everything. (An agent here just means AI that does a task on its own instead of waiting to be asked — in this case, listening and writing up the call.) We made the same joke a lot of you have probably made by now: one of these days, our two agents are going to have the meeting without us.
We laughed. Then I couldn't stop thinking about it.
Set the meeting itself aside for a moment — we'll come back to whether you'd ever want the agents running that one. Because the joke pointed at a bigger question. What would an agentic accounting firm actually look like — a firm that fully embraced the agentic world? Not AI bolted onto what you already do, but a firm built so the client's software talks directly to yours.
System by system, your client's stack is becoming reachable
Think about where your client's business already runs on automatic connections. Their bank feeds transactions straight into Xero or QuickBooks. Their payroll platform pushes data without anyone keying it in. Their card processor, e-commerce platform, and point-of-sale each expose a way for other software to plug in and pull what it needs.
This stopped being a forecast in July. OpenAI's ChatGPT Work now gives any business owner a persistent agent that connects to their apps and runs scheduled tasks, and Claude's Cowork reached web and mobile the same week. Monday's roundup ranked those two launches as the week's top story — this piece is what they mean for your firm specifically. Your client's agent isn't coming — for a growing number of clients, it ships with the subscription they already pay for.
That kind of plumbing now has a name in the AI world: MCP. Think of it as a universal adapter that lets one system talk directly to another — the same way a bank feed lets the ledger pull transactions without a human in the middle, except it works for almost anything.
Here's the uncomfortable part. As that happens, every meaningful system in your client's financial life becomes reachable — except the firm that's supposed to be the most intelligent of the lot. Their accountant is still reached by a portal login, an email, or a wait for someone to answer. In an agentic stack, the firm is the analog holdout.
And the bank is reachable for a reason: it's one system behind one door. Your firm is tax intake, payment, return prep, and a portal — overlapping tools with no single authoritative view, and so no front desk for an agent to walk up to.
Designing for AI agents, not just people
We've spent years designing client experiences for human eyes. Portals to log into. Dashboards to read. PDFs to download.
The portal was already our attempt to kill the "can you send me last year's return" email — and mostly it failed, because it relied on the client remembering to log in and go look. They don't.
For the last six months I've been rethinking what an application even is. By recent counts, more than half of all internet traffic is now bots, not people — the 2025 Imperva Bad Bot Report put automated traffic at 51%, the first time it has passed human traffic in a decade. Web apps, SaaS products, even plain websites are increasingly visited by software, not someone browsing — and that changes who you're building for.
You're now building for two users, not one. The human, for whom interface, design, and experience are everything. And the agent, which cares nothing for how a page looks and everything for clean access to the content underneath. Developers everywhere are being asked to expose their APIs and stand up MCP connections so an agent can pull data and start a transaction without ever touching a screen built for a person.
The firm of the future designs for the agent as much as for the person — and for some tasks, instead. That's not a portal with a fresh coat of paint. That's a rebuild. And it finally delivers what the portal always promised, because the client never has to remember anything — their agent goes and gets it.
Start where nobody will miss the friction
You don't begin with the hard stuff. You begin with the contact nobody enjoyed in the first place. "When's my next tax payment due?" "Can I get a copy of last year's return?" "Where's my latest management report?"
Today those questions arrive by email and burn a staffer's afternoon hunting down a document the client already had access to.
Now picture the overnight version. Your client's agent asks yours, at 2am, and gets the answer — no email, no staffer, no wait. Run it the other way too. Your team has open questions on a year-end file; the client's agent checks each morning, finds what you asked for, and answers directly. A whole category of back-and-forth clears itself while everyone sleeps.
And it's more secure, not less. Emailing a tax return as an attachment is one of the least safe things firms do every day. A scoped, authenticated connection that reaches only what it's allowed to and logs every request retires that exposure instead of repeating it. Done properly, it's the safest channel you've got.
Who builds the front desk? The practice-management gap
Here's the part that isn't really about you with a keyboard. You run a practice, not a software company — you're not going to write the layer that turns those scattered tools into one authoritative view yourself. That's a practice management problem, and most of today's stack doesn't solve it.
So make it your filter. When you next evaluate or renew your stack, the question isn't "which portal looks nicest." It's "who gives my client one front desk an agent can actually reach?" — and now that the platforms have started selling exactly that, a second question rides with it: who owns the front desk once they build it? That pair of questions sorts the vendors who saw this coming from the ones still shipping a prettier login.
And if you won't wait — you don't have to. That connective layer can be built today, over the tools you already run. Most firms won't. The few that do will have a front desk while everyone else still has a building full of locked rooms.
The door, and the meeting
Everything so far is the same half of the problem — the friction. The overnight answers, the single front desk an agent can reach: all of it is contact nobody enjoyed in the first place, and it should just go.
But remember the meeting. The agents transcribing while you and your client actually talked — that was never friction. So here's the question I'd sit with this week: if your client's agent came knocking tomorrow, could your firm even answer the door? And once it can — which conversations will you still want to have yourself?
Designing your firm for the agent, not just the person, is a rebuild — and that's exactly the work we do inside AI Practice Transformation. If this is the year you stop bolting AI onto the old process and start building the firm an agent can reach, that's where to begin: theaiaccountant.ai/transformation.