Product

Know what you sign. Before you sign.

The counterparty's contract is written in their favour. Navabi reads it against what you normally accept and shows per article what deviates.

How it works

From their paper to your terms.

Your standard positions

At the start we record what you normally accept: liability, term, payment, governing law. Every contract is read against that.

  • Record once, use every time
  • A lawyer monitors changes

Redline with an explanation

Every change comes with the reason and the risk. You do not have to guess why something needs to change.

  • Per article: agreed, deviation or risk
  • A proposal for what to say back

Negotiation

When a counterproposal comes in, you see per article what the counterparty accepted, what it did not, and where you can give way.

  • Every round in the same file
  • All versions kept
What it costs

A fixed price per item.

The price in credits is fixed, however long the work takes. Full price list

ItemCredits
Short contract check (NDA, data processing agreement, quote)1
Employment contract2
Redline of a commercial contract, including a reply to one counterproposal3
Extra negotiation round1
Shareholders agreement or term sheet8
Counterparty memory

What this counterparty accepted before.

Navabi records every negotiation round: which proposal, which response, which outcome. For your next contract with the same party, the agent knows what is achievable before the first round starts. The memory grows with every matter, from yours and, anonymised per clause, from all clients in your sector.

Better with every next contract

A counterproposal is no longer a guess. "Liability twelve months: this party accepted that in two of three rounds" is information a law firm does not have, because it does not measure.

  • Per counterparty: previous rounds, accepted and rejected positions, response time
  • Per clause and sector: what gets accepted in the market, without names
  • In the agent's proposal: the chance a point gets accepted, with the reason

Part of Contracts in every plan; the memory fills from your first matter.

Technical

Versions, formats and proof.

A contract goes back and forth a few times before it is signed. This is how we track what changed when, and what was delivered in the end.

PartHow it works
VersionsEvery file is stored by its content (SHA-256). Every change is a new version; nothing is overwritten.
DependenciesEvery document we produce records which source versions, template version and playbook version it rests on. If one changes, it is marked "possibly outdated" and you are told.
To the counterpartyA .docx with real tracked changes, generated from our own clause-by-clause comparison. The counterparty simply keeps working in Word.
From the counterpartyWe read their redline into the same model. You accept or reject each change, tested against your standard positions. Reject something critical and the system tells you.
FinalPDF/A with an advanced electronic signature from Navabi (PAdES-B-LTA) and a qualified timestamp. If the Word file is edited afterwards, the hash shows what was delivered.
TemplatesFixed content fields instead of free formatting. Your answers are structured data, so every document can be rebuilt from template plus answers.
Questions

Short answers.

In which languages?

Dutch and English.

Does it also work with my own templates?

Yes. Your own templates become your standard. If you do not have them yet, we draft them.

Who keeps track of the versions?

Navabi. Every version is kept, with who made it and when.