Partner programme: earn 20% on every referred purchase.Partner programme: 20% per referred purchase

Become a partner for freeBecome a partner

Company Brain: find, understand and share company knowledge.

A colleague is away, and nobody can find the right answer? A Company Brain makes selected company knowledge available to authorised staff, with traceable sources, clear ownership and boundaries.

2026-09-27
Illustration: Four glass tiles for analysis, design, implementation and optimisation

What is a Company Brain?

Think of a shared place for your team’s recurring questions. Instead of searching several folders and old emails, a colleague asks in everyday language. The system searches approved documents and drafts an answer with a source reference.

“Company brain” is a metaphor, not a thinking replacement for your staff. AI does not automatically know what people carry in their heads. That knowledge must first be documented. Nor does it decide which rule applies in your business.

How it works: six simple steps

1. Choose one question

For example: which documents does a colleague covering a role need to assess a complaint? Start with one bounded knowledge area.

2. Gather reliable knowledge

Organise procedures, documents and practical knowledge. An accountable owner identifies the current version and missing information.

3. Set access boundaries

Not everyone should see everything. Define and test who may read each source before connecting it. Keep confidential areas separate.

4. Ask in everyday language

A colleague asks a question. The assistant retrieves relevant passages from approved sources; training a model on all company data is not necessarily required.

5. Check the answer and source

Answers point to their basis. Missing or conflicting information should be flagged and referred to a person. Test this behaviour in the pilot.

6. Keep knowledge current

Named owners maintain changes. Use real questions to review answer quality, access permissions and the effort needed to check results.

An example from everyday work

The colleague handling complaints is on holiday. Their cover asks: “What do we need before we can assess this complaint?” The assistant finds the approved procedure, lists the required documents and links to the relevant passage.

If a special rule for this customer has not been documented, a person must clarify it. The assistant must not invent a commitment. This is an illustrative workflow, not a measured customer case.

What it can support, and what people must decide

A Company Brain can support search, onboarding and cover during absences. We check whether it saves time using your typical questions and the effort of reviewing answers. A convincing answer alone is not enough.

Technology cannot replace reliable sources or accountable people. Provider, hosting location, privacy, permissions and allowed actions are agreed before implementation. If a maintained guide is sufficient, we recommend that simpler start.

Start with a free knowledge consultation

In 30 minutes, we examine one knowledge bottleneck in your business. You do not need a finished knowledge base or to upload confidential documents.

  • Which question keeps coming up, and who needs the answer?
  • Where is the authoritative source, and who keeps it current?
  • What should come next: a guide, better structure or a bounded pilot?

No obligation. The optional preparation questionnaire is sent only after a confirmed booking. A pilot is offered separately only when it fits your needs.

Four phases with verifiable deliverables

Assessment and prioritisation

Deliverable: a defined use case with baseline measures, data sources, accountable owners and unresolved prerequisites. Expected benefits remain estimates until measured.

Solution design

Deliverable: a workflow specifying systems, permitted actions, human approvals and exception paths. We establish where fixed rules suffice and where an AI model is useful.

Pilot and acceptance

Deliverable: a bounded workflow with agreed test cases, logging and acceptance criteria. Before production approval, quality, rework and handovers are compared with the baseline.

Operation and improvement

Deliverable: defined responsibilities for monitoring, exceptions and changes. Further optimisation follows actual usage, quality and total cost. Ongoing operation is agreed separately in the scope.

What to bring to the consultation

Describe a recurring task: its trigger, current steps, systems and intended outcome. Anonymised examples, known volumes, handling times and exceptions are useful. Name an accountable process owner. Do not include credentials or original personal records in the initial enquiry.

From consulting findings to a decision

Each phase ends with a decision: start a pilot, improve data or processes first, or postpone automation. Before delivery, we agree scope, system access, responsibilities and measurable quality goals. A workshop alone is not an approved production system.

How effort and cost are established

Interfaces, data quality, exceptions and approvals determine effort. Account separately for setup, model or software usage, hosting and human review. A specific proposal follows the agreed scope; it does not justify an advance fixed-price or savings guarantee.

Choose your starting point

Ready-made package for trades businesses

Fixed price instead of a project: a clearly scoped assistant for businesses in DACH.

Request a strategy call

If you can name the operational priority clearly, we can structure the right entry path fast.

Start potential analysis

If you want to prioritize a real process, a few clear inputs are enough for a strong first assessment.