Missed it live, or want to go back over the setup? This is the recap of the session where Paul Lacey built the foundations on screen: the shared brain on Claude Cowork, the scheduled tasks that keep it alive, what changes when an agent owns the outcome, and the honest conversation about trust and supervision with Lorna Khemraz and Lili Breidenbach. The full recording and the slide deck are both here.
Individual lawyers are getting faster with AI everywhere. The question Jake opened with is the one that actually matters: has the throughput of your legal function changed, or are individuals just quicker at their own tasks? That gap is what the whole session was about.
Paul answered it in three moves. First, the foundation: a shared, layered knowledge base (the "brain") that every Claude Cowork seat in the company plugs into, kept alive by scheduled tasks rather than left to rot like most knowledge bases. Second, the work you don't want done faster but gone entirely: purpose-built Flank agents that pick up requests where they already arrive and own the outcome. And third, with Lorna and Lili, the honest part: what it actually takes to trust an agent's work, and why the supervision burden falls over time instead of staying flat.
Every slide from the session: the shared-brain layers, the Cowork setup, the supervision surface, and the effort curve from the trust conversation.
Paul's live build, the Flank walkthrough, and the conversation with Lorna and Lili. If you'd rather skim, the written recap below covers the essentials.
Everything Paul showed is the setup Flank actually runs on, live on screen, not a canned demo. It starts with the four building blocks of Claude Cowork.
The interesting part isn't Cowork itself. It's the "brain" behind it: one knowledge base every seat in the company plugs into, so the whole team works from the same context instead of diverging.
Under the hood it's nothing exotic: plain markdown files in Box. Two design choices do the heavy lifting. Every document opens with instructions for agents, because the system is written for AI to read, not humans. And a single README tells Claude how to navigate the whole thing, so it goes straight to the right folder instead of reading everything. Faster, cheaper, more reliable.
Nobody wrote the brain by hand. The team pointed Claude at everything lying around: laptops, drives, LinkedIn, the website. Claude drafted the documents, flagged gaps and contradictions, and humans reviewed. Start with a small, coherent version one. It's easy to grow from there.
Every legal team knows the SharePoint graveyard: built with goodwill, dead within a year. The difference here is that the brain maintains itself, on a schedule that matches each layer.
AI tools are only as good as the context they're given. When the context goes stale, they stop being used.
And the "marketing brain" label is a misnomer. Jake's framing: this matters more in legal than almost anywhere else. Consistency of positions, house language, knowing who's an existing client, how a specific customer likes things formatted. Enterprise teams are fragmented and lossy; people leave and take context with them. The brain is the team member who holds all of it and never resigns.
Paul's honest boundary: Cowork is excellent, and Flank uses it everywhere. But a tool can only make a person faster. For high-volume, routine, quasi-legal work, the kind you'd push to an ALSP or an offshore center, faster isn't the goal. Off the team's plate is the goal.
That's the domain-specific side. Flank agents deploy where requests already arrive: shared inboxes, Salesforce, Ironclad, Teams. No new tool for the business to learn, no change management. Paul showed it end to end: he emailed a licence agreement drafting request with deal documents attached, the way anyone would email legal, and the agent replied with a draft and a summary of what it did.
If a lawyer has to check everything, you've saved nothing. The supervision panel exists so the lawyer checks only what's essential. Customers start by supervising a lot, and the burden drops week by week, toward only the genuinely high-risk third.
Lorna Khemraz leads legal AI alignment at Flank and spends her days inside real enterprise deployments. Her opening admission set the tone: the first reaction to "the agent does the work" is confusion, then scepticism. And that's rational.
Every legal task hides dozens of micro-decisions, and lawyers are rightly wary of outcomes they can't trace. Handed a finished review with no visibility, Lorna said she'd do what any lawyer would: check the whole thing end to end, because she's still accountable. At which point you might as well have done it yourself.
What changes that is visibility plus consistency. With the supervision panel, there are no unanswered questions: why the agent made each call, what it escalated and why. Over time she checks less and less, "because the agent is effectively acting as an extension of me. It's working to my standards."
Legal teams have made this trust journey before, every time work moved to a new hire, a service center, an ALSP, or a law firm. Competence was never the whole question; context was. You supervise everything at first, then let go task by task. The only difference now is that the new resource is infinitely scalable. And for some work you'll never go fully autonomous, which is fine: your people stop doing the work and become the arbiters of what good looks like.
This thread continues. Lorna Khemraz goes deep on exactly this territory in the next webinar: The 2027 operating model for in-house legal. Building systems your team can actually rely on, and the skills it takes to run them.
Share the full presentation with your team, IT, or procurement. Everything Paul walked through, in one PDF.