Home / Services / Institutional Knowledge

Institutional Knowledge
Mapping

Afraid of losing twenty years of know-how the day one key person leaves? The way your company actually works is written down nowhere. We extract it, map it and turn it into an asset you own, before the day you need it.

"Your best people are not irreplaceable because they work hard. They are irreplaceable because nobody wrote down what they know."

When you need this

  • A key person is leaving. Retirement, resignation or succession: the clock is visible and the knowledge walks out with them.
  • You are selling or raising. "The business is in the founder's head" is a valuation discount. A mapped business is a sellable business.
  • Onboarding takes six months. Every new hire learns by osmosis because the real process exists only as folklore.
  • You want to automate. Automation built on the documented process fails, because the documented process is fiction. The map comes first.

How it works

01

Extract

Structured interviews with your key people plus your documents, contracts, systems and data. AI does the heavy lifting; judgment does the sense-making.

02

Map

One coherent picture of how the business actually runs: processes, decisions, dependencies, risks and the unwritten why behind them.

03

Operationalize

The map becomes onboarding material, a queryable knowledge base, and the blueprint for what to automate next.

$100M+
revenue business mapped end to end
667
contracts distilled into one term sheet
40+
interviews and recordings synthesized
Weeks
not the months a consultancy takes

These numbers come from one real engagement: a $100M+ media group whose operating logic lived in a handful of heads. The full story is here.

Common questions

How is this different from writing SOPs or a wiki?
Wikis capture what people remember to write down, which is the least valuable layer. Interviews plus document analysis capture the why: the pricing logic, the risky dependencies, the client quirks, the decisions nobody documented. And unlike a wiki, the output is designed to be used: onboarding, succession, automation.
Will my people cooperate?
Usually yes, and more openly than you expect. A structured interview by an outside operator is flattering, not threatening, when it is framed as capturing their expertise rather than replacing them. Framing is part of the engagement.
How does it stay current?
The initial map is a snapshot; staying current is a light recurring rhythm: periodic re-interviews of changed areas plus automated capture from the systems you already use. We scope this honestly, because a map nobody maintains is a report in a drawer.

Whose head is your business in?

If a name came to mind, that is the conversation. It is cheaper before they resign than after.

Start the mapping