← Back to Resources

Legal Tech Talks: Advocacy's Téo Doremus on AI Skepticism

Company founders, attorneys, and other legal-technology professionals share their journeys into the industry, the challenges of working with law firms and legal departments, and common misconceptions about technology in the practice of law.

I never planned to end up here, but in retrospect, every step was preparation for it.

My career has been a series of translations. I was born and raised in Paris, earned a civil law degree, and spent years in cross-border M&A in China before pursuing an LLM at UC Berkeley. The transition from transactional work to litigation came later, but when it did, I found myself working on complex federal court cases and Delaware Chancery Court litigation at Robbins Geller.

Transactional work and litigation are fundamentally different beasts — the prose, the pace, the rules, the pitfalls, the etiquette. Virtually everything.

Litigation begins from opposition. You're working across millions of documents, depositions, motions, and evolving strategy as case law shifts. There's a third party, too: the court. And no AI-native solution existed for this space. Most tools were bolted onto legacy platforms or designed for transactional workflows that don't fit the work litigators actually do.

§ 2Common Misconceptions Attorneys Have About Working With New Technology

First misconception: AI is arcane. You don't need to be an automotive engineer to understand what a car does. The same applies to AI tools. A litigator needs to understand what the system does, how it processes information, and where it might fail — but not necessarily how the underlying algorithm works.

Second: once you buy the tool, the problem is solved. Technology is a tool, not a replacement for judgment. It won't solve your problems if you don't have a strategy for using it, governance around its deployment, or clarity on what you're trying to achieve.

There's also a persistent expectation that AI works like a search engine — you type something in and get an answer. Litigation doesn't work that way. Litigation starts with analyzing documents and ends with drafting work product. Everything in between is building context. The quality of the output is tied directly to the quality of the context the system has about the case.

§
Request a demo