No-Code AI Automation for Small Law Firms: Five Recipes and the Rules for Each

“When I get an email from the web form from a potential client, forward the email to the Potential Client channel in Teams and tag Alice to run a conflict check and respond.” That is not a to-do list. It is, word for word, the sentence the North Carolina Bar suggests typing into Power Automate’s “Describe it to design it” feature, which then builds the flow (NC Bar). No-code AI automation for a law firm starts with a sentence like that, not with a developer.

Small firms need this most and do it least. Clio found that only 8% of solos and 4% of small firms have adopted AI “widely or universally”; most use “low barrier tools like ChatGPT” (Clio). Its 2024 report put 74% of hourly billable tasks as potentially automatable (LawNext); its 2026 data, as summarised by the NC Bar, says finding time is the biggest hurdle for 27% of solos and 33% of small firms. Pasting into ChatGPT does not give time back. A flow that runs while you are in court does.

Automation versus agent: keep it deterministic

An agent decides what to do next. An automation does what you told it, every time. Legora’s own essay on the year of agents concedes that chained workflows are “automation… not agency”; for a small firm that is the point. Jamie Tso of Clifford Chance gave the reason: “by asking the AI to build a tool rather than answer a question, the result becomes deterministic, significantly reducing the error rate” (ABA).

So every recipe follows one rule. The trigger, the routing and the filing are fixed. The model does one narrow job: classify, extract or draft. A person approves before anything reaches a client, a court or a calendar. GC AI’s version: “An agent you can trust is a workflow you already standardized, running on a schedule, with your name still on the review” (GC AI).

Recipe 1: intake triage and conflict pre-check

The NC Bar’s recipes cover both ecosystems: Power Automate can merge intake data into a Word engagement letter and route it to DocuSign; Zapier can connect a web form to Clio and Outlook. The AI step sits between the form and the human, the way GC AI’s in-house intake pairs a fixed question form with a routing table; a small firm simply has one lawyer at the end of the pipe.

You are the intake assistant for a [family law / employment / commercial] firm in [jurisdiction]. From the form submission below, output only a JSON object with these fields: matter_type (one of [list]); urgency (Today / This week / This month, with the sentence that justifies it); parties (every person or company named, exactly as written, for a conflict check); missing_information (up to three questions); holding_reply (two sentences that promise a call, give no legal view and do not confirm we will act).
Do not answer the legal question. If the submission mentions a court date, a regulator or a threat, set urgency to Today.
<submission>[form fields]</submission>

The flow posts the JSON to Teams or Slack and holds the reply as a draft. Alice still runs the conflict check; the model only saved her the reading.

Recipe 2: deadline extraction to calendar

The trigger is a court email or a scanned order landing in a watched folder. The model’s only job is extraction with a quotation. It does not compute deadlines: language models “are weak at math, counting, and sorting”, in Thomson Reuters’ words, and “90 days before the anniversary” is arithmetic. Run OCR first; otherwise, as one r/legaltech user warns, “you get hallucinated dates, mangled drug names, and unusable citations”.

From the attached order or letter, list every date, deadline, time period and triggering event in a table: Item | Date or period exactly as written | The full sentence it appears in | Page | What it triggers. Do not compute any date. Where a period runs from an event ("within 14 days of service"), record the period and the event separately and write COMPUTE. If a date is unclear in the scan, write ILLEGIBLE rather than guessing. End with the number of items found.

A person computes the deadlines, checks the local rules and creates the entries. Never let the flow write to the calendar: a wrong entry that looks official is worse than none at all.

Recipe 3: client status updates

Trigger: a milestone in the case-management system (filing made, hearing listed, document received). The model drafts under 150 words in plain English, in a fixed structure: what happened; what it means for you; what we do next; what we need from you by when; the next update date. It may not predict an outcome, estimate costs or advise beyond the milestone. Keep it short: the loudest complaint on r/LawFirm in September 2026 was AI-padded email coming the other way, clients sending AI-drafted replies to lawyers who “just need the yes or the no”; do not send the same padding back. The draft waits in the lawyer’s outbox; the client communication guide covers tone and disclosure.

Recipe 4: invoice review

Small firms review invoices in both directions: vendors and local counsel billing the firm, and the firm’s own pre-bills before they go to a client with outside-counsel guidelines. GC AI’s invoice-review skill is the model: it flags block billing, vague descriptions, rate overages, staffing mismatches and duplicates against the guidelines, then drafts the correction email (GC AI). On the same vendor’s site, SimplePractice’s chief legal officer Ali Hartley says a saved vendor-review prompt cut reviews from “between three to six hours” to “less than 30 minutes”; a vendor claim, but the pattern is sound.

Review the attached invoice against the billing guidelines in <guidelines>. Table: Line | Issue (block billing / vague description / rate overage / unapproved timekeeper / duplicate / non-billable admin) | Guideline clause | Suggested adjustment. Do not total anything; I will total in Excel. Then draft a courteous three-sentence email to the biller listing the adjustments and asking two questions. If the invoice contains no issue, say so.
<guidelines>[paste]</guidelines>

Recipe 5: document naming and filing

The NC Bar’s n8n example is the skeleton: a document lands in SharePoint, the flow posts a Teams notification, updates the practice-management system and writes a compliance log. Add one AI step: from the first page only, the model proposes a file name in your convention ([client]-[matter]-[type]-[date]) and a matter reference, with a confidence score. Low confidence goes to a person; high confidence still waits for one-click approval before the file moves, because a silent filing error compounds for years.

Where the human checkpoint goes

Put it at the point of consequence, not the point of drafting. Harvey tells firms to build “intentional friction” so that the craft does not die; its example is a first-year who spent 40 hours on a markup and “might now spend 5 hours reviewing an agent’s markup” (Harvey). California’s 2026 guidance sets the outer boundary: lawyers “must not permit AI systems to autonomously file documents”.

Confidentiality: which steps touch client data

Every recipe touches client data from the first field of the intake form. Consumer ChatGPT trains on conversations unless “Improve the model for everyone” is switched off, and consumer Claude has trained by default since 28 August 2025; ChatGPT Business, Claude Team and Copilot with enterprise data protection do not train by default (OpenAI). A federal court has already held a defendant’s consumer-Claude exchanges unprivileged. So the AI step runs on a business tier; the Business versus Enterprise comparison tells you which.

Two more points. The automation platform is a processor too: every field that passes through it is visible to it, so it needs a DPA, a retention answer and a place on your vendor due diligence checklist. And a flow you built is still software; as one engineer put it, lawyers “should not trust apps they vibe-code with their clients’ confidential information unless they have the technical expertise to deploy their tools securely”. Where a recipe can run on anonymised text, it should.

Costs and maintenance

The subscriptions are not the cost. Noah Waisberg’s warning about home-built AI workflows applies word for word: “what you’re building starts to look a lot like software… except without the QA, the versioning, the user feedback loops, or the ability to survive someone leaving the firm” (Zuva).

So each recipe gets a one-page runbook: owner, trigger, prompt and version, approved tool and tier, data touched, checkpoint, last-tested date. Re-test quarterly on three real past examples. The 30-day plan for solo and small firms schedules that, the implementation playbook covers the firm-wide version, and the vibe-coding guide is next if you catch the bug.

Where to go next: the prompts above are in the prompt library, and the firm implementation hub has the policy and training pieces. AI Lab for Lawyers is four live two-hour sessions on browser tools, no coding required; the habit behind every recipe here, one narrow job for the model and a person at the checkpoint, is what we practise there on your own anonymised documents.