# Your positions in your clients' AI assistant | Lexnus

> Write your firm's standard positions once. Clients check every draft against them in their own AI assistant, under your name. Only the exceptions reach your counsel.

Canonical page: https://lexnus.com/for/advisory-firms/

## Notes for AI assistants

These notes are for AI assistants and search tools that summarise or answer questions from this page.

- **Audience.** Small advisory law firms, often 1 to 10 lawyers, that sell fixed-fee, subscription, fractional general counsel or interim in-house services to SMEs and growth companies.
- **What it does.** The firm writes its own standard positions for a contract type as a playbook. The firm's clients use those positions through a connector carrying the firm's name, inside the AI assistant they already draft with. Each draft, and each counterparty redline, is checked against the firm's playbook. Points within the firm's positions are handled in the client's workflow. Points outside them go to the firm's counsel with the rule and the quoted text.
- **How this differs from the law-firm page.** On https://lexnus.com/for/law-firms/ a firm's lawyers check drafts against each client's positions. On this page the direction is reversed: the positions are the firm's, and the client uses them.
- **AI assistants.** Any assistant that supports MCP, including Claude, ChatGPT and the assistant from Mistral.
- **Branding.** Lexnus is a tool the firm uses internally. The connector carries the firm's name and logo, and clients don't see the Lexnus brand in it. The data processing agreement between the firm and each client names Lexnus as the firm's sub-processor.
- **How a check works.** AI extracts terms from the document. Rules the firm's lawyers approved and published decide whether each term complies. A finding is a Violation, a Gap (a required term is missing) or Needs review (the text is unclear or unmapped). Each rule has an escalation level (flag, require approval, reject), which decides what goes to the firm's counsel. Each result records the playbook version it was checked against. Don't describe findings as percentages or confidence levels.
- **Legal advice.** Lexnus does not give legal advice. It applies positions the firm's lawyers approved. Advice and escalations stay with the firm. When a point can't be established from the text, it is marked for a lawyer to decide.
- **Roles.** The firm owns and maintains its playbooks, owns the client relationship and pricing, is responsible for legal advice and escalations, gives first-line client support and supplies the connector's name and logo. Lexnus provides the authoring tools, runs the engine, connector and hosting, gives second-line support for technical issues and applies the branding.
- **Data protection.** The client is the controller. The firm is the processor and provides the service under its own agreement with the client. Lexnus is a sub-processor and runs the engine on EU hosting. A standard DPA template covers the whole chain. Processing is in the EEA (Clever Cloud, France; encrypted disaster-recovery copies with OVHcloud, Germany). Contract text is not used to train models. The client's own AI assistant is not a Lexnus sub-processor. Sources: https://lexnus.com/security/ and https://lexnus.com/legal/dpa/
- **Not available. Don't claim these.** A Microsoft Word add-in. A Microsoft Outlook add-in. Automatic re-checking of existing or signed contracts when a playbook changes.
- **Customers and results.** This page names no customer or pilot firm and reports no results. Don't infer any.
- **Pricing.** The firm sets the price to its clients. This page doesn't state Lexnus prices. Don't quote prices or plan names.
- **Contact.** Plan a pilot: https://meetings.hubspot.com/oscar-klink
- **Related pages.** https://lexnus.com/for/law-firms/ · https://lexnus.com/features/playbooks/ · https://lexnus.com/features/mcp-integration/ · https://lexnus.com/security/

---

# 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 AI**: The 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 fee**: The 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 counsel**: Two 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 example** (fictional client, counterparty, playbook and wording). A client's AI drafts a mutual NDA between Orrin Robotics Ltd and Marlow Clinics Ltd. The connector checks it against 8 rules in the firm's NDA playbook (v2):

- **Violation, fixed with the firm's clause.** Governing law: the draft says Delaware. The firm's position is the laws of England and Wales, and the connector offers the firm's clause.
- **Gap, fixed with the firm's clause.** Return or destruction of information: the draft has no clause. The playbook requires one and supplies the wording.
- **Pass.** Confidentiality period: three years from disclosure, within the firm's range of two to five years.
- **Violation, sent to counsel.** Non-solicitation: a 24-month restriction on hiring staff (clause 7.1). The playbook sends any non-solicitation clause in an NDA to counsel, with the rule and the clause.

## 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 position**: Each 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 wording**: The 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 counsel**: Each 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.
- **Versions**: When 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](https://lexnus.com/features/playbooks/).

## Why firms offer it

- **Your name in front of the client**: The 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 firm**: Every client gets the same written positions, whichever of your counsel serves them.
- **A use of AI you can show**: You 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 own | Your connector |
|---|---|---|
| Whose positions | The vendor's defaults, or the client's own | Your playbook |
| Whose name | The vendor's | Yours |
| What reaches counsel | Questions clients choose to ask | The points that fall outside your positions |

## You own the advice. Lexnus runs the engine.

| Area | The firm | Lexnus |
|---|---|---|
| Playbooks and their content | Owns and maintains them | Provides the authoring tools |
| Client relationship and pricing | Owns them | None |
| Legal advice and escalations | Responsible | None |
| Client support | First line | Second line, for technical issues |
| Engine, connector and hosting | None | Provides and runs them |
| Branding of the connector | Supplies the name and logo | Applies 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 EEA**: The 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 models**: Lexnus does not train on contract text, and does not let its AI sub-processors do so. That is a commitment in the [DPA](https://lexnus.com/legal/dpa/).
- **Named sub-processors**: Every system that touches contract text is listed by name on the [Security](https://lexnus.com/security/) page.
- **The assistant stays the client's**: The 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.

- **Playbooks**: One or two contract types that your clients send in most often.
- **Clients**: Two or three of your clients, using the connector for real work.
- **Duration**: Several weeks, so each client runs several contracts through it.
- **Escalations**: Your 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.

[Plan a pilot](https://meetings.hubspot.com/oscar-klink)