Answers from your documents
Your contracts, policies and manuals already contain the answer. Ask a question in plain language and get it back with the page it came from, so anyone can check it.
What this is
Companies rarely lose knowledge. They lose the path to it. The clause is in a contract somebody signed four years ago, the procedure is in a manual with three versions in circulation, and the answer to today's customer question was given by a colleague in an email last March. Finding it takes twenty minutes, and knowing it exists at all takes years of experience.
This is a search box that answers in sentences instead of listing files, and that shows where each sentence came from. It uses your documents and nothing else. When your documents do not answer the question, it says so, which is the single most important thing it does: an assistant that guesses is worse than no assistant, because people stop checking it.
It answers from your files and quotes them, so any answer can be verified in one click. We test it against real questions with known answers before anyone else sees it, and the files stay on EU infrastructure.
What it does
One question in, one checkable answer out.
01
Takes a question the way a person asks it
Not keywords. Whether we can end the Mueller contract early and what it would cost is a question it should handle in one go.
02
Answers from your documents only
No general knowledge and no filling in of gaps. If the answer is not in the files, the answer is that it is not in the files.
03
Shows the source
Every answer carries the document, the page and the passage it came from, so the person reading it can confirm it in seconds.
04
Respects who may see what
It uses the permissions you already have. Somebody who cannot open a folder does not get answers out of it by asking nicely.
05
Tells you what it is being asked
An admin view of the questions people ask and the ones it could not answer. That list is the best map of what is missing from your documentation you will ever get.
What you walk away with
A tool one team is already using, and the test that says whether it can be trusted.
Search and answers over one collection
A named set of documents: the contract archive, the policy library, the product manual, the tender folder.
A test set of real questions
Around forty questions from the people who will use it, with the correct answers written down, and a score. Re-run on every change.
The permission model, in writing
Who may ask what, how it is enforced, and what happens the day somebody changes role or leaves.
The code and the deployment
Running on EU infrastructure, in your account or ours, with a runbook and a session for whoever will own it.
How it runs
Pick one collection
One set of documents with one audience. Everything at once produces an assistant that is mediocre at everything.
Write the questions first
We sit with the people who will use it and collect the real questions, with the answers they know to be right. This is the test, and it exists before the build does.
Build and score
We build it, run the questions and show you the score: how often it is right, and how often it correctly declines to answer.
One team, then wider
It goes to one team, we watch what they ask, and we fix what the log shows. Rolling out to everybody on day one only hides the problems.
Who this suits
Legal and contract teams
Hundreds of agreements, a handful of clauses that matter, and questions that always arrive on a deadline.
Support and service desks
The answer is in the manual. Finding it while a customer waits is the hard part.
Bid and tender teams
Every proposal repeats something you have already written well once. This is where it is.
What it costs in time
Calendar time, assuming access to the documents and a couple of hours from the people who will use it.
Questions and documents
We collect the real questions, look at the files, and say which parts of the collection are usable and which need cleaning up first.
A version you can try
Answering over your documents with sources, scored against the questions from week one.
Permissions and rollout
Wired into your access rules, given to one team, then corrected against what they actually ask it.
Bring us ten questions you cannot answer quickly
Real questions from real people, and the documents that should contain the answers. We will tell you whether this would work on your files.
Book a call