Director, Content Collections

Clio is the global leader in legal AI technology, empowering legal professionals and law firms of every size to work smarter, faster, and more securely.  We are transforming the legal experience for all by bettering the lives of legal professionals while increasing access to justice . Summary: The Director of Content Collections owns Clio's legal content collection as a single global portfolio — the substrate of the company's content moat and of Vincent AI's research quality and directly manages the team of Content Managers who have individual ownership and responsibility of the various jurisdictions' datasets. The overarching role of the Content Managers is to own the end-to-end strategy, performance, and resilience of Clio's data collections, a cornerstone of the company's legal-content moat and Vincent AI engine. They assess the ongoing quality and competitiveness of the data sets they're responsible for and determine the strategy and prioritization of ongoing data expansion. Where each Content Manager owns one or more jurisdictions end to end, this role owns the system they operate in; the standards that make collections comparable, the capital allocation that decides which jurisdictions get investment, the single prioritized demand signal into Data Ops and Content Engineering, and the team of managers themselves. Most of its leverage outside its own team comes from the quality of its specifications and the credibility of its ROI cases, not from reporting lines. Success is measured less by any single collection than by whether every collection is getting better, faster, and cheaper at the same time and whether Vincent's research answers hold up in every market Clio sells in. What You'll Do 1. Lead and Develop the Content Manager Team Hire, onboard, and develop country and regional Content Managers, building a bench deep enough that opening a new jurisdiction isn't gated on a new hire. Set the operating rhythm; roadmap reviews, quarterly business reviews, coverage-parity readouts, and 1:1s that raise the quality of judgment, not just the reporting of status. Define the Content Manager role ladder and performance standards, making the difference between a good and a great collection owner explicit and coachable. Create the Content Manager guild, so jurisdictional learnings, source-acquisition tactics, and enrichment patterns propagate across countries rather than being rediscovered. Own succession and continuity so no collection carries single-person risk. 2. Own the Global Collection Portfolio Define the multi-year content strategy: which jurisdictions Clio invests in, at what depth, in what sequence, and anchored to Product's market roadmap and to the coverage bets worth making ahead of it. Allocate budget, headcount, licensing spend, and partner-team capacity across jurisdictions against a consistent value model — not by whoever argues loudest. Maintain the global coverage picture: parity versus AI-native players (Harvey, Legora), global legal publishers (Westlaw, LexisNexis), and regional incumbents, with a clear view of where Clio is ahead, at parity, or exposed. Set the bar for what "market-ready" means in a new jurisdiction, own the go/no-go on launch readiness, and arbitrate trade-offs between depth in mature collections and breadth into new markets. Own the build/buy/license decision per jurisdiction with Secondary Content, Licensing, and Corp Dev — including when licensing a collection makes more business sense than building one. 3. Govern Content Surfacing and Vincent Research Quality Set the framework governing where each collection surfaces. The same content is exposed differently in Clio Library, Clio Work, and Vincent for licensing, cost, and product reasons; Content Managers co-own the call with Product, and this role is accountable for consistency across the portfolio and for keeping licensing and cost constraints honoured. Own the global framework for the Vincent research skill: how sources are tiered across Clio Library, private index, and agentic web search, and what evidence is required to move a source between tiers. Own the evaluation methodology, benchmark question sets, and quality gates that make Vincent answer quality measurable by jurisdiction rather than anecdotal — so "good research output" means the same thing in São Paulo as in London. Diagnose research-quality failures to the right owner — missing coverage, bad parsing, weak citator linking, retrieval configuration, or model behaviour — and drive remediation with that team rather than escalating undifferentiated complaints. 4. Set the Standards the Content Supply Chain Runs On Own and version global metadata and structural standards — citation models, court and legislation hierarchies, amendment tracking, document typing — so cross-jurisdiction features are possible at all. Data Ops and Content Engineering implement to these standards; Collections defines them. Define acceptance criteria and quality thresholds for ingested and enriched content, and own the sign-off on whether output meets spec. Specify citator requirements per jurisdiction treatment types, linking depth, precision and recall targets as the authoritative input to Content Engineering's build. Set freshness, reliability, and data-integrity requirements for the portfolio, and make the business case for the pipeline resilience and disaster recovery they imply. Set the enrichment agenda: what is worth human effort, what should be AI-assisted, and what should be automated outright — with the quality bar and evaluation method that makes those calls evidence-based, and generalizable patterns productized once rather than solved per country. 5. Partner with Product on Roadmap and Content Readiness Serve as Product's counterpart for content: translate roadmap intent — a Clio Work launch in a new market, an enterprise segment push, a new research capability into a costed, sequenced content plan with an h