Your standards for liability, termination, data protection and governing law should be the same for everyone who reviews a contract. Put them in a Lexnus playbook. Lexnus checks each incoming agreement against those rules and shows what needs attention, and why.
Your policy exists. Applying it the same way every time is the hard part.
Most legal teams have decided their positions. The liability cap. The notice period. When a DPA is required. The problem is that each review starts from memory and a PDF nobody opens.
It lives in documentsA policy memo, a set of templates, a checklist on the intranet. None of them read the agreement for you.
Reviewers apply it differentlyTwo counsel, two answers on the same notice period. Neither is wrong by their own reading.
The same issues come backThe same short notice periods and missing DPAs arrive every week, and each one is caught by hand.
From policy to finding
01
Build the playbook from what you have
Import your policy or playbook memo from a Word document. Lexnus proposes rules from it. Your team reviews each one, adds your approved clauses and publishes a versioned playbook.
02
Check the agreement
Upload a PDF or DOCX. Lexnus flags terms that break a rule, required terms that are missing and anything it can’t establish from the text. Each finding quotes the clause and names the rule.
03
Route what needs a decision
Each rule has an escalation level: flag, require approval or reject. A rule that requires approval goes to an approval group, where either one member or all of them must sign off.
04
See the basis for every result
Each finding points to the rule and the playbook version behind it. When your policy changes, earlier results still show which version they were checked against.
Example. Your policy requires 90 days’ notice to terminate. The agreement allows 30. Lexnus quotes clause 12.1, shows the difference and names the rule that applies.
Incoming agreement
Software Services Agreement
Brightwater Analytics Ltd (the Supplier) and your company (the Customer)
7. Limitation of liability
7.2 Each party’s aggregate liability is limited to the fees paid in the twelve months before the claim.
12. Termination
12.1 Either party may terminate this Agreement for convenience on thirty (30) days’ written notice.
21. Governing law
21.1 This Agreement is governed by the laws of the Supplier’s jurisdiction.
Supplier agreements playbook
Checked against 12 rules
Violation · Requires approvalTermination for convenienceNotice is 30 days. Policy requires at least 90.
MissingData protectionNo data processing terms. Policy requires a DPA when the supplier processes personal data.
Needs reviewGoverning lawRefers to “the Supplier’s jurisdiction” without naming it. A lawyer should confirm.
PassLimitation of liabilityCapped at 12 months’ fees. Meets policy.
Playbook v5 · published 3 Sep 2026
Illustrative. Fictional supplier and figures.
Legal judgement stays with your team
AI reads the agreement and extracts its terms. The rules your legal team approved decide whether it complies. The outcome is a pass or a fail against your rule, not a confidence score.
When a term is unclear, Lexnus marks it for review instead of guessing. Your team decides what to accept, what to negotiate and when to make an exception.
One policy, wherever the contract is handled
Lexnus delivers the playbook itself, not just a review screen. Over MCP, an AI assistant such as Claude can read your rules and approved clauses, and check a draft against them before it reaches legal. The same published version applies in the app and in the assistant.
A playbook can be shared into the workspaces that need it, so each team works from the policy legal approved rather than its own copy.
Who it helps
General CounselSet the standard once. See which agreements depart from it and which exceptions reached approval.
Legal counselStart every review with the policy already applied. Spend the time on the points that need judgement.
Legal operationsRun one versioned source of policy instead of memos, checklists and template folders.
The wider businessGets a consistent answer from legal, whoever handles the review.
What to bring to the walkthrough
The walkthrough runs on your material, not a demo contract.
01One contract typeSupplier agreements, NDAs, customer MSAs. Pick the one your team reviews most.
02Your current policyA playbook memo, a checklist or your standard template. Whatever your team reviews against today.
03A representative agreementOne your team has already reviewed, so you can compare the result with your own markup.
Your contracts stay in Europe
Processed in the EEAThe platform runs on Clever Cloud in France. Contract files are replicated to OVHcloud in Germany for disaster recovery, as sealed ciphertext.
Never used to train modelsLexnus does not train on your contract text, and does not let its AI sub-processors do so. That is a commitment in the DPA, not a setting.
Named sub-processorsEvery system that touches contract text is listed by name on the Security page.
You stay the controllerLexnus processes personal data as your processor under the GDPR and acts only on your instructions.
Questions from in-house teams
Does Lexnus replace our lawyers’ review?
No. It applies the rules your team approved and shows where an agreement departs from them. Negotiation, exceptions and advice to the business stay with your lawyers.
How is this different from a CLM?
A CLM manages the contract workflow: routing, storage, signatures and reminders. Lexnus checks whether a contract meets your policy. It works alongside a CLM or on its own.
What if our policy has thresholds and exceptions?
Rules and clause variations can carry conditions, such as a different cap above a certain contract value. Use a separate playbook for each contract type.
What happens when our policy changes?
Edit the rule and publish a new version. New reviews use it. Earlier results keep the version they were checked against.
What if Lexnus can’t tell from the text?
It marks the point for review instead of guessing, and shows which rule it relates to. A lawyer decides.
Where is our contract data processed?
Inside the EEA, on European infrastructure. Contract text is never used to train models. Both are commitments in our DPA. The Security page names every sub-processor.
See it on your own contract type
Bring one contract type and a representative agreement. We’ll show you what a working playbook and a review result look like for your team.