An SOP and policy brain for a free-zone company
Staff ask how to raise a purchase request or request leave. The answer comes from the current SOP, shows the passage, and refuses a folder the asker cannot open.
In short. Aiwah Labs builds company brains for businesses in Dubai, Abu Dhabi and across the UAE: internal AI knowledge bases that answer staff questions from your documents in Arabic and English and show the source. The first use case is live within a week, and we build on it. Typical setup is from about AED 9,000.

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 how to raise a purchase request or request leave. The answer comes from the current SOP, shows the passage, and refuses a folder the asker cannot open.
New joiners ask the questions they would put to a colleague. The answers come from the HR handbook and procedures, in Arabic or English.
Someone needs the terms of a past contract. The brain finds the clause and shows the page, 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.
أين أجد نموذج طلب الإجازة؟
In English: Where can I find the leave request form?
ستجده في مجلد الموارد البشرية، ضمن سياسة الإجازات.
In English: You will find it in the HR folder, under the Leave Policy.
Who approves a purchase request over the limit?
The finance director approves it first, then the purchasing officer places the order. This is in section 3 of the Procurement SOP.
Procurement SOP, section 3. Answered within this person’s folder access.
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 UAE dirhams 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.
Serves businesses across Dubai, Abu Dhabi and the wider UAE.
A company in Dubai, mainland or free zone, tends to keep its rules in several places: an HR handbook in Arabic and English, a procurement SOP on a shared drive, an approval matrix in somebody’s inbox. A company brain gives staff one place to ask. The answer comes from the current document, shows the passage, and refuses a question about a folder the asker cannot open. We start with an audit of the questions your staff ask, in Arabic and in English, and we test retrieval across both languages on your own documents.
Data protection decides where the index sits. The UAE’s Personal Data Protection Law, Federal Decree-Law 45 of 2021, applies to electronic processing of personal data inside or outside the UAE, generally requires consent, and sets conditions for sending data abroad. Staff files hold exactly that kind of data: ID copies, contracts, salary letters. So the design starts with a short list of what the brain may read, an index that sits in a UAE region of your cloud account where your provider offers one, and a record of which model provider sees each question. A question sent to a model hosted abroad counts as a transfer, and the build treats it as one. Ask your counsel to check the PDPL’s executive regulations as they stand when you start.
A company registered in the Dubai International Financial Centre has a second law to read. DIFC Law No. 5 of 2020 is the centre’s own data protection law, so the audit starts by naming which regime covers each source the brain will index.
The UAE Personal Data Protection Law (Federal Decree-Law No. 45 of 2021) came into force on 2 January 2022. It applies to electronic processing of personal data inside or outside the UAE, generally requires consent, and sets requirements for cross-border transfers.
UAE Government portal, data protection laws (updated 4 December 2025)The Dubai International Financial Centre has its own data protection law, DIFC Law No. 5 of 2020, listed by the UAE Government alongside the federal Personal Data Protection Law.
UAE Government portal, data protection laws (updated 4 December 2025)Shams Business Center, Sharjah Media City Free Zone, Al Messaned, Sharjah, UAE
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 passage behind them. Published work on the pattern, with no claim about where the client sits.
EssayEight controls every production AI agent needsAn internal agent still stops at the decision a person owns.Yes, where your cloud provider offers a UAE region. We place the index and the store there and name every model provider that sees a question. A provider hosted abroad counts as a transfer under the PDPL, which we design for.
Yes. We test retrieval across both languages in the audit, so a question in Arabic can find an English policy and the reverse. We report the results on a sample of your real questions before you rely on it.
Setup is typically from about AED 9,000, one-time, scoped after the audit. There is no monthly maintenance fee. Model usage is billed at provider cost, with no markup from us.
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.
No. Where the source system exposes an access list, the answer follows it. Where it does not, we scope a narrower source, so the brain never becomes a side door.
Tell us the call, the thread or the record. Every setup on this page starts with a call.
Book a call