Tools are rented, knowledge should not be: who keeps your institutional memory?
· 5 min read · Your Own Software
A clinic has used the same booking program for five years. Which patient tends not to show up at which hour, which treatment rises in which season, which reminder actually works — it is all in there. One morning the program announces: "our prices have changed, the old plan is being retired." What does the clinic do?
Most accept. Because five years of knowledge are inside that program. Moving it is hard; losing it is impossible. This is the invisible price of renting: when you rent the tool, you also pawn your knowledge.
Three things end up in someone else's hands
Data. Patient, customer and company records sit on the provider's server. There is an "export" button, but the file it produces does not go into another system as it is. The relationships built up over the years — notes, tags, history — get lost.
Institutional memory. The workflow has been shaped around the program. Staff have learned "press this key in the program", not "this is how we do this job". When the program goes, the method goes with it.
Control. Price, features, access, whether it continues at all — all of it is the provider's decision. You are a user, not the owner.
The difference between a tool and knowledge
What can be rented is the tool: servers, e-mail services, payment infrastructure. These are standard, replaceable and create no dependency.
What should not be rented is knowledge: how you know your customers, how you run your process, which data you base your decisions on. This accumulation is the business's real asset and it grows every day. If it is growing inside someone else's product, it is becoming someone else's asset.
How to protect it
- Separate the critical processes. Which job, if it stops, stops the business? The systems for those processes should belong to you.
- Keep the data in your own infrastructure. Even when a system is rented, the database can be yours; ask for it.
- Document the process, not the program. Have a document called "the booking flow", not "booking in program X".
- Ask for an exit plan. Ask every provider: if we leave tomorrow, in what format and how quickly do we get our data?
What ownership means
The code is yours. The data is yours. The infrastructure is in your name. The system runs under your own logo and your own address. If the provider disappeared tomorrow, the system would keep running. You choose a partner for maintenance; you are not bound to one.
Every system Doveify builds is delivered on this principle. Because tools are rented. Knowledge should not be.