EPISODE · Apr 28, 2026 · 37 MIN
The Building Blocks of the AI-Native Law Firm: People, Process, and Tech
from Version Up · host Kaj Rozga
What are the fundamental building blocks for becoming an AI-native law firm? Julian Gilson comes on the pod to lay out a framework for a successful transformation: people, process, and tech. Julian is founder of IntensifAI, which advises law firms on AI transformation end-to-end. He brings a grounded perspective forged by a product management background to try to answer a question many law firms are asking themselves as they emerge from the fog of war of an AI-disrupted legal services market. The conversation starts with first principles. Julian's framework for AI readiness is three-pronged: digitalization, data quality, and workflow design. The surprising entry point is digitalization — because even in 2026, some of the key work that law firms do (phone calls, internal meetings, client communications) goes uncaptured, unstructured, and therefore unusable. You can't train AI on data you don't have. At the same time, a maximalist approach must be reined in where necessary to meet the confidentiality and security requirements of a regulated legal industry. The data prong goes deeper than most firms realize. Completeness and consistency are the twin failure modes: data fields that exist but aren't reliably filled in, and metadata that's been input by humans in a dozen different formats when it should have been standardized. Julian describes how AI can now be used to manage and generate metadata fields — turning what was once a multi-year, consultant-heavy remediation project into something that can be built into the intake process from day one. The people and process dimensions often get underweighted. Julian is direct: if you're not already a tech company, don't try to become one. The cultural gap between law firms — where failure is stigmatized — and tech companies — where experimentation is the operating mode — is large enough that even well-resourced firms with innovation offices can underestimate it. The CTO you need isn't the one managing vendors and doing data migrations; it's the one who knows how to build. And if you really want to make the transition to AI-native, behind the CTO you will need to a team of technologists (developers, data scientists, etc.) who can build — although AI automation of coding means you may need fewer than you used to. As for the tech stack, set reasonable goals. Don’t look to rebuild from the ground up. And remember that, as Julian puts it, “no on wants another UI,” Instead, build on top of the legacy systems, creating connectivity between them (MCPs, etc.) and a hybrid on-prem/cloud infrastructure that securely leverages your data to develop value-add AI solutions that work. But don’t over-correct your course from buying tools where it makes sense. Being vendor-agnostic gives you flexibility, and vendor lock-in is real. But so is the risk of a non-technical organization trying to own a custom tech stack it can't maintain. His recommendation for most law firms starting out their AI transition: start with the foundation models, hire contractors before you hire full-time, and treat the vendors you do engage as training wheels — valuable for learning what's possible, but not necessarily a permanent solution. versionup.ai IntensifAI | Julian Gilson on LinkedIn
What this episode covers
What are the fundamental building blocks for becoming an AI-native law firm? Julian Gilson comes on the pod to lay out a framework for a successful transformation: people, process, and tech. Julian is founder of IntensifAI, which advises law firms on AI transformation end-to-end. He brings a grounded perspective forged by a product management background to try to answer a question many law firms are asking themselves as they emerge from the fog of war of an AI-disrupted legal services market. The conversation starts with first principles. Julian's framework for AI readiness is three-pronged: digitalization, data quality, and workflow design. The surprising entry point is digitalization — because even in 2026, some of the key work that law firms do (phone calls, internal meetings, client communications) goes uncaptured, unstructured, and therefore unusable. You can't train AI on data you don't have. At the same time, a maximalist approach must be reined in where necessary to meet the confidentiality and security requirements of a regulated legal industry. The data prong goes deeper than most firms realize. Completeness and consistency are the twin failure modes: data fields that exist but aren't reliably filled in, and metadata that's been input by humans in a dozen different formats when it should have been standardized. Julian describes how AI can now be used to manage and generate metadata fields — turning what was once a multi-year, consultant-heavy remediation project into something that can be built into the intake process from day one. The people and process dimensions often get underweighted. Julian is direct: if you're not already a tech company, don't try to become one. The cultural gap between law firms — where failure is stigmatized — and tech companies — where experimentation is the operating mode — is large enough that even well-resourced firms with innovation offices can underestimate it. The CTO you need isn't the one managing vendors and doing data migrations; it's the one who knows how to build. And if you really want to make the transition to AI-native, behind the CTO you will need to a team of technologists (developers, data scientists, etc.) who can build — although AI automation of coding means you may need fewer than you used to. As for the tech stack, set reasonable goals. Don’t look to rebuild from the ground up. And remember that, as Julian puts it, “no on wants another UI,” Instead, build on top of the legacy systems, creating connectivity between them (MCPs, etc.) and a hybrid on-prem/cloud infrastructure that securely leverages your data to develop value-add AI solutions that work. But don’t over-correct your course from buying tools where it makes sense. Being vendor-agnostic gives you flexibility, and vendor lock-in is real. But so is the risk of a non-technical organization trying to own a custom tech stack it can't maintain. His recommendation for most law firms starting out their AI transition: start with the foundation models, hire contractors before you hire full-time, and treat the vendors you do engage as training wheels — valuable for learning what's possible, but not necessarily a permanent solution. versionup.ai IntensifAI | Julian Gilson on LinkedIn
NOW PLAYING
The Building Blocks of the AI-Native Law Firm: People, Process, and Tech
No transcript for this episode yet