Knowledge sits in people's heads, folders and old emails. New staff keep asking the same questions, and when someone is ill, nobody knows how things work.
The scope of a clearly defined starter project. Exactly what is included is set out in your proposal.
For the agreed scope you get a written proposal with a fixed price. Ongoing support only if you want it. How a proposal comes about
Use cases for orientation – not customer projects.
An office makes manuals and checklists searchable. The answer to “How do I create a new customer?” links to the right page in the manual.
A trade business collects installation instructions; fitters ask on site by phone and see the source.
Clarify documents, access rights and data questions, choose the provider.
With test documents, so you see early what answers look like.
With real questions from everyday work – are the answers and sources right?
More documents and users, after your approval.
Training and a plan for keeping the collection up to date.
We clarify that before we start: with which provider, in which country, under which contract. I suggest solutions where the storage location and the use of the data are governed by contract.
Yes. That's why it shows the source for every answer, and we test it with real questions before everyone works with it. For important topics, the source remains authoritative, not the summary.
Not necessarily. The assistant can build on documents you already have. What makes sense becomes clear after the inventory.
Quick chat
Tell me what kind of documents you have and who asks questions about them – I don't need any confidential content for that.
Daniel ErochokDeveloper from Iserlohn – you talk to me directly
I'll call you back – approx. 15 minutes, no obligation. Your name and number are all I need.
I'll get back to you personally.
If you like: a few details in advance – then I'm already prepared for our call. Everything is optional.
Thank you – your details have been added and have reached me.