Which AI tools does this work with?

Any tool that supports MCP, which includes Claude, ChatGPT, and Mistral. The integration is not exclusive to one provider. If your organisation switches AI vendors next year, your playbook and clause library come with you.

Does the team have to change how they work?

No. They keep drafting in the tool they already use. Lexnus runs underneath it. The visible change is that clauses come back from your approved library rather than being written from scratch.

How long does setup take?

Most teams publish a first playbook in under an hour from the first upload. There is no implementation project and no onboarding fee on any plan.

What if a clause cannot be evaluated reliably?

It is flagged as Unknown and surfaced for a human. Lexnus does not produce a pass on a provision it could not read properly.

Where is our data held?

EU infrastructure, with no US CLOUD Act exposure. Contract text is not used to train any model.

There is a free tier with one playbook and ten analyses a month. Paid plans start at €400 a month. No setup cost on any plan.

Let the business move at AI speed. Keep your legal standards intact.

Someone in sales is drafting an NDA with ChatGPT this afternoon. An associate is redlining an MSA with Claude in Word. None of that language has been reviewed by anyone in legal, and there is no process that catches it before it reaches a counterparty. Lexnus sits underneath whichever tool your organisation has chosen and evaluates every clause against your playbook first.

Your policy is already written. It is sitting in the contracts you have signed and the templates you have built. Lexnus reads them, extracts the rules, and runs them on everything that follows.

You did not approve any of this

AI drafting reached your organisation without a procurement decision. Nobody ran an evaluation, nobody signed a DPA, and legal was not asked. It arrived through individual accounts and personal habits, and it is already producing contract language that goes out under your company name.

Blocking it does not work. Teams that ban the tools get shadow usage they cannot see. Teams that allow them get language nobody reviewed. Neither position gives the General Counsel any control over what the contracts actually say, which is the only thing that matters when a dispute arrives three years later.

How it works

Upload your templates and signed contracts

Lexnus reads your Word templates and executed agreements and builds a first playbook from what it finds. Your liability caps, your notice periods, your governing law positions, all extracted from documents you already have. No workshop, no rules written by hand.

Review the rules and publish

You go through what was extracted, change what needs changing, and publish. This takes most teams under an hour. Nothing is enforced until you have approved it.

Connect the AI tools your team already uses

Lexnus exposes your playbook and clause library over MCP. Claude, ChatGPT, and Mistral can all call it. When someone drafts a clause, the tool retrieves your approved language instead of generating new language. When a counterparty sends paper, it is evaluated before a lawyer opens it. A human stays in the loop throughout: anything Lexnus cannot evaluate reliably is flagged and routed to a person, not passed through.

Who this is for

General Counsel who have been asked whether the company can use AI on contracts and do not have a good answer yet.

Legal Ops who need AI drafting to produce auditable output rather than plausible output.

In-house lawyers who are reviewing the same three issues every week because nothing in the process remembers last time.