AI and knowledge
What is a knowledge system for a business?
Direct answer
A knowledge system is the way a firm keeps the answers, documents and decisions people keep asking for, so the next person can find the current version and trust it. It can be a structured library, a search layer over approved files, or an assistant that will only speak from those files. A shared drive only stores what was uploaded; a knowledge system adds an owner and a rule for what is current.
The problem it is for
Every small firm has a set of questions that are answered from memory: what we send a new client, which clause we no longer use, how this clinic prepares a particular visit, which drawing status means “issued”. The answers exist. They exist in a partner's head, a departed employee's laptop, and three PDFs with similar names.
A knowledge system is justified when that repetition has a cost: slow onboarding, inconsistent advice, or a client given last year's version. It is not justified as a place to pour every file the firm has ever touched and hope search will cope.
How it differs from a drive, a wiki, and a chatbot
A shared drive is storage. It will not tell you which of two files is the one the firm stands behind. A wiki can be a knowledge system if someone retires old pages and every important answer has an owner. Most wikis become a second drive, written in paragraphs.
A chatbot trained on the open internet, or on an unreviewed export of the drive, will answer fluently from both the current policy and the one you abandoned. That is worse than no search, because it hides the conflict. An assistant belongs in a knowledge system only after the sources are chosen and the outdated ones are excluded.
What a small firm needs first
Start with the twenty answers that are asked every week, written as the firm wants them said, each with an owner and a date. Put the current templates next to them. Decide who may see client-specific material and who may see only the general method. Then, if volume justifies it, add search or an assistant over that set.
Client files are not the same library as the firm's method. A matter, a patient, or a tax working paper is a record with access rules. Mixing it into a general “ask me anything” box is how confidential material gets into an answer for the wrong person. The data-privacy guide covers why that split matters.
Someone has to retire the old answer
The system fails on the day the firm changes its mind and leaves both versions in place. Retirement is a feature: an old page is marked, redirected, or removed, and the assistant can no longer quote it. Name the person who does that. A knowledge system without that person is a drive with a search bar.
Sunbeam builds the library, the access and, where it has earned it, the assistant. We start from the questions the team is tired of answering, not from a catalogue of models.