MyCase AI Review: A Practicing Lawyer's Look at the Practice-Management Suite
MyCase has been a fixture in small-firm practice management for years. What changed recently is the AI layer: MyCase IQ, which stitches drafting, document analysis, and intake summarization into the platform lawyers already use for matters, billing, and client communications. This review looks at the tool the way a practicing lawyer would: what it actually does, where client data ends up, and whether the confidentiality posture squares with current ethics guidance.
Basil, which publishes this review library, is an on-device meeting notetaker. MyCase is a practice-management platform. They do not really compete head-to-head, so I have tried to review MyCase on its own merits. Where relevant, I note that firms often pair a practice-management system with a separate capture tool for meetings — see Basil for Law if that is a gap in your stack.
What MyCase Actually Does
MyCase is a cloud-based practice-management platform aimed at solos and small-to-midsize firms. The core modules cover matter management, contact and calendar sync, document storage, time and expense tracking, invoicing, trust accounting, e-signature, client intake, and a client portal for secure messaging and payments. It runs on a browser and has mobile apps. See the official features page for the current module list.
The AI layer, MyCase IQ, sits inside that platform. Based on the vendor's own descriptions, it offers document drafting assistance, document summarization and clause extraction, and an intake assistant that turns lead conversations into structured records. The pitch is not "replace your associate" — it is "reduce the friction of the routine drafting, summarizing, and intake work you already do inside MyCase." That framing is honest, and in my testing that is roughly where the value lives.
Where MyCase shines is integration. Because billing, matters, contacts, and documents already live in one place, the AI features have real context to work with. A summary generated from a document that is already tagged to a matter and a client is more useful than a summary produced by a standalone chatbot with no context. That is the argument for using AI inside your practice-management system rather than bolting on a general-purpose assistant.
The Confidentiality Lens
This is the section that matters most for lawyers, and it is where any honest review has to slow down.
MyCase is a cloud service. When you use it, client data — matter notes, documents, communications, intake responses, and anything you feed to MyCase IQ — is transmitted to and stored on MyCase's infrastructure. That is not a criticism; it is the architecture. The relevant questions are (1) what the vendor does with that data, (2) how long it is retained, (3) whether it is used to train models, and (4) what a subpoena served on MyCase could reach.
MyCase publishes a privacy policy and terms of service. Lawyers evaluating the platform should read both, and specifically look for: the sub-processor list (which typically includes the underlying LLM provider used by MyCase IQ), the data-retention schedule, and any AI-specific addendum describing whether prompts and outputs are used for model training. Do not rely on a sales rep's verbal assurance — get the written commitments, ideally in a data processing addendum.
A subpoena served on MyCase could, in principle, reach anything MyCase stores on your behalf: documents, messages sent through the client portal, matter notes, and depending on retention, AI prompts and outputs. That is a structural feature of any SaaS practice-management tool, not a MyCase-specific defect. It is the reason lawyers should think about what they store where, and it is a good reason to keep especially sensitive attorney work-product in systems with tighter access controls, or to process it locally where feasible.
The related concern is the LLM sub-processor. MyCase IQ, like most legal AI features, is built on top of a third-party foundation model provider. That means content sent to the AI feature may transit a second vendor's systems, subject to that vendor's enterprise terms. Ask MyCase in writing: who is the sub-processor, is training on your inputs contractually disabled, and what is the retention window on the AI provider's side. These are answerable questions and the answers should be in a DPA.
Ethics-Opinion Fit (ABA 512)
ABA Formal Opinion 512 (July 2024) is the current baseline for lawyers using generative AI. It does not ban cloud AI tools. It does require that lawyers understand the tool well enough to competently supervise it (Rule 1.1), protect client confidentiality (Rule 1.6), communicate with clients about material uses of AI where appropriate (Rule 1.4), and reasonably review outputs (Rules 5.1 and 5.3).
Practically, using MyCase IQ can be consistent with Opinion 512 if a firm does the work: read the DPA, confirm training is disabled on inputs, understand the sub-processor chain, review AI outputs before they leave the firm, and consider client notice for matters where AI use is material. It is not a checkbox — it is diligence.
Two other reference points worth knowing. In US v. Heppner (S.D.N.Y. Feb 2026), Judge Rakoff held that a litigant's chats with a public AI platform were not privileged. That case involved a consumer AI product, not an enterprise legal tool with a DPA, but the lesson generalizes: the terms under which you send content to an AI matter, and "I typed it into a chatbot" is not automatically privileged communication. The Brewer v. Otter.ai (2025) putative class action and West Technology Group v. Sundstrom (D. Conn. 2024) similarly underscore that lawyers are on notice about the confidentiality posture of the tools they choose. None of this makes MyCase IQ unusable. It means the DPA and the sub-processor terms are the risk-reduction instruments that matter.
Where the AI Actually Helps
Setting confidentiality aside for a moment, the AI features that felt genuinely useful in a small-firm context were: intake summarization (turning a long lead conversation into a structured record), document summarization for matters with a lot of prior filings, and first-draft generation of routine letters and standard clauses. Time-entry assistance — turning activity data into billable narratives — is another area where AI inside a practice-management system has a natural advantage over a standalone tool, because the billing context is already there.
Where I would not lean on it: novel legal analysis, jurisdiction-specific research without independent verification, and anything you are not going to read line by line before it goes out. That is not a MyCase-specific caveat; it is generative AI in 2025.
Pricing and Who It's For
MyCase publishes its plan tiers on its pricing page. AI features are typically included in higher tiers or as an add-on. Rather than quote numbers that shift, I would send you to the vendor page and note that the meaningful comparison is total cost per user per month with the AI tier enabled, plus any e-signature and payment-processing costs your firm will actually use.
The firm profile MyCase fits best: solo through roughly 25-lawyer firms doing consumer or small-business work — plaintiff PI, family, estate planning, small-business, immigration, criminal defense — where the value is in one integrated system for matters, billing, intake, and client communication. Larger firms and firms with heavy document-management or complex conflicts requirements typically end up on different platforms.
Firms that already have a practice-management system and just want AI-assisted meeting capture separately will want to look elsewhere, because MyCase's strength is the integrated platform, not a standalone AI feature. For that narrower need, an on-device notetaker like Basil for Law pairs well alongside any practice-management system.
Verdict
MyCase is a mature, well-integrated practice-management platform, and MyCase IQ is a sensible AI layer for the routine drafting, summarization, and intake work that fills a small-firm day. The confidentiality posture is standard-cloud-SaaS: usable with diligence, not zero-risk. Read the DPA, confirm the sub-processor terms, and use the AI features on matters where the risk-reward makes sense.
| Pros | Cons |
|---|---|
| Genuinely integrated: AI has real matter context | Cloud storage means broader subpoena surface than local tools |
| Strong intake, billing, and trust-accounting modules | Third-party LLM sub-processor adds a second vendor to diligence |
| Client portal and payments in one place | AI features gated to higher pricing tiers |
| Mature vendor, long track record in small-firm market | Not a fit for larger firms or complex document management needs |
| Reasonable fit with ABA 512 given proper diligence | You must actually do the DPA and sub-processor review — it is not automatic |
This review is for information only and is not legal advice.
Frequently asked questions
Is MyCase IQ safe to use with client-confidential information?
It can be used consistent with confidentiality obligations if the firm does the diligence: read the data processing addendum, confirm that inputs are not used to train the underlying model, identify the LLM sub-processor and its retention terms, and review outputs before they leave the firm. It is a cloud service, so a subpoena served on MyCase could in principle reach stored content, which is a structural feature of any SaaS practice-management tool.
Does MyCase train its AI on my client data?
Firms should confirm this in writing through MyCase's data processing addendum rather than relying on marketing pages or sales assurances. The relevant commitments are typically that customer inputs are not used to train foundation models, and that the LLM sub-processor's enterprise terms carry the same restriction. Ask for both in writing before onboarding sensitive matters.
How does MyCase compare to Clio or Smokeball?
All three target the small-firm practice-management market. MyCase is generally strongest in integrated client intake, payments, and portal communication. Clio has a broader third-party integration ecosystem. Smokeball emphasizes automatic time capture and Microsoft Word integration. AI feature parity is a moving target — evaluate on your firm's actual workflow rather than feature-list length.
Does using MyCase IQ create ethics issues under ABA Formal Opinion 512?
Opinion 512 does not prohibit cloud AI. It requires competent understanding of the tool, protection of confidentiality, appropriate client communication, and reasonable output review. Using MyCase IQ is consistent with those duties when a firm reads the DPA, understands the sub-processor chain, supervises outputs, and considers client notice on matters where AI use is material.
Can I use MyCase for meeting notes and recordings?
MyCase is a practice-management platform, not a dedicated meeting notetaker. Some firms record meetings elsewhere and upload notes into the matter file. Lawyers who want structured meeting capture typically pair MyCase with a separate notetaker; on-device options like Basil keep the recording and transcript on the lawyer's own device rather than a vendor cloud.
What should I ask MyCase for before onboarding?
Request the current data processing addendum, the sub-processor list including the AI model provider, written confirmation that inputs to AI features are not used for model training, the data-retention schedule, and the security documentation (SOC 2 or equivalent). Also confirm your ability to export and delete data on termination.
Meeting notes with no server to subpoena
Basil transcribes and summarizes entirely on-device — privilege-safe by architecture. See Basil for Law →
This review is for information only and is not legal advice.