Henchman is a Belgian legal tech company providing AI-powered contract drafting tools that enrich data from document management systems for faster, higher-quality drafting. Acquired by LexisNexis in 2024 for reportedly ~$160M (Crunchbase, unconfirmed). Previously raised €6.5M Series A (2023) led by Adjacent VC and Acton Capital. Works natively in Microsoft Word, Outlook, and Copilot. Core capability: retrieves previously negotiated clauses, definitions, and positions from firm’s DMS (iManage integration confirmed), building a dynamic clause bank without manual setup. Multi-LLM approach for clause translation, verbiage changes, and enrichment. Language-agnostic — equally performant in all languages. ISO 27001 certified, SOC 2 compliant, GDPR compliant. Won BLTF Legal AI Supplier of the Year and ALM Legal Innovation & Technology awards. Hundreds of customers across 5 continents. G2: 4.5/5 (10+ reviews). Now integrated with LexisNexis content via Lexis+ AI platform. r/LawFirm user confirms positive experience. Target: law firms and in-house teams (15-5,000 employees) with complex contract drafting in M&A, Corporate & Commercial, Real Estate, IP & Tech.
Capabilities
Spans 2 product areas: Contract Automation and Drafting (Through Signature), Knowledge Management.
Workflow Coverage
Based on published feature listings, this tool maps to 8 workflow areas:
- Document Drafting & Automation — Approval Process Management, Collaborative Drafting and Editing, Contract Clause and Content Management, Contract Attachments Support (+8 more)
- Client & Matter Lifecycle — Buyer/Seller Qualifications Tracking, Completion Status Tracking
- Firm Operations & Growth — Integrations with CRMs, Proposal and RFP Generation
- Billing, Time & Finance — Pricing Integration, Quotes Preparation
- Research & Analysis — Reports and Dashboards
- Document Review & Management — Version Control
- Filing & Compliance — Compliance Tracking
- Communication & Collaboration — Mobile Access to Contracts in Progress
Workflow mappings derived from published feature lists. Not independently verified.
What We Haven’t Verified
This page was assembled from publicly available information. Feature claims and workflow mappings are based on what the vendor and third-party listings publish — not hands-on testing or practitioner feedback.
Workflows
Based on practitioner evidence, Henchman is used in these workflows:
What practitioners struggle with
Real frustrations from legal professionals — the problems Henchman addresses (or should address). Sourced from practitioner reviews, Reddit threads, and case studies.
Contract redlining is a nightmare — 7 rounds of Track Changes in Word, counterparty turns off tracking, and nobody knows what changed between v5 and v7
BigLaw firm with 1,000+ lawyers has decades of work product locked in DMS folders — the precedent brief the partner drafted 3 years ago is unfindable, institutional knowledge walks out the door when partners leave, and junior associates waste hours recreating work that already exists somewhere in the system
Associate reviews a 60-page credit agreement against the firm's playbook — manually checking each clause against preferred positions takes 6-10 hours, and fatigue-induced errors in the final sections are almost guaranteed
Law firm's knowledge management system is a SharePoint graveyard — thousands of precedent documents, know-how articles, and practice guides that nobody can find because the search is terrible and nobody maintains the taxonomy, so associates reinvent the wheel on every matter
Where it fits in your workflow
Before Henchman
Lawyer opens contract in Word → Henchman add-in activates → connects to firm's DMS (iManage) and LexisNexis content → retrieves relevant clauses and definitions.
After Henchman
Draft completed with best-practice clauses → sent for review/negotiation → final version stored back in DMS.
Integrations & hand-offs
Associate → Henchman (retrieves clauses from DMS). Henchman → Word (inserts enriched clauses). Reviewed contract → DMS for storage. DMS → Henchman (learns from new documents).
Also used by similar teams
Community Data
Loading practitioner-sourced data…