Most AI pitches to law firms start with a product. This one starts with an audit — and a question about whether buying software was ever the right move for a solo or small firm in the first place. Jerry Dearden of David AI joins Ron and Heather to unpack what it actually takes to build AI around a firm instead of forcing a firm into someone else's software. It's the David AI origin story, the pricing, and the pitfalls — no punches pulled.
Listen/Watch On
Lawyers are getting sold AI products constantly — Harvey, Legora, a million verticals promising to fix your firm. But what if the right move isn't buying another product at all — what if it's building one custom to how you actually practice?
IN THIS EPISODE:
- How David AI's "fitting" audit works before any code gets written — firm size, niche, workflows, tech stack
- The difference between reactive AI (you prompting a chatbot one task at a time) and proactive AI (an agent that acts on its own and reports back)
- Why firms keep bumping into Harvey and Legora, then walking away because the pricing and scale don't fit solo and small practices
- How David AI builds agents that live wherever a lawyer already works — iMessage, Slack, Teams, or inside existing case management software
- The "company brain" concept: connecting a firm's tools so AI has full context instead of starting from zero every time
- Data protection, DPAs, and how David AI's own contract terms changed after a listener-style question exposed a gap
- Build-versus-buy: when David AI tells a firm to keep its existing software instead of building something new
- Pricing structure — audit fees, build costs, and ongoing maintenance
- A real AI paralegal build for a small Utah firm, including a lawyer-avatar project still in testing
- The insurance defense billing bottleneck, and how AI could translate time entries into carrier-acceptable language automatically
WE ALSO DISCUSS:
- Kirkland & Ellis's $500 million, multi-year investment in a proprietary AI platform, and why Jerry calls building your own LLM "frying an egg on a volcano"
- Claude's connector ecosystem and what it means for firms trying to build a unified knowledge base
- Staff resistance to AI and the "Iron Man suit" framing David AI uses to get buy-in
- This season's ongoing FSJ knowledge-standardization exercise — this week's step is making firm documents AI-readable
- A tease for Season 3: "users and builders"
KEY TAKEAWAY
Jerry's answer to almost every question comes back to the same place: don't buy a tool and force your firm into it, fit the tool to how you actually work. That's a different pitch than most AI vendors make, and it only works if a firm is willing to open up its internal processes to an outside audit first.
This episode's FSJ moment comes from the ongoing build series Ron's been running with listeners since the start of the season. Four weeks in, the assets are identified, organized, and cleaned. This week's step is standardizing them: a Flintstones lawyer writes a plain description at the top of one form, a Simpsons lawyer turns client questions into a consistent Q&A format, a Jetsons lawyer breaks a workflow into sequential steps. It's a reminder that "AI-ready" starts with structure a human puts in place — long before any model touches the data.
MENTIONED IN THIS EPISODE:
- David AI
- Harvey
- Legora
- Claude / Anthropic
- ChatGPT / OpenAI
- Reddit
- Clio
- Microsoft Teams, Slack, iMessage
- Spellbook
- Kirkland & Ellis
- TimeSolv (billing software Ron used in practice)
- Claude's connector ecosystem
[email protected]