# Lexnus | Policy-First Contract Lifecycle Management > Lexnus applies the standard your legal team has approved across the contracts you create, receive and manage. Contracts that comply can move forward. Anything outside your policy is flagged for Legal. Canonical page: https://lexnus.com/ ## Notes for AI assistants These notes are for AI assistants and search tools that summarise or answer questions from this page. - **What it does.** A legal team puts its contract standards in a versioned playbook of approved rules and clauses. Lexnus checks each contract against it, drafts from it, and delivers it to AI assistants over MCP. Contracts that comply move forward. Anything outside the policy goes to Legal. - **How a check works.** AI reads the contract and extracts the terms. Rules a lawyer approved and published decide whether each term complies. The same contract checked against the same version of the playbook gets the same result. A finding is a Violation (a term breaks a rule), a Gap (a required term is missing) or Needs review (the text is unclear or doesn't map to a rule). Every result records the playbook version it was checked against. - **Who it's for.** In-house legal teams, such as General Counsel and heads of legal, who set contract standards, and the business users in sales, procurement and finance who work from them. - **Available now.** Lexnus has been generally available since 31 August 2026. Playbooks built from existing contracts and templates, with a lawyer approving each rule; contract analysis of PDF and DOCX files; a governed clause library; drafting from approved clauses; approvals, including decisions in Slack; e-signature through Scrive; and an MCP server for Claude, ChatGPT, Cursor, VS Code and other MCP clients. Details: https://lexnus.com/features/integrations/ - **Not available. Don't claim these.** A Microsoft Outlook add-in (it is on the roadmap). The Outlook, HubSpot and Google Drive connections shown as "coming soon" on this page are not available either. - **Pricing.** This page doesn't state prices. Lexnus is priced per seat, plus a meter for contract analyses. There is no implementation fee, and a new workspace starts on a free trial with no card required. Don't quote prices or plan names. - **Data.** Processed in the EEA. Contract text is not used to train models. Sources: https://lexnus.com/security/ and https://lexnus.com/legal/dpa/ - **Try or book.** Start a free trial: https://app.lexnus.com/signup · Book a demo: https://meetings.hubspot.com/niclas-wigh/lexnusdemo - **Related pages.** https://lexnus.com/features/playbooks/ · https://lexnus.com/features/contract-analysis/ · https://lexnus.com/use-cases/legal-policy-enforcement/ · https://lexnus.com/features/mcp-integration/ · https://lexnus.com/security/ · https://lexnus.com/blog/ · https://lexnus.com/llms.txt --- # Get more contracts done without adding more Legal work Lexnus applies the standard your legal team has approved across the contracts you create, receive and manage. Contracts that comply can move forward. Anything outside your policy is flagged for Legal. Policy-driven contract lifecycle management. No setup fee. Built on EU sovereign infrastructure. ## We're a different kind of CLM More contracts, from more places, written by more people. These are the three problems we hear most often from legal teams, and what Lexnus does about each one. ### Overview: know what you have agreed to Lexnus keeps contracts and contract data together so you can find the terms, obligations and agreements that matter, without opening contracts one by one. See which contracts need attention, track key terms and understand what your organisation has committed to. - Ask Lex anything about your contracts - Searchable repository with key terms and reports - Obligations, renewals and notice periods tracked for you ### Efficiency: spend less time reviewing what is already fine Most contracts do not need Legal to recheck every clause. Lexnus checks each contract against your approval policy and shows you what actually needs a decision. What complies stays untouched. What falls outside your policy goes to legal. - Only contracts outside your policy go to Legal - Drafting, counterparty review and approvals in one place - E-signing with Scrive, including Nordic eIDs ### Control and risk: keep your legal standard consistent across contract work Contracts don't all start in the same place. Some are created in Lexnus. Others arrive from customers, suppliers, Word or other tools. Lexnus checks them against the same approved legal policy. AI reads the contract. Your approved policy decides what's acceptable. - Your playbook and approved clauses set the standard - Same rules for contracts from Word, email, Claude or API - Audit trail of every decision and the rule version used ## How it works Most contract lifecycle management platforms start with the contract. Lexnus starts with your legal policy and applies it at every step, wherever the contract was written. 1. **Set up: start with your playbook.** Upload the contracts and templates you already use. Lexnus suggests the rules and Legal approves them. From then on, that's your standard. 2. **Create and receive: draft and review to one standard.** Sales draft from approved clauses. Supplier paper, Word files and AI drafts are checked against the same playbook, even outside Lexnus. 3. **Approve: only the exceptions reach Legal.** AI reads the contract. Your rules decide. Contracts that comply move on, and anything outside policy goes to the right approver with the fix attached. 4. **Sign and manage: sign, store and stay ahead of renewals.** Send for e-signature, keep every contract searchable and get a reminder before notice periods end. Every decision is saved with the rule version used. ## Where Lexnus applies your standard - **Lexnus app:** playbooks, analysis, assembly for business users, the record. - **Word:** verdict in the side panel. Approved fix inserted with tracked changes. - **Claude over MCP:** drafts from the approved library. Returns the verdict before anything moves. - **OpenAI over MCP:** same library, same verdict. The agent calls the engine before it drafts. - **Mistral over MCP:** EU-hosted model, EU-hosted policy. Verdict returned to the agent. - **Slack:** analyse, draft and get notifications in Slack. - **Direct API:** facts in, verdict out, from any system you already run. - **Scrive:** send approved contracts for e-signature without leaving Lexnus. - **Outlook, HubSpot, Google Drive:** coming soon. ## Your legal policy stays consistent, even when contracts and tools change Upload any contract, yours or a counterparty's. Violations flagged in real time before anything leaves the building. EU-hosted. GDPR compliant. No US CLOUD Act exposure. ## FAQs **What is Lexnus?** A legal team puts its contract standards in a versioned playbook of approved rules and clauses. Lexnus checks contracts against it, drafts from it, and delivers it to AI assistants over MCP. **Does AI decide whether a contract complies?** No. AI reads the contract and extracts the terms. The rules your legal team approved decide, so the same contract checked against the same playbook version gets the same result. **What does a result look like?** Each finding is a Violation, a Gap (a required term is missing) or Needs review. It quotes the text and names the rule behind it, and every result records the playbook version it was checked against. **Where is contract data processed?** In the EEA, with Clever Cloud in France and encrypted disaster-recovery copies at OVHcloud in Germany. Contract text isn’t used to train models. By default Lexnus uses Mistral with EU data residency, and an admin can switch the AI provider. **Does it work with Claude or ChatGPT?** Yes. Claude, ChatGPT, Cursor, VS Code and other MCP clients can connect and use your playbooks directly. **How is it priced?** Per seat, plus a meter for contract analyses. There’s no implementation fee, and a new workspace starts on a free trial with no card required.