A

Antidote

Remove the models and there is no product. Antidote ships no document system, no workflow engine and no time recording of its own; it is explicitly an overlay on the firm's existing time recording and practice management software. Every function it performs is a model task: extracting billing rules from a client's outside counsel guideline documents and the firm's historical billing data to build Individual Client Standards, analyzing time entries continuously through the billing cycle against those standards, and generating a corrected narrative for a fee earner to accept.

The vendor's own naming makes the same point, describing the analysis layer as Antidote AI. There is no rules engine or template library underneath that would survive the models being taken away, and no conventional software product the AI is a feature on.

Grounding is described at the level of its inputs, and accuracy is asserted without measurement. The source material is named concretely: outside counsel guideline documents, internal firm guidelines and historical billing data, combined into Individual Client Standards for each client against which entries are checked. That is a real account of what the output is grounded in. Everything testable is missing. No accuracy figure, test set, evaluation, error rate or description of retrieval method appears, and nothing addresses what happens when the model misreads a guideline or rewrites a narrative into something the fee earner did not do.

Accuracy is instead asserted, with corrected recommendations said to ensure compliance. There is no published statement about hallucination in either direction.

A human approval step is part of the published design, and the threshold structure around it is absent. The workflow is stated plainly: Antidote sends suggested fixes directly to email so fee earners can review, approve and move on, and corrections are described as recommendations accepted with one click. Nothing is presented as writing to the billing system unattended, which matters because the output is text that reaches a client invoice.

What is not published is the control structure around that review. Nothing says what happens to entries nobody approves, sets a threshold at which the system acts alone, surfaces a confidence signal to the reviewer, or describes what a supervising partner sees as against a fee earner. No escalation path is described.

No production evidence is published on the vendor's own pages. There are no named customers, case studies, testimonials or customer logos; the only logo strip is headed Backed by and shows investors rather than users. The home page figures are modeled rather than observed, and the vendor says so in a footnote. The 8 to 10 percent write off rate, the 30 extra days to payment, the 17 million dollars of working capital tied up and the 800,000 dollars of partner time are based on a firm of 100 partners billing 200 million dollars annually.

That basis is disclosed, but a hypothetical firm is not a deployment. Trade coverage of the January 2026 funding round refers to adoption by firms in the United States, United Kingdom and Australia without naming any of them, and funding coverage is not deployment evidence.

Confidentiality is asserted in general terms, and every specific commitment sits behind an access request or in an unpublished contract. Antidote's trust center states that the commitment to data privacy and security is embedded in every part of the business. It lists a Data Protection Policy, an Information Security Policy and an Encryption Policy, all behind a Get access flow. The published privacy notice expressly excludes the material that matters.

It records that users may upload confidential company information, which may include personal data, and that its collection and protection are subject to a separate agreement and not covered by that policy. Nothing published addresses training on customer content, separation by matter or client, tenancy, or what the named model provider may retain. The content ingested is time entry narratives, which describe what a lawyer did on a matter and are routinely redacted in fee disputes for that reason.

The advice line and jurisdiction limits matter little here, and professional responsibility, which does apply, is unaddressed. The product gives no legal advice and has no surface for consumers. The terms restrict access to Law Firm Users authorized by a law firm, require use in a commercial capacity, and state that the services are not intended for personal use. Professional responsibility applies directly. Antidote generates the narrative that describes a lawyer's work and then travels to the client on an invoice, which engages the rules on fee reasonableness and candor to a client.

Nothing published addresses it: no rule of professional conduct, bar or regulator, no ethics guidance, no statement that a fee earner remains responsible for the accuracy of a narrative the model rewrote, and nothing on whether an entry corrected by AI must still reflect the work actually done. The nearest provision runs the other way, with the terms disclaiming any liability for a law firm's delivery of legal services to its clients.

No governance position is published for a system that rewrites the record of billable work. There is no responsible AI page, no principles statement, no named owner accountable for model behavior, no evaluation before release, no testing regime and nothing on bias. The navigation and footer list How it works, Resources, About, Contact, Terms and Conditions, Privacy Notice, Cookie Policy and the trust center, and none of them carries governance material.

The trust center's documents all concern security: an Acceptable Use Policy, Backup Policy, Data Protection Policy, Encryption Policy and Information Security Policy. Security controls are a different subject from AI governance. The trust center does carry one candid line about an adjacent gap, recording that an application security monitoring program is being put together.

Real material exists around the edges, and the published policy does not reach the content the product ingests. Published: a retention table giving 180 days from the end of the relationship for identity and account records, 12 months for technical and usage data, and 7 years for inquiry records. International transfers rest on UK adequacy regulations or the International Data Transfer Agreement, and an ICO registration number, ZB821053, can be checked on a public register.

A named subprocessor list covers Amazon Web Services, Anthropic, Google, Linear and WorkOS, and storage is offered in the EU, US or Australia. The rules for customer content are absent, and the privacy notice says so expressly: uploaded confidential company information is subject to a separate agreement and is not covered by that policy. So no retention period, deletion route or incident notification commitment applies to time entries, narratives or ingested guideline documents. Encryption and Backup Policies sit on the trust center behind an access request.

Nothing published allocates loss for the platform, and the published document says so itself. The only language allocating loss is in the website terms of use. They exclude indirect and consequential loss and loss of profit, revenue, contracts, data and goodwill, and preserve liability for death, personal injury and fraudulent misrepresentation. They then state that any liability for losses arising from use of the services is limited as set out in the separate agreement between Antidote and the user's employer.

That agreement is not published, and website terms do not govern the platform, so the published terms point to a document no one can read before signing. No indemnity of any kind, no warranty on output and no cap figure appears anywhere. Antidote's trust center lists a Cyber Insurance document under Legal, behind the Get access flow, so an insurance position exists, with its scope and limits not published.

Integration is the product's whole delivery model, and not one system is named. The claim is central and repeated: the product works inside existing workflows, promises no workflow disruption, and sits on top of a firm's existing time recording and practice management software. That is true of the architecture, since Antidote reads and corrects entries held elsewhere. But there is no integrations page. No practice management, time recording, ebilling or document management system is named on the vendor's own pages, and there is no API reference, connector list or statement of what syncs in which direction or what a firm must configure. A real capability is claimed with nothing an implementer could use.

Residency is offered as a choice, and processing is not addressed separately from storage. Antidote's home page states that data is stored in region and names three options: the European Union, the United States or Australia. Amazon Web Services is identified on the trust center as the hosting subprocessor, so the infrastructure provider is named. Tenancy is never addressed: nothing states whether the platform is single or multi tenant, and no dedicated or isolated option is offered.

Where processing happens is not stated as distinct from where data is stored. That matters because Anthropic and Google are named subprocessors and no location is given for model processing, so choosing EU storage does not establish that the model call stays in the region.

Named certifications and a real trust center, without evidence that can be read openly. The SafeBase portal at trust.antidotelegal.com renders in full and carries three compliance entries: GDPR, ISO/IEC 27001:2022 with the standard version named, and SOC 2 Type 1. Its document set lists an Antidote Legal Security Summary 2026, a Pentest Report, the certification documents, Cyber Insurance and five policies. The certifications are stated rather than implied, and a route to the underlying reports visibly exists.

No report can be read openly. Every document sits behind a Get access flow that offers to start a security review, view and download sensitive information or ask for information, without saying whether fulfillment is self serve or runs through a sales conversation. No auditor is named, no audit period or report date beyond the year appears, and no scope statement is published. The attestation is SOC 2 Type 1, an assessment of control design at a point in time, not Type 2.

The provider is named and the rest of the chain is not. The trust center publishes a subprocessor list without an access request, naming Amazon Web Services, Anthropic, Google, Linear and WorkOS. Anthropic's listing identifies whose models process customer content. Google appears alongside it, though the list does not say whether that entry is infrastructure or a second model provider. No model is named, only the provider, so which model or version reads a time entry is not stated.

Where model processing runs is not stated; naming a cloud host says where the platform sits, not whose model reads the content. No commitment to notify customers when a subprocessor, provider or model changes is published.

No pricing information is published at any level, including the unit of charge. The navigation and footer include no pricing page. Every call to action on every page is Book a demo, routing to a contact form. Nothing states whether the product is charged per fee earner, per timekeeper, per entry checked, per matter or as a platform fee, and no tier, minimum, term or implementation cost appears. The terms of use refer to placing an order and to a separate agreement with the customer's employer without describing any commercial term.

The product's own pitch is quantified in pounds and dollars of recovered revenue, so the site gives a detailed model of the benefit and nothing about the cost.

The buyer is claimed broadly and the boundary is drawn only in the contract. Marketing addresses leading law firms and leading global firms without defining either. The only quantitative indicator of segment is the modeled example of a firm of 100 partners billing 200 million dollars a year, which is an illustration rather than a statement of who the product is for. The real boundary sits in the terms, which restrict access to Law Firm Users authorized by a law firm and exclude personal use.

In house and government legal teams are therefore outside the product by contract rather than by any published statement of scope. Practice area matters little here, since billing compliance works on time entries whatever the matter type. Size and geography are not stated plainly. No firm size range, minimum timekeeper count or jurisdictional coverage appears, and the only geographic signal is the choice of storage regions.