The accounts
Horus, Pennylane or your software: open invoices, trial balance, general ledger. This is running at a clinic with several companies.
The AI assistant
Which invoices are open, where is that contract, which email is still waiting for a reply: you ask in your own words, the assistant reads your software and documents and answers with its source. It reads; it writes nothing.
The problem
Every week the same questions go to the accountant, the office or the IT person. The answer already sits in a program, but someone has to open it, know where to look, or find the time.
Meanwhile the decision waits: the reminder that goes out too late, the contract nobody can find, the forgotten request.
A real example
“Which supplier invoices are still open this month?” Someone in the team asks their assistant. It reads the accounts at the moment of the question, with that person's rights and nothing more.
Today
The method
You don't judge an AI on a demo. Before opening access, you give us twenty or so questions your team really asks. We put them to the assistant, compare its answers with what you know, and record every mistake.
As long as it gets common questions wrong, we don't open it. And even once open, it always cites its source: you never take its word for it.
What we connect
The assistant only sees what you open to it, and only to read.
Horus, Pennylane or your software: open invoices, trial balance, general ledger. This is running at a clinic with several companies.
SharePoint, OneDrive, a file server or a mailbox: contracts, procedures, letters, with each person's rights.
Your request-tracking tool: what is waiting, since when, with whom.
Patient and staff data without a written framework agreed with you before the first line, with full respect for medical confidentiality. A payment, never.
Your data
Your data stays in your software. The assistant reads it at the moment of the question, through a connector hosted by DeepIT, and each person signs in with their own account: they only see what they already see.
Before opening, a written framework sets out what is connected, who has access, which AI service is used and where it is hosted. You approve it, and you can cut everything off at any time. The details: your data under control.
Getting started
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 and approved before we start.
Twenty or so real questions. We see where the assistant goes wrong and fix it.
Each person has their own account and only sees what they already see in their software.
No. Access is limited to reading, and the connector refuses any write before it even reaches your software. A payment, never.
Start by knowing what they paste into it. Copying an invoice, a contract or a patient record into a public tool takes that data out of your control. An assistant connected to your software reads at the source, with each person's account, without copy and paste, and says where each answer comes from.
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 opening.
Yes, sometimes. That is why we test it on your real questions before opening it, and why every answer cites its source, so you can check it. An assistant decides nothing in your place.
Tell us which, and we'll tell you whether your data can answer it.