The answer is written down.
Nobody can find it.
Manuals, product documentation, support tickets, process instructions, intranet pages. The knowledge exists — it is just spread across tens of thousands of pages that nobody can search properly, so the same questions keep landing on the same few people. We build an assistant that answers from your documents only, shows the source of every answer, and says it does not know when the answer is not there.
Free 60-minute workshop, no obligation. You leave with an honest read on whether your documents are ready — and if they are not, we say so.
The same five questions reach the same senior person every week, and they answer from memory.
The right answer was written two years ago, in a folder nobody opens.
A new hire spends them learning where things are, rather than doing the job.
From the first call to something
running in your business.
Four steps. We start by checking whether your documents are ready at all — if they are not, we say so before anyone spends money. The assistant runs in your environment, on your credentials.
- Free workshop60 minutes
We look at what documents you actually have, what state they are in, and which questions matter most — then tell you honestly whether they are ready. If they are not, we say so.
- Connecting your documents1–3 weeks
We organise your documents so the assistant can search them properly. Folder and menu names stay in your own language rather than English — on its own, that removes a large share of wrong answers.
- Rules and testing1 week
You write down what it should and should not answer. Then we try to break it ourselves. The assistant answers from your documents, or it says it does not know.
- Handover1 session
It runs in your environment on your credentials. We train the person who will own it.
You provide
A knowledge owner, the document sources, sample questions with known answers, and an IT contact to approve access. About eight hours of your time, plus getting the documents into one place.
KajoAI delivers
The source connection, indexing, the assistant workflow, source references, evaluation with your own testers and handover.
Agree before building
Supported topics, access boundaries, answer-quality criteria, and how unsupported questions are handled.
1,400+ documents in the first index, plus online help content. The support team asks in the intranet and opens the source behind every answer.
Project example — Visual Components, phase 1 (Feb–May 2026)
Know what you are buying
before the build starts.
Fixed price, agreed scope, a working solution in weeks — not an open-ended project. Each package builds on the one before it.
PACKAGE 1
Pilot
€4,900
+ €150/month
1 document set, 1 team · 3–4 weeks
- One set of documents connected — manuals, process documents or support tickets
- Every answer shows the document and section it came from, so anyone can check it
- Tested against your real questions and judged by your own people
Free source-material review
RECOMMENDED
In production
€9,500
+ €250/month
full document base + your intranet · 5–7 weeks
Everything in Pilot, plus:
- All your documents connected, and kept current as they change
- Lives where people already work — intranet, Teams or a web widget behind your logins
- The rules written with you — then we try to break them before go-live
Guardrail and behaviour workshop
PACKAGE 3
Many languages, many teams
€16,000
+ €450/month
multi-language + access levels · 7–10 weeks
Everything in the production package, plus:
- A separate version per language, each built in its own language rather than machine-translated
- Access levels, so each audience only sees what it should
- A report of what people ask, what it could not answer, and what you should write down next
30-day answer-quality review
Prices exclude VAT. The fixed price covers the standard scope described above. The monthly fee covers hosting, keeping documents current and support. Additional work is agreed separately.
Results show up as numbers,
not as a feeling.
Questions answered without asking a colleague, time spent searching, and how quickly a new starter can work on their own. We agree the starting point with you before the pilot, so the change is measured rather than asserted.
The assistant is yours
to keep.
You keep the editable workflows, the index and the handover documentation. Where it runs is your decision: for the University of Turku the assistant runs on their own servers, with an EU-hosted vector database as the only external service and no US cloud providers involved.
Three alternatives,
and where each one stops.
These are the options people weigh up before calling us. Each of them works for something — just not for answering from your own documents, with sources, in your own environment.
Instead of
ChatGPT, Claude or Copilot
General assistants answer from the public internet and from training data. They do not know your installation guide, your escalation checklist or your pricing rules — and they will answer anyway, confidently. A grounded assistant answers only from your documents, shows which document it used, and says it does not know when the answer is not there.
Instead of
Zapier or Make
Connecting two apps is the easy part. A knowledge assistant has to take documents in, split them sensibly, keep the search index current, find the right passages and check who is allowed to see what. That needs branching, custom logic and a full log of every run — and the option to run on your own servers. That is why we build on n8n.
Instead of
A closed assistant product
A packaged assistant starts quickly and then cannot be changed. You cannot adjust how documents are split, which model answers, where the data is hosted, or what it does when it is unsure. With n8n you can change any of those without rebuilding — and if you stop working with us, the workflow is still yours.
The four questions we get
on almost every first call.
It answers from your documents or it says it does not know. Every answer cites the document it came from, so anyone can check it in one click. Before go-live we write the guardrails with you and then attack them ourselves — the assistant should refuse a question it has no source for, every time.
About eight hours, plus the work of getting your documents into one place. One person on your side needs to own the source material — in our experience that single choice decides how good the answers turn out, and it is not something we can do for you.
You own it and it runs on your credentials. New and changed documents have to be added — we either show your person how, or do it for you as part of the monthly fee. You are not locked in either way.
That depends on the agreed setup, and we settle it with your IT before connecting anything — hosting location, which services process the data, who has access, how long it is kept. The strictest version we have built runs entirely on the customer’s own servers, with an EU-hosted vector database as the only external service and US cloud providers ruled out. Other builds use managed services because that suited the customer better. Your call, not ours.
Which question does
your team keep asking?
Bring one recurring question and the documents that should answer it. In a free 60-minute workshop we check whether your source material is ready, pick the three questions worth answering first, and tell you whether a pilot is worth scoping.
The aim of the session
An honest read on your source material, the three questions worth answering first, and a clear decision on the next step. If your documents are not ready, we will say so.
Free 60-minute workshop · No obligation to proceed.