AI Tools for Practicing Lawyers

Ron Drescher

AI Tools for Practicing Lawyers delivers practical, no-nonsense guidance on how attorneys can use artificial intelligence tools in their law practices — right now. This podcast is for practicing lawyers who want real-world answers, not hype. Each episode focuses on clear, understandable explanations of AI tools that can help attorneys work more efficiently, communicate more effectively, and make better business decisions — without requiring technical expertise or coding knowledge. We cover topics such as: • Using AI responsibly and ethically in legal practice • Drafting, research, summarization, and document review tools • Client communication and intake automation • Practice management efficiencies • Emerging AI platforms relevant to law firms • Real examples attorneys can apply immediately Whether you are a solo practitioner, small-firm attorney, or part of a larger practice, this podcast is designed to help you understand what AI can — and cannot — do for lawyers today. No futurism. No speculation. Just practical tools for practicing lawyers. Hosted by Ron Drescher

  1. 5d ago

    Episode 036 Workflow Options: Vaquill Ai for Legal Research

    SHOW NOTES Every legal AI vendor will tell you their tool doesn't hallucinate. Priyansh Khodiyar, co-founder and CTO of Vaquill, said it on our show, and Heather didn't let it slide. Vaquill feeds verified statutes and regulations straight into Claude and other AI tools through an API and an MCP connector. That fixes a real problem. It also raises a harder one: if the source is clean and the AI still gets it wrong, whose mistake is it? In this episode: - How a lawyer's blog and a flood of reader questions turned into a U.S. legal data infrastructure company - What Vaquill actually is: statutes, regulations, court rules, and constitutions delivered to AI tools through an API and MCP connector - How Vaquill tracks amendments: hundreds of crawlers, daily redline-style diffs, and a human check on anything that looks off - Whether a legal database had already caught the permanent Chapter 13 and Subchapter V debt-limit increase, and how fast it should - Why rich metadata on every statute section pushes AI tools to cite the law instead of guessing at it - The new research model: working inside Claude with connectors to Vaquill, Westlaw, and Lexis instead of logging into each platform - Heather's challenge to "no hallucinations," and why the source can be clean while the AI's answer still isn't - Vaquill's plan to add case law, and why case law is the harder hallucination problem - Why a small vendor may give you faster support and fewer conflicts of interest than the incumbents We also discuss: - OpenAI's reported losses and whether AI pricing is headed for sticker shock - The AI labs' push into legal and other industry verticals - Data center politics in the United States and India - Whether small firms need an AI person separate from their IT provider - Priyansh's advice to lawyers: build your own small tools, or hire someone who will - Free Vaquill API access for legal aid organizations Key Takeaway A verified database fixes the source. It doesn't fix the reader. Vaquill can hand Claude the exact text of 11 U.S.C. § 362, every line cited. Claude can still misread it. Availability is not authority, even when what's available is the actual statute. The human in the loop doesn't go away. The checkpoint just moves. This season we talk about Users and Builders. Builders, the lawyers wiring Claude into their own tools, get a two-minute signup and an open API instead of an enterprise sales cycle. Users got a blunter message, and Priyansh was honest about it: if you'll never touch an API, find someone who will. For a solo or small firm lawyer already dabbling in Claude and wondering what a connector is, that is the real decision this episode puts on the table. Mentioned in This Episode - Priyansh Khodiyar, Co-Founder and CTO, Vaquill (vaquill.ai) - Arshita Anand, Co-Founder, Vaquill - Vaquill legal data API and MCP connector - Vaquill free API access for legal aid organizations (vaquill.ai/legal-aid) - Westlaw - Lexis / LexisNexis - Claude and Anthropic - ChatGPT and OpenAI - Gemini - Perplexity - Model Context Protocol (MCP) connectors - 11 U.S.C. § 362 (the automatic stay) - Chapter 13 and Subchapter V debt limits - LinkedIn, Reddit, and Hacker News Highlight Reels on YouTube and Instagram info@drescherlaw.com

  2. Nov 5

    Episode 035 HR, AI and the Proactive Solopreneur

    SHOW NOTES Every legal tech conference wants to talk about AI drafting and contract review. Almost nobody talks about the business behind the practice: the virtual assistant in the Philippines, the outsourced paralegal, the 1099 you found through a Facebook ad. Natalie Dalton, founder of Out of the Box HR, says that's the blind spot. Lawyers keep buying software before they understand how their own firm actually works. Her rule is simple: diagnose before you digitize. So what happens when you plug AI into a process that was broken to begin with? In this episode: - Why HR is really organizational design, not just payroll, benefits, and handbooks - Whether a solo lawyer with an outsourced paralegal and an offshore assistant needs HR at all - Employer of record arrangements and the compliance risk of hiring overseas workers directly - Starting with strategic objectives: defining roles, decision rights, and accountability before you hire - Using ChatGPT and Claude as a planning partner, and why an AI-drafted employee handbook only gets you about 80% of the way there - AI resume screening: setting must-haves and deal breakers, and keeping human eyes on the shortlist - Natalie's time at Document Crunch, an early AI platform that put construction contract knowledge in the hands of field teams - Natalie's AI Decision Tree and Law Firm AI Playbook, built around "diagnose before you digitize" - Reactive vs. proactive firm owners, and the hidden time bomb of a disengaged employee - Using AI to structure one-on-ones and turn meeting notes into follow-up action items We also discuss: - Why an AI that always tells you you're right is a risky HR advisor, and how Heather's AI assistant Bosley pushes back - AI memory failures, even with instructions stored in GitHub - Adding an HR consultant to the classic startup team of insurance agent, lawyer, and accountant - How Heather tested AI resume screening against a human assistant before trusting it - The 2026 midterm ballot measures on AI data centers, and whether slowing AI development would be such a bad thing - AI as "durable infrastructure," and why "AI app" will soon sound as dated as "internet app" - Voters in 13 states weighed 50 local ballot measures on AI data centers in 2026, and nearly every decided result went against development. Is slowing AI down such a bad thing? Ballotpedia — Data center-related ballot measures, 2026 Download: Natalie Dalton's AI Decision Tree and Law Firm AI Playbook A practical framework for deciding where AI belongs in your firm before you spend money on software. - Starts with the business, not the tool - Identifies where time and expertise are being wasted - Separates technology problems from management, training, and workflow problems - Helps you avoid automating a process that doesn't work Key Takeaway Natalie's point is blunt: install technology on top of an ineffective process and you just make that process ineffective faster. Before you buy another subscription, figure out whether your real problem is the tool, an unclear role, a broken workflow, or a person nobody is managing. Mentioned in This Episode - Natalie Dalton, founder of Out of the Box HR - Natalie's AI Decision Tree and Law Firm AI Playbook - Document Crunch - ChatGPT - Claude - Anthropic and OpenAI - Propel (outsourced paralegal services) - Indeed - Bosley (Heather's AI assistant) - Hugging Face (discussed in [Episode 033]) - 2026 midterm ballot measures on AI data centers - Jen Grondahl Lee (returning guest) Highlight Reels on YouTube and Instagram info@drescherlaw.com

  3. Oct 29

    Episode 034 Jane Jetson’s Book Club and the Demise of Prompting

    SHOW NOTES Students in 2026 can't imagine writing a ten-page paper without ChatGPT. Judges are split between refusing to touch AI and quietly using it to draft. Lawyers keep filing hallucinated citations despite years of headlines and sanctions. Maura Grossman, the lawyer and computer scientist who helped prove machine learning could outperform human document review, joins Ron and Heather to separate what AI does well from what has to stay human. Is human judgment actually wiser than AI judgment, or is it just a bigger pile of data? In this episode: - The state of the bench in October 2026: a "wild west" of judges who refuse AI, judges who use it freely, and almost no uniform guidance - Why judicial resistance to AI is mostly fear, and how an hour of hands-on training changes it - Heather's challenge: lawyers miscited cases for generations, so shouldn't the standard focus on the final work product rather than how it was produced? - Whether pro se litigants deserve more slack than licensed attorneys for hallucinated citations - Why harsh sanctions haven't reduced hallucinations, and a judge who solved one with a simple warning - The "sandwich approach": the judge thinks first, AI helps in the middle, the judge decides at the end - The live debate over whether prompting is dead, and why "just talking to your AI" is still prompting - Maura and Gordon Cormack's research showing generative AI's claimed edge over older machine learning in e-discovery largely disappears in an apples-to-apples comparison - Why human judgment matters: alignment, culture, morals, and Bostrom's paperclip problem - What happens to mentorship and learning when AI does the research a junior lawyer used to do We also discuss: - A law student who admitted he never read a single case in three years, summarizing everything through ChatGPT - Maura's classroom fix: a personal journal where AI use is prohibited - Clients who arrive convinced by ChatGPT that their case is worth a million dollars - The lawsuit alleging ChatGPT told a litigant she was being snowed by her lawyer - Whether AI companies should compensate authors and artists whose work trained their models - Practice Signals: a new solo litigator who wants to add contract drafting with zero transactional experience Key Takeaway Maura's closing advice cuts through most of the noise: the problem should drive the solution. Don't buy AI because the firm down the street has it. Find the pain point in your own practice, then find the tool that fixes it. And whatever tool you pick, it can't do the thinking a judge or lawyer is paid to do. That stays with you, at the start and at the end. This season the show shifted from Flintstones, Simpsons, and Jetsons to users and builders, and this episode lands on both. Users need to know enough to verify what the tool hands them. Builders need to remember that a beautifully engineered workflow doesn't make them competent in an area of law they've never practiced. Jane Jetson may think prompts are so March 2026. Maura's research says the jury is still out. Mentioned in This Episode - Maura R. Grossman, Research Professor, School of Computer Science, University of Waterloo; Adjunct Professor, Osgoode Hall Law School; Visiting Professor, Duke Law School - The Judicious Judge's Guide to Generative Artificial Intelligence and Large Language Models (forthcoming) - "Utopia or Dystopia" paper on self-represented litigants and AI - Grossman and Grimm general-principles paper, Sedona Conference Journal (2025) - Grossman and Cormack, 2011 study on technology-assisted review in e-discovery - Judge Paul Grimm (Podcast Episode 023 Deepfakes and the Liar's Dividend) - Gordon Cormack, University of Waterloo - Judges Maritza Braswell (Colorado), Scott Schlegel (Louisiana), and Xavier Rodriguez (Texas) and their judges-only AI group - Federal Judicial Center AI toolkit for federal judges - National Center for State Courts and Thomson Reuters Institute - Georgia Bench and Bar Conference - MIT research on brain engagement when writing with LLMs - Nick Bostrom's paperclip maximizer thought experiment - Federal Rule of Civil Procedure 11 - Nippon Life lawsuit against OpenAI - ChatGPT, Claude, Gemini, Vertex AI, Google Cloud, Microsoft - Harvey, Legora - Westlaw, Lexis - Reddit  Highlight Reels on YouTube and Instagram info@drescherlaw.com

  4. Oct 22

    Episode 033 The AI Has Left The Building

    SHOW NOTES Every AI tool lawyers use was trained on the whole internet, including the good sites, the bad ones, and the ones that say the moon landing was faked. Jonathan Schaeffer has spent more than 40 years in AI and helped teach computers to master checkers and poker, and he thinks that is exactly the problem. His answer is Kind, an AI that runs entirely on your own desktop, never touches the cloud, and knows nothing except what you give it. Ron and Heather press him on whether a walled-off AI really solves the problems lawyers face. Then the conversation turns to AI agents that did not stay walled off at all. Is the safest AI for a law office the one that knows the least about the outside world? In this episode: • Why Jonathan treats privacy, safety, security, and accuracy as non-negotiable requirements for any AI tool • How Kind works: an AI that runs on your desktop, answers only from your own files, and never sends data to the cloud • The difference between Kind Hybrid and Kind Local, and what fills Kind Local's six-gigabyte footprint • Jonathan's live demo for an Alberta bar group, where an ethics question about Alberta came back with Maryland citations • Jonathan's claim that source-linked answers drawn from a closed collection can't produce a hallucinated citation, and Ron's pushback on whether that is even the right use case • Ron and Heather challenge Kind's auto-updating legal collections: does linking to a live website break the walled garden? • The consistency checker, which uses an idle desktop to find logic and fact contradictions across a collection of files • Law firm use cases: client files that never leave the machine, and matter-specific collections paired with one jurisdiction's law • The open letter on AI cybersecurity risks Jonathan signed, and Ron's concern that calls for scientific unity can be used to silence dissent • Jonathan's sobering prediction that it may take a disaster before governments regulate AI We also discuss: • The July 2026 Hugging Face incident, in which OpenAI test agents escaped a contained environment and broke into outside systems • Why Jonathan compares escaped AI agents to a virus that mutates in minutes rather than months, and why a kill switch is not a real answer • Practice Signals: a lawyer on Reddit asks how to show a 16-year-old in another state what practicing law is really like • Ron's method: feed Delaware's bar admission clerkship checklist into an AI and have it build a version for a high school student • Heather's pitch for Chris Ryan to spin BenchSim into a resource for aspiring lawyers • Jonathan's closing case for keeping the human in the loop, especially in education Key Takeaway Jonathan's strongest point is about authority, not privacy. An AI trained on the whole internet will answer an Alberta ethics question with Maryland law and sound confident doing it. Availability is not authority. A tool that can only answer from the files you load forces you to decide what the law is before you ask the question. As Ron pointed out, that is what lawyers are supposed to be doing anyway. That opens a door for Flintstones and Simpsons lawyers who have stayed away from AI because they won't upload client files to someone else's server. The catch is that the walled garden only works while the walls stay up. Once you link a live website or connect collections, you are making the same judgment call you would make with any cloud tool. Jetsons lawyers will still want the reach of internet-connected tools. Everyone else has to decide which work belongs inside the wall. Mentioned in This Episode • Jonathan Schaeffer, Professor Emeritus, University of Alberta; Founder and CEO, Synsira Software Solutions • Kind by Synsira (Kind Hybrid, Kind Local, and the forthcoming Kind Shared) • Alberta Machine Intelligence Institute (Amii) • ChatGPT, Claude, and Gemini • OpenAI and Meta • The Hugging Face incident (July 2026) • METR's independent investigation of the OpenAI/Hugging Face incident • Instadocs: AI Gone Wild (Netflix, 2026), a 27-minute documentary on the Hugging Face hack • The AI Doc: Or How I Became an Apocaloptimist (documentary) • Open letter from scientists on AI cybersecurity risks • Chris Ryan and BenchSim (featured in Episode 016: Can an Al Judge Train You Better Than the Real One?) • Delaware bar admission clerkship checklist • Reddit (source of this episode's Practice Signals story) info@drescherlaw.com Highlight Reels on YouTube and Instagram

  5. Oct 18 ·  Bonus

    AI Builds: How Secure is Google?

    SHOW NOTES Your clients' bank statements, tax returns, and credit reports may already live on Google's servers. Gmail, Drive, Docs, and now Gemini. Google probably protects that data better than the server in your closet ever could. But Google securing its infrastructure doesn't mean your client's information is secure. **If Google is doing its job perfectly, who's responsible when client data still gets out?** **In this episode:** - The four separate security worries lawyers lump together: outside hackers, Google employees, AI model training, and your own firm handing out access - Why Google's infrastructure likely beats the typical small-firm setup of a closet server, an on-call IT consultant, and an untested backup - Google's shared responsibility model: Google secures the platform, and the firm controls who and what gets in - How a mis-shared folder, a compromised account, or an over-permissioned app exposes client data while Google's systems work perfectly - Limited-scope authorization and the drive.file permission, which give an AI app one matter's files instead of the whole filing cabinet - Three Gemini environments with different data terms: consumer Gemini, Gemini under Workspace business terms, and Vertex AI - Why "doesn't train on your data" is not the same as "doesn't retain your data," including abuse monitoring, caching, and 30-day grounding retention - What a security readiness review of Ron's own AI bankruptcy platform revealed, and why the answer to "ready for real client data?" was no - Four failures Google's infrastructure can't fix: one firm seeing another firm's files, a departed paralegal who still has access, temporary copies never deleted, and no incident response plan - Five things lawyers should do now: know your account, require strong sign-in, check third-party permissions, question AI vendors, and treat security as ongoing **We also discuss:** - Why having a Gmail address doesn't put you under Workspace business protections - Consumer Gemini configurations where humans may review your conversations - Why zero data retention on Vertex AI takes affirmative configuration choices - Passkeys and security keys as phishing-resistant sign-in, even though multi-factor authentication is a pain - The questions every AI vendor should be ready to answer, including what happens to your documents when you cancel > **Download: AI Builds — How Secure Is Google? (Three-Legged Stool Visual Guide)** > A six-page, click-by-click guide to Google's admin console for locking down client data, organized around Ron's three-legged stool: Google's security, the application's security, and the firm's own practices. > - Requiring 2-Step Verification and passkeys across the firm > - Controlling who in the firm can use the Gemini app > - Reviewing which third-party apps hold OAuth access to firm data, and how much > - Setting external Drive sharing boundaries and Gemini conversation retention **Key Takeaway** Google can protect the vault. It can't stop you from handing someone the key. Ron's own platform had good safeguards on paper. It had limited Drive access, firm isolation, and an audit trail, and it still wasn't ready for real client data, because designing protections and proving they work are two different things. The question isn't whether Google is secure. It's whether every link in the chain touching your client's information is secure. For Users, the work is unglamorous. Know which account you're signed into, turn on strong sign-in, and read what an app is asking for before you click Allow. For Builders, the bar is higher: test firm isolation, offboarding, deletion, and incident response before the first real client file arrives. And expect lawyers to start asking how you tested those protections. **Mentioned in This Episode** - Google Workspace (Gmail, Google Drive, Google Docs) - Gemini (consumer) - Gemini in Google Workspace business accounts - Google Vertex AI - Google's shared responsibility model (Google Cloud documentation) - Google's drive.file limited-scope permission - Google Workspace privacy documentation and Vertex AI enterprise terms - Passkeys and security keys - Ron's AI-assisted consumer bankruptcy platform and its internal security readiness review Google Workspace Generative AI Privacy Hub — Google's commitments concerning training, confidentiality, human review, and Workspace data. Google Cloud: Vertex AI and Zero Data Retention — Training restrictions, caching, retention exceptions, and configuration requirements. Google: Choose Google Drive API Scopes — Explains how developers can limit an application's access to individual files. Google Cloud Shared Responsibility — Explains what Google secures and what customers remain responsible for. Google: Turn the Gemini App On or Off — Explains the differences in protection between qualifying Workspace accounts and other configurations. Highlight Reels on YouTube and Instagram > info@drescherlaw.com

  6. Oct 18 ·  Bonus

    AI Builds: How Secure is Microsoft?

    SHOW NOTES Your email is in Outlook. Your briefs are in Word. Your client files sit in SharePoint and OneDrive. Now Microsoft wants to put Copilot in the middle of all of it, and Copilot will find anything your permissions already let you see. In this AI Builds episode, Ron Drescher argues that the real risk isn't Microsoft's security. It's whether your firm ever configured it. How secure is Microsoft, and how secure is your firm's use of it? In this episode: - The three-legged stool applied to Microsoft 365: Microsoft secures the platform, your firm configures it, and every user still holds a key - What Microsoft 365 actually protects (encryption, multifactor authentication, sign-in monitoring, auditing) and why your subscription tier decides which protections you have - The two questions to ask about any Microsoft security feature: does my plan include it, and is it turned on? - "Folder mania" in the cloud: how years of loose SharePoint and OneDrive permissions become a live problem once AI can search them - Why Copilot can surface a confidential client file without breaking a single rule: it followed the rules, but the rules were wrong - Sorting out the Copilot family: consumer Copilot, Microsoft 365 Copilot Chat, and the fully integrated Microsoft 365 Copilot - What you are really authorizing when you click "Connect your Microsoft 365 account" on a third-party legal AI tool - User-level vs. application-level permissions, and four questions to ask any AI vendor before granting access - The five admin locations a small firm should know: Microsoft 365 Admin Center, Microsoft Entra, SharePoint Admin Center, Microsoft Defender, and Microsoft Purview We also discuss: - Why cloud storage is not a backup or disaster recovery plan - Ransomware as a business continuity question: could you meet tomorrow's filing deadline? - Why you shouldn't change unfamiliar security settings in the middle of a workday - The "miscellaneous" folder nobody has opened since 2017 - Five questions to bring to whoever manages your firm's technology - The AI paradox: new tools make old security mistakes more expensive Download: How Secure Is Microsoft? A Microsoft 365 Security Guide for Solo and Small-Firm Lawyers A nine-page companion to this episode (and to How Secure Is Google?) It walks you and your IT provider through six places to review in Microsoft 365, with Microsoft-published screenshots and exact menu paths. - Users, administrators, and stronger sign-in through security defaults or Conditional Access - Client sharing limits in SharePoint and OneDrive, and the permissions you've already granted to outside apps - Oversharing reports to run before Copilot, plus how to confirm Purview auditing actually works - A plain-English licensing page and a printable firm security checklist https://lawyeraitoolkit.com/deliverables#row-WoaNrpcH4Y Key Takeaway Copilot doesn't create your permission problems. It exposes them. A SharePoint site that has been quietly overshared for five years was a low-grade risk when nobody could search it. Put an AI assistant on top, and an associate can surface another client's confidential file by asking one question. Microsoft built the lock. Your firm decides who holds the keys. Simpsons lawyers feel this first. They've turned on Copilot or connected a new legal AI app without ever opening Entra or the SharePoint Admin Center. Flintstones lawyers running Microsoft 365 out of the box carry the same oversharing risk; they just haven't triggered it yet. Jetsons lawyers building on Microsoft data need to know exactly what permissions their tools hold. The answer is yes to AI inside Microsoft 365, if you've audited who can open the folders first. Mentioned in This Episode - Microsoft 365 (Business Basic, Business Standard, Business Premium) - Outlook, Word, Excel, PowerPoint, Teams - Exchange Online, OneDrive, SharePoint - Microsoft Entra - Microsoft Copilot (consumer), Microsoft 365 Copilot Chat, Microsoft 365 Copilot - Microsoft 365 Admin Center - SharePoint Admin Center - Microsoft Defender - Microsoft Purview - Companion episode: AI Builds: How Secure Is Google? - Prior episode on "folder mania" - Microsoft's security documentation Microsoft 365 Copilot: Data, Privacy, and Security — Microsoft's explanation of how Copilot handles organizational information, protects prompts and responses, and respects existing Microsoft 365 permissions. Particularly relevant to the distinction between using AI and giving AI access to your firm's documents. Microsoft: Enterprise Data Protection for Copilot — Explains Microsoft's enterprise data protection commitments, including restrictions on using organizational prompts and responses to train foundation models. Useful for distinguishing business Copilot experiences from consumer AI services. Microsoft Entra: Permissions and Consent — Explains how third-party applications obtain permission to access Microsoft 365 information, including the important distinction between delegated permissions and application permissions. This is especially relevant when a lawyer connects an outside legal AI product to Outlook, OneDrive, or SharePoint. Microsoft Cloud: Shared Responsibility Model — Explains which security responsibilities belong to Microsoft and which remain with the law firm, including user identities, device security, access permissions, and configuration. This is the official Microsoft resource supporting our Three-Legged Stool concept. Microsoft Learn Microsoft: Manage Copilot Chat — Explains how administrators can manage employee access to Copilot Chat, including restrictions and application availability. Useful for lawyers who want to control when and how AI becomes available within their Microsoft environment. Microsoft Learn Microsoft: Copilot Security and Governance — Explains how Microsoft addresses excessive document sharing, AI access to organizational information, and compliance controls. Particularly relevant to our Foldermania discussion and the risk of Copilot discovering documents that employees already have permission to access but shouldn't.  info@drescherlaw.com Highlight Reels on YouTube and Instagram

  7. Oct 18 ·  Bonus

    Field Note: Which is More Secure, Google or Microsoft?

    SHOW NOTES Google or Microsoft? Most lawyers treat that as a question about Outlook versus Gmail. It isn't. It's a question about who protects your clients' confidential information, and the honest answer surprises people: neither platform wins on paper. The real question is whether you bought the right protections, turned them on, and trained your people to use them. In this episode: - Why passkeys and phishing-resistant authentication belong near the top of a law firm's security shopping list - How one "anyone with the link" share can expose a client's tax returns, bank statements, and bankruptcy schedules - Data loss prevention (DLP): what it does, and why both Google and Microsoft tie it to specific subscription tiers - The lost-laptop scenario, and why Microsoft 365 Business Premium (Intune plus Defender for Business) gives Microsoft an edge for Windows-based firms - Third-party AI apps that ask for access to your Google Drive or OneDrive, and who in your firm has authority to approve them - Gemini and Copilot: why AI assistants inherit your existing permission problems and make them easier to exploit - Why the cheapest subscription may not be cheaper in any meaningful sense - Five questions every firm should be able to answer about its security posture We also discuss: - "Folder mania" and the stakes of giving an AI app access to entire folders - Microsoft Purview sensitivity labels for classifying and protecting confidential documents - Why Ron, a longtime Mac user, isn't sure Microsoft's device-management advantage applies to him - Reviewing contractual commitments on data use, retention, and model training before enabling enterprise AI - The three-legged stool of AI security: technology, configuration, and people Companion Resources: AI Builds on Google Workspace and Microsoft 365 Ron's companion AI Builds episodes walk through the specific settings behind this comparison, with materials to help you find them. - AI Builds: How Secure Is Google? - AI Builds: How Secure Is Microsoft? - Companion materials Google - Companion materials Microsoft Key Takeaway Security isn't a brand you buy. Google and Microsoft both offer excellent technology. Whether it protects your clients depends on which edition you paid for, whether anyone configured it, and whether your people follow the rules. A locked front door does nothing if your paralegal hands out the key in a shareable link. Flintstones lawyers who assume their email provider handles security by default need to look again. Simpsons lawyers about to switch on Gemini or Copilot need a permissions review first, because the AI will find every overshared folder. Jetsons lawyers connecting third-party apps to their files need to know exactly which ones have access and who approved them. Mentioned in This Episode - Google Workspace - Google Drive - Gmail - Gemini - Microsoft 365 - Microsoft 365 Business Premium - Microsoft OneDrive - Microsoft SharePoint - Microsoft Outlook and Word - Microsoft Copilot - Microsoft Purview - Microsoft Intune - Microsoft Defender for Business - Microsoft Entra - AI Builds companion episodes on Google Workspace and Microsoft 365 (linked above) - The three-legged stool of AI security info@drescherlaw.com Highlight Reels on YouTube and Instagram

  8. Oct 15

    Episode 032 Workflow Options: BK Fastlane

    SHOW NOTES Every vendor at next year's bankruptcy conventions will say their product "uses AI." The better question is what the AI is actually allowed to do without a lawyer signing off. Colorado consumer bankruptcy attorney Matt McCune, a returning guest, gives a live first look at BK Fastlane, the AI-driven intake and document platform he built for consumer bankruptcy practices. Throughout, Ron keeps returning to one question: where does the lawyer stay in control? In this episode: - The debtor-facing secure portal: account creation, multifactor authentication, firm branding, and "Sarah," the AI onboarding agent - An intake form mapped to the schedules, the voluntary petition, and the Statement of Financial Affairs, with required fields and hard stops - A "never ask for a document you don't need" rule: no mortgage statement if there's no house, no pay stubs if there's no job - How the client screws up the form, and how the software gets them back on track - The attorney-facing CRM workspace and its four-stage pipeline, from new lead to ready for petition prep - AI document review: the AI suggests accept or reject, but a human approves every document, including high-confidence ones, "for now" - The automated chase list: daily follow-up emails for rejected or missing documents, so nobody on staff has to call the client - The AI tab: an instant means test analysis, a confidence score, and a case complexity score - Matt's cardinal rule: the AI never takes an action, especially with the client, without lawyer approval - Ron's question from his Infusionsoft days: how far do you let rules-based client emails run on their own once AI can customize them? We also discuss: - Two intake paths: a free consult for routine cases, and a paid $250 consultation for complex or messy ones - The three-phase roadmap: intake and CRM now, post-filing workflows next, electronic filing and petition prep last - Why a bankruptcy-only "vertical" product can do things a horizontal platform like Clio can't - Passkeys vs. multifactor authentication, and the bankruptcy court's new authenticator app requirement - Users vs. Builders: why Matt wants early-adopter "builder" firms now and Flintstones firms after all three phases ship - Matt's years of suing bad-actor bankruptcy lawyers under Sections 526, 527, and 528, and why that shaped his mission for the product Watch the full demo on YouTube: https://youtu.be/pEbOWwf8tHM Click here for a PDF slideshow of the software demo Key Takeaway The most important thing in this demo isn't a feature. It's the approval button. Matt built BK Fastlane so the AI can read a pay stub, flag a fuzzy Social Security card, and run a means test, and still not move a document or send an email until a human says yes. His answer to whether high-confidence documents should skip review was blunt: not yet. "I don't trust it. I don't think anyone should trust it." Matt himself drew the line between Users and Builders. Right now he wants early-adopter firms that are curious about how this gets built but have no time to build it themselves. His target for Flintstones lawyers is roughly a year out, once all three phases ship. If you're a Simpsons-stage consumer bankruptcy lawyer still stitching together four or five products, this is a look at where single-practice-area software is heading. It is not a recommendation to switch today. Mentioned in This Episode - Matt McCune, consumer bankruptcy attorney (Colorado), founder of BK FastPass - BK Fastlane, the first product from BK FastPass - NACBA (National Association of Consumer Bankruptcy Attorneys) and its April 2027 convention in Orlando - Microsoft Azure - Claude Cowork - Clio, Clio Grow, Clio Manage, Clio Jubilee - Lawmatics - NextChapter - Best Case - PracticePanther - Rocket Lawyer - Infusionsoft (now Keap) - Zillow - BAPCPA (2005) - 11 U.S.C. Sections 526, 527, and 528 info@drescherlaw.com Highlight reels: YouTube: https://www.youtube.com/@AIToolsforLawyers Instagram: https://www.instagram.com/aitoolsforlawyers

5
out of 5
7 Ratings

About

AI Tools for Practicing Lawyers delivers practical, no-nonsense guidance on how attorneys can use artificial intelligence tools in their law practices — right now. This podcast is for practicing lawyers who want real-world answers, not hype. Each episode focuses on clear, understandable explanations of AI tools that can help attorneys work more efficiently, communicate more effectively, and make better business decisions — without requiring technical expertise or coding knowledge. We cover topics such as: • Using AI responsibly and ethically in legal practice • Drafting, research, summarization, and document review tools • Client communication and intake automation • Practice management efficiencies • Emerging AI platforms relevant to law firms • Real examples attorneys can apply immediately Whether you are a solo practitioner, small-firm attorney, or part of a larger practice, this podcast is designed to help you understand what AI can — and cannot — do for lawyers today. No futurism. No speculation. Just practical tools for practicing lawyers. Hosted by Ron Drescher

You Might Also Like