The conversation about AI and privilege usually stops at hallucinated citations. This episode goes somewhere more dangerous: the moment you choose the wrong tier of AI tool, you may have already compromised your client's confidentiality. Matt Lafferman, a Dentons partner on the firm's AI task force, breaks down exactly how to build privilege defensibility into an AI workflow — from output labeling to mandatory human review to policy documentation that holds up in court.
Listen/Watch On
When AI becomes a privilege problem, most lawyers are still treating it like a productivity hack.
Solo and small firm attorneys hear constantly that AI saves time. What they hear far less often is that the AI tool they chose — and more specifically, the tier they're using — may have just waived their client's privilege. This episode forces that conversation. If you're putting client material into any AI tool without understanding exactly how that tool handles your data, you're not just taking a risk — you're potentially handing opposing counsel a gift.
Why the tier of AI tool you're using (free, Pro, Enterprise) is a privilege and confidentiality issue, not just a performance issue
The U.S. v. Heppner case: how using Claude at the Pro tier — not Enterprise — led to a court finding that confidential materials weren't protected
The Trembly v. OpenAI case (2024 U.S. Dist. Lexis 141362) and what it establishes about AI outputs as opinion work product
Why Harvey's architecture makes it suitable for confidential client material when Claude's public tiers do not
How to build privilege defensibility into your AI workflow: mandatory human review, output labeling, and policy documentation
Matt Lafferman's framework for ensuring AI outputs qualify as opinion work product rather than discoverable fact work product
Ron's "record everything" hot take — and Matt's push back on where that logic breaks down in sensitive matters
How in-house counsel faces a unique AI challenge because business and legal functions blur, and only the legal portions are privileged
Automating law firm intake: what tools like Clio, MyCase, and PracticePanther are building, and what Dentons is already doing
How Dentons uses Harvey as a document vault, including running tiered relevancy scoring on large document sets
The README file as the next frontier: why tech-sector in-house counsel may need to rethink document formats entirely
Ken Griffin's reversal on AI — from calling it "garbage" in January to expressing alarm at what agentic AI is doing to PhD-level work
Whether AI saves time or elevates work product quality — Ron and Matt respectfully disagree
The challenge AI poses for junior associate development and entering the legal market right now
The FSJ closing segment: Flintstones, Simpsons, and Jetsons advice from a Big Law AI task force member
Download: Notice of Intent to Use AI in Discovery Helps lawyers disclose AI use in litigation in a structured, defensible way. Covers:
When and how to disclose AI use to opposing counsel
Language for protective orders that includes AI tools in the definition of authorized agents
How to frame AI outputs as generated at the direction of counsel
Adaptable to different jurisdictions and risk profiles
Availability is not authority — and that principle extends to tool tiers. Using an AI tool that collects your prompts, trains on your outputs, and discloses data to third parties isn't just a privacy concern. It's a privilege waiver waiting to happen. Matt Lafferman's framework is straightforward: choose the right tool, mandate human review, mark everything as work product, and document your policy so you can show a court exactly how your AI workflow maintains privilege at every step.
For Flintstones lawyers, this episode is a fire alarm — the risks are real and courts are already ruling on them. For Simpsons lawyers using Claude Pro or a free tier for anything client-adjacent, this is the moment to audit your setup. Jetsons lawyers building custom agents should be baking these privilege protections into their workflow architecture from day one, not retrofitting them after a discovery dispute.
Harvey (enterprise AI platform for legal)
Claude (Anthropic) — Pro tier vs. Enterprise tier distinction
Microsoft Copilot
Clio
MyCase
PracticePanther
U.S. v. Heppner — Claude Pro tier, privilege, and work product
Trembly v. OpenAI, 2024 U.S. Dist. Lexis 141362 — AI outputs as opinion work product
Ken Griffin / Citadel — remarks at Stanford Business School on agentic AI
Judge Rakoff, Southern District of New York
Rule 26(f) AI Discovery Protocol Addendum
Notice of Intent to Use AI in Discovery
README / .md files as emerging document format for in-house counsel
WhatsApp communications in crypto litigation
Daubert motions
Ron's "record everything" CLE hot take