Features
Contract Drafting
Lexnus assembles contracts from your approved Clause Library based on playbook rules and deal-specific inputs. Business users describe the deal. Lexnus produces a compliant DOCX. Every clause in the output has been reviewed and approved by legal. Nothing else gets through. Drafting speed and legal compliance are no longer in conflict.
How it works
Describe the deal
A business user in sales, procurement, or HR describes the deal in plain language or answers a guided questionnaire. What type of contract is needed. Who the counterparty is. What the value is. What the governing law should be. Lexnus uses these inputs to populate Smart Fields.
Lexnus selects the right clauses
Based on the Smart Field values and the active playbook, Lexnus selects the appropriate clause for every section of the contract. A $2M deal with a UK counterparty gets a different liability cap variant than a $200K deal with a Swedish counterparty. Conditional clauses, such as a company car clause or a reporting structure clause, are included or excluded based on the deal context. All of this is automatic.
Approval routing where needed
If any clause selection or deal parameter triggers a rule that requires approval (high-risk terms, large deal values, exceptions to standard policy), the contract is routed to the designated approver before a document is produced. Business users cannot generate a contract that bypasses this step.
DOCX output
The assembled contract is exported as a standard DOCX, ready for counterparty exchange. Section numbers are computed automatically. Variable tokens are populated. The document is clean, professional, and compliant with your policy.
Key capabilities
- Policy-governed assembly — Clause selection is driven entirely by your playbook rules and Smart Field values. No business user can insert unapproved language or modify clause text.
- Smart Fields — Structured data points (counterparty name, contract value, governing law, notice period, payment terms) that drive clause selection and populate contract text dynamically.
- Conditional clause inclusion — Clauses are included or excluded based on deal context. The contract structure adapts to the deal without requiring manual configuration.
- Approval routing — Deals that exceed defined thresholds or trigger exception rules are routed to legal before a document is produced.
- Clean DOCX output — Standard Word document output. Section numbering computed automatically. No proprietary format. Counterparties receive a normal Word file.
- Onboarding included — Lexnus helps you set up your first playbook and clause library from existing templates. Live in under an hour. No implementation fee.
Who uses this
Business users in sales, procurement, and HR use contract drafting to generate their own contracts without involving legal for every deal. They describe the deal, answer a short set of questions, and receive an approved DOCX. Legal has already encoded the rules. Business users operate within them.
General Counsel benefit by removing themselves as the bottleneck on standard contracts. Routine NDA and MSA generation no longer requires legal review. The playbook has already done the work.
Lawyers use drafting for outbound contracts where speed matters. The assembled draft starts from approved clauses, so the negotiation begins from a compliant position.