Accounts
Horus, Pennylane or your own software: open invoices, trial balance, general ledger. This is the case we set up at a clinic.
Three specialities, one team.
Offer · Assistant on your data
Accounts, documents, tickets: an assistant that answers from your own data, read-only. AI is a tool, not a promise.
For managers and team leads who ask their accountant, their office staff or their IT person the same questions every week: which invoices are open, where is that contract, how many requests are pending.
The assistant only sees what you open up to it, and only to read.
Horus, Pennylane or your own software: open invoices, trial balance, general ledger. This is the case we set up at a clinic.
SharePoint, OneDrive or file server: contracts, procedures, letters, with each user's permissions.
Your support or tracking tool: what is waiting, since when, with whom.
Patient data, unless there is a GDPR framework agreed with you before the first line. A payment, never.
How it works
Just one to begin with: the accounts, or the documents. Not everything at once.
Which data, for whom, hosted where, and what never leaves. Written down and approved before we start.
You ask twenty real questions. We look at where the assistant gets it wrong and we correct it.
Each user has their own account and only sees what they already see in their software.
No. Access is limited to reading. Writing is only enabled if you decide so, for a specific task, and never for a payment.
It stays in your software. The assistant reads it at the moment of the question. The written framework states which AI service is used and where it is hosted: you approve it before go-live.
We don't connect it without a GDPR framework agreed with you: which data, for what use, hosted where. Often the right answer is not to connect it at all.
Yes, sometimes. That's why every answer cites its source, so you can check it in one click. An assistant decides nothing for you.
Tell us which one, and we'll tell you whether your data can answer it.