🎙️ TSL Lab’s Deep Dive into Our May 18, 2027, editorial, “AI Won’t Replace Solo and Small Firm Lawyers. It Will Supercharge Them”!

/ The Tech-Savvy Lawyer.Page/

📌 Too Busy to Read Our May 18, 2026, Editorial?

Join us for an AI-powered deep dive into the ethical challenges facing legal professionals in the age of generative AI. 🤖 This week’s Tech-Savvy Lawyer Lab’s podcast unpacks my editorial, “AI Won’t Replace Solo and Small Firm Lawyers. It Will Supercharge Them,” and translates it into practical, ethics-aware guidance for solo and small firm professionals navigating AI in real time.

We explore why AI is unlikely to replace lawyers but highly likely to transform how legal work is unbundled, priced, and delivered. We walk through Jevons Paradox, ABA rules on competence, supervision, and confidentiality, and the very real risks of hallucinated filings and careless use of public AI tools. You will see how treating AI as a supervised junior associate can expand your capacity, open new micro‑niches, and make your practice more human-centered, not less. ⚖️

In our conversation, we cover the following:

  • 00:00:00 – Why “doom hype” around AI is targeting the legal profession and why the collapse-of-lawyers narrative falls apart in real life.

  • 00:01:00 – Introducing Michael D.J.’s editorial “AI Won’t Replace Solo and Small Firm Lawyers. It Will Supercharge Them.”

  • 00:02:00 – Setting ground rules: educational discussion only and why this episode is not legal advice.

  • 00:02:30 – Rethinking what a “job” really is and the idea that legal work is a bundle of tasks, not one monolithic activity.

  • 00:03:00 – Comparing big-firm specialization to the tightly packed bundle of tasks handled by solo and small-firm lawyers.

  • 00:03:30 – Why AI can pull on individual threads in that bundle, but cannot run the whole practice for you.

  • 00:04:00 – The solo master-chef metaphor: AI as the kitchen machine doing prep work while the human focuses on taste and judgment. 🍲🤖

  • 00:05:00 – How AI can draft preliminary summaries or case law lists while the lawyer still owns strategy and verification.

  • 00:05:30 – The “mental verification” problem: when typing and thinking used to be the same act for lawyers.

  • 00:06:00 – What changes when AI writes the first draft and why verification must become a separate, deliberate step.

  • 00:06:30 – The risk of hallucinated filings and viral stories of fake cases generated by AI. 😬

  • 00:07:00 – Data points showing the profession is adapting, not dying: more lawyers, more bar-required jobs, rising law school interest.

  • 00:07:30 – Revisiting the e‑discovery panic and predictions that predictive coding would wipe out junior associates.

  • 00:08:00 – How cheaper e‑discovery led to an explosion of data and actually increased demand for legal work.

  • 00:08:30 – Introducing Jevons Paradox and why greater efficiency can increase, not decrease, total demand.

  • 00:09:00 – The widened-highway analogy: more lanes, more traffic, and how that maps onto AI in law. 🛣️

  • 00:10:00 – How AI lets small firms tackle big, complex matters and offer more predictable flat-fee pricing.

  • 00:11:00 – Expanding access to legal services for the middle class and why cheaper legal work grows the market.

  • 00:11:30 – Turning to ethics: ABA Model Rule 1.1 on competence and the duty to understand relevant technology.

  • 00:12:00 – The solo’s burden: you are the IT department and the innovation committee, all at once. ☕💻

  • 00:12:30 – A practical definition of technological competence for solos and small firms.

  • 00:13:00 – Starting small with AI: summaries, first-draft emails, and extracting checklists from dense legislation.

  • 00:13:30 – AI as the “junior associate you don’t have to hire but must supervise” under Rules 5.1 and 5.3.

  • 00:14:00 – Why you remain responsible for AI’s output just as you would for a paralegal or junior lawyer.

  • 00:14:30 – The solo’s question: Does it really make sense to write a formal AI policy for just one person?

  • 00:15:00 – How a short written AI policy creates hard boundaries before you are stressed and rushed.

  • 00:15:30 – Defining approved uses, high‑review tasks, and absolute “no-go” zones for AI in your practice.

  • 00:16:00 – Model Rule 1.6 on confidentiality and the special risk solo and small firms face with cloud tools.

  • 00:16:30 – Why pasting sensitive client facts into a generic consumer chatbot is an ethical minefield.

  • 00:17:00 – How consumer AI tools tokenize your text and use it to train future models.

  • 00:17:30 – The “megaphone in a public square” analogy for pasting confidential data into public AI tools. 📣

  • 00:18:00 – Moving from megaphones to soundproof vaults: using enterprise modes or legal-specific platforms.

  • 00:18:30 – Why a single data breach can be existential for a solo firm and why clients should care about tool choices.

  • 00:19:00 – Legislative inflation: constant growth in complex rules, norms, and regulations across jurisdictions.

  • 00:19:30 – How AI helps solos track regulatory change, generate client alerts, and update templates in real time.

  • 00:20:00 – Carving out lucrative micro‑niches with AI, such as hyper‑specific regulatory domains.

  • 00:20:30 – Pairing niche expertise with SEO and content marketing so a solo can compete at scale.

  • 00:21:00 – The junior lawyer dilemma: what happens to entry-level training when AI eats the grunt work.

  • 00:21:30 – Why firms still need junior lawyers to build a future bench, not just to type memos.

  • 00:22:00 – What AI fundamentally cannot do: build trust in person, join community events, or create referral networks.

  • 00:22:30 – How automation pushes lawyers toward more human-centric, relationship-focused work. ❤️

  • 00:23:00 – The core conclusion: the real existential threat is the AI-literate competitor down the street, not the robot.

  • 00:23:30 – Treating AI as a supervised junior associate while protecting ethics, productivity, and client outcomes.

  • 00:24:00 – Final reflections: mapping your own “bundle of tasks” and deciding what to offload so you can supercharge yourself. ⚡

RESOURCES

Mentioned in the episode

👉 If this episode helps you think more clearly about AI, ethics, and your own “bundle of tasks,” share it with a colleague and subscribe so you never miss a future Tech-Savvy Lawyer deep dive. 🚀

Ep. #136: How Law Firms Can Actually Use AI: Practical Intake, Document, and Workflow Automation with Hamid Kohan

/ The Tech-Savvy Lawyer.Page/

My next guest is Hamid Kohan, founder of LegalSoft and LawPractice.ai, and one of the most practical voices on applying AI inside real-world law firms.🧠 He joins me to break down how firms can move beyond the “we’ve done it this way for 40 years” mindset, modernize their tech stack, and start using AI today without taking on unnecessary risk.

Join Hamid and me as we discuss the following three questions and more!

  • What are the top three ways law firms can integrate AI using solutions like LegalSoft and LawPractice.ai into their intake, case management, and document workflows to improve efficiency and accuracy?

  • From your work directly with law firms, what are the top three challenges lawyers face in adopting AI, and how can they overcome them to modernize their practice?

  • Looking ahead, what are the top three emerging technologies beyond AI that attorneys should start exploring today to stay competitive in the legal industry?

In our conversation, we cover the following

  • 00:00 – Welcoming Hamid and overview of his tech-heavy environment

  • 00:30 – Why his team is 90% Mac while he stays on PC and Android

  • 01:10 – Running a pure cloud and SaaS setup with no true desktop environment

  • 02:00 – Treating devices as “Uber” to the web and why local power matters less

  • 02:30 – Hardware choices: HP PC, massive Samsung monitors, and 60+ browser tabs as a to‑do list

  • 03:30 – Working across 12 entities and using tabs to monitor departments and initiatives

  • 04:00 – Living in Google Chrome and managing resource usage for heavy browser workflows

  • 04:40 – Chrome extensions Hamid relies on: Adobe, malware protection, McAfee, offline document tools

  • 05:20 – Why he uses Chrome’s built-in password manager

  • 05:40 – Android Samsung smartphone and keeping mobile simple

  • 06:00 – Question 1: top three ways to integrate AI into intake, case management, and document workflows

  • 06:20 – How legal is “stuck in the past” and why Hamid saw law firms as a scaling opportunity

  • 07:10 – From CRMs and workflows to KPIs: the pre‑AI foundation for scaling law firms

  • 07:40 – The “sky dropped” moment when AI hit the legal industry

  • 08:10 – Vendor noise, “Me Too AI,” and why vertical, single‑purpose AI tools overwhelm firms

  • 08:50 – Why multi-solution AI platforms (like LawPractice.ai) will ultimately win

  • 09:20 – Why firms must start using AI now instead of waiting for perfection

  • 09:50 – Where lawyers should start with AI: document collection as a low‑risk entry point

  • 10:30 – Using AI to automate document requests via SMS, email, and calls

  • 11:00 – AI document summary that checks whether a client sent the correct document

  • 11:40 – Why AI collection and summaries are “risk-free” compared to AI drafting

  • 12:10 – Using AI for document chronologies and conservative workloads

  • 12:40 – Explaining LegalSoft: global virtual staffing for law firms across eight countries

  • 13:30 – How virtual legal staff can cut overhead by up to 75% for firms

  • 14:20 – Why Hamid launched LawPractice.ai to AI‑enable both law firms and LegalSoft’s 4,000 professionals

  • 15:10 – Question 2: the top three challenges lawyers face when adopting AI

  • 15:30 – Challenge 1: finding the right AI tool in a crowded, noisy market

  • 16:00 – Challenge 2: underestimating implementation, training, and real‑world usage

  • 16:20 – Case example: an employment firm that changed its view of AI after proper training

  • 17:10 – Challenge 3: signing long-term AI contracts before proper testing

  • 17:30 – Why firms should insist on “try before you buy” pilot periods

  • 18:00 – Making AI usage mandatory to avoid adoption resistance inside the firm

  • 18:40 – Parallels with CRMs like Clio, Filevine, and CasePeer and partial user adoption

  • 19:20 – How poor CRM data entry disrupts the entire legal workflow

  • 20:00 – Question 3: “beyond AI” tech and why Hamid says it’s “AI, AI, AI” for now

  • 20:30 – The real three “emerging tech” priorities: selecting, implementing, and integrating AI

  • 21:00 – Why locking into long-term tech contracts is risky in a fast-moving AI landscape

  • 21:30 – The trap of attractive multi‑year discounts and what firms should watch for

  • 22:00 – Where listeners can find Hamid and book a one‑on‑one through LegalSoft

Resources

Mentioned in the episode

  • Hardware mentioned in the conversation

  • Software & Cloud Services mentioned in the conversation

Word of the week: “Legal AI institutional memory” engages core ethics duties under the ABA Model Rules, so it is not optional “nice to know” tech.⚖️🤖

/ The Tech-Savvy Lawyer.Page/

Institutional Memory Meets the ABA Model Rules

“Legal AI institutional Memory” is AI that remembers how your firm actually practices law, not just what generic precedent says. It captures negotiation history, clause choices, outcomes, and client preferences across matters so each new assignment starts from experience instead of a blank page.

From an ethics perspective, this capability sits directly in the path of ABA Model Rule 1.1 on competence, Rule 1.6 on confidentiality, and Rule 5.3 on responsibilities regarding nonlawyer assistance (which now includes AI systems). Comment 8 to Rule 1.1 stresses that competent representation requires understanding the “benefits and risks associated with relevant technology,” which squarely includes institutional‑memory AI in 2026. Using or rejecting this technology blindly can itself create risk if your peers are using it to deliver more thorough, consistent, and efficient work.🧩

Rule 1.6 requires “reasonable efforts” to prevent unauthorized disclosure or access to information relating to representation. Because institutional memory centralizes past matters and sensitive patterns, it raises the stakes on vendor security, configuration, and firm governance. Rule 5.3 extends supervision duties to “nonlawyer assistance,” which ethics commentators and bar materials now interpret to include AI tools used in client work. In short, if your AI is doing work that would otherwise be done by a human assistant, you must supervise it as such.🛡️

Why Institutional Memory Matters (Competence and Client Service)

Tools like Luminance and Harvey now market institutional‑memory features that retain negotiation patterns, drafting preferences, and matter‑level context across time. They promise faster contract cycles, fewer errors, and better use of a firm’s accumulated know‑how. Used wisely, that aligns with Rule 1.1’s requirement that you bring “thoroughness and preparation” reasonably necessary for the representation, and Comment 8’s directive to keep abreast of relevant technology.

At the same time, ethical competence does not mean turning judgment over to the model. It means understanding how the system makes recommendations, what data it relies on, and how to validate outputs against your playbooks and client instructions. Ethics guidance on generative AI emphasizes that lawyers must review AI‑generated work product, verify sources, and ensure that technology does not substitute for legal judgment. Legal AI institutional memory can enhance competence only if you treat it as an assistant you supervise, not an oracle you obey.⚙️

Legal AI That Remembers Your Practice—Ethics Required, Not Optional

How Legal AI Institutional Memory Works (and Where the Rules Bite)

Institutional‑memory platforms typically:

  • Ingest a corpus of contracts or matters.

  • Track negotiation moves, accepted fall‑backs, and outcomes over time.

  • Expose that knowledge through natural‑language queries and drafting suggestions.

That design engages several ethics touchpoints🫆:

  • Rule 1.1 (Competence): You must understand at a basic level how the AI uses and stores client information, what its limitations are, and when it is appropriate to rely on its suggestions. This may require CLE, vendor training, or collaboration with more technical colleagues until you reach a reasonable level of comfort.

  • Rule 1.6 (Confidentiality): You must ensure that the vendor contract, configuration, and access controls provide “reasonable efforts” to protect confidentiality, including encryption, role‑based access, and breach‑notification obligations. Ethics guidance on cloud and AI use stresses the need to investigate provider security, retention practices, and rights to use or mine your data.

  • Rule 5.3 (Nonlawyer Assistance): Because AI tools are “non‑human assistance,” you must supervise their work as you would a contract review outsourcer, document vendor, or litigation support team. That includes selecting competent providers, giving appropriate instructions, and monitoring outputs for compliance with your ethical obligations.🤖

Governance Checklist: Turning Ethics into Action

For lawyers with limited to moderate tech skills, it helps to translate the ABA Model Rules into a short adoption checklist.✅

When evaluating or deploying legal AI institutional memory, consider:

  1. Define Scope (Rules 1.1 and 1.6): Start with a narrow use case such as NDAs or standard vendor contracts, and specify which documents the system may use to build its memory.

  2. Vet the Vendor (Rules 1.6 and 5.3): Ask about data segregation, encryption, access logs, regional hosting, subcontractors, and incident‑response processes; confirm clear contractual obligations to preserve confidentiality and notify you of incidents.

  3. Configure Access (Rules 1.6 and 5.3): Use role‑based permissions, client or matter scoping, and retention settings that match your existing information‑governance and legal‑hold policies.

  4. Supervise Outputs (Rules 1.1 and 5.3): Require that lawyers review AI suggestions, verify sources, and override recommendations where they conflict with client instructions or risk tolerance.

  5. Educate Your Team (Rule 1.1): Provide short trainings on how the system works, what it remembers, and how the Model Rules apply; document this as part of your technology‑competence efforts.

Educating Your Team Is Core to AI Competence

This approach respects the increasing bar on technological competence while protecting client information and maintaining human oversight.⚖️

This approach respects the increasing bar on technological competence while protecting client information and maintaining human oversight.⚖️