L2Law firmsContract review against your playbook
Review the other side's contract clause by clause against your playbook
Reads the counterparty's contract, even 60 pages long, and checks it clause by clause against your playbook: red, amber or green by written rules — the double signature of art. 1341, art. 1229, the 60 days of D.Lgs. 231/2002, the art. 28 GDPR processor agreement — with the change to ask for.
The problem
A large client's general terms arrive in Word, sixty pages. Finding the void clause, payment beyond 60 days, the missing DPA and what needs the double signature, before signing, is slow reading.
Who it is for, and when
- Who it is for
- The lawyer of a one-to-five-lawyer practice and the legal or purchasing office of a company that receives the other side's contracts; the owner of a small business a large customer asks to sign its general terms.
- When
- Every time a contract arrives to be signed "by tomorrow": the general terms to join a customer's supplier list, the main contractor's subcontract, the software vendor's processor agreement, the NDA before a negotiation.
What you give it, what you get
You give it
The contract as it arrives — Word or PDF, even 60 pages — and its kind (supply, works contract, DPA, NDA); once, your playbook in Knowledge with your limits.
You get
The red clauses first, each with its rule; the table of every clause — present, missing or against the playbook — with its quote checked against the text and the change to ask for; the double-signature list; the table in Word to sign and in Excel.
How it works, in three steps
- Upload the contract and pick its kind
- Read the reds first and check the quotes
- Sign the table and send the changes to the other side
On its own, in a flow. Connect it to the mailbox or the folder where contracts arrive: each one is read, the table goes to the lawyer for approval and, once approved, reaches whoever asked for it in Word and Excel.
The rules it applies
In the agent's own words: what it checks and what it never does.
- Red by rule: void under art. 1229, past the 60 days, no DPA
- The double-signature list: what art. 1341 needs and misses
- Every quote found in the contract, the change to ask for
- Read-and-recommend only. The agent never moves money.
A real example
A case from the demo catalogue, with anonymised documents.
The software vendor's processor agreement: no sub-processors, no deletion, no audit
FieldApp Cloud, the software Acme's technicians close their jobs with, sends its data processing agreement to sign with the licence renewal: customers, addresses, signatures and the technicians' positions go through it. The office manager uploads it as a DPA before signing.
The recorded result
Nomina a responsabile (art. 28 GDPR) di FieldApp Cloud S.r.l.: 10 punti dell'art. 28 c. 3 · 3 mancano: sub-responsabili (lett. d), cancellazione o restituzione a fine rapporto (lett. g), audit e ispezioni (lett. h)
real time 3 min 58 s33 credits
Frequently asked questions
What is the playbook?
Your rules on what you accept and what you don't, uploaded to Knowledge. The agent compares every clause with them and with the written rules — art. 1341, art. 1229, D.Lgs. 231/2002, art. 28 GDPR — and proposes the change to ask for; you approve.
What does it cost, and how long does it take?
Usually 24–49 credits a contract (≈ €0.99–2.02) and 3–6 minutes. It depends on the contract: more pages and more clauses to re-check cost more; colours, rules and quotes are code and cost nothing. The recorded example cost 33 credits in about 4 minutes.
Can it run on its own, in a flow?
Connect it to the mailbox or the folder where contracts arrive: each one is read, the table goes to the lawyer for approval and, once approved, reaches whoever asked for it in Word and Excel.
Who checks what the agent did?
You do — and it takes a minute, not an afternoon. Every run is a trace: the live timeline, each tool call, each document read, the cost per step, the confidence and sources. Actions that leave the building wait for your approval. The platform never sends, never touches a live store, never moves money.
Where does my data live, and how do you handle GDPR?
Your data is stored in the EU, on one server in Germany. The EU/US data-region setting limits which models an agent can be saved with, not where your data is stored. A no-retention mode and a local runner on your own machine are available. Your plan sets how many days your data is kept — you can change it — and when they run out it is deleted automatically. You download each run's results and delete files, agents and connections in the console; an owner deletes the whole workspace and each person their own account from Settings. The “Your data” page names the services that handle your data.
Related agents
- L1Court deadlines from acts and PECReads the notified act or the PEC as it arrived and computes every procedural deadline by written rules: appeal, long term, opposition, statement of defence, the 171-ter briefs.
- L3Contract and deadline registerReads contracts, policies, permits and certificates and computes every deadline: tacit renewals, notices, policies, DURC.
- L4Debt recovery dossierBuilds the dossier the lawyer files for a payment order: each invoice against its signed delivery note and the bank, the interest to the day, the evidence the court asks for and what is missing, the court, the formal notice as a PEC draft.
Try it on your own documents
The demo shows the recorded cases without an account; with your own workspace you run it on your files.