Associations, professional societies and public bodies have thousands of pages - and visitors who cannot find the right one. The knowledge navigator understands the intent and routes to the right source, the right chapter, the current version. It formulates solely on the basis of sources it has found.
The situation
The common pattern: the answer has long been in your corpus - nobody finds it because the question is phrased differently from the heading.
Full-text search finds pages that contain words. Without the technical term you get twelve hits or none and have to sort them yourself.
The most common practical failure in specialist corpora is not the wrong answer but the outdated one. An archived version that merely ranks lower resurfaces on the next search.
Whatever is not found in the corpus arrives as an email or call at the office or the support desk, often the same question yet again.
A real classification
The assistant in the bottom right of this site runs on the same machinery, indexed on our own corpus. Below is its unedited output for a real question - nothing about it has been touched up.
What the visitor typed
„We want to migrate from VMware to Proxmox and secure operations.“
What the system does with it
Classification
WZ-IT reads your project as a strategic migration from a VMware environment to Proxmox VE, to reduce licence costs and regain control over virtualisation. This is not only about the technical move but also about securing operations through high availability, backup and disaster recovery.
The main solution combines the migration itself with building a stable operational base. Proxmox VE handles virtualisation, while backup, monitoring and network infrastructure secure stability. The migration runs in stages: analysis of the current environment, test migration, cutover and final operational hardening.
WZ-IT delivers planning and architecture, including risk analysis and rollback strategy. In operations we take on monitoring, CVE watching, backups and updates.
Matching building blocks
Direct fit for migrating VMware ESXi/vSphere to Proxmox VE, focused on planning, test migration, cutover and operational hardening.
Supports building a Proxmox-based private cloud with high availability, backup and disaster recovery as the target architecture.
Securing operations after the migration through monitoring, backups and updates is central to the project.
So we can start where it matters
How many ESXi hosts and VMs are currently in use?
What are the requirements for high availability, backup and disaster recovery?
Should workloads be migrated one to one or restructured?
The assistant handles these projects too - ask it yourself:
The assistant is in beta and can classify a request wrongly, which is why every classification carries a route to a human. For knowledge corpora, the sourced passage with chapter and version replaces the offer building blocks.
Use cases
Visitor asks
I need something that meets a specific requirement - which of these fits?
Navigator
The navigator clarifies the decisive attributes in one or two follow-up questions, routes to the matching catalogue entries and links the data sheet and the contact.
Visitor asks
Is there any funding for our project?
Navigator
It narrows down by region, project type and eligibility and routes to the matching programme - with deadline, version and a link to the application. It never promises an approval.
Visitor asks
What does the current version say on this topic?
Navigator
It routes to the right chapter of the valid version, names the version date and flags superseded editions. Judging the individual case stays with the professional.
Visitor asks
Why does this not work for me?
Navigator
It routes to the matching help article or how-to - and where nothing fits, straight into the contact form instead of sending the visitor further through the archive.
Visitor asks
How is this handled here?
Navigator
It routes to the valid policy or form template including its version, instead of an outdated PDF that is still linked somewhere.
Visitor asks
What applies to my case?
Navigator
It distinguishes audiences - member, professional, press, general public - and routes each into the right area, including the contact and booking path.
Approach
The effort is not in the model, it is in the structure: what belongs to the corpus, what is archive, and which intent leads where?
Inventory from the sitemap, samples per content type, exclusion rules for archived versions. The result is a written assessment with the number of processable documents, the outliers and what should be tidied up first.
Sitemap, CMS API and document stores are opened up. First we clarify what belongs to the valid corpus, what is archive and who owns which area editorially.
Content is split by chapter and enriched with metadata: area, language, date, version. Archived editions are excluded, not merely ranked lower.
A curated catalogue defines which intent leads where, where a follow-up question is asked and where a human takes over. That is editorial work, not model selection.
We test with real questions from your actual intake and check every answer against the cited source. Wrong paths are corrected in the catalogue, not talked away in the prompt.
A daily diff keeps the index current. The unanswered questions are the most valuable output: they show where the corpus is missing content.
Guardrails
With public expert knowledge, a wrong answer costs more than a missing one. That is why the limits are architecture, not phrasing, anchored in the index rather than in the prompt.
| Guardrail | How it is enforced |
|---|---|
| Answers only from cited sources | Without a hit in the corpus there is no answer, only a handover. Free model knowledge is not an admissible source of answers. |
| Citation is mandatory | Every statement carries a link, chapter and version date. An answer without evidence is discarded rather than delivered. |
| The valid version comes first | What currently applies is found first; archive is excluded from the search space. If a version has been superseded, the navigator names both and says which one applies. |
| Escalation to a human | If nothing fits or the question becomes case-specific, the navigator visibly routes to the contact form or booking page - not into an endless loop. |
| No legal, medical or financial advice | Case-specific assessments are rejected before the model call. Inputs are checked for personal data beforehand. The navigator names the authoritative source and the way to the responsible professional. |
| Logging | Query type, chosen path, source and result are logged - without storing personal input as raw text. The log lives in your system; you decide who may see it. |
| Switchable off at any time | The navigator is a component of your site, not a replacement for it. It can be disabled per area or entirely without making content unreachable - important while a corpus is being revised. |
Result
Not access to a platform, but a system that belongs to you and whose parts you can name.
The corpus analysis regularly surfaces problems that have nothing to do with AI: broken sitemap references, unreachable files, duplicates between language versions. You get told about those whether or not the project happens.
Price
The build costs from €14,900 excl. VAT. We name the fixed price for your corpus and ongoing operations with index maintenance and reporting after the corpus analysis. These six points determine it:
Limits
A guided navigator is deliberately narrower than a chatbot. That narrowness is exactly why you can point it at public expert knowledge.
Page count alone does not justify a navigator. What matters is whether the corpus is versioned, whether different audiences need different parts of it, and what a wrong answer costs. Three hundred heavily versioned guidelines are a case for it; two thousand flat pages often are not, and there a good search is cheaper.
Where we stand: the navigator is currently being built in a pilot project on a large medical knowledge corpus. We will publish figures and results once the project is finished and cleared.
Answers to the most important questions
Further reading
Reviews & projects
From a knowledge base with an AI assistant and local AI integration to data sovereignty and ongoing operations.
AI Platform
We were looking for a secure yet easy-to-use alternative to the large American providers and came across WZ-IT. WZ-IT advised us on choosing the right models and implemented the integration for us. Beforehand, we were able to try everything out calmly on a test instance. Today WZ-IT runs Open WebUI for us on our own domain, with a convenient Microsoft login and open-source models hosted by a German provider. Our team can now work productively with AI without resorting to external tools or shadow AI. Working together is straightforward, and questions are answered quickly and clearly. With WZ-IT we also have a partner at our side for further AI projects. (translated)
Carl-Frederic KornHead of E-Commerce & Online Marketing, Krüger Dirndl GmbH
Knowledge Management & AI
The knowledge from many years in the solar industry lived in the head of our former managing director, and it still lives in the heads of our employees today. We wanted to secure it, not as a folder full of notes, but in a way that lets us ask questions in daily work and get reliable answers. WZ-IT advised us from the start and weighed different approaches and knowledge management systems against each other with us before we decided. What was built is a custom knowledge base with an AI assistant that brings together conversations, notes, documentation and manuals: from the platform through onboarding our team to support in operation. Conversations are transcribed and facts are extracted; we review and correct everything ourselves before it is stored, because we do not want to trust an AI blindly. The system runs in our own environment, and the data stays with us. What surprised us was how efficient it was: WZ-IT used existing open-source software and extended it specifically for our requirements, instead of selling an expensive custom build from scratch, as is often usual with IT service providers. Timo and Robin understood our actual problem, preserving knowledge during the generational handover, and implemented it step by step: from the proof of concept through setup and validation with our own data to productive operation, explaining everything clearly along the way. Next, we want to extend this to the knowledge of our employees, so that this does not depend on individual people either.
Joshua von AmelnManaging Director, solarwerkstatt berlin GmbH
International
WZ-IT designs, develops and operates infrastructure and software for clients in Germany and internationally. We deliver projects remotely and continue supporting them in ongoing operations after go-live.
Enquiry
Describe the corpus, audiences, and content visitors should be guided to.
The conversation is free and non-binding.
WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.
Jakob ÖschlbergerInno7 GmbH
WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.
