Step 1 · We map the sourcesWhere does the knowledge live today?
The answer exists in the company,finding it is what takes the time.
Contracts, procedures, price lists, past correspondence and technical files gather in one searchable source. When the system writes an answer it puts the page of the document it came from next to it, so you check it yourself instead of asking three people.
Connected sources
Google Drive
Notion
Gmail
Slack
PostgreSQL
Claude
- File server
From documents sitting scatteredto an answer that arrives with its source.
The first job is working out which folder and which inbox the knowledge lives in today. Then we connect the sources to one index and carry each source's permission rules over unchanged. Last, we start tracking the questions that go unanswered.
Step 2 · One index is builtAll of it enters the same search.
Step 3 · The gaps closeUnanswered questions become a list.
It finds the answerand shows you the source.
Six modules take on the four sides of search: source, permission, citation and gap list. An answer with no document behind it is never produced.
Scattered documents, one search
PDFs, Word files, spreadsheets, decks and scanned documents go into the same index. When a document changes the index updates itself, and the old version stays on the record.
Every answer is tied to a document
Underneath the answer it says which document and which page it came from. You click the link, open the source, and see for yourself that the sentence is really there.
Access is limited by role
Who can see which document is written by role, with document-level exceptions where needed. Because every query is logged, who looked at what is visible afterwards.
It says when it does not know
For a question with no match in the sources, the system does not invent an answer. It says it could not find one and writes the question to the gap list, which shows which document is missing.
Conflicting documents are flagged
If two documents say different things about the same subject, the system shows both and flags the conflict. A person decides which one applies.
What is being asked becomes visible
The most asked subjects, the unanswered questions and the missing-document list reach you every month. That list shows which document needs writing.
Wherever a document sits,it enters the same search.
In Drive, in Notion, in an email attachment or on your own server. Adding a new folder needs nothing for the team to learn; the folder joins the same index and brings its own permission rules with it.
- The source is your own documents
- Answers give a page number
- Access is limited by role
Knowledge platformFrequently asked questions
No. The index and the search run on your own infrastructure. Your documents are not used to train models; only the question itself and the relevant passage go out, never the full archive.
The permissions at the source are preserved exactly. Someone who cannot see a folder cannot see an answer drawn from a document in it either. Role-based permissions are written during the build and every query is logged.
Every answer shows which section of which document it came from. You click the link and open the source. An answer with no document behind it is not produced.
It is constrained not to. For a question with no match in the sources it does not form a sentence; it says it could not find one and adds the question to the gap list, which shows which document is missing.
Both. The system does not decide which is right; it flags the conflict, puts the two passages side by side and shows their dates. A person picks the version that applies, and that choice is recorded.
PDF, Word, Excel, decks, plain text and scanned documents. Text is extracted from scans; a page that cannot be read is flagged rather than silently skipped.
The index updates itself and the new version applies. The old version stays on the record, and which version an answer came from is always visible.
Discovery takes a week. In that week we work out which folders the knowledge lives in and what the permission rules are for each source. The first live workflow opens within 4-8 weeks; the range depends on document volume, the number of sources and how complex the permission rules are. Your own timeline is written into the discovery report.
Two things are measured during discovery week: how long it takes to reach a piece of information, and how many people get asked per question. Both are measured again after search opens, next to the length of the gap list. The number of answers given without showing a document is zero.
Wherever the knowledge sits,that is where it is read from.
Each source is connected with its own permission rules. Who can see a document stays exactly as it is at the source; the platform opens no new door for anyone.
Google Drive
Contracts, procedures and decks are indexed the moment they change, and folder permissions are preserved.
Notion
Internal documentation syncs instantly and space permissions carry over.
Email attachments
Proposal, invoice and correspondence attachments are scanned daily; mailbox permissions are preserved.
Slack channels
Decision and announcement history is indexed daily, and channel permissions carry over.
Your own database
Product, price and client records are read hourly; access stays role-based.
File server
Technical drawings and archives are scanned overnight; a page that cannot be read is flagged rather than silently skipped.


The process first, the proposal after
In a short discovery call we map the process together and tell you plainly whether it is worth automating. If it is not, we say that too.
30 minutes · no preparation needed





