Your documents come together in one place: quotes, plans, reports, contracts, emails with their attachments. There you ask in perfectly normal sentences, just as you would ask a long-standing employee. Every answer names the source in your documents – the numbered reference opens the original so you can check for yourself.
It is about the knowledge that is written down in your company: instructions, service reports, project documents, contracts, correspondence. What was sold, ordered and invoiced stays in your industry software. Whether and how documents from it can get into the knowledge base, we check before we start – the plan is only to read from it; nothing is changed there.
Scans and photos become searchable too. Handwriting is the hardest case.
Your documents come together in one place; scans and photos go through text recognition (OCR). The system suggests customer, project and date; a person confirms the document type, because that determines who sees it.
Attachments are meant to come in straight from the mailbox. Whether yours fits, we check in advance.
The plan is for attachments to come in straight from the mailbox, without saving and moving them. Whether and how your mailbox, for example Outlook or Microsoft 365, can be connected, we check before we start.
The search goes by meaning, not by keyword. Every statement carries a numbered reference to the source.
You ask the way you would ask a colleague. The search goes by meaning, even if the file is called “Scan_0047.pdf”. Every statement carries a numbered reference that opens the source in the original.
In the browser, nothing to install: on a computer, tablet or phone.
Nothing to install: you open a page in the browser, on a computer, tablet or phone. Everyone signs in with their own account, and the connection is encrypted. Type a question, read the answer, open the source.
Drag it in or take a photo. Once confirmed, it is ready for questions.
Your team drags a new document into the browser, or on the go sends it as a photo from the phone. As soon as a person has confirmed the document type, it is ready for questions. That way the collection grows with everyday work.
Access by role and document type, set once.
Access depends on the role and the document type, not on the individual file. Payslips are seen only by management, the maintenance instructions by the whole team. If access is missing, the system says so openly.
Speak a note into your phone, read it through, approve it.
A lot is not written down anywhere. Your fitter speaks the note into the phone after the job; it is typed up and put into shape. You read it through, change it if needed and approve it; only then does it become part of the collection.
Organised by customer, project, equipment or location, in your own terms.
In advance, we clarify which documents your company produces and what you search by day to day: customer, project number, equipment or location. That becomes the structure in which everything is filed, in your own terms.
We fill it in advance and introduce your team using your own documents.
We fill the knowledge base with your documents in advance, so that the first questions go to your real collection. Then we introduce your team using your own documents; a short guide stays with you.
We support you up to acceptance against twenty questions from the kickoff.
At the kickoff we record twenty questions. In the weeks that follow, we look at what is being asked and what is missing; in week six, acceptance takes place against these questions. What applies if they do not pass is set out in the offer.
Updates, backups and a contact person who knows your instance.
We take care of updates, security updates and backups. If something does not work, you reach a fixed contact person who knows your knowledge base and your structure.
Your own instance on servers in Germany, no training on your data.
Every company gets its own instance on servers in Germany; the language model runs in the EU. Your documents are not used for training; this is set out in the contract, and the data processing agreement (DPA) is included.
Demo · 30 minutes by video
Using examples from your industry: how you ask, what the source looks like and what happens when there is nothing.
The annual maintenance covers a visual inspection of the hydraulics, a function test of the emergency lowering and lubrication of the guide rails.
What is included in the setup and in ongoing operation is listed in the scope of services on the pricing page.
The usual office formats: PDF, Word, Excel, PowerPoint, text and CSV files, as well as images and scans (JPG, PNG, TIFF). Plus emails with attachments (.eml/.msg), ZIP archives and voice memos. Scans and photos go through text recognition (OCR), including older documents. How well that works for your documents shows on your own collection; handwriting is the hardest case.
As many as you have – from a two-person office to a company with dozens of people. Who sees which documents, you decide via roles and document types. The number of users does not affect the price: you pay a flat fee per company, not a per-user licence.
Not for running the knowledge base: we take care of setup, updates, security and backups, and the instance runs on our servers. It is used in the browser; we show your team how during the introduction. If a server at your company is to be mirrored, or an IT service provider looks after you, we coordinate access with the people responsible.
Your documents remain your property throughout. What happens to them is governed by the contract together with the data processing agreement (DPA). When the contract ends, you receive an export of your collection, and then it is deleted. Your documents are not used to train AI models.
Yes. In a thirty-minute video demo, we use examples from your industry to show how questions are answered and what the source looks like, before anything is agreed. Before we start, we also go through the answers together on real questions from your company.
It sends nothing on its own: on request (in the Premium package), an answer becomes a Word, Excel or PDF document or an email draft — which is only sent by hand. It does not automate processes and does not make decisions. And it does not replace an ERP: the ERP knows what was sold – the knowledge base knows how it is done. It is built for one thing: questions about documented company knowledge, answered with evidence. If you are looking for process automation, talk to us — that is a separate topic.
Thirty minutes by video, using examples from your industry: how you ask, what the answer with its source looks like and what happens when there is nothing on a question.
Thirty minutes · by video · no obligation
Would you rather see how it works first?
In the demo, we use examples to show how a question is asked and what an answer with its source looks like. You don’t need any of your own documents for this.