Xerum for legal teams

An answer without a citation is not an answer

Every other industry treats provenance as a nice-to-have. In legal work it is the job. A model that produces a confident, uncited, unverifiable paragraph is not a tool — it is a professional-conduct problem waiting to be discovered.

Get an instance See how it works

Sound familiar?

Uncited output cannot be used

A summary of a position with no traceable source cannot go in a memo, cannot go to a client, and cannot be relied on by anybody who would be answerable for it. So it gets rewritten by hand, and the tool saved nobody anything.

Matter knowledge lives with one person

The reasoning behind a position taken two years ago — what was argued, what was conceded, why — is in one partner's memory and a thread nobody else can find.

Privilege makes shared tooling hard

A multitenant service holding privileged material is a conversation with risk and insurance before it is a conversation about features, and it usually ends there.

What changes

Provenance ends at the source

The revision, the resource and the origin URL travel with every answer. Verification is a click, and an unverifiable claim is visibly unverifiable.

Partner review, as the data model

Members propose, owners decide — the loop your practice already runs, enforced by the store rather than by a policy nobody reads before they paste.

Physical isolation per client firm

Your own container, your own database, your own storage prefix. Not a tenant column with a filter over it, which is the design that produces the incident notice.

Positions kept, never overwritten

Nothing is edited in place, so the position taken at the time is still readable at the revision it was taken — the question that gets asked when it is challenged.

What this industry buys

Citation + curation + isolation

Three properties at once — which is why this is the industry the pitch is easiest in and the diligence is hardest.

  • Every answer walks back to a URL and a named author
  • Nothing joins the record without an owner approving it
  • One container and one database per firm; no shared index anywhere
  • Permission filtering inside the query — hidden is indistinguishable from absent
Get an instance

Isolation is architecture here, not a contractual promise about a shared system.

Give your team an AI answer you could put your name on

Built today, not on a roadmap. Every property above is already how the store works.