Legal Operations (Legal Ops) is the function that runs the systems, data, vendors, and process behind a corporate legal department. Where the General Counsel owns legal advice and risk, Legal Ops owns the operational machine that delivers it: the contract pipeline, the matter management system, the outside-counsel spend, the legal AI stack, and the metrics that justify the legal team’s headcount and budget to the CFO.
What a Legal Ops team actually does
The day-to-day breaks into five areas, codified by CLOC’s Core 12 framework but practiced more pragmatically:
- Contract operations. Owns the contract lifecycle management platform (Ironclad, Agiloft, SirionLabs), intake forms, approval routing, clause libraries, and the playbooks reps and procurement use for self-serve contracts.
- Matter and spend management. Tracks every matter (litigation, transactions, regulatory) and every dollar spent on outside counsel. Owns legal spend management tools and reporting.
- Vendor and tech management. Selects, procures, and integrates the legal tech stack — research (Westlaw, Lexis), AI (Harvey, Spellbook, Claude + custom Skills), CLM, ediscovery, billing.
- Knowledge and self-service. Builds knowledge bases, contract templates, and intake portals so the business can answer routine questions without involving counsel.
- Data and reporting. Pipeline of contracts in flight, cycle time by contract type, outside-counsel spend by matter, AI adoption metrics. Whatever the GC needs to defend the budget.
Legal Ops vs General Counsel
The General Counsel is the head of legal — owns the legal advice, attorney-client privilege, and the ultimate risk decisions. Legal Ops sits inside the legal department but is usually a non-attorney function (most Heads of Legal Ops are not lawyers). The split mirrors how RevOps sits under the CRO without itself selling, or how Sales Ops supports sales without carrying quota.
Legal Ops typically reports to the GC. In larger organizations, the Head of Legal Ops or VP Legal Ops reports directly to the GC and sits on the legal leadership team alongside the deputy GCs.
When does a company need Legal Ops?
The trigger is rarely company size — it’s contract volume and outside-counsel spend.
- Below ~$5M annual outside-counsel spend, the GC’s executive assistant or paralegal handles ops by hand
- Between $5-20M, a single Legal Ops Manager (often a non-attorney with a process or operations background) is enough
- Above $20M, the function professionalizes — Director or VP Legal Ops, dedicated tooling budget, sometimes a Legal Ops engineer for CLM customization and AI integration
A second trigger: when the legal team becomes the bottleneck on revenue. If sales cycles slip because contracts sit in legal queues for two weeks, the CFO will fund Legal Ops to fix it before they fund more attorneys.
Why Legal Ops matters more in the AI era
Pre-AI, Legal Ops was about workflow, vendor management, and reporting. AI changes the scope. Whether to deploy Harvey, Spellbook, Thomson Reuters CoCounsel, or Claude with custom Skills is now a Legal Ops decision, with implications for cycle time, cost, and quality. The function went from cost-center plumbing to the team that decides how the corporate legal department adopts AI.
Related
- Contract lifecycle management — the largest single Legal Ops responsibility
- Matter management — the system underneath outside-counsel and litigation tracking
- Legal spend management — how Legal Ops controls outside-counsel cost
- Ironclad — the most-deployed CLM in growth-stage Legal Ops stacks