I turn high-volume, messy documents into structured data teams can trust — extraction pipelines, real quality bars, and automated workflows that hold up at scale. Proven in legal, built to transfer: 100+ production models, 50,000 documents processed, 95%+ accuracy, every time.
"Most people on this work are either lawyers who don't trust the model or engineers who've never read a contract. I've done both — and that changes everything about how I build."
Most AI implementations in legal fail for one of two reasons: engineers who don't understand contracts, or lawyers who don't trust AI outputs. I've spent years on both sides of that problem.
With 6 years as a certified paralegal and 1+ year building enterprise data systems, I translate domain risk into model and data requirements — then build, evaluate, and deploy to a 95%+ production standard. Contracts are where I proved it; the method works on any document set that has to be right.
I've worked across financial services, energy, government, and law firm portfolios. I know how source data varies by industry and jurisdiction, how to design pipelines that survive expert scrutiny, and how to present model performance to stakeholders who have never seen a precision-recall curve.
That combination is rare. It's why teams bring me in when the stakes are high — and why the discipline transfers to any data that has to be trusted, not just contracts.
Detection modeling, extraction pipeline design, and structured dataset creation from unstructured documents — proven on legal language under attorney scrutiny, and built to work on any high-stakes document set.
Multi-agent orchestration with the patterns enterprise AI deployments need: doer + reviewer agent pairs, structural HITL gates at every handoff, low-confidence escalation, and event traces that show exactly what each agent did. See Stride for a live, working demonstration.
End-to-end delivery across 12 enterprise engagements: discovery workshops, governance design, pilot programs, change management, and reusable playbooks that compress program setup from days to hours.
I present AI performance findings to attorneys, legal ops leaders, and executives — bridging the communication gap most technical teams can't close, and accelerating sign-off where it matters.
A financial services client needed to extract and analyze key clause provisions across a massive contract portfolio. Manual review at that volume was cost-prohibitive and slow.
Designed the full clause taxonomy and extraction architecture. Built and evaluated detection models for indemnification, limitation of liability, termination, assignment, and payment obligations using prompt engineering on Relativity's AI platform.
Ran precision, recall, and F1 evaluation at every iteration. Built reviewer playbooks and labeling guidelines so attorneys could audit and trust model outputs before any result entered production.
Rather than starting from zero on each engagement, I developed reusable clause libraries, prompt templates, and reviewer playbooks that could be adapted across financial services, energy, and law firm clients — compressing onboarding time and raising the quality floor on every new matter.
Before building AI models, I was the person doing the work they would eventually replace. In private practice: estate planning, probate, M&A, corporate transactions, and real estate closings across 50+ concurrent matters. Then a city attorney's office: 1,500+ contract requests a year at zero backlog on a 24-hour turnaround, plus 200+ bills and resolutions drafted and shepherded to public record. That range — and working across differing court systems and jurisdictions — is the foundation of how I design data systems today.
Beyond client engagements, I ship working systems end-to-end — designed, evaluated, and deployed at production standards. Each one is real and working, hosted on chantelhill.com or running live in Google Workspace, and demonstrates a different facet of how I build: multi-agent orchestration, human-in-the-loop governance, workflow automation, and the same evaluation rigor I apply to client clause-detection work.
A working AI tool for project managers. Seven specialized agents — status synthesizer, risk detective, meeting prep, action tracker, comms tailor, tracker curator, and a reviewer/analyst that critiques every doer's output — execute in parallel and surface drafts at human-in-the-loop gates before any output advances. Built on the Anthropic SDK with client-side orchestration, parallel doer + reviewer phases, deterministic curator logic, and a persistent status tracker that survives across runs.
A working prototype that validates marketing attribution against measured causal incrementality. Built on synthetic data with known ground truth (50 cities, 26 weeks, 100K users), a hand-rolled geo-lift engine using two-way fixed-effects panel regression with cluster-robust standard errors, and a self-evaluation harness scored on precision, recall, F1, and threshold sweeps.
A six-tab project system that does the manager's prep itself. A live dashboard rolls up KPIs and team load with zero manual entry; a weekly status report writes its own headline and sections from tracker data; a follow-up builder mail-merges ready-to-send stakeholder drafts from any row; and a 7 AM Apps Script digest emails everything overdue or due for follow-up, unprompted. Priority-aware alert logic, 1,400+ live formulas, and every row pre-armed so new work inherits the system automatically.
Not because a client asked for it — because anything less isn't defensible in a legal context. If a model can't meet that bar, I iterate on prompt design and labeling guidelines until it does. Attorney trust is too expensive to lose on a bad output.
AI in legal doesn't replace attorney judgment — it has to earn it. Every model I deploy includes confidence thresholds, escalation paths, and audit trail design. Legal ops teams need to be able to explain what the AI did and why.
Gut-checking outputs isn't evaluation. I run rigorous statistical validation, track error patterns across categories, and document what breaks and why. That's what separates a model that works in a demo from one that holds up on 50,000 real documents.
When attorneys ask "why did the model flag this?" I can answer in legal terms. When engineers ask "what should the model extract?" I can give them a structured requirement. That's where most AI legal implementations break down.
The same concept reads completely differently across industries and jurisdictions — indemnification in a financial services agreement looks nothing like it does in a municipal contract. Six years of hands-on review means I build systems that handle that messiness, not just the clean examples that make demos look easy.
Not every AI use case in legal is worth building yet. Part of my consulting work is helping clients figure out where AI actually saves time versus where the error rate makes it a liability. Sometimes saying "not yet" is the highest-value thing I can offer.
If you're scaling AI-assisted contract review and need someone who understands both the legal risk and the technical execution, let's talk.