How Paloren builds a company brain: the technical specification
The boundaries, permissions and checks behind a company brain, written for your technical team.
The boundaries, permissions and checks behind a company brain, written for your technical team.
A company brain is a unified, governed, time-aware knowledge layer over a business's documents, records and conversations, queried with permission-aware, source-cited answers.
It connects the systems you already run so your team asks in plain English and gets answers with sources and access rules kept. Paloren builds them; see the company brain service.
Our toy-versus-product framing is brand positioning: a demo works for its builder on clean data; a company brain works for your whole team on real data, with a named owner.
A company brain is only as trustworthy as its boundaries.
This specification walks one worked example (account A-104, two open tickets, one meeting note) through the six decisions we make before a first answer ships: the source and identity contract, which records may be calculated and which documents may only be quoted, how permissions reach the answer and are rechecked, how freshness and deletion are enforced, which evaluation cases gate the release, and who operates the system afterwards. A typical first release takes 8 to 12 weeks.
What this can change for your team
Source and identity contract: what we decide before the first answer ships.
How we make this work
The request is: "What is unresolved for account A-104 before its renewal review?" The contract separates the customer identity from the identity of the person asking.
Records for calculation, documents for context: what we decide before the first answer ships.
How we make this work
Two approved issues are in scope: T-31 is open and T-44 is pending. A versioned query over the permitted structured rows returns an unresolved count of two. The language model does not estimate the count from retrieved text.
Permissions that reach the answer: what we decide before the first answer ships.
How we make this work
In this example, the connector can ingest more than U-18 may read. Connector access is not permission to disclose that content to the user.
Freshness, deletion and recovery: what we decide before the first answer ships.
How we make this work
The ticket feed has a maximum age of 30 minutes. A last successful sync at 09:00 cannot support a current-status answer at 09:45. The brief labels issue status unavailable rather than presenting the old count as current.
Evaluation cases and release evidence: what we decide before the first answer ships.
How we make this work
Run evaluation cases with a versioned fixture pack, including source snapshots, role assignments, query definitions and model configuration.
Operating ownership after release: what we decide before the first answer ships.
How we make this work
A read-only release still needs someone responsible when a source changes. The handover assigns roles to named people before live use, not to a shared inbox with no accountable owner.
When a custom build is and is not the right choice: a vendor copilot wins when the question lives inside one tool's data. A bundled SaaS knowledge tool wins when standard needs fit its shape.
Self-hosted patterns win when your team wants the control and can run the plumbing. An in-house build wins when your engineers have the time and a named owner this quarter.
A Paloren company brain wins when questions cross your CRM, help desk, documents and chat, and one set of access rules has to hold across all of them. These examples are illustrative, not client results. Adjacent guides: AI implementation guides.
Send the specification to your CTO or IT lead with your questions. A Paloren engineer replies within one business day, and a 45-minute technical review is free before any scope is agreed.
Review this specification with usA typical company brain engagement runs 8 to 12 weeks. The timeline depends on the number of sources, the complexity of joins, and the volume of documents to test.
Structured data from your CRM, ERP, service system or reporting database. Documents from approved folders, wikis, or help systems. The sources must have APIs or scheduled data delivery. We plan which sources and fields before ingestion.
Source definitions and access rules are agreed upfront. Changes trigger re-testing of the evaluation set before release. Your business owner approves any changes to what people can see or ask about.
No. Rows and passages are filtered before they reach the model, and the permission version is checked again before the answer is returned. If access changed during generation, the answer is withheld.
The evaluation set includes at least 2 revoked-access cases and 1 cross-account case, and any disclosure blocks release.
Weeks 1 to 2: record source IDs, identity mappings, permitted fields and update signals for each system.
Weeks 3 to 7: join approved records, retrieve only authorised passages, attach source versions and timestamps.
Weeks 8 to 10: run the evaluation set against missing, conflicting, revoked and stale inputs; fix release blockers.
Weeks 11 to 12: agree alert routing, pause and restore procedures, change approval and support hours. Typical total: 8 to 12 weeks, USD 60k to 150k.
A source and identity contract for every connected system, with owners named.
A bounded answer path: approved records for calculation, permitted passages for context, sources cited.
An evaluation set covering missing records, revoked access, stale feeds and deletions, with recorded results.
A runbook and named operators for alerts, pauses, restores and change approval.
A Paloren company brain takes 8 to 12 weeks from source contracts to handover. The range depends on how many systems connect and how complex the permission rules are. Timelines are indicative until the project is scoped.
Typical total: 8 to 12 weeks, from $60k, typically up to $150k. The top of the band comes from more connected sources, deeper permission work and record-system integration. Prices are indicative until scoped.
Documents, wikis, chat tools, email, code repositories and record systems such as your CRM and help desk. Each source gets a written contract covering what is indexed, how fresh it must be and who can see it. The source list is agreed in the first week.
No. Permissions are enforced at retrieval, not at the prompt, so a query returns only records the asking user is authorized to see. We test this boundary with evaluation cases before release, including denied-access attempts.
A vendor copilot suits one tool's data; a company brain spans every system you run with one set of access rules. If your questions cross tools, or you need deletion and freshness guarantees, a governed build is the better fit. Sometimes the answer is that you don't need one yet.

Want your technical team to pull this apart before you commit?
Review this specification with us