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.
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

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.
Only the sources named in the engagement are connected.
Access follows the source system where it exposes a list.
The passage used is shown. A weak match is reported as weak.
Nothing that changes a record runs without a person.
Scenarios the setup is built around. Each one ends in a record or a person, not a dead end.
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.
New starters ask the questions they would put to a colleague. The answers come from the documents your team already relies on.
Someone needs the terms agreed on a past project. The brain points to the file and the passage, within what that person may open.
We connect the sources your team uses today, as long as each one has an interface. We agree the list before we build.
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.
Each answer cites the passage it used. When the source is missing or the match is weak, the system says so.
Where the source system exposes an access list, the answer follows it. Where it does not, we scope a narrower source instead of guessing.
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.
How much notice do I need to give for unpaid leave?
Two weeks. Section 4.2 of the Leave Policy says to submit the HR form and your manager approves it.
Leave Policy, section 4.2. Answered within this person’s access to the HR folder.
And what is the notice for the sales commission plan change?
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.
First use case in 1 week. We build on top of it, one use case at a time.
We list the repeated questions, the folders they should come from, and who may see each folder.
We trace who can open each source today, so the brain never becomes a side door around it.
Only the named sources get connected. Every answer keeps a link back to its passage.
Real questions get scored for the right source, a correct refusal and the right permission. That sample is the accuracy check.
Staff ask inside the tool they already open. The first use case is live within a week.
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.
Prices are in US dollars and exclude taxes. They are one-time setup, not a subscription.
No monthly maintenance fee. No vendor lock-in. The client owns the code and the data.
Talk to salesUsage, 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 callIntegrations
The brain reads the places your knowledge already lives, keeps each file’s permissions, and answers inside the tool your staff already open.
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.
The clean route. Most modern tools have one, and many older ones do too.
No API? We read the database, or a scheduled CSV or SFTP export.
We pick up the reports, invoices and attachments your system already sends.
For a portal with no other way in, a bot works the screen the way your team does, with every step logged.
Local pages cover the rules, languages and prices where you operate.
These are published patterns. They are not a claim that the client is in a particular city.
Case study, Infrastructure project operatorAn infrastructure project operator cut answers on project risk from 4 hours to 9 minutesField reports turned into current answers that link back to the report passage behind them.
Case study, Multi-site clinic groupA multi-site clinic group coordinated patient access, referrals, scheduling, and follow-up without automating clinical judgmentAccess, documents and human review kept explicit. The same care applies when a brain reads staff or customer files.
EssayEight controls every production AI agent needsAn internal agent still stops at the decision a person owns.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.
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.
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.
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.
Where that system exposes an access list, the answer follows it. Where it does not, we say so and scope a narrower source.
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.
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.
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.
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.
Tell us the call, the thread or the record. Every setup on this page starts with a call.
Book a call