You're the person everyone asks everything.
Time off, invoices, refund rules: you know the answer, and you get interrupted every time.
Your team asks and the archive answers, with the document it came from. We set it up, and you decide where your data lives.
Who it's for
Time off, invoices, refund rules: you know the answer, and you get interrupted every time.
What they know stays in their head. If they're out or they leave, that knowledge goes with them.
Manuals, procedures and contracts scattered across folders, emails and PDFs.
We start from the documents. If a procedure isn't written down anywhere, the Brain has nothing to answer from.
Sample company and documents. Tap a question.
Scripted example. No live AI runs on this page.
How do I ask for a day off?
Send the request in the HR tool. Your team lead approves it, then administration confirms.
Source: Employee handbook, Vacation and time off
What we do
The hard part isn't the software. It's getting the documents in order, checking the answers and keeping the archive up to date.
We read what you have, scans included. We remove duplicates and old versions and give every document a title and an area.
Everyone sees only their own part. An employee can't read a contract that isn't theirs.
Before opening it to the team, we ask the questions you ask every day and fix where it gets them wrong. If it can't find the answer, it says so instead of making one up.
New documents go into the archive. Every month you see the questions left unanswered: those are the documents you're missing.
Your data
Three ways to run it, depending on how confidential your documents are.
The simplest
The archive sits in the EU. The model that writes the answer runs outside the EU, under standard contractual clauses.
For procedures, manuals and price lists.
More confidential
Archive and model both run inside the EU: your documents never leave Europe.
For anyone handling customer or staff data.
Maximum confidentiality
A server of your own, with models running on it: no request leaves your network. Answers may be less precise and you need a suitable server.
For your most sensitive data. Quoted on request.
Before we start, we tell you in writing which providers handle which data and where. We comply with GDPR from day one.
How we work
Almost everything is done remotely. On site is needed only in a few cases.
| Remote | On site | |
|---|---|---|
| When it fits | Cloud and entirely in the EU. Also a local server, if it's already connected to the network. | A local server on an isolated network, or if you'd rather have someone at your company. |
| What you do | You give us read-only access to the documents. For a local server, your IT team opens an access for us. | You prepare the server and the place to put it. |
| What we do | We configure, test and update from here. | We install in person, test with your team and train them. |
| Your control | Time-limited, logged access that you can revoke whenever you want. | No external connection: we bring the updates ourselves. |
We decide together before we start. Each person sees only the documents in their own area.
It says so. It doesn't make anything up, and the question goes on the monthly list, so you know which document is missing.
No. We build, activate and maintain everything. For a local server, we only need someone from your IT team to open the access.
Yes, what we deliver is yours.
They can build it on their own too. The work you can't improvise is putting the documents in order, testing the answers and keeping it up to date: that's where we can work alongside them.
We quote after understanding how you work, and we agree the timeline with you before we start. There is no standard package.
Tell us where your company's information lives and we'll show you how to make it available to everyone.