PIPELINEGuide
AI knowledge base: contract, ownership and exit
Who owns the data, access credentials, and outputs in the end? The answer to this question says more about a provider than any reference list — and belongs before the signature, not after.
Before commissioning an AI knowledge base, clarify in writing: data and access belong to the client, in which format and within which timeframe they will be handed over upon termination, what later changes will cost, and that documentation is a quote line item and not a verbal promise.
01 — Contract
What needs to be clarified in writing
- Ownership of data and access. They belong to the client. If a provider won't clearly confirm this, that's the most important information from the conversation.
- Handover upon termination. In what format, within what timeframe, at what cost.
- No minimum term without consideration. Lock-in is justifiable if something is delivered in return — otherwise not.
- What a later change costs. The total cost isn't determined by the project price, but by the hourly rate in year three.
- Documentation as a deliverable. Not as a promise, but as a line item in the proposal.
02 — Questions
Questions you should ask
- What happens if the project becomes more expensive than estimated — who bears that?
- Who owns data, access, and, if developed, the source code?
- What does operation cost in the second and third year?
- What does the documentation we receive at the end look like?
- How would you measure whether the project was successful?
- Is there a case in which you would advise us against this?
03 — Warning signs
When to be skeptical
- Guaranteed results. Anyone promising top Google ranking or a specific revenue increase is selling something they can't deliver.
- No pushback. A provider who thinks every project is a good idea has either not listened or is only selling.
- Time pressure. Limited-time discounts on project prices are a sales tool, not an offer.
- Unclear ownership. Anyone who won't clearly say who owns data and access doesn't have your interests at heart.
- No contact with technical expertise. If only sales sits in the first meeting, that's where misunderstandings arise.
04 — Questions
Frequently asked questions
Will everyone see everything?
No. The permissions from your existing systems are carried over. If someone isn't allowed to open a folder today, they won't get answers from it either.
Does this have to run in the cloud?
No. For sensitive areas, we use models that run entirely on your own hardware. That costs more to set up and slightly reduces answer quality, but no document leaves the building.
What if we have multiple languages in our document base?
No problem — the search understands questions and documents regardless of language and finds the right answer even when the question and source are written in different languages.
Can we roll this out to more departments step by step?
Yes, that's the usual approach. Start with one department, learn from their questions and results, then connect the next one — rather than releasing everything at once.
How do we detect outdated answers?
Through date references and marking of documents flagged as obsolete. Analytics also show which sources are used most often — those you maintain first.
Our documents are a mess. Will it still work?
To a certain extent, yes — the system handles different formats and structures. What it cannot do is resolve conflicting information. If three versions of a price list are in circulation, you need to clarify which one applies first.
How long does setup take with a large document base?
It depends less on volume than on condition: well-structured repositories with few duplicates are ready in a few weeks, grown repositories with many old versions need a cleanup round first.
05 — Next
Related pages
- AI Knowledge Base — Overview
- AI knowledge base — risks
- AI knowledge base — practical examples
- AI Knowledge Base — DIY
- AI knowledge base — checklist
- AI knowledge base — AI disclosure
- AI knowledge base — pros and cons
- AI knowledge base — common mistakes
- AI automation
- Document processing with AI
- AI chatbot
- All guides
Next step
Initial assessment, no obligation.
Briefly describe what you need. You'll get an honest answer about what's realistic and what it will roughly cost.