For a small law firm, an AI agent is software that takes a goal and carries out several steps itself, such as reviewing a set of contracts and proposing redlines. Spellbook's Associate works that way; Clio Work and Smokeball's Archie mostly assist inside a matter. Either way, a lawyer checks authorities, facts, dates and every edit before relying on them.
The word "agent" is doing a lot of marketing work, and the three vendors use it differently on their own pages. Spellbook calls Associate "the AI agent for transactional law". Smokeball calls Archie its AI matter assistant. Clio calls Clio Work an AI-powered workspace and never calls it an agent; the place Clio's pricing page does use the word is for the phone, web and email intake agents in Clio Grow. So judge each tool by what it does between your instruction and your review, not by its label.
Assistive and agentic: the distinction that matters for a lawyer
Instead of arguing about the word, ask three questions of any tool.
- How many steps does it take without you? One answer to one prompt is assistive. A chain (find the documents, compare them, change the terms, produce a report) is agentic.
- What can it change? Reading and summarising is low risk. Editing a document, filing something to a matter or sending a message is higher risk, because the mistake lands somewhere real.
- Where is the checkpoint? A well-designed tool stops at a review point: tracked changes you accept, a draft you send, a summary you file. Know exactly where it stops.
Those three questions matter more than any label, and they give you a way to compare tools that call themselves different things. Put to the three products small firms meet most often, they give three different answers. If you want a broader product comparison, Clio, Smokeball and Lawmatics compared goes through the platforms.
Spellbook Associate: the most openly agentic of the three
Spellbook's website describes Associate as an AI agent for transactional law, aimed at research, review and redlining across sets of documents. Its own page says Associate breaks goals into tasks and executes them, and lists multi-document workflows: changing terms and party details across a set of documents, revising several documents with a single action, and linking information between documents. Example projects named include dataroom reviews, financing documents, disclosure schedules and employment packages.
In plain terms: instead of opening ten agreements and reading each, you tell it the goal (find every assignment clause, change the governing party name in all of them, list the inconsistencies) and it works through the set. That is agentic, and it is also where mistakes can multiply, because one wrong instruction is applied ten times.
The Spellbook site also advertises a seven-day free trial and a demo booking. It lists no prices on the pages I read, so I give none here. The pages I read do not state explicit human-review requirements for Associate, so the review process is yours to define, and the checks below are what I would put in place.

The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowSmokeball Archie: an assistant that works inside the matter
Smokeball describes Archie as its AI matter assistant and, on the Archie page, as "legal AI that knows your matter": it works inside your matter to draft, review and answer questions. The capabilities listed there are matter questions and answers (what has happened, what is missing, what comes next), with summaries linked to the source; suggested next steps that update as the matter changes; document comparison to find conflicting terms; drafting replies to email threads in Outlook and drafting or editing text in Word; and Archie Apps for jobs such as bank statement analysis, legal chronologies and audio transcription. The home page FAQ says the final call stays with the legal professional.
On data, the Archie page says it works only within the matter you are in and is visible only to staff already assigned to that matter, that your data is never shared with third parties for viewing, training or AI modelling, and that it runs under zero-data-retention agreements. On the pricing page, Archie appears as an add-on on the Boost, Grow and Prosper+ plans (not on Bill), and the page shows no dollar amounts; the FAQ says pricing depends on the number of users, the plan and the contract term. Ask the vendor for a quote.
This is closer to assistive than agentic: it does well-bounded tasks inside a matter and returns them for you to use. The suggested next steps are the most proactive part, because Archie raises them without being asked, but it still proposes rather than acts. The value is context. Because it sits in the matter, it already has the documents and details, so you do not paste them into a separate tool.
Clio: a drafting workspace plus a practice-management assistant
Clio has two relevant products, and mixing them up is common. Clio's own site blocks automated reading, so the descriptions below come from Internet Archive copies of its Clio Work and pricing pages taken on 20 October 2026; check the live pages before you buy.
- Clio Work is what Clio calls "your AI-powered workspace", sold as "the only AI that understands your cases, their context, and the law". For litigators, the page lists reviewing discovery, pleadings and case files, surfacing precedent and supporting authority, flagging gaps and weak citations in opposing arguments, and drafting motions and briefs. For transactional lawyers, it lists reviewing contracts and extracting key terms, spotting risky, missing or unusual clauses, and comparing drafts. It also builds a matter timeline from your documents, links every output to its source, matches authority to your jurisdiction, runs a built-in citator, and lets you draft in Clio Work or Microsoft Word. Clio says client files are processed under zero-data-retention agreements and are never used to train public AI models. The page offers a free trial and a demo.
- The AI built into Clio Manage, Clio's practice-management product, is a different thing. Clio's pricing page says AI is included from the Core plan upwards as part of the plan rather than as an add-on, and lists drafting client updates, flagging risks, prioritising tasks and preparing billing. What Clio Manage AI costs and how to switch it on covers the plan side.
Is Clio Work an agent? Clio itself does not call it one. Its page describes analysis, strategy and drafting that you start and then review, and the pricing page FAQ says Clio's AI "handles the first pass" while "you review and approve everything before it reaches a client or the court". That matches my reading: it is a powerful assistant that does multi-part research and drafting across a whole matter, with you at the checkpoint. The archived pricing page shows no public price for Clio Work, so ask Clio for a quote.
The three side by side
| Question | Spellbook Associate | Smokeball Archie | Clio Work and Manage AI |
|---|---|---|---|
| Vendor's own label | AI agent for transactional law | AI matter assistant | AI-powered workspace; AI built into Clio Manage |
| Main job | Review, redline and research across sets of contracts | Draft, review and answer questions inside a matter | Research, analysis and drafting; admin and insights in Manage |
| Steps without you | Many, across multiple documents | Few, bounded to a matter | Several within a research or drafting task |
| What it can change | Document terms across a set | Drafts and summaries | Drafts, memos and analyses; saves to a matter |
| Where it sits | Alongside Word and document tools | Inside the practice-management matter, Outlook and Word | Own workspace built around the matter; drafts in Word too |
| Pricing on public pages | None shown; 7-day free trial | No amounts; add-on on Boost, Grow and Prosper+ | No price shown for Clio Work; free trial offered; Manage's AI from Core up |
The table shows why comparing prices first is the wrong order. The real decision is about which job you want the tool to do and where your documents already live.
What a lawyer must review, whichever tool is used
Treat this list as a standing checklist and put it in your firm's AI policy. It applies to agents and assistants alike.
- Every authority and quotation. Open the source. A citation that links to a source can still be mis-summarised, and a source can be outdated. See how to stop AI inventing case law for a routine you can adopt.
- Every change an agent made. Use tracked changes and review each one. Check defined terms, cross-references, numbering and party names, because multi-document edits can break links between clauses.
- Client facts. Compare names, dates, figures and addresses against the source documents. Tools summarise what they are given, including mistakes in it.
- Jurisdiction and court rules. Check that the law applied is the right one for the matter, since vendor sources vary in coverage.
- Deadlines. A timeline that an AI builds from your documents, as Clio Work does, is a reading aid, not your calendaring system. Keep your dedicated deadline controls and verify any date an AI produces.
- What was not found. "No unusual clauses found" is a claim. Sample-check a few documents to see whether the agent missed something.
- Confidentiality and permissions. Confirm who can see which matters through the tool, and read the data terms before real client files go in.
Rules about supervising technology and protecting client information come from your professional body or regulator, and I cannot tell you what yours require. Ask them, or a qualified adviser, if you are unsure.
A worked example: one contract task with an agent, step by step
Say a small commercial firm acts for a specialist food importer that has twelve supplier agreements to refresh after a change of legal entity. The partner wants every party name updated, the governing-law and termination clauses compared, and a list of anything unusual.
Without an agent. A paralegal opens each of the twelve documents, updates names, copies clauses into a comparison table and flags oddities. Illustrative time: about five hours, with the usual risk of a missed instance in a long document.
With an agent in a tool like Associate. The associate lawyer uploads the twelve documents and gives the goal in one instruction: update the supplier-side party name to the new entity, produce a table of governing law and termination notice periods, and list clauses that differ from the first agreement. The tool works through the set and returns tracked changes plus a table. Illustrative time to run: a few minutes. Illustrative review time: ninety minutes to two hours, because every change is checked.
The review is where the value is won or lost. In the first test, say the lawyer finds the party name updated correctly in eleven agreements, but in one the old name remains inside a schedule, and in two the new name changed a defined term used elsewhere. The termination table is right for ten and wrong for two where notice depends on a schedule. None of these is dramatic; all would have mattered. A fair summary of the test is: roughly two hours instead of five, with errors caught only because every change was reviewed. Those figures are invented for illustration; run your own test on past matters before you believe any estimate, including this one.
A second example, inside the practice-management matter
Now a different job. A kitchen-fitting client has a dispute over a contract, and the partner asks an assistant inside the matter for a chronology from the correspondence and documents, then a draft holding letter. The assistant returns a chronology of fourteen entries and a two-paragraph draft. The lawyer checks each entry against the source document, finds that one date came from an email's sent time instead of the event it described, and fixes it. The draft letter says the client "denies liability", which the instructions never said. It is removed. Again the pattern: useful first draft, real errors, human review.
Questions to put to every vendor in writing
Marketing pages answer how a tool feels. These questions answer whether your firm can use it responsibly. Send them to each vendor, keep the replies, and compare them side by side.
- Where is our data stored and processed, and can we choose?
- Is any customer content used to train or improve models, now or by default in future?
- Who at the vendor can see our content, and under what circumstances?
- How does the tool respect matter-level permissions? Can an ethical wall be enforced?
- What is logged, and can we export the log (who ran what on which matter)?
- What happens to uploaded documents when we delete them or leave?
- Which actions can the tool take without a human confirming, and can we turn them off?
- What are the sources for legal research, and how current are they?
- What did the vendor change in the last six months that affected output quality?
Smokeball's Archie page, for example, says Archie is visible only to staff assigned to the matter and that data is never shared with third parties for training; Clio's Clio Work page says client files run under zero-data-retention agreements and are never used to train public AI models. Those are the kind of statements to put in your file with the date, and to ask the vendor to confirm in the contract rather than only on a web page.
A filled-in review record for an agent-assisted task
A review is only useful if it leaves a trace. Here is an illustrative record for the supplier-agreement task above, kept in the matter file.
| Item | Entry |
|---|---|
| Task | Update party name, compare governing law and notice periods across 12 agreements |
| Tool and date | Contract agent, 4 November |
| Instruction given | Saved copy of the prompt attached |
| Output reviewed by | Associate lawyer; partner spot-checked 3 of 12 |
| Changes accepted | 41 of 44 tracked changes |
| Changes rejected | 3 (defined term altered in two documents; schedule edit wrong) |
| Errors found in tool output | Old name left in 1 schedule; notice period wrong in 2 summary rows |
| Time | Run: minutes; review: about 2 hours |
| Sign-off | Partner, 4 November |
After a month of such records you know, from evidence, which tasks each tool does reliably and which it does not. That is a far better basis for renewal than a vendor's case study, and it helps with any conversation with a client or insurer about how you use AI.
Which tool wins in which firm
There is no best agent in the abstract. These rules of thumb come from matching tool shape to the work, not from any ranking.
- A firm that mostly drafts and reviews contracts (commercial, property transactions, employment packages) should test a transactional agent first, because multi-document work is where it differs from an assistant.
- A firm already running every matter in one practice-management system should test that system's own assistant first. Context and permissions are already there, and adoption is easier when staff stay in one screen.
- A litigation-heavy firm should weigh research quality and citation checking above everything, and test on a closed matter where the right answer is known.
- A firm doing volume work with simple documents (wills, standard letters) may find a general chatbot with strict rules enough. The comparison of ChatGPT and a legal AI tool for a small firm sets out when.
A first-pass review prompt, and why agent mode is not magic
Whatever tool you pick, the quality of the instruction decides much of the quality of the result. A clear instruction looks like this:
Review the attached supply agreement from the supplier's side.
List, in a table: clause number, what it says in one line, and whether it is unusual compared with standard commercial terms.
Cover: payment terms, termination and notice, liability cap, indemnities, governing law, assignment, exclusivity.
Quote the exact words for any clause you mark unusual. If a topic is absent, write "not found" and do not infer.
Do not rewrite anything. Do not give a recommendation.
Illustrative output is a seven-row table, with, say, a liability cap quoted exactly and marked unusual because it excludes the supplier's own breaches, and exclusivity marked "not found". What you check: that the quoted words really appear in clause 12.3, that "not found" is true (search the document yourself), and that nothing in the table was inferred. If a tool's agent mode runs this across ten documents, the same checks apply ten times, so spot-check at least a third and every row marked "not found".
How to test a tool on your own work before paying
- Pick one repeatable task you already do and can time: first-pass NDA review, lease abstracts, chronologies, client update letters.
- Use closed matters or anonymised copies for the test, with the data terms checked first.
- Time the old way and the new way, including the full review time of the AI output.
- Count the errors you caught and what kind they were (wrong fact, missed clause, invented citation).
- Ask the vendor where data is stored, who can access it, whether it is used for training, and how permissions work.
- Decide with numbers. If review time eats most of the saving, the tool is not paying for itself on that task yet.
Spellbook's seven-day trial and the free trial on Clio's Clio Work page make such a test cheap; for Smokeball, ask for a demo and a pilot arrangement, and with every vendor insist on seeing the tool handle your type of matter. The wider AI implementation plan for a small law firm shows how to sequence this over ninety days.
Three misunderstandings worth correcting early
"Cited means correct"
A link to a source shows where an answer came from, not that the answer is right. Open the source and read the passage.
"It lives in my practice software, so it is safe"
Permissions help, and vendors describe them, but you still decide what goes in and who can use it. Review your own access settings and write a short internal rule.
"An agent will replace the junior"
What you can reasonably expect from these tools is faster first drafts and first-pass review, with more checking work for whoever supervises. The skill shifts towards reviewing, and the junior's training needs to cover how to check machine output as well as how to produce a draft.
Writing the firm rule that makes any of them safe to use
Keep it to one page and put it in front of everyone who can use the tool:
- Approved tools and approved tasks only.
- No client file goes in until the data terms are checked and the client's position is understood.
- Every output is reviewed by a lawyer before it leaves the firm; the reviewer's name is recorded on the file.
- Authorities are opened and read.
- Tracked changes on, always, for document edits.
- Errors found are logged, so the firm learns what each tool gets wrong.
If you would like help choosing the first task and setting those rules, my AI implementation consultation covers exactly that, and the AI guide collects the related tutorials. For the pricing side of the decision, per-seat or pay-as-you-go legal AI pricing is the natural next read.
Questions small firms ask about legal AI agents
Is an AI agent different from an AI assistant?
In practice the difference is how much the tool does between your instruction and your review. An assistant answers or drafts when asked. An agent breaks a goal into steps and carries them out, perhaps across several documents. Vendors use both words loosely, so judge the tool by what it does without you.
Do I still have to check agent output?
Yes. Clio says you review and approve everything before it reaches a client or the court, Smokeball says the final call stays with the legal professional, and professional rules generally place responsibility on the lawyer. Check authorities, quotations, dates, client facts and every edit an agent makes before you rely on or send anything.
Can I try these tools before buying?
Spellbook's Associate page offers a seven-day free trial, and Clio's Clio Work page offers a free trial and a demo. Smokeball shows no prices and offers a demo. Whatever you try, use sample or anonymised material first, and confirm the data terms before any real client file goes in.
Which tool should a small firm start with?
Start with the job you do most. Transactional contract work points to Spellbook; a firm already running its matters in Clio or Smokeball will find the built-in assistant the easiest to adopt. Pick one task, test it on past matters, and decide after you have measured the review time.
Further reads
- Clio vs Smokeball: Which AI Assistant Suits a Small Firm? — Head to head on the practice-management assistants.
- How Small Law Firms Use AI to Draft Letters and Routine Documents — Routine letters and documents drafted with AI.
- AI Client Intake for Law Firms: Qualify Enquiries Out of Hours — Qualify enquiries out of hours without losing control.
- What an AI Consultant Does for a Law Firm, and What It Costs — What an AI consultant does for a law firm.
- AI Readiness Checklist for Accountants, Solicitors, Consultants — Check the firm is ready before adding agents.
- AI Contract Review Software for Lawyers: Spellbook vs Gavel Exec — Compare Spellbook, Gavel Exec and Copilot in Word on pricing, playbooks and data handling, then test all three on one planted-error contract.
- Spellbook Pricing: How a Small Firm Should Read the Quote — Spellbook is quote-only with a 7-day free trial. How a small firm can read the quote beside Copilot and Gavel Exec, line by line, and test all three on one NDA.
- Clio Automations: What to Set Up First and Where AI Fits — A setup order for a small firm's Clio automations: task lists per matter stage, generated documents, intake handover, and where Manage AI fits.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Spellbook Associate page (agent description, multi-document workflows, 7-day trial); Smokeball home page, Archie AI page and pricing page (Archie features, data statements, add-on on Boost, Grow and Prosper+, no published prices); Clio's Clio Work page and pricing page, read from Internet Archive copies of 20 October 2026 because clio.com blocks automated reads. Vendor claims are the vendors' own statements.