Executive masterclass · sixteen sessions
Built for a room that already runs legal teams. Not an explainer — a working method for deciding what to adopt, what to refuse, and how to prove either.
The approach
The masterclass does not run on vendor demonstrations. The major legal AI platforms are assessed through their own documentation, vendor materials and published independent evaluations — which is precisely the position a general counsel occupies when deciding whether to buy one. Participants bring their own stack; the method is tool-agnostic and is assessed on reasoning and justification rather than on which product was used.
Governance is treated as a design input from the first session rather than a compliance afterthought. The room is senior enough that the interesting question is never what the technology is, but what would have to be true before you would let it near a client matter.
A tool that is right ninety per cent of the time creates a supervision problem, not a productivity gain. Most of the course is about the other ten per cent.
The programme
A three-session hands-on review lab runs through phases two and three, built on a fictional facility agreement with defects planted in it. Nothing in the lab is drawn from a client matter.
What the stack is, what the evidence says, and where your own work sits in it.
Turning legal standards into artefacts a system can act on.
Whether the thing you built survives being checked, and who answers for it if it does not.
Present what you built, defend it, and look at what comes next.
Who is in the room
The masterclass is deliberately mixed: general counsel, law firm partners, senior associates and legal operations professionals, from private practice, in-house teams and regulated financial institutions. A GC's adoption problem is not a partner's billing problem is not a legal ops implementation problem, and putting the three in one room surfaces the trade-offs faster than any lecture does.
Practitioner guests contribute to specific sessions, drawn from firms and in-house teams that have actually deployed these systems — including the deployments that did not work.
Nobody in this room needs to be told what a large language model is. They need to know what they will be accountable for when it is wrong.
Assessment
What participants take away
The developments that matter, tested against the documents.
SubscribeDelivered via Substack. No spam — unsubscribe anytime.