Before designing an infrastructure, we need to understand what problem actually exists.
When relevant knowledge is distributed across teams, documents, applications and systems, the same organisation may maintain several versions of reality without being fully aware of it.
The Enterprise Diagnostic defines the problem before a decision is made about implementation.
We analyse which knowledge matters, where it is held, who has authority over it, which definitions conflict and which conditions limit its use.
A knowledge problem can look like a search, AI, documentation, process or integration problem.
But implementing a tool before understanding which information should be treated as valid usually transfers the inconsistencies into a new system.
The diagnostic helps separate:
The scope is adapted to the domain and the organisation’s complexity.
It may include:
Where the relevant knowledge currently lives and the role each source performs.
Which concepts, products, services, policies, organisations or assets need a stable identity.
Where incompatible, duplicated or ambiguous versions of the same information exist.
Who may create, validate, modify or withdraw knowledge within the domain being analysed.
Which information is active, what has been superseded and what needs to be retained as historical information.
Which information depends on other information to retain meaning and context.
Which person or system may use specific knowledge, and under what conditions.
Which risks arise when assistants, RAG, agents or other systems retrieve and reuse that information.
The diagnostic does not end with a collection of observations.
The deliverable must support decision-making.
Depending on the scope, it includes:
At the end, you should be able to answer more precisely:
That is a valid outcome.
The problem may be solvable by:
The purpose of the diagnostic is not to justify an infrastructure.
It is to avoid building one when it is not needed.
It is generally useful when:
From €4,800 excl. VAT
The price depends on the domain, the number of sources and systems involved, the participating teams and the depth required.
The diagnostic has a fixed scope before work begins.
Starting question
A knowledge infrastructure can become a critical part of an organisation.
That is precisely why it should not begin with a tool or a predetermined architecture.
It should begin with one question:
What does this organisation actually need in order to trust its knowledge?
Depending on the agreed scope, it analyses the sources and systems involved, critical entities and definitions, contradictions, authority, currency, relationships, access conditions and the risks of reuse by AI systems.
No. The diagnostic should make it possible to decide what to retain, what to change, what should not be built and whether there is a genuine case for an infrastructure. Any later implementation is a separate project.
Depending on the scope, it delivers a domain map, a source inventory, critical entities and relationships, contradictions, authority criteria, risks, dependencies, priorities, acceptance criteria and a recommendation on whether an infrastructure is worth implementing.
It is usually useful when several teams or systems describe the same entities, there are contradictions or doubts about canonical sources, a corporate AI project is being prepared, a RAG system or assistant returns answers that are difficult to validate, or traceability, governance, access or exposure requirements apply.
The Enterprise Diagnostic starts at €4,800 excl. VAT. Pricing depends on the domain, the sources and systems involved, the participating teams and the depth required. The scope is agreed before work begins and does not automatically include an implementation.