Find answers in company documents — and check the source
I bring the documents we choose together into one place, and add a chat — you ask it the way you would ask someone in the office, and each answer carries links to the documents that were searched.
Someone asks in an ordinary sentence and gets an answer along with links to the documents the system found for that question. One click shows whether the answer really follows from them — an answer without a source is just a machine's opinion.
Arrange a call about your documentsWhat breaks today and what changes
The answer exists, but only in one person's head
TodayOne person knows the procedure by heart. When they are away, everyone else guesses — or calls the customer back about something the company answered long ago. System search does not help here: it finds a word in a file name, not the situation someone is asking about.
AfterA question that today always lands with one person lands with the system instead. When that person is away, nobody guesses and nobody calls the customer back about something the company answered long ago.
Two versions, both look current
TodayLast year's price list and the current version sit in the same folder. Whichever gets opened first wins.
AfterAnswers carry links to the documents, so you click instead of digging through folders. If two price lists stay in the collection, the system may answer from the older one — it does not decide which applies, and that is why you settle it before launch.
New people ask what the last ones asked
TodayA new colleague asks exactly what someone else asked three months ago — and again somebody answers from memory.
AfterA new hire asks the system instead of a colleague — and sees the same documents someone else used three months ago.
In short
- Included
- I sort out the documents we pick together. I set up search that understands what you are asking, not just the words you typed. Answers carry links to the documents that were searched. Every new document — from the scanner, folder or mailbox we choose together — lands in a closed queue first. The person running the queue sees it; everyone else only once access is granted. I set up backups and prove them with a restore at handover. You get a message when a document fails to arrive or a backup does not run. And we start with a small set.
- What I need from you
- I need access to the documents and to the channels they arrive from. You name the person running the queue and their stand-in, and decide who sees which documents, where the backup lives and for how long, whether the disks are encrypted and who holds the recovery key. Before the trial I need 10–15 real questions, someone to judge the answers, a one-time login from each user, and your team's time for handover.
The path of one document
This is what happens to a single file after rollout — from where it sits to an answer with a reference.
- 01
Wherever the documents are today
I collect the set we picked together
a file from the scanner, a folder, a mailbox set up just for documents, or the upload form in the archive
- 02
Preparation
I split it into passages and describe them — the labels are learnt from your own documents
a passage linked back to its source
- 03
Versions
You decide which version applies — no system can guess that
the version you designated before the collection went into the system
- 04
Search
I match the question by meaning, not by keyword
the best-matching passages
- 05
Answer
The model writes an answer and links to the source.
an answer with a link to the source
When there is no answer
When the documents do not contain the answer, the system may still answer from the closest matches. That is why the trial also covers questions with no answer — I do not promise it will refuse every such question.
What you get
- A working assistant over the chosen collection, linking the documents it found for each question.
- A map of the documents: what went in, what was deliberately left out, and why.
- Test questions from your day-to-day work, with a record of how the system answered them.
- A list of the gaps in your documentation that the pilot exposed — often worth more than the assistant itself.
- Backups with a restore carried out in front of you, not promised.
- A handover where we trigger an import failure and a missed backup, and check that the message reaches the named person.
- An attempt with an ordinary staff account: whether a document outside their permissions can be found or opened — including after a restore.
- A short guide: how to add a document, how to retire an outdated one, who sees what, and who keeps an eye on it after handover.
Evidence
- Role
- Designed and delivered by me as part of my employed role — not a client reference for this service.
- Scope
- Internal knowledge system answering questions from company documents
- Environment
- Internal production system — organisation confidential
- Type of evidence
- Running in production — details confidential
- As of
- 2026-08
- What you can check yourself
- The live demo on the homepage uses the same principle: ask about my public articles and see the sources used in the answer.
What this evidence does not show
I do not publish the document volume or architecture because they are confidential, and I do not quote an accuracy figure because there is no publishable measurement. The demo searches public articles and does not show the production system.
Public material
How the project works
- 01
A conversation about specifics
I ask about the three questions that come up most often with you, and where the answers sit today. 30–45 minutes, remote, no charge.
- 02
The archive
Entry channels, order, permissions, and a backup with a restore. This stage has its own handover and stays yours even if you stop here.
- 03
Testing the assistant on your questions
I put the assistant into service and test it on your questions, roles, documents and hardware. A negative result ends the stage with a report — the archive keeps working, and anything custom is a separate decision.
- 04
Tuning and handover
Before the test we record the expected source, the acceptable answer, and who judges it. We check every substantive claim in the answer, not just the link.
- 05
Four weeks after launch
I collect the questions people actually asked and improve what can be improved without new hardware. It ends with a short report.
How I price it
For the trial run you pay a figure agreed up front — we settle it after the first conversation. I give the price for the whole thing only after the trial. Before that nobody names it honestly, because nobody knows what state your documents are in.
You pay for:
- Your own machine handles documents, questions and answers (default variant)
- Each person sees only what I set for them
- The right documents in the collection
- Answers checked against your own questions
Common questions
Can the system get it wrong?
Yes. That is why each answer carries links to the documents it searched — you can open them and check whether the answer follows. I do not promise a system that answers everything and never errs; nobody honest should. The system uses only your own documents, but when the answer is not there it may still answer from the nearest passages — which is why the trial also covers questions with no answer.
If a chat like this often comes with the program, what am I paying for?
For setting it up and fitting it to your work, not for the idea. Some programs ship a chat feature, and I do not sell it as my own invention — I say so plainly, so you do not pay for something you could have yourself. You pay for four things. First: in the default variant, your own machine handles the document content, the recognised text, the questions and the answers, not an outside AI provider. The offer lists separately which outside connections are needed and where the backups live. Second: I set for each person separately what they can see. Third: the right documents make it into the collection. Fourth: I check the answers against your own questions, not my examples. At the end you get the record: what the assistant answered and where it came from.
What if our documents are a mess?
That is the normal starting point, and it is exactly what the pilot is for: it shows how much work sits in putting them in order before you decide on the full engagement. It is different if the documents do not exist yet — then they have to be written first, and that is not a job for software. The same applies when the set changes hourly and nobody owns what is in it. Labelling new documents does not work by itself from day one either: the system learns your labels on the first batches, and you correct it until it gets them right unprompted.
Who sees which documents?
As much as we settle. I set who may open which documents — and the same for the search, so it does not show a passage somebody should not see. From you I need one decision: who sees what. That is technical work, not a legal assessment.
Does the data leave the company?
It does not have to. It can stay on your own server — that is the default, not a surcharge. Licences for the systems the documents come from stay with you. The other route: the heavier part runs on an outside provider's model — cheaper to start, a monthly fee instead, and excerpts from the documents do leave the company. I tell you which ones before you decide.
Does this make us compliant?
No, and I do not claim otherwise. I do the technical part and say where it ends. Whether your case needs further formal steps is a question for your own adviser. The company is answerable for what the documents say; I am answerable for the mechanism and for every answer naming its source.
What is not included?
A complete company archive — we work on the set we picked. A guarantee for every individual answer. A ruling on whether you comply with regulations.
Can I get a price range up front?
For the pilot, yes — fixed scope and fixed price, both set after a conversation about the specifics. I do not quote the full engagement before the pilot, because until then nobody honestly knows the cost: it depends on the state of the documents. No open-ended hourly billing and no generic price range for a system I have not assessed.
Let's talk about your documents
Tell me the three questions that come up most often and where the answers live today. I will tell you whether a pilot makes sense — including when my answer is no.