For advisory firms

Your positions reach every client who drafts with AI, under your firm’s name.

Write your standard positions for a contract type once. Your clients get a connector with your firm’s name in the AI assistant they already use. Every draft they write, and every redline a counterparty sends back, is checked against those positions. Only the points that fall outside them reach your counsel.

Clients draft with AI and send you the result

Your clients no longer start from your template. They ask an AI assistant for an NDA or a supplier agreement, and the draft arrives in your inbox for review. The language reads well, but it carries the assistant’s defaults, so someone at the firm goes through it line by line.

Drafts written by AIThe assistant picks its own governing law, confidentiality period and liability cap. Each one has to be found and corrected by hand.
Review on a fixed feeThe client pays the same whether a draft takes twenty minutes or two hours. On a fixed fee or a subscription, every hour of redlining comes out of your margin.
Answers that vary by counselTwo lawyers in the firm may give a client different answers on the same point when each works from their own precedents.

How it works

01

Build a playbook for one contract type

Start from your templates or a positions memo, uploaded as a Word document. Lexnus proposes rules from it, such as the confidentiality period you accept or the governing law you insist on. A lawyer at your firm reviews each rule and publishes it, and no rule goes live before that.

02

Put your firm’s name on the connector

Lexnus applies your firm’s name and logo to a connector for your clients. Each client adds it to the AI assistant they already draft with.

03

The client drafts, and the connector checks

A client drafts a contract, or receives one from a counterparty, in their AI assistant (Claude, ChatGPT or Mistral, connected over MCP). The connector checks the text against your playbook. Each finding quotes the clause and names the rule behind it.

04

Your counsel sees what falls outside your positions

Points within your positions are handled in the client’s own workflow. Points outside them go to your counsel with the rule and the quoted text, so the review starts from the question that needs a lawyer.

Illustrative. Fictional client, counterparty, playbook and wording.

What goes into a playbook

A playbook holds your firm’s positions for one contract type. Your lawyers write and approve every part of it, and the connector checks drafts against nothing else.

Rules for each positionEach rule states one position, such as the governing law you require or the range you accept for a confidentiality period. A rule can carry conditions, such as a different limit above a certain contract value.
Your approved wordingThe playbook holds your clauses and fallback wording. When a draft breaks a rule or leaves out a required term, the connector offers your wording in its place.
What goes to counselEach rule has an escalation level. It can flag the point for the client, require approval from your counsel, or reject the term. You decide for each rule which points need a lawyer.
VersionsWhen you change a position, you publish a new version of the playbook. Every client’s next check uses it, and each result records the version it was checked against.

AI reads the draft and extracts the terms. Your published rules decide whether each term complies. Each finding is a violation, a gap where a required term is missing, or a point that needs review. When the text is unclear, the connector marks it for a lawyer instead of guessing. Read more about playbooks.

Why firms offer it

Your name in front of the clientThe connector carries your firm’s name, so the client sees it every time they draft a contract or check a redline.
One standard across the firmEvery client gets the same written positions, whichever of your counsel serves them.
A use of AI you can showYou can show clients how the firm uses AI in its own service, with your lawyers’ positions behind each check.

Alongside the AI tools you recommend

Your clients keep the assistant they use today. The connector adds your firm’s positions to it.

 AI tools clients use on their ownYour connector
Whose positionsThe vendor’s defaults, or the client’s ownYour playbook
Whose nameThe vendor’sYours
What reaches counselQuestions clients choose to askThe points that fall outside your positions

You own the advice. Lexnus runs the engine.

AreaThe firmLexnus
Playbooks and their contentOwns and maintains themProvides the authoring tools
Client relationship and pricingOwns themNone
Legal advice and escalationsResponsibleNone
Client supportFirst lineSecond line, for technical issues
Engine, connector and hostingNoneProvides and runs them
Branding of the connectorSupplies the name and logoApplies them

Who controls the data

Your client owns the contracts and the personal data in them, so the client is the controller. Your firm provides the service under its own agreement with the client and acts as processor. Lexnus runs the engine on EU hosting as your sub-processor.

A standard DPA template covers the whole chain. We welcome a review by your privacy counsel before the first client goes live.

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 contract text, and does not let its AI sub-processors do so. That is a commitment in the DPA.
Named sub-processorsEvery system that touches contract text is listed by name on the Security page.
The assistant stays the client’sThe AI assistant your client drafts in runs under the client’s own agreement with its provider. It is not a Lexnus sub-processor, and the no-training commitment above does not cover it.

What a pilot looks like

A pilot runs on real client work, with a scope small enough that you can judge the result.

01PlaybooksOne or two contract types that your clients send in most often.
02ClientsTwo or three of your clients, using the connector for real work.
03DurationSeveral weeks, so each client runs several contracts through it.
04EscalationsYour counsel handles them in the same way as today.

What we measure

  • Review time on drafts that come from pilot clients.
  • Whether clients use the connector without being prompted.
  • How long it takes to write a playbook your lawyers find usable.
  • What your clients would pay for the service.

Questions from advisory firms

Does Lexnus give legal advice?

No. It applies the positions your lawyers approved. Advice and escalations stay with your firm.

Will our clients see Lexnus?

No. Lexnus is a tool your firm uses internally. Your clients use a connector with your firm’s name and logo, and the Lexnus brand does not appear in it. The data processing agreement with each client still names Lexnus as your sub-processor, as the GDPR requires.

Which AI assistants does it work with?

It works with any AI assistant that supports MCP, including Claude, ChatGPT and the assistant from Mistral.

Who sets the price to the client?

Your firm sets the price, and the client relationship stays with you.

What if a point can’t be established from the text?

The connector marks it for a lawyer to decide instead of guessing. Your counsel sees which rule it relates to and what was missing or unclear.

Start with one contract type and a few clients

Bring your template or positions memo for the contract type your clients send most. We’ll build the playbook with your lawyers and set up the connector for two or three of your clients.