Every requirement in this JD maps to something I have already built.
The role bridges legal practice, business operations, and technology. It coordinates, facilitates, measures, and enables. Below is the evidence, organized by the four function areas of the JD — 8 MVPs shipped, 990 automated tests, 30+ workflows, 150+ professionals trained monthly.
Function Area 1
AI Strategy & Solution Design
JD: Partner with legal teams to identify AI opportunities in client workstreams
Embedded at Fortune 500 SaaS — 4 departments, discovery-first, workflow mapping before any build
Separation agreement agent — ~100 agreements/year across US, EMEA, Australia
Legal metrics agent — natural-language access to contract data and outside-counsel spend
Result: ~190 hrs/year saved. 5 agents deployed in 6 months across departments that had never used AI
JD: Translate business and legal needs into AI solution requirements; facilitate proof-of-concept development
AESOP OS — 990 tests, 6 eval modes, 30+ workflows. Turns discovery into structured requirements and PRDs
Legal AI OS — 9 legal functions built and deployed, each started as a POC
Matter Intake Evaluator — configurable rubrics that adapt to the firm
Result: evaluation time: hours of manual review → minutes of automated scoring. 8 MVPs shipped, 7 POCs proven
JD: Ensure AI solutions align with governance, ethics, and risk standards
4-dimension scoring engine — Safety, Bias, Accuracy, Compliance. 990 tests. Hard veto on critical failures
Independent Harvey evaluation — same engine ported to Legal AI OS. Vendor can’t grade its own homework
ABA Formal Opinion 512 — 6 duties baked into compliance evaluation prompt
Result: governance: manual committee → automatic on every change. 1.4M test executions
Direct Experience
Employment legal agents with strict access controls walling employment data from commercial legal — the exact confidentiality gap that blocked prior tools.
Direct Experience
Legal metrics agent giving leadership natural-language access to contract execution data and outside-counsel spend.
Platform
9 legal AI functions built and deployed in Legal AI OS — Matter Intake, Contract Review, Due Diligence, Regulatory Monitor, and more.
Platform
AESOP authored discovery maps inherited processes then questions structural assumptions — finding where AI changes the operating model, not just speeds it up.
Function Area 2
Program Management & Execution
JD: Lead end-to-end delivery of AI-enabled client projects from concept through implementation
AESOP OS — 10 stages, 6 evaluation modes, 30+ workflows. Each stage instrumented with structured telemetry
Legal AI OS POC pipeline — Discovery → Build → Review → Graduated/Cancelled. WIP limits, department filtering
Contentful — 5 agent engagements, 4 departments, discovery through deployment
Enablement kit — workshop deck, prompt engineering guide for lawyers, adoption playbook, AI literacy FAQ
Champion network identification — deployed across 4 departments, 150+ professionals
Result: adoption planning ships with the agent, not after. Change management as pre-launch artifact
JD: Promote a culture of experimentation, measurement, and continuous improvement
Continuous feedback loops — test, iterate, measure, repeat. Every change verified before it ships
Drift detection — 7 dimensions. Catches degradation before it becomes liability
POC pipeline — graduates what works, kills what doesn’t
Result: 1.4M test executions across the portfolio. Measurement as continuous, not quarterly
Cross-Cutting Themes
Privacy, Governance, Discovery
Three themes that run through every project and map directly to the operating realities of a law firm deploying AI.
Privacy & Confidentiality
In a law firm, confidentiality isn't a feature — it's an existential requirement. ABA Formal Opinion 512 names it as one of six core duties. I've built confidentiality architecture into every system I've deployed.
Enterprise
Strict access controls walling employment legal data from commercial legal at Contentful — the exact confidentiality gap that had blocked adoption of prior contract-management tools.
Architecture
Tenant data isolation enforced at the database level across all platforms. Not middleware. Not app logic. Client data cannot leak. The architecture guarantees it.
Compliance
ABA 512 compliance evaluation prompt in the Harvey monitoring system — every agent output scored against the 6 duties, with confidentiality weighted at 30% of the safety dimension.
Pattern
Human-above-the-loop architecture: auto-generate everything, auto-send nothing. Every automated output has a human review gate before it touches a client.
Governance
The firm published its AI governance framework in June 2026 — 5 principles. I build the tools that turn principles into enforcement.
Evaluation
4-dimension scoring engine with veto power — Safety, Bias, Accuracy, Compliance. 990 tests. Any critical failure blocks deployment. Governance as code, not committee.
Monitoring
Drift detection across 7 dimensions — Tone, Scope, Refusal, Instruction Erosion, Hallucination, Safety, Disclaimer. Catches degradation before it becomes liability.
Audit
Append-only audit trail with explainability and traceability. Every evaluation, every override, every drift alert — timestamped and immutable.
Independence
Harvey can't grade its own homework. The Legal AI OS provides independent evaluation of vendor-deployed agents. The evaluator is structurally separate from the evaluated.
Discovery
Finding where AI creates value isn't guesswork. It's a structured process I've productized.
Method
Two-phase authored discovery: Phase 1 maps the inherited process. Phase 2 questions structural assumptions through 7 decision-first categories. Finds the highest-value points of intervention.
Enterprise
Stakeholder listening sessions and workflow mapping across Legal, Procurement, Finance, and People Operations before any build. Requirements grounded in what people actually do.
Output
Decision surface: a structured artifact capturing what changes, who owns it, what boundaries apply, what evidence proves it worked. Executive-ready, not consultant-speak.
Platform
POC pipeline from discovery through graduation. Every AI initiative tracked. What's in discovery, what's in build, what's in review, what graduated, what got killed and why.
Honest Scope
What I Don't Overclaim
The role scope document is clear about what this role does not own. I match that scope.
Not applying as the architect who unifies post-merger DMS/KM. That belongs to IT, KM leadership, and external consultants. I build the POCs that prove what's worth unifying.
Not applying as the Harvey deployment owner. Technology owns vendor relationships. I build the independent evaluation layer that proves Harvey is working — because Harvey can't grade its own homework.
Not applying as the AI governance framework author. The firm published its 5 principles in June 2026. I bring the tools that operationalize them: scoring engines, drift detection, compliance mapping.
Not applying as the pricing strategist. Pricing/LPM owns AFA design. I provide the time-saved data and cost-impact analysis they need to price.
Not applying as the client relationship owner. I'm the technical specialist the relationship partner brings into the room. I build the deck, the FAQ, the audit trail, and the confidence.
The Narrative
What I Carry Into the Room
I understand how law firms make money and where AI creates tension with that model. I know how to find the highest-value AI use cases inside practice groups, run small POCs to prove them, track everything so we know what's working, and teach lawyers to use the tools. I've done all of this — the workflow discovery, the POC builds, the portfolio tracking, the enablement programs. I bridge the gap between what the practice groups need, what the technology team can build, and what the pricing team needs to price.
The one-line answer: 85% of firms don't track AI ROI. I've built the systems — the POC pipeline, the portfolio dashboard, the ROI framework with calibrated baselines — that put a firm in the 18% that does. Backed by 1.4 million test executions and 30+ production workflows.