Legal Nodes Newsletter


Your Legal AI Doesn’t Need a Better Model. It Needs a Better Memory.


Legal teams keep asking the same question:

Which AI model should we use?

But a more important question is emerging:

What does the model actually know about our business, our entities, and the decisions we have already made?

Because even the most advanced AI cannot give a reliable answer if it has to reconstruct your legal context from scattered documents every time you ask a question.

The model stayed the same. The results changed.

The new Legal Context Engineering Benchmark from NetDocuments tested what happens when the model and agent setup remain fixed and only the context layer changes.

Across 300 questions based on ten real legal matters, adding a Legal Context Graph reportedly reduced the cost per correct answer from $0.68 to $0.36 while maintaining almost the same level of accuracy.

That is approximately 48% less per correct answer.
The improvement did not come from switching to a more powerful model. It came from helping the existing model find and understand the right context.

The benchmark points to an important shift in how legal teams should evaluate AI:

The value of legal AI is not determined only by the model. It is also determined by the context the model can access.

Documents contain information. A context graph contains relationships.


Most legal teams already have the underlying knowledge AI needs.

It is distributed across:

πŸ–‡ corporate records;
πŸ–‡ contracts and amendments;
πŸ–‡ board resolutions;
πŸ–‡ emails and internal messages;
πŸ–‡ compliance documents;
πŸ–‡ and the knowledge held by individual team members.

But access to documents is not the same as access to context.

This is where the idea of a context graph becomes powerful.

That’s what we call the Legal Brain. We’re building with the Legal Brain: a legal context graph that gives AI structured, connected knowledge it can actually work with.

At our upcoming workshop, we’ll show you how to start building one for your own entity knowledge.

​[Register for the workshop on 1 September]​

For legal teams, this could mean connecting:

Entities β†’ People β†’ Documents β†’ Events β†’ Decisions β†’ Sources

Instead of searching through a folder to reconstruct an entity’s history, an AI Coworker could follow those connections and answer questions based on a structured, source-grounded record.

Build your first Legal Brain with us


On 1 September, we are hosting a practical workshop:

Build Your Legal Brain: Give Your Entity Knowledge to an AI Coworker

During the session, we will show you how to:

  • structure entity knowledge so AI can understand it;
  • connect entities, people, documents, and events;
  • build an event-based entity timeline;
  • give an AI Coworker access to this structured context;
  • and generate source-grounded answers with citations.

You will leave with a practical framework you can begin applying to your own entity knowledge.

AI models will continue to change.

The context your legal team builds can become an asset that grows more valuable with every entity, event, decision, and source you connect.

The next legal AI advantage may not come from choosing a smarter model.

It may come from building a better Legal Brain.

Reserve your place for the workshop "Build Your Legal Brain: Give Your Entity Knowledge to an AI Coworker"

πŸ“… 01 September, 16:00 BST (London/Dublin)

πŸ‘¨β€πŸ’» Host: Nestor Dubnevych, Co-founder Legal Nodes

Click the link below πŸ‘‡

​
​Unsubscribe Β· Preferences​

Legal Nodes Newsletter

Get emails from the Legal Nodes team.

Read more from Legal Nodes Newsletter

AI can monitor the regulation. Context tells it whether it matters to you. The Legal AI race is no longer just about who has the smartest model. For legal teams, the more important question is becoming: β€œ Does the AI understand enough about your business to actually do the work? A regulatory update is a good example. A model may be able to summarise what changed. But before Legal can advise Product, Operations or HR, someone still needs to determine: which entity or product is affected;...

What can your regulatory feed not tell you about your business? When legal teams discuss regulatory monitoring, the conversation often starts with sources: which websites to check, which alerts to subscribe to, and how frequently to look for changes. Those are sensible questions, but they only cover the first part of the work.Once an update appears, someone still has to work out whether it applies to the company, what it could mean for a particular team or process, and whether it calls for...

"The Fintech Brief" by Iryna Kuzyk & the Legal Nodes team A quick note from Iryna The most interesting fintech story of the last two weeks isn't really about fintech. It's about AI agents becoming economic actors. Visa, Mastercard and Ant are already working on how to identify an AI agent and verify what it's allowed to do. The question I'm more interested in comes after verification: who is responsible when an authorised agent makes the wrong decision? That's the theme running through this...