Nemosyne
Menu

For law firms

Every matter your firm has handled, cited

The clause you negotiated two years ago, the position the firm took on it and the reason a partner conceded it are all in the document management system — and in practice they are gone, because finding them costs more than redrafting. Nemosyne makes the firm's own precedent reachable.

Where the work already lives.

Connected in place, under the permissions those systems already enforce.

  • The document store — SharePoint, Google Drive or Box — with the drafts and the executed versions.
  • The matter file: engagement letter, scope, and the correspondence that changed it.
  • Negotiation playbooks, and the fallback positions the firm has actually agreed to.
  • Email and message threads where a point was conceded and the reason given once.
  • Matter lists exported from the matter-management system, saying which client, which team, which year.

Matter confidentiality is not a convention here. Visibility is taken from the source at capture, so a matter walled off from the rest of the firm stays walled off inside the memory, and an answer for someone outside it is assembled without it.

Three kinds of recurring work.

The same three shapes come round every quarter. What changes is not that the work disappears — it is that nobody has to reassemble the record before it can start.

Drafting from precedent

a fee earner searches the system, finds forty documents, opens six, and drafts from whichever looked closest.

the executed agreements and the threads around them come back cited, matter by matter, so the position taken and what the other side pushed for are read rather than remembered.

Scoping a new matter

the estimate rests on whoever has done one like it, and last time's scope creep is remembered anecdotally or not at all.

comparable matters can be found and read with the fee each engagement letter agreed, every later variation kept as history, and the correspondence about scope cited.

Continuity when people leave

when a partner leaves, the reasoning behind their matters leaves with them.

a reason the file gave — a decision and who took it, a handover note, a lesson drawn — is kept as cited memory on the client, so a successor can read it.

A worked example.

Illustrative — the firms, names and figures below are invented

Ashcroft Partners acts for a client on a supply agreement. The counterparty asks for an uncapped indemnity, and the associate wants to know what the firm has accepted before.

Playbook · 2023
Fallback position: indemnity capped at 100% of fees, with a sub-cap for data breach.
Matter A · 2024
Accepted a 150% cap after the client instructed commercially.
Matter B · 2024
Held the 100% cap; the counterparty conceded.
Email · Matter A
Partner records the reason: the client wanted the contract signed before quarter end.
Engagement letter
Scope excludes tax advice; a later email extended it.

The playbook and the practice disagree. The firm's stated fallback is 100%, and it has accepted 150% once, for a stated commercial reason, on one matter. The answer sets the playbook's line beside each matter's own record, cited, so one deviation reads as one matter's choice rather than quietly becoming the firm's position.

What your assistant answers.

Through the same Claude, ChatGPT or Cursor your firm already uses — one connection per firm, and each person sees only what they are allowed to see.

What indemnity cap has the firm accepted on supply agreements?

The playbook's fallback is 100% of fees with a data-breach sub-cap, and one matter held it against pressure.

One matter departed from it, accepting 150% on the client's commercial instruction; the reason is on the file.

The associate opens the matter that departed and reads why, instead of inferring a firm position from a single instance.

See how the answer is assembled →

The first thing we would ask you.

Which areas of law do you practise — litigation, corporate, employment, IP, something else?

A litigation practice and a corporate practice leave different documents behind — pleadings and judgments on one side, drafts and executed agreements on the other. The answer decides what Nemosyne reads first, and it is the kind of thing we would rather be told than infer.

Questions this raises.

Does this reach privileged material?
It reads what you connect, under the permissions that source already enforces. A matter you do not connect is not read, and a matter walled off inside the document store stays walled off inside the memory.
Is the firm's work used to train a model?
No. Documents are read to build your memory and for nothing else. Model calls run under enterprise terms that exclude training, and on private cloud or self-host they run under your own keys.
Can it draft?
It supplies the cited context and your assistant drafts. The distinction matters, because every sentence it hands over names the document it came from and can be checked against it.
What about matters that never reached the document store?
Email and message threads are ordinary sources. A point conceded once in a thread becomes a fact with that thread as its citation, rather than something only one person remembers.

Start with what your firm already knows.

Free for three people and about a hundred documents. No card, no expiry.

Start free →

Also written up for Private equity · Private credit · Tax · Accountancy · Audit