Legal

Build document agents for legal

The obligation you need is in clause 7 of an agreement signed in 2019, in a file named after the counterparty. NourSoft builds agents that read at clause level and point back to the page.

Challenge

The answer is in the contract. Finding it is the job.

  • Obligations and renewal dates live inside clauses, not in anyone’s calendar
  • Comparing two versions of an agreement is done line by line, by hand
  • Precedent sits in past matters nobody can search by substance
  • Tender documents are assembled under deadline, from templates of varying age
Solution

Read at the clause, not at the file.

  • Extract obligations, dates and parties at clause level, each one traceable
  • Compare versions and surface what actually changed, not what merely moved
  • Search past matters by what they decided rather than by file name
  • Assemble tender documents from a governed, current template set
Use cases

Agents for common legal workflows

01
Clause Extractor
Pulls obligations, dates and parties, each with a page citation.
02
Version Comparer
Shows what changed between two drafts, clause by clause.
03
Precedent Finder
Retrieves prior matters by their substance, not their filename.
04
Tender Assembler
Builds كراسة الشروط from the approved template set.
Arabic document reality

The documents this actually runs on.

Generic pipelines describe documents in the abstract. These are the artefacts, correspondence patterns and approval chains the work is really made of.

Document types
عقود اتفاقيات مذكرات تفاهم لوائح كراسات شروط صكوك
Correspondence
خطاب مطالبة إشعار تجديد مذكرة قانونية إحالة للإدارة القانونية
Workflow
صياغةمراجعة قانونيةتفاوضاعتمادتوقيعمتابعة التزامات
Why NourSoft

What makes an agent trustworthy here.

Arabic before anything else
Arabic reading order, mixed Arabic/English pages and local terminology are handled as a core capability, not a localisation layer added afterwards.
It stays where your policy says
On-premise, isolated, private or national cloud, or hybrid. The deployment model is a governance decision, not something a vendor imposes.
Answers carry their source
Every extracted value can be traced back to the page and region it came from, so an answer can be checked rather than trusted blindly.
Confidence, stated honestly
Fields are marked high confidence or needs review. What needs a human goes to a human, instead of being reported as a number.
One layer, not five tools
Ingestion, understanding, extraction, governance and retrieval in a single pipeline rather than five products stitched together.
Built to sit beside what you run
Designed to work over existing content, storage and data platforms rather than requiring you to replace them first.
How it works

From a scanned page to an action you can audit.

01
Connect
Reach into the repositories, shares and systems where the documents already live — no migration project first.
02
Understand
Recover the structure of the page, then read it: layout, tables, Arabic and English text, signatures and stamps.
03
Act
Extract into a defined schema, classify, route, validate and log — with anything uncertain sent for review.
04
Govern
Identity, classification, policy and audit apply to the derived knowledge, not just to the source files.
Deployment

Runs inside your environment.

NourNexus is designed to support alignment with Saudi data governance and cybersecurity requirements. NourSoft makes no claim of NCA, NDMO or SDAIA certification on this page — any certification statement will be published only against documented evidence.

Next step

Bring a real document set.

The fastest way to judge this is on your own content, under your own governance constraint. We will show you what the platform reads from it, and where that processing runs.