Skip to content

Company brain implementation

In short. Aiwah Labs builds company brains: internal AI knowledge bases that answer staff questions from your own documents, show the source, and follow who may open each file. The first use case is live within a week, and we build on it. Setup is typically from about $2,500, with no monthly maintenance fee. You own the code and the data.

Available inBengaluruDubaiLondon, Ontario

Documents arranged through checkpoints with a separate exception path
Starting price
$2,500
Typical one-time setup, in US dollars. No monthly maintenance fee.
Timeline
First use case in 1 week
We build on top of it, one use case at a time.
You own
Code and data
Plus the prompts and the accounts set up for you.

What is a company brain?

A company brain is an internal system that answers staff questions from your own documents and records. It shows the source, and it refuses what the asker may not see. It prepares answers. A person still approves anything that changes a record.

Uploading a folder to a public chatbot makes a private copy outside your control, under that product’s retention rules. A company brain runs inside your operation, with permissions, a source for every answer, and a store you own. For the wider controlled workflow, see knowledge and back office.

  1. Your documents, drives and tools

    Only the sources named in the engagement are connected.

  2. Index with permissions

    Access follows the source system where it exposes a list.

  3. Answer with its source

    The passage used is shown. A weak match is reported as weak.

  4. Person approves changes

    Nothing that changes a record runs without a person.

How a question moves through a company brain, and where a person approves.

Where it helps.

Scenarios the setup is built around. Each one ends in a record or a person, not a dead end.

Policy and procedure questions

Staff ask a question instead of searching a shared drive. The answer shows the passage it came from, and says so when the match is weak.

Onboarding new starters

New starters ask the questions they would put to a colleague. The answers come from the documents your team already relies on.

Finding what was agreed

Someone needs the terms agreed on a past project. The brain points to the file and the passage, within what that person may open.

What we build.

We connect the sources your team uses today, as long as each one has an interface. We agree the list before we build.

Sources

Google Drive, SharePoint, OneDrive, Confluence, Notion, email exports, or the internal database your team treats as the record. The engagement names the list, and it stays the list.

Retrieval

Each answer cites the passage it used. When the source is missing or the match is weak, the system says so.

Permissions

Where the source system exposes an access list, the answer follows it. Where it does not, we scope a narrower source instead of guessing.

Where it runs

The index sits in your own cloud account, in a region you choose. Staff ask in Slack, Teams or a simple web page. The models that draft the answer can be swapped later. The files stay yours.

Staff question in the team chat
Team member:

How much notice do I need to give for unpaid leave?

Company brain

Two weeks. Section 4.2 of the Leave Policy says to submit the HR form and your manager approves it.

Source shown

Leave Policy, section 4.2. Answered within this person’s access to the HR folder.

Team member:

And what is the notice for the sales commission plan change?

Company brain

I cannot find that in the documents you may open. I have asked the finance lead to answer.

Answers follow the folder access each person already has.

Illustrative example. Not a real conversation.

From one real case to a live path.

First use case in 1 week. We build on top of it, one use case at a time.

  1. Days 1–2Audit

    Audit the questions staff ask

    We list the repeated questions, the folders they should come from, and who may see each folder.

  2. Days 2–3Design, before build

    Separate permission from search

    We trace who can open each source today, so the brain never becomes a side door around it.

  3. Days 3–5Build

    Index the agreed sources

    Only the named sources get connected. Every answer keeps a link back to its passage.

  4. Days 5–6Test, before anyone relies on it

    Score a sample of answers

    Real questions get scored for the right source, a correct refusal and the right permission. That sample is the accuracy check.

  5. End of week 1First use case

    Put it where the work happens

    Staff ask inside the tool they already open. The first use case is live within a week.

  6. Then, use case by use caseAfter the first use case

    Build on top of it

    The next use case goes on top of the first, one at a time, with the same source for every answer and the same permissions.

Talk to sales.

Prices are in US dollars and exclude taxes. They are one-time setup, not a subscription.

Typically from about$2,500One-time setup

No monthly maintenance fee. No vendor lock-in. The client owns the code and the data.

Talk to sales
  • The sources agreed in the engagement, such as files, a drive, or a tool with an interface
  • Answers that show the source they used
  • Permissions that follow the source system where that system exposes them
  • A person reviews any step that would change a record
  • You own the code and the data. Model providers keep their own service terms.

Usage, such as LLM tokens, is passed through at provider cost. We add no markup.

Bring one call, thread or workflow. We scope from there.

Book a call

What you own at the end.

You own

  • The code
  • The index and the data store
  • The prompts and the question sets used to check answers
  • The cloud and model accounts, which can sit in your name
  • The build itself, with no vendor lock-in

Controls that stay in place

  • Answers show their source. A weak match is reported as a weak match.
  • Permissions follow the source system where it exposes them.
  • Nothing that changes a record runs without a person.
  • No monthly maintenance fee and no vendor lock-in. You own the code and the data. Model providers keep their own terms.

Integrations

Every source in. One place to ask.

The brain reads the places your knowledge already lives, keeps each file’s permissions, and answers inside the tool your staff already open.

Documents and drives

  • Google Drive
  • SharePoint
  • OneDrive
  • Dropbox
  • Box
  • Confluence
  • Notion

Mail and sheets

  • Gmail
  • Outlook
  • Google Sheets
  • Excel
  • Airtable

Records and tickets

  • Salesforce
  • HubSpot
  • Zendesk
  • Jira
  • Asana
  • ClickUp

Databases

  • PostgreSQL
  • MySQL
  • MongoDB
  • Snowflake
Company brainOne index that keeps who may see what

Staff ask in

  • Slack
  • Microsoft Teams
  • Google Chat
Examples, not the full list. Logos do not imply a partnership with their makers.

Not on the list? We still connect it.

If your system lets data in or out, we connect to it. If it does not, we find a workaround, and we tell you how dependable that route is before we build. We also connect scanned PDFs, old file shares, intranet pages, email archives and any internal system with an export.

  1. API or webhook

    The clean route. Most modern tools have one, and many older ones do too.

  2. Database or export

    No API? We read the database, or a scheduled CSV or SFTP export.

  3. Email and shared folders

    We pick up the reports, invoices and attachments your system already sends.

  4. Screen automation

    For a portal with no other way in, a bot works the screen the way your team does, with every step logged.

How we approach integrations →

Straight answers.

What is a company brain?

It is internal software that answers from your own documents and records, shows the source, and respects the access the source system exposes. People keep the decisions. The system keeps the trail.

How is it different from uploading documents to ChatGPT?

A consumer chat product is someone else’s account, with its own retention. A company brain is built so you own the code and the data, every answer cites a source, and a person who may not see a file does not get it through the bot.

How long does a company brain take?

The first use case is live within a week, and we build on top of it, one use case at a time. We do not quote a total timeline. Which use case comes next, and how many sources and permission rules it involves, is agreed as we go.

How much does a company brain cost?

Setup is typically from about $2,500, one-time, scoped after the audit. There is no monthly maintenance fee. Model usage is billed at provider cost, with no markup from us.

Does it respect existing permissions in Drive, SharePoint or Slack?

Where that system exposes an access list, the answer follows it. Where it does not, we say so and scope a narrower source.

Which sources can it connect?

The ones named in the engagement: files, a drive, a chat export, or a database with an interface. The list is part of the scope.

How do you measure answer accuracy?

We score a sample of real questions for the right source, a correct refusal and the right permission. The sample is yours, so you can rerun it after any change.

Where does our data sit, and can it run on our own cloud?

Yes. The index and the store sit in your cloud account, in the region you choose. A model provider, if you use one, processes each question under its own terms, and we name it in the scope.

Who owns the brain?

You do: the code, the index, the data and the prompts. The cloud and model accounts can sit in your name. There is no vendor lock-in and no requirement to stay on our hosting.

Bring one workflow.

Tell us the call, the thread or the record. Every setup on this page starts with a call.

Book a call