Who holds which knowledge?
Which business-critical knowledge exists only in people's heads, with time horizon until departure and the damage its loss would cause.
Foundation first, tooling second
Scattered knowledge, outdated documents and unclear permissions can complicate AI adoption. The knowledge audit assesses these prerequisites within an agreed scope and provides a basis for deciding the next steps.
2–3 consulting days3 weeks to readoutUseful even without follow-up work
What we assess in your organization
Which recurring questions cannot currently be answered reliably? We identify knowledge holders, sources and maintenance owners. A planned staff transition is a concrete reason to prepare a handover.
Permissions need review before integration. Technical access does not automatically establish a legitimate business purpose. Conflicting sources, missing rights and outdated information belong in the assessment.
Choose the next step for your needs
Company Brain: make knowledge usable
Start with one knowledge bottleneck. A free introductory call helps assess whether better documentation, an audit or a bounded pilot is appropriate.
Understand the full project cost
Calculate setup, ongoing operation and internal review separately. An illustrative calculation is not an offer.
Assess completed project scopes
Distinguish the described work from evidenced outcomes. A similar workflow does not guarantee the same impact.
30 minutes one-to-one — pick your own slot
Instead of a fixed weekly session we talk about your case directly: one concrete bottleneck, 30 minutes on Zoom, free and without obligation.
30 minutes1:1Zoom
After booking you receive the confirmation with the Zoom link. Free and non-binding, no purchase required.
Three questions the audit answers
These are the questions rarely answered online, because they require knowledge of your operation rather than of a product.
Who may see what?
Current and intended state of access rights, including the permissions that today reach further than anyone assumes.
What stays current?
Which knowledge is stable enough to be written down, and which must always come from the system of record.
Three weeks, four steps
Two to three consulting days spread across three weeks from kickoff to readout.
1
Kickoff
Objectives, scope, contacts and data protection framework. Half a day.
2
Interviews
Four to six conversations of 45 minutes: management, two or three knowledge holders and one operational successor.
3
Inventory
Existing documentation, storage locations, systems and permissions. Where does knowledge exist only in someone's head?
4
Analysis and readout
Evaluation, a written document and a 90-minute presentation to management.
The readout document
15 to 25 pages, written for a decision rather than as a technical report.
- Knowledge risk map: who holds which critical knowledge, with time horizon and impact assessment
- The five processes with the best ratio of knowledge risk to how well they can be secured
- Rights matrix: who may receive which information, and where today's storage contradicts that rule
- Separation by volatility: what gets written down and what must come live from the system of record
- Implementation roadmap with sequence, effort range and prerequisites
- Make-or-buy assessment per process: in-house, standard software or guided introduction
Two sequences
The difference between a system still used after six months and one nobody opens again.
Tooling first
- Licences are bought before the sources are clarified
- The assistant answers from outdated documents
- Access rights surface only in live operation
- Nobody owns maintenance, and trust erodes
Foundation first
- Sources, rights and ownership are settled before purchase
- Every answer has a named system of record
- Permissions are part of acceptance, not an afterthought
- Maintenance is agreed before the system goes live
Frequently asked
Do we need an AI strategy first?
No. The audit is the basis for that decision. The result remains useful even if you introduce no AI at all, because the knowledge risks and rights questions exist regardless.
Are you selling us your own software?
No. Where a tool is needed we use existing solutions and pass their cost through unchanged. Our work is the order beforehand and the maintenance afterwards.
What happens to our documents?
The inventory needs structure and storage locations, not confidential originals. The data protection framework is agreed at kickoff and processing follows it.
What does the audit cost?
It is a fixed-price engagement, depending on size and the number of areas included. We state the exact price in the first conversation, together with scope and acceptance criteria.
Knowledge audit acceptance
- Each prioritized process has documented sources, an owner, user groups and unresolved questions.
- The access matrix distinguishes permitted and blocked access. Open risks have owners and next steps; an audit is not a production permission test.
- Management and project owners review the agreed deliverables together. Any later system implementation requires separate tests, approvals and operating rules.
Describe an area, receive an assessment
Describe one area anonymously: which questions keep coming back, who answers them today, and what happens when that person is away? Please do not send customer data or credentials.
Start potential analysis
If you want to prioritize a real process, a few clear inputs are enough for a strong first assessment.