Introducing Lexnus: your legal standards, enforced on every contract

In a live webinar on 1 September 2026, Oscar Klink, CTO, who came up with the idea for Lexnus, and Mahé Bonnot, Legal Expert, introduced Lexnus. They explained why it exists and then showed the product: building a playbook from a contract, drafting against it and checking a contract from a counterparty.

This page summarises what they covered. The demo starts after the first five minutes of context. If you prefer YouTube, the recording is also on the Lexnus channel.

Why legal teams need a way to stay in control of contracts

Mahé opened with how the contract landscape has changed over the last decade, from mainly paper contracts to something far more digital, with AI speeding the shift up. She quoted figures that 25% of lawyers use AI daily and that 92% have used it in the last year.

It is not only lawyers. AI has given a lot of people access to legal knowledge, and they can now draft simple contracts themselves. For legal teams, that makes it harder to stay in control of what is being drafted.

Oscar added the longer view. When e-signing was the big thing, nobody talked about automating contracts. Now contract creation needs to become more democratised in the organisation: legal should not draft every contract and should not be the bottleneck. Lexnus takes that one step further and starts from a different question. If a contract is a document, what governs what is in it?

What is a playbook?

Oscar's answer is a policy. It is either a written document or it exists in people's heads: these are our boundaries, this is what we can agree to and this is what we cannot. It is the risk and reward calculation every lawyer makes when reading a contract, and Lexnus is built to capture it.

At the core of Lexnus is a playbook that contains rules and clauses. The idea is that the same playbook can be used in every tool your organisation uses to draft a contract, not only in Lexnus.

How to build a playbook from a contract you have already signed

Mahé walked through the onboarding that new users see when they register. It is meant to be short:

• Start setup. Upload a template, or start from scratch. The file does not need to be a polished internal template. It can be the contract you signed yesterday.
• Let Lexnus clean up the document. It extracts the clauses and replaces counterparty names with variables.
• Choose clauses for the clause library. Clauses you add can be reused in other playbooks. Some content blocks stay specific to this playbook.
• Select the smart fields. Fields already in your workspace are reused, and you add any that are missing. In the demo, three.
• Review the proposed rules. Lexnus proposes rules just by reading the contract, with no input from you. Two examples from the demo: the delivery end date must come after the first delivery date, and the governing law must be included.
• Publish. Once the rules are added and the playbook is published, users can draft or analyse contracts against it.

If your rules already live in a Word document, you can import them instead. If they only live in people's heads, they need to be written down first.

Rules that flag, require approval or block

Each rule decides what happens when a contract does not meet it. A rule can flag the issue without blocking, trigger an approval, or block the contract. The same rules apply when a user drafts from the template and when they import a third-party contract.

Clauses are global, with variants

Clauses live in a clause library rather than inside one playbook or template. Oscar explained why: a liability clause should be much the same across your contracts, with some variation, so that you keep control. Clauses support conditional wording and fallback clauses.

Mahé showed variants. You might use one version of a liability clause in an NDA and another in a sales agreement, and you create those variants in the library.

Drafting a contract against the playbook

Mahé then drafted a mutual NDA. She started a new draft, chose the playbook and answered a few questions. Oscar explained what the screen is doing: an agent fetches the information from the playbook and works out what it needs to collect from the user to draft the contract. Support for MCP in this step is planned, so the agent could look up details in a system such as HubSpot or Salesforce, suggest the values and leave the user to confirm or change them.

Along the way, Lexnus picked up an inconsistency in the wording, a mix of English and Swedish, and asked which version to use. When the draft was done, it was checked against the playbook, and it was flagged: the penalty in the contract was well above the playbook's limit of 100K. Mahé said the example was set up on purpose.

From there the user has two options. Wait for an approval, or, if it was a genuine mistake such as an extra zero, fix the clause on the spot. The contract is then analysed again against the playbook.

Checking a contract from a counterparty

The last part of the demo showed the other direction. You upload a contract and choose the playbook to check it against. Mahé used her mutual NDA playbook again, with an NDA a counterparty had sent her.

Oscar described the process. The contract can be one you received, or one signed outside the platform, which he said happens a lot. Lexnus takes it apart: it divides it into clauses and extracts the values the playbook needs, the smart fields connected to the rules. If a value is missing or uncertain, it asks you to supply it, because the rules need it.

The compliance check flagged the penalty clause again, above 100K, so Mahé would have had to update the contract before signing. What happens next depends on the rules. The contract can need approval, be flagged or be blocked completely. A blocked contract cannot be sent for signing, and one that needs approval or has been rejected cannot go to signing either. In Oscar's words, it is a compliance check. See contract analysis and counterparty review for more.

Where is Lexnus data hosted?

Oscar called this the legal team's favourite question. The decision was made before anything was built or set up: Lexnus would be a fully EU-based service. Every sub-processor added to the DPA needs to be European, preferably hosting its servers in Europe and European-owned. All the data is hosted with European providers rather than the big American ones, with a focus on smaller European vendors that offer stable, good service. As one example, Lexnus uses Mistral as its language model.

Mahé, speaking as the legal adviser, said it helps her sleep better at night. Oscar added that it is also about supporting European providers, because most companies default to the big giants. Read more on the security page.

How Lexnus connects to the AI tools you already use

On integrations, Oscar said the only thing built from scratch was an MCP server, so that Lexnus works with any AI provider that supports MCP. You can draft and analyse contracts from those tools. If you work on a contract in Claude, it will tell you when what you drafted violates your playbook. The idea is one playbook connected to everything. See MCP integration.

The second integration was Slack, which the first test customer asked for. The team took the AI assistant that already exists inside Lexnus and made it available in Slack. You also get notifications there, such as a pending approval or a signature.

Oscar's view is that integrations should come from users. A contract is not a silo. It is one step in a larger process, whether that is an employment, sales or partnership agreement, so Lexnus is a puzzle piece in a bigger puzzle, and the team builds the integrations its users need. See integrations for what is available.

What does the name Lexnus mean?

Asked about the name, Oscar said that naming a product is one of the hardest parts of building it. Lexnus combines "lex", law, with "nous", the ancient Greek word for intelligence or mind. The name puts law and intelligence in one word.

Try it and tell the team what you think

The speakers closed by inviting everyone to sign up and try Lexnus. The first version is built and development continues, so ideas, feedback and requests for the first integrations are welcome. If you want a deeper demo or have a question, you can start a free trial or book a demo.