Company Brain AI: Ready Platform or Custom System?
Choose a ready knowledge platform or a custom company brain by checking sources, permissions, write-back and seat economics against one workflow.
A company brain gives people and agents shared context from documents, systems, decisions and rules. The useful choice is the smallest route that meets your permission and process requirements.
Syntalith
A company brain connects the information people use to make decisions: documents, CRM and ERP records, events, procedures and approved outcomes. An employee can receive an answer with its source. An agent can receive the context needed for one task, follow its authority rules and return an approved result to the shared record.
At Syntalith, the first company-memory workflow starts from €6,000 net. We scope one process such as preparing a proposal, checking a policy exception or assembling a client brief. The Company Brain AI service covers the implementation path; this guide helps you decide whether a ready platform already fits.
Three levels of shared knowledge
Start by naming the job your team needs done:
| Level | Core job | A suitable route |
|---|---|---|
| Enterprise search | Find a current document across known sources | Search in the systems your team already uses |
| Knowledge assistant | Answer questions with citations and source permissions | A ready platform when its connectors and access model fit |
| Company brain | Give people and agents context, decisions and approved outcomes over time | A custom system when the process crosses sources or writes back to systems |
The third level needs more than retrieval. It needs identity, source ownership, effective dates, conflict handling and a record of who approved a result. If those elements do not affect the work, a simpler level may be the better purchase.
The four checks that decide the route
Source shape
List every source needed for the first workflow. Include shared drives, ticket systems, CRM and ERP records, databases, scanned documents and the mailbox where exceptions arrive. A ready platform is strongest when the sources sit in one supported ecosystem. A custom connector becomes relevant when a decisive record lives in a specialist system or an archive that the platform cannot reach.
Permission shape
Write down which roles may see each source and which actions each role may request. Permission should be checked before context is assembled. A person asking about one customer may have access to a contract while another role may see only the status. An agent may need a narrower scope than either person because its task is limited.
Test these cases with real role definitions:
- a user has access to the source but only for one business unit;
- a document is superseded while its history remains relevant;
- a user can read a record but cannot change it;
- an agent prepares a change that requires approval from a different role.
The permission-aware RAG guide explains why access checks belong before generation.
Memory shape
Decide which facts should remain useful after a conversation ends. A system may need the current contract, a prior exception, a decision owner and the date for the next review. Store provenance, effective time and access scope with the record. Keep a proposed agent result distinct from an approved decision.
Action shape
The route changes when the system must prepare or perform work. Retrieving a procedure is a knowledge task. Preparing a CRM update, creating a task or sending a customer message introduces an approval boundary. Define each tool, the fields it may change, the person who approves it and the evidence saved with the action.
Ready platform or custom system?
Use this comparison with the product and security owner:
| Question | Ready platform tends to fit | Custom system deserves consideration |
|---|---|---|
| Where is the knowledge? | One ecosystem with supported connectors | Several business systems or specialist archives |
| What is the output? | Search and cited answers | Context for a defined multi-step process |
| How are permissions managed? | Source permissions map cleanly to user roles | Roles and purpose require an additional policy layer |
| Does the system write back? | Answers stay in the knowledge product | Approved tasks or status changes return to CRM or ERP |
| What does the budget look like? | Subscription multiplied by seats and terms | Build, hosting, maintenance and model usage |
| Who owns operations? | Vendor plus an internal platform owner | Your team or an implementation partner with a handoff plan |
A ready platform can be a good answer for a company that wants searchable procedures across one workspace. A custom system can be a good answer when the first workflow depends on live records, decision history or controlled actions. Run the same test set through both routes before signing.
Evaluate a platform on your own cases
Prepare a small evaluation pack from the first workflow:
- questions with one current source;
- questions where two versions conflict;
- a role that must receive a redacted answer;
- a question whose answer is absent from the sources;
- an action that should be prepared and held for approval.
For each case, record source accuracy, permission result, freshness, response time, reviewer effort and the cost of the query. A vendor answer about security or search quality becomes useful when it is tied to these cases and to the contract terms.
Ask how you can export documents, metadata, embeddings, decision records and audit logs. Ask who can pause indexing, revoke a connector and delete a record. The exit path belongs in the purchase decision because company memory is operational data.
Model the two-year cost
Use the same horizon and assumptions on both sides:
Ready-platform cost = seats × quoted monthly rate × months
+ setup, connectors and extra usage
Custom-system cost = implementation
+ hosting and maintenance × months
+ model usage
+ internal data preparation and reviewSyntalith lists the first company-memory workflow from €6,000 net. The pricing page lists the implementation specification from €1,200 net, which can be credited toward a commissioned build. Treat both as our offer starting points, then add the sources, tests, approval path and support you actually need.
Seat economics can favour a ready platform for a large group with a simple question-and-answer job. A small team with a complex ERP workflow may reach a different result. Substitute the rate in the quote, the actual seat count and the real maintenance hours.
A decision you can hand to the owner
Choose a ready platform when its connectors, permission model and export terms cover the first workflow. Choose a custom route when a named process needs cross-system context, decision memory, controlled write-back or a deployment boundary the platform cannot provide.
For the first release, name one workflow, one owner, one source set and one approval path. A free process scan takes 30 minutes with an engineer and is followed by a written takeaway within two business days. Bring the source list, role map and one decision people currently reconstruct from email.
Book a free process scan | See Company Brain AI | See pricing
FAQ
What is a company brain AI?
It is shared operating memory for people and agents. It connects documents, records, events, rules and approved decisions, then supplies the right context to a person or an agent. Syntalith scopes the first workflow from €6,000 net.
When does a ready platform fit?
A ready platform fits when your knowledge sits in one supported ecosystem, its permission model matches your roles and the work ends with cited answers or search. Compare the vendor quote at your actual seat count and confirm the export path.
When should a company build its own system?
Consider a custom system when sources include an ERP, databases or specialised archives, when permissions cross several systems, or when an agent must prepare an action and return an approved result to company memory.
Is a company brain the same as RAG?
RAG retrieves relevant passages for a response. A company brain adds identity, permissions, source freshness, decision history, approval and controlled write-back for a defined process.
How much does a custom company brain cost?
Syntalith lists the first company-memory workflow from €6,000 net. A complete quote also covers integrations, data preparation, evaluation, hosting, maintenance and the approval path.
Related articles
Free process scan
Start with a free process scan.
- A 30-minute call with the engineer who would lead the work.
- A review of the processes that cost you the most time and money.
- A written summary of what to automate first and the likely cost range.
The scan chooses one process to assess, and within 2 business days you receive a recommendation, including when a simpler route is the better fit.
€0
30 minutes · written takeaway within 2 business days
Times are shown in your own time zone. We work with clients across time zones.
Describe the process in the form