CompanyMind reads every source your company already owns, organizes it into one connected index, and answers out of it. Each clause in the answer keeps a pointer back to the artifact it came from. All of it runs on your hardware.
Everything you own.Not just the tidy parts.
Point CompanyMind at a share, a mailbox, a chat export, a folder of scans. It reads what it finds. A contract, a forgotten spreadsheet tab, a photographed whiteboard and an hour-long call all arrive as the same thing: text the brain can reason over, with a path back to the original.
- q3_risk_review.docx
Read with its structure intact. Headings, tables and footnotes stay attached to the meaning they carry.
- contract_terms_tracker.xlsx
Every tab, every row, every cell. Including the tab nobody has opened since the person who made it left.
- meridian_msa_executed.pdf
Parsed clause by clause, so a citation can point at Schedule 2 §4.1 rather than at page fourteen, somewhere.
- scan_0042.tiff
A photographed page is a picture until something reads it. OCR turns it into text you can search and cite.
- re_meridian_redlines.eml
The thread in order, attachments included, with the date the decision actually landed.
- deal_desk_export.json
Messages in sequence, with who wrote them and when. The thread from March stops being folklore.
- whiteboard_2026-03-12.jpg
Screenshots, diagrams, photos of a board. The text inside them is read, and the image is indexed next to it.
- meridian_call_14mar.m4a
An hour of call becomes a timestamped transcript. What was agreed at 00:41 stops being something two people half-remember.
12 ingest adapters implemented today, from .docx to .m4a to a scanned .tiff.
Scattered goes in.Connected comes out.
Reading the files is the easy half. What makes it a brain is what happens next: the copies collapse, the formats disappear, and everything that talks about the same thing ends up next to it.
Duplicates collapse
Four files called final become one document with a history. The version that was actually executed is the one that answers.
One connected index
The contract, the tracker row that summarizes it, and the call where it was argued stop being three systems. They become three neighbours.
Formats stop mattering
A sentence is a sentence whether it arrived as a slide, a scan, or a voice note. Retrieval works on meaning, not on file extension.
Permission-aware from the start
Access control comes in with the data and stays attached to it. Someone who could never open the file cannot retrieve a sentence out of it, and cannot see it cited in an answer.
Permissions are not a filter bolted on at the end. They are a property of the index. Nothing is ever flattened into one pile everybody can read.
A question in.An answer you can check.
Answers are built out of what your data says, not out of what a model remembers reading somewhere else. Every clause keeps a pointer to the span it was made from, and the pointer is in the answer itself — not in a footnote you are asked to trust.
What did we commit to on data residency in the Meridian contract?
All customer data stays in-region, with no cross-border transfer and no offshore replica.1 Retention was negotiated down to 18 months from the original 36.2 Legal drove that change after flagging the 36-month term as outside policy.3 The customer accepted on the 14 March call, on the condition that deletion is evidenced every quarter.4
Illustrative. The artifacts are the customer’s own files, and the answer is assembled only from them. Each marker resolves to a location inside a specific artifact — a page, a row, a timestamp — and opens the original there.
How that happened
Every answer carries a citation because there is no other way to build one. The answer is assembled from retrieved spans, so a sentence with no source has nothing to be made of.
- 01
Read
The question is interpreted against your index, by a model running on your hardware. It never leaves the building to be understood.
- 02
Retrieve
Candidate spans are pulled from the artifacts this person is already cleared to see. Nothing else is a candidate.
- 03
Assemble
The answer is written out of those spans. Each clause carries the pointer to the span that produced it.
- 04
Cite
Pointers resolve to artifacts and to locations inside them. Open the original and read it yourself. That is the whole point.
- 05
Log
The question, the answer and every source consulted land in your audit trail, in your systems, on your retention schedule.
When the answer is not there
CompanyMind says so, and shows you where it looked. In a regulated file a confident guess is worse than silence.
No source, no claim. If your data does not say it, CompanyMind does not say it either.
None of thisever leaves.
Every step on this page — the ingest, the index, the model, the answer, the audit log — runs on hardware you control. There is no vendor cloud in the path, because there is no vendor cloud. How that is built, and what it means for the obligations you already carry, is its own page.