Continuity risk
Critical client and process knowledge was concentrated among a limited number of employees and owners. Absence immediately meant lost context.
← All projects
Project case · Knowledge continuity
From knowledge in people’s heads to an organisational memory that grows stronger every day.
For a professional services firm, we built a living Company Memory that brings together documents, workflow knowledge and employee expertise. Six users can now ask the agent about clients, engagements and company processes while retaining source control, access rules and an audit trail.
Sector
Professional services
Users
6 employees
Core objective
Knowledge continuity
Data source
Google Drive + workflows
The system in practice
From separate files to visible, governed organisational memory.
The knowledge graph makes relationships between documents, clients, workstreams and processes visible. In the vault, each knowledge item retains its audience, status and source.
Executive summary
Knowledge continuity became a system capability, not an individual responsibility.
The breakthrough was not simply better search. For the first time, the organisation gained one operational memory connecting documents, client context, process knowledge and lessons from completed work.
Critical context is therefore no longer dependent on one experienced employee being available. The agent makes that knowledge accessible when needed, while governance determines which information is reliable and visible.
Starting point
A growing firm with an invisible dependency on key people.
Slow onboarding
New employees received documents and fragmented explanations, but not the full story behind clients, decisions and working methods.
Knowledge lost after delivery
Valuable lessons from engagements and workflows were not systematically reused and disappeared into heads and folders.
The intervention
Not a chatbot on top of a folder, but a governed memory for the entire operation.
The solution connects four layers into one working system. Each layer addresses a different part of the knowledge problem.
01
Sources
Existing Drive documents and knowledge from completed workflows.
02
Memory vault
Summaries, relationships and context around clients, processes and engagements.
03
Governance
Status, scope, source, human review and a growing audit trail.
04
Agent
One conversational interface that retrieves only context permitted for each user’s access level.
The shift
From person-dependent to institutional memory.
01
Knowledge lived in heads and separate folders.
→Knowledge is systematically captured in one connected organisational memory.
02
Colleagues needed to know who to ask.
→The agent retrieves relevant context about clients, engagements and processes.
03
Onboarding started with searching and verbal handovers.
→New employees gain a coherent starting point for how the company operates.
04
Context disappeared after work was completed.
→Completed workflows enrich memory and build an audit trail.
Governance by design
The agent knows not only what the organisation knows, but which knowledge may be used.
Canonical
Leading knowledge that the organisation and agent may use as reliable context.
Agent-managed
Current document knowledge maintained by the agent pipeline and made available when safe.
Needs review
Uncertain or sensitive information remains outside agent context until reviewed by a person.
Scope and access
Each item is linked to the organisation, a client or workstream, or restricted to founders. The agent builds its answer from the signed-in user’s permissions, so different roles can receive different context.
Operational effect
The company keeps learning, even when people change.
Six users now work from the same accumulated company context. Knowledge remains available during absence or departure, onboarding gains a much clearer starting point and each new workflow can enrich collective memory. At the same time, a verifiable audit trail captures where knowledge came from and how it is used.