Connecting an assistant to the ledger answers the questions you never built a report for. It does not touch the part of advisory that takes your week, which is everything happening between the numbers and the client.
Worth being clear about both halves before setting it up, because the second half is where practices are usually disappointed.
What it is good at
Questions across clients. Which of my clients had a worse quarter than the last one. Which have revenue growth but falling margin. These are answerable from the ledger and nobody has a report for them, because the question changes every time you ask it.
The first pass at a review. Pulling the figures a quarterly conversation needs, before a person decides what they mean. The pulling is the slow bit and the deciding is the valuable bit, and this reverses the usual time split between them.
Explaining a number. Why is this line different from last year. An assistant that can read the detail answers in a sentence what otherwise takes a drill-down.
Where it stops
The ledger knows what was transacted. It does not know what was agreed.
It does not hold what you promised the client in March, who owns the three actions that came out of that meeting, whether the documents you asked for ever arrived, or what you will open with when you see them next. None of that is a number, and none of it is in Xero, so no connection to Xero will produce it.
That is the gap that makes advisory feel like it runs on memory, and it is unaffected by how good the assistant reading your ledger is.
The practical set-up questions
| Question | Why it matters |
|---|---|
| Which actions does the server publish | Decides whether you get answers or also actions |
| Does it write | Most ledger connections read only, deliberately |
| Whose permissions does it use | It should act as the person connecting, not an admin |
| Are actions logged | You need attribution on client data, not just access |
| Can access be withdrawn centrally | Staff leave. Connections should not outlive them |
Two more that are specific to a practice. Check that your engagement terms cover processing client data this way, because the answer is often yes and occasionally not. And decide who in the practice is allowed to connect at all, before someone does it on a Sunday.
The sequence that works
Connect it to your own practice numbers first, not to client files. You will learn what the action list actually supports in an afternoon, with nothing at stake.
Then pick one recurring question, the one you ask before every review, and see whether it answers it well. If it does, that question is now free. If it does not, you have learned something specific about the published actions rather than a general impression.
Only then widen it, and only to the clients where you have checked the terms.
What this does not solve, and what does
Advisory is slow for a reason that has nothing to do with the numbers. The plan is in a document, the actions are in an email, the progress is in somebody's memory, and the quarterly review is rebuilt from all three the night before.
Empiraa GPS is a strategy and client delivery platform that helps advisors and consultants manage client plans, demonstrate progress and grow recurring revenue. Each client's plan, actions and documents sit in their own portal, so the review is written from a live record rather than reassembled. Xero connects natively for actuals and Xero Practice Manager connects through the MCP, which is what the connection pills say and all they say. GPS shipped its own MCP in version 1.22, so a compatible assistant can work with that record within your permissions, and it is included on every tier.
Related reading: Claude for accountants, what it can and cannot do in a practice, and what an MCP server is, and what it is not.
What an MCP actually is covers the concept if this is the first you have met it.
