Customer agreements
Exactly what was promised about price, delivery time or warranty — and by whom. Often it’s in one inbox, sometimes it was only said out loud.
Bedrijfsgeheugen: definition, where it leaks and how to measure it
Every company has a bedrijfsgeheugen. The question isn’t whether it exists, but how much of it resides in people and how much in the organization. That difference determines what happens during vacation, illness, someone’s departure, or an acquisition.
Definition
A bedrijfsgeheugen is the complete set of knowledge, agreements, and reasoning recorded in a place the organization can access—and not in the heads, mailboxes, or personal files of individual employees.
It's not just about what has been recorded, but whether it can be found when someone needs it, and whether it's correct.
30 minutes, no obligation. We first look for the biggest knowledge or continuity risk. A paid deeper analysis only follows if there is enough value.
Why a company has a memory
An organization does hundreds of things every day that were decided on at some point. Why that one customer has a different payment term. How you get a rush order through. Which supplier you no longer call and why. Who you need to have if the system goes down.
Almost none of it is written down. It lives in people, in habits, in “that’s how we’ve always done it.” As long as the same people are there, it works fine. It isn’t a problem — until suddenly it is.
A bedrijfsgeheugen doesn’t leak with a bang. It leaks through a vacation, a bout of flu, a resignation, and an acquisition—and in between, nobody notices.
The eight places where it leaks
In practice, knowledge loss always comes from the same places. These eight form the basis of every scan we do.
Processes
How the work really happens, not how it's described in a manual. The difference between the two is usually the interesting part.
Systems and integrations
Which data is stored where, what’s the source of truth, and what gets retyped manually because two systems don’t communicate.
Decisions
Not what was decided, but why. Without the reason, every decision gets revisited a year later.
Key personnel
The people whose absence brings things to a standstill. Every company has them; almost none have mapped them out.
Suppliers and contracts
What was agreed, when it expires and who discussed it at the time.
Work instructions
The steps for tasks that don’t happen every day. Those are exactly the ones people forget, and exactly the ones that take time when someone is absent.
Access and rights
Who can do what. It becomes noticeable when the person who knew isn’t available.
Do it yourself
Type over this order number. Once is doable. Forty times a day, every day, is a job.
NL-2026-8841-KX
The clock starts as soon as you begin.
What a business memory isn’t
The concept is easily confused with a system. It is not: it is a property of an organization, which you can support with systems.
| Not the same as | Difference |
|---|---|
| A CRM | One system for customer data. Bedrijfsgeheugen also includes processes, decisions and the reasons behind them |
| A knowledge base | A place where documents are stored. That says nothing about whether they’re correct, can be found, or are used. |
| Document management | It's about files. Most business memory is not stored in files |
| A wiki | A tool. Without an owner and maintenance, a wiki is wrong within a year, and wrong is worse than empty |
| Digitalization | Digitalization means putting knowledge into systems. Safeguarding it means making sure the organization can access it when needed |
How to measure it
Business memory is not visible until it fails. That is why you measure it upfront, with questions that have a factual answer.
The self-assessment
Twelve questions covering the eight areas above. Five minutes, and you'll immediately see where you stand.
Take the self-assessment →
The Completion Index
Measure whether what you started last year is still there. Safeguarding and ownership are two of the four components.
To the Afmaakindex →
De Frisse Blik
The extended version, together with your team. Where work is duplicated, where knowledge depends on one person.
Book a Fresh Look →
Where it hurts in practice
| Moment | What happens then | Read more |
|---|---|---|
| Someone leaves | Knowledge walks out the door. When a key person leaves, part of the work is under pressure for months | Knowledge retention |
| Vacation or illness | Work comes to a halt or goes wrong because nobody knows exactly how a task is done | Work instructions |
| Systems don't talk | The same data in two places, and nobody knows which one is correct | Connect systems |
| Handover or sale | A buyer pays less for knowledge that’s in people’s heads than for knowledge that’s documented | Due diligence |
| Bring in AI | AI works with what’s documented. If there’s little to work with, it delivers little — regardless of the model | AI adoption |
This last point will become clear fastest in 2026. Companies bring in AI and find that it delivers little. The cause is rarely the model and almost always what lies beneath it: there isn't enough information on record to work with. The figures consistently point in that direction.
Where the term comes from
The idea that an organization has a memory isn't new. In organizational studies, it exists as organizational memory: the entirety of stored knowledge that allows an organization to reuse past decisions. This concept is academic, broad and rarely practical.
We use Bedrijfsgeheugen as the practical Dutch version, tailored to companies with 3 to 250 employees: not as theory, but as something you can measure, fix, and maintain. The eight components above are how that takes shape.
This definition is free to use, provided you cite the source. If you adopt or refine it, we’d love to hear from you — a concept becomes clearer through use, not ownership.
Figures and context: AI use in SMEs, why AI projects fail and preserve knowledge when employees retire.
Read more: Excel as a CRM — where the limits are.
Read also: Company Brain versus Bedrijfsgeheugen.
\nThe way it works now
- The appointment is in one colleague's mailbox
- Data is manually retyped from one system to another
- The person who knows is on vacation
- No one can see afterwards why this decision was made
As it is
- The agreement is stored with the client, findable for everyone
- Once entered, information flows through to the rest
- Work continues, even if someone is absent
- Every decision has a source, an owner, and a date
drag with your finger
What if Peter leaves?
Two out of five rules on this page disappear. That's how it feels when knowledge isn't part of the company.
What is your next step?
Free self-assessmentTwelve click questions, three minutes, immediate score and your biggest risk.
Fresh LookBusiness case, benchmark and priority. Settled once we build after this.
What it costsFixed price per package, no price per user, no hourly billing.
From the fieldWhat changed at companies that started with this.
Also good to know: frequently asked questions · security and data · terms and conditions · partners · research and figures · templates · what's changing · where you start
Where does the process break down in practice?
Agreements and work instructions are scattered across people's heads, documents and systems. What must a colleague be able to find without asking?
Direct answer
First make the real bottleneck, the owner and the desired outcome explicit. Then choose the smallest working solution and measure whether it demonstrably delivers value.
What we do
We connect analysis, business intelligence, data and execution so you don't get stuck in advice or loose tooling.
How it works
- We clarify the current situation, data and the real bottleneck.
- We determine the smallest working solution, owner and measurable outcome.
- We implement or prioritize the next step and verify the result.
- We secure what works and stop or fix what doesn't work.
What you get
A concrete analysis, priorities, decision criteria, an executable next step and visibility into what needs to be built, integrated or secured next.
For whom and whom not
Right for Dutch SMB organizations that want to solve a concrete process, knowledge, data or AI problem. Not for organizations looking only for a generic tool demo or unproven AI promise.
Costs and choice
Price and scope depend on the chosen next step. View the current fixed packages and pricing logic at pricing for digitization.
Risks and concerns
We work step by step, make assumptions and ownership explicit, use only the minimum necessary data, and maintain human control over decisions and execution.
Frequently asked questions before you decide
Does everything have to be done at once?
No. The preference is one clearly defined problem with a measurable outcome, then scale up.
What does it cost?
The current pricing and package logic is on the pricing page; custom work is only chosen if the scope really requires it.
How do you prevent a trajectory without results?
By defining the problem, owner, success metric and stop criteria in advance, and doing readback and verification after each step.
How we assess your situation
We map your current process, systems, exceptions and costs. Only then do we advise whether an off-the-shelf solution, a custom integration or another approach makes sense.
From insight to execution
This page supports the following concrete solution.
Continue in Powerhouse
Choose the next step that fits what you are viewing now.