Use this guide to distinguish an available capability, a controlled pilot and a roadmap proposal. The categories below are evaluation questions for a purchaser, not a complete census of the legal-technology market or a claim about named customers.
How to grade a trend: the shipped test
Ask whether the capability is available in the service and plan you can purchase, what onboarding it requires and what limitations apply. A guided deployment can be a released product, while a self-serve demo may still show sample data. Record availability, observed behaviour and customer-reference evidence separately.
Shipped: citation-grounded research and review
For research and review, inspect the sources behind material conclusions. The Stanford study of legal-research tools provides a dated example of why vendor claims need testing; its findings are not a current universal product score. Test your sources, jurisdiction and task, and keep failures visible. Our citation-grounding guide explains the workflow.
Shipped: document workflows at batch scale
The second graduation is scale: not "AI reads a contract" but AI works a set: reviewing a batch against one standard with a cross-file view, answering the same questions across a data room into a typed and cited grid, extracting candidate dates from thousands of pages into a chronology with deadlines flagged. This is the unglamorous layer where legal hours actually concentrate, which is why it shipped: the demand was never speculative. The tell of maturity is structural output (grids that export to Excel, chronologies to Word or calendar files, findings to tracked-changes redlines) rather than prose in a chat window. If a vendor's batch story is "paste documents into the conversation", the workflow has not shipped; it has been simulated.
Shipped: layout-preserving legal translation
For translation, test the document structure, numbering, tables, schedules and substantive wording with a qualified reviewer. Record the language pair and scan quality. The availability of a translation feature does not establish fitness for a formal filing or a measured saving for your practice. See the translation review workflow.
Partially shipped: agents, drafting autonomy, analytics
Three trends earn a genuine "partially":
| Trend | What shipped | What did not |
|---|---|---|
| AI agents | Bounded multi-step automation with checkpoints: research plans exploring several angles in parallel, review pipelines that run end to end | Autonomous matter-handling without lawyer oversight: blocked by both reliability and professional responsibility |
| Drafting | Draft-from-brief and template drafting that emits tracked changes a lawyer accepts or rejects, with authorities cited beside clauses | "Send without reading": no serious vendor offers it, and none should |
| Analytics | Practical usage and matter analytics: adoption, feature use, activity trails that support governance and ROI measurement | Litigation-outcome prediction as a dependable science; judge-behaviour models remain directional at best |
The pattern across all three: the shipped half is the half that keeps a human in the loop. That is not a coincidence: it is the professional-duty constraint expressing itself as product design, as our piece on human-in-the-loop legal AI argues.
Still hype: the robot lawyer and friends
Ask for evidence whenever a pitch claims autonomous legal judgment, a probability of winning or complete error elimination. Identify the task, dataset, scoring method and limits. If those are unavailable, record the claim as unverified rather than declaring a whole technology category either proven or impossible.
Separate what you observed in a trial from what a roadmap promises. Do not base a deployment decision on a feature that is not available in the purchased service.
The quiet winners nobody keynotes about
Three shipped capabilities generate outsized value while attracting no headlines: OCR and document intelligence (scans made searchable, parties and dates and clauses extracted on upload, duplicates flagged) the enabling layer everything else stands on; templates as institutional memory: review checklists, matrix question sets, and drafting outlines that turn one lawyer's judgment into the whole team's default; and governance features (role-based access, audit trails, usage analytics) which decide whether adoption is supervised or shadow. Buyers rarely shortlist on these; users depend on them daily within a month. They are worth explicit weight in any evaluation.
Buying through the hype: three questions
- Can we try it self-serve, today, on our documents? A capability that requires a guided demo to appear is not shipped for you.
- Can we open the sources behind an output? Verifiability is the load-bearing property; everything else is furniture.
- Who uses it weekly in production, and on what? Reference use in real matters (not pilot enthusiasm) is the maturity signal.
After a bounded pilot, expand only where the evidence supports it. Record training needs, template changes, reviewer effort and unresolved limitations. A successful demonstration is a reason to investigate further, not proof of organisation-wide returns.
How Judicio approaches the shipped standard
Judicio documents its released workflows at Review Matrix getting started and the related product guides. Use a permitted trial set to inspect questions, sources, corrections and exports. Confirm the selected plan and configuration, and measure your own results. This article does not assert customer adoption figures or an independent performance benchmark.
This audit reflects the market as of mid-2026 and is general information, not investment or purchasing advice. Grade every claim (including ours) against your own trial.