Who it's for
Who it is for
Any team where decisions live in threads, being wrong has a cost, and access is not uniform. Software teams first, then legal, finance, pharma, professional services, media, support and government.
Teams that build
Software & product
Provenance + time travelThe 'why is it built this way' question gets asked daily and answered by archaeology. Xerum answers it with a citation and a revision.
Professional services
Curation + versioningEvery new engagement re-answers questions the firm already answered. The record is the only thing that outlives the team that made it.
Customer support
ProposalsThe first market where agents genuinely need to write. Proposals are how they do it without anyone losing control of the knowledge base.
Media & research
Citation + curationYou already run this process by hand. Citation and editorial sign-off are the two properties the store enforces by construction.
Where being wrong is expensive
Legal
Citation + curation + isolationCitation is an obligation, partner review is already 'members propose, owners decide', and privilege demands physical isolation. Three properties, all built.
Financial services
Versioning + auditResearch memos, deal history and IC decisions, in a store where the record cannot be rewritten after the fact.
Pharma & R&D
Audit + curationTraceability is already a legal obligation. A curated append-only record maps onto the audit culture rather than fighting it.
Government & defence
Scopes + isolationNeed-to-know is a pre-filter inside the query; physical isolation per customer is the deployment story you already mandate.
Weighing it against something you already run? Comparisons →