How does MentX capture a key person's knowledge?
MentX is a personality-aware knowledge base. It captures the knowledge of your company's key person from two channels — the meetings he is already in, and a guided intake track led by us — and builds it into a living, temporal knowledge graph with full source attribution. No extra writing work for your expert. The result is queryable from day one through DigiME.
Step 1 — Connect: the meetings he is already in
Your expert spends his days explaining, deciding and correcting — in meetings. MentX connects to those meetings and ingests them. Each insight is extracted and stored with its source: who said it, in which conversation, on which date. Nothing depends on your expert finding time to write; the capture rides on work that already happens.
This channel is broad but shallow. It catches what comes up. It does not catch what nobody thought to ask.
Step 2 — Deepen: the guided intake track
That is what the intake track is for. In structured sessions, led by us, we work through the areas meetings never reach: the history behind today's setup, the reasoning behind recurring decisions, the heuristics your expert applies without noticing them. The track is personality-aware — it follows how this person thinks and explains, not a generic questionnaire.
Sessions are spread over weeks, not compressed into a farewell interview. Knowledge surfaces in layers; a single session gets the first layer only.
What the knowledge lands in: a temporal knowledge graph
Everything captured goes into a knowledge graph — a structured network of facts, decisions, people, machines and their relationships — with two properties that matter:
- Temporal. Every statement carries its date. The graph knows that a process changed in 2021 and what the reasoning was before and after. Knowledge is allowed to evolve; the graph keeps the history instead of overwriting it.
- Full source attribution. Every statement carries its origin. When the knowledge base answers, you can trace each claim to the meeting or intake session it came from. The knowledge stays checkable — it never degrades into "the system says so".
Step 3 — Converse: DigiME
DigiME is the first use case built on the MentX knowledge base: a digital knowledge copy of your key person you can converse with. It answers in his knowledge, his reasoning style and his voice of thought — with sources under every answer. Read how a DigiME conversation works →
What does it ask of your expert?
Presence in meetings he already attends, plus the intake sessions. No writing, no maintaining a wiki, no "documentation Fridays". The expert also keeps veto rights over his profile: he reviews what enters his digital knowledge copy and can strike anything. Capture works with him, not on him.
Does the knowledge base go stale when the expert leaves?
The graph keeps answering from everything captured, with dates and sources intact. New knowledge from the team can extend the same Knowledge Space, so the base stays living rather than becoming an archive. See what the knowledge base unlocks over time.
Do it yourself: the guides
The methods behind the capture, written to be usable with or without us:
Capture a retiring founder's knowledge
Map, prioritize, capture from use, verify while he can correct.
Build a knowledge transfer plan
Count backwards from the date; match instruments to knowledge types.
Identify your concentration risk
A one-month diagnostic: interruptions, absence test, paper-trail check.
Succession planning for tacit knowledge
Give knowledge its own workstream next to the legal track.
Onboard a successor with the base
Day-one access, query-first habits, a capture backlog from gaps.
Run a key-person dependency audit
Four strands, real-case replaceability tests, board-ready reporting.
Interview an expert properly
Cases not opinions, probe the forks, return in layers.
How does this compare to what you already do?
Most companies already have something: SOPs, a wiki, an exit-interview template, a mentoring pair. Honest comparisons, including when the alternative is enough:
SOPs vs a living knowledge base
Procedures cover the foreseen; judgment covers the rest.
Exit interviews vs continuous capture
Why timing decides what capture yields.
Documentation project vs knowledge graph
Why the big writing push stalls at 60%.
Generic AI chatbot vs DigiME
A bot over documents has a documented ceiling.
Wiki vs personality-aware knowledge base
The busiest expert writes the least.
Hiring vs capturing
A successor fills the role, not the context.
Mentoring vs digital knowledge copy
The gold standard, minus its four limits.
Full source attribution
Every answer carries its sources — who said it, where, and when.
GDPR-native, EU-based
Built for European companies from day one.
Expert veto rights
The expert keeps veto rights over his profile.
Your own Knowledge Space
Data stays in your company's own Knowledge Space.
Limited to 5 companies
A guided intake and your first Knowledge Space at founding-partner conditions.
Message Nicolas for an intro call