The contract is not the problem. The missing policy layer is.

Where Lexnus comes from

Precisely has run contract lifecycle management since 2014, out of Gothenburg, Sweden. Years spent watching legal teams manage contracts kept surfacing the same gap: General Counsel set the standards, and had no reliable way to make sure those standards were followed. Templates existed. Enforcement didn't.

Lexnus is what we built to close that gap. It reads the policy a legal team already has, turns it into rules a computer can check, and applies those rules to every contract the organisation touches — the ones it sends, the ones it receives, and the ones drafted with AI.

Lexnus reached general availability on 31 August 2026, led within Precisely by Oscar Klink as CTO and Niclas Wigh as CRO. Read the launch announcement.

What we believe

Every CLM on the market treats the contract as the primary object: create it faster, sign it faster, store it better. Lexnus treats the policy as the primary object. The contract is the output.

When a sales rep generates a contract from a template, something should know whether that liability clause is the one legal approved last month. When a lawyer receives a counterparty's contract, something should check it against the organisation's actual standards before she does. When someone drafts a clause with AI, something should verify it against approved language before it reaches anyone outside the building. That "something" hasn't existed. We built it.

What Lexnus is not

Where it runs

Every system that touches contract text runs inside the EEA, operated by European companies, with nothing used to train outside models. That isn't a policy statement — the Security page names every sub-processor.

Company facts