# Your company’s knowledge, there for everyone. With exactly the rights each person already has. > Staff ask Claude or ChatGPT and get answers from your documents, emails and systems, with sources and within their rights. Fewer questions, no knowledge silos. Source: https://schuetze-web.com/integrations/company-brain Staff ask their AI and get the answer from your documents, emails and systems, with the source. Fewer questions land with the decision makers, knowledge no longer sits with single people, and the brain grows by itself with every system it reads and every chat. With skills it also works the way your company works. ## What changes ### Fewer questions to decision makers Prices, agreements, how things are done: staff find the answer themselves, with the source, instead of asking the managing director. A decision is made once and then it is known. ### No knowledge silos What one person knows is there for everyone who may see it. When someone is on holiday or leaves, their knowledge stays in the company. ### Grows by itself Documents, emails and systems flow in automatically. What gets clarified in chats is proposed as new knowledge and, once confirmed, answers the next question. ## Who may see what The brain takes over the rights from the connected systems: whoever may not open a contract in the document store does not get its content from the AI either, not even in a summary. The same question from two people: - Sales · CRM, contracts, price lists · Read - Support · Tickets, product documents · Read and add - Management · Everything · Confirm ## How the brain grows Nobody has to keep a wiki up to date. The brain reads along in your systems and learns from the questions your team asks. - Read Documents, emails, CRM and tickets flow in automatically, every day. - Ask Staff ask their AI and get answers with their sources. - Learn What gets clarified in a chat is proposed as new knowledge. - Confirm The person responsible confirms it, and from then on everyone with access knows it. ## Not just knowledge, but know-how Skills capture how your company does things: how an offer is built, what a contract is checked against, what minutes look like. Your best people describe it once, and everyone’s AI works that way, with the same rights as the knowledge. ### Write an offer In your structure and tone, with current prices and terms from the brain. ### Check a contract Against your playbook: liability caps, notice periods, data protection clauses. ### Take minutes In your format, with decisions, owners and deadlines, filed where they belong. ## One question, two ways A new colleague wants to know how discounts are approved. ### Today - She asks her team lead - He isn’t sure and forwards it to the managing director - The managing director answers two days later, between two meetings - The answer sits in a single email thread - Next month someone else asks the same question Two people interrupted, two days lost, and the answer is gone again. ### With the company brain One question, an answer in seconds with its source, and nobody was interrupted. ## What your team asks Prepare a customer meeting in two minutes. New colleagues find their way without asking every day. Answers from earlier tickets instead of starting from scratch. Know what was decided, and why. ## Set up in three steps ### Connect systems Document store, email, CRM, wiki, tickets: we connect what holds your knowledge, whether Microsoft 365, Google Workspace or your own systems. ### Take over rights The brain uses the roles and rights that already exist in these systems. Nothing has to be maintained twice. ### Roll out to the team Your staff use the brain in the AI they already work with. ## You stay in control Every answer names its source. New knowledge from chats only goes into the brain once the person responsible has confirmed it, outdated knowledge can be marked or removed, and a log shows who asked what. ## Questions ### Which systems can be connected? Most of what holds knowledge in a company: Microsoft 365 and SharePoint, Google Workspace, email, CRM, document management, wikis, ticket systems, and your own systems through their API or database. In the intro call we look at yours. ### How are the rights enforced? The brain checks every answer against the rights the person has in the source system. What they cannot open there, they do not get from the AI, not even in a summary. ### Does the AI see everything? Only what you connect, and each person only what they may see. You decide which systems and folders flow in. ### What if knowledge is wrong or outdated? Every answer names its source, so it can be checked. Newer documents take precedence, outdated entries can be marked, and new knowledge from chats is only added once the person responsible confirms it. ### Where is the data stored? We decide that together with you, depending on your requirements and the systems you use. The knowledge stays under your control and can be deleted at any time. ### What is the difference between knowledge and skills? Knowledge is what your company knows: documents, agreements, decisions. Skills are how it does things: the steps, structure and tone for an offer, a contract check or minutes. The brain holds both, and both follow the same rights. ### Does it replace our wiki? It can, but it doesn’t have to. An existing wiki is read in like any other source; the difference is that nobody has to keep the brain up to date by hand. --- Contact: book an intro call at https://schuetze-web.com/book or write to simon@schuetze-web.com.