"Can I put Friday's lunch through the books?", "when is my next VAT deadline?", "I need my compliance certificate for a contractor", "how does my apprentice count towards headcount?". Taken one at a time, these questions last three minutes. Multiplied by a portfolio of sixty files, they take half a day a week per member of staff, as interruptions, at the worst possible moment, and they are almost never billed.
The difficulty is not that the questions are hard: it is that they repeat and that the right answer depends on the file. The same VAT question has a different answer for a builder and for a property company. An AIOS handles exactly that layer: it reads the question, pulls the client's real position from the file, drafts the reply in your own wording, and hands over to you the moment the subject carries your professional liability.
The problem
- Everyday questions arrive by email, by text and by phone, in the middle of production, and break the concentration of whoever was reviewing a set of accounts
- The right answer depends on the file (tax regime, legal form, industry agreement), so nobody can reply quickly without opening the file first
- The clients who ask the most questions are rarely the best billed, and the engagement letter is almost never invoked
- The same answer is rewritten ten times a year by five different people, at five different levels of precision
How the AIOS handles it
It works out the question and the file behind it
An email lands: the AIOS recognises the client, opens their file and pulls whatever drives the answer, VAT regime and filing frequency, legal form, the director's social security status, the applicable industry agreement, upcoming deadlines. A question asked with no context ("and what about the car?") is attached to the earlier thread instead of starting from nothing.
It writes a grounded answer, not a general one
The reply is built on your internal documentation and on your usual positions: what the firm normally says about meal costs, about benefits in kind, about whether a vehicle is deductible. Every answer names what it relies on, so reviewing it takes thirty seconds rather than ten minutes.
It separates what goes out alone from what goes through you
A deadline reminder, a certificate to send, an explanation of which receipt is expected: that leaves directly, in the firm's tone. A structuring question, anything touching on tax planning, a borderline case or a delicate client: that stops in your approval queue, already drafted, leaving you to adjust and sign. You set that boundary, it is never decided for you.
It builds on itself instead of starting over
Every approved answer feeds the firm's knowledge base. Within a few weeks the most frequent questions have a reference answer, worded the way you word it, and your corrections carry over to all the following ones. The subjects that come back most often also make good candidates for a note sent to the whole portfolio before anyone even asks.
A concrete example
What came in from clients this morning?
Eleven questions. Seven went out on their own: three VAT schedule requests, two compliance certificates, a reminder of the filing date on the Lemoine file, and how to handle a toll receipt. Three are waiting on your review, already drafted: Cardoso asks whether he can deduct meals taken alone while travelling (answer ready, including the caveat about the commute), the Vidal company wants to move a vehicle to a long-term lease (I have costed both options, it deserves your view), and Ferrand raises a dividends versus salary question, which I have left whole for you. The eleventh is from Nadal, asking the same thing for the third time in a month: I suggest sending him a one-page note on his own situation, which I have drafted.
Other use cases: Chasing missing paperwork · Tax and employment law monitoring
Main page: Accountants