P

Precedent

The models drive a core capability on a service platform that would still work without them. Claim setup with the carrier, policy verification and medical record retrieval are operational services with a workflow and human core. The vendor presents them as the first three of four steps before AI enters, and a firm could buy them alone and receive a working service. The models power the fourth step, which holds the flagship.

Demand Composer drafts the demand package from the case documents, MedChron builds medical chronologies, and Global Demand produces packages for several plaintiffs. Other tools sort incoming files, benchmark demands and anticipate adjuster tactics, and a voice assistant called Ask Casey sits alongside them.

Grounding is real, documented and checkable. In what the vendor calls a Closed Loop, every medical fact, diagnosis and billing code in a demand letter is linked directly to its source page in the raw medical record. The vendor tells buyers they need not trust the AI, because they can click the citation and see the document. The same page carries a heading that reads Zero Hallucinations, yet the vendor also has reviewers check factual integrity before delivery, which a system free of hallucinations would not need.

Accuracy therefore rests on source links and human review rather than on model behavior. That is a sound design, and it is not what the headline claims. No measured accuracy figure, test set or method is published, and no failure mode is named.

Human review is written into the workflow at two stages, and the controls around it are not published. The vendor's own trained expert reviewers check each draft for narrative logic and factual integrity before the firm sees it, an oversight step inside the vendor rather than an obligation placed on the buyer. The attorney then receives what the vendor calls a draft ready for review, with every medical fact traceable to its page in the record, so checking is a designed workflow rather than an instruction.

No mode is described, no threshold is stated at which the system stops or escalates, and nothing says what happens when output is wrong. The source linking architecture is named rather than described as a control with stated limits.

Deployment evidence is real and partly unverifiable, with one headline figure out of step with its source. A named case study with Hines Law Firm reports settlements up 16 percent and the likelihood of tenders up 71 percent, measured across hundreds of personal injury cases. Named customer logos include Catania, Ramos Law and Sand Law. Testimonials carry a person and a role, among them a Personal Injury Director at Hines Law who describes drafting thirteen demands in a day.

Aggregate figures are more than 100 law firms, more than 50,000 demands sent, a 95 percent retention rate and a 4.7 star rating, none with a stated basis. The case study page was not opened, so the method, comparison basis and period behind its figures are not known and the page may say more. The home page banner claims 25 percent higher settlements while the case study it links reports 16 percent, and nothing reconciles the two.

Confidentiality is covered in contract and in architecture, while privilege and work product are not addressed anywhere. The Master Service Agreement puts Protected Health Information inside its definition of Confidential Information, binds both parties to strict confidence that survives termination, and requires subcontractors to be bound. It also commits to handling consistent with HIPAA. Behind the contract sit isolation between firms, encryption, and a bar on using case files for training or sharing them across clients.

The firm is said to own its data. Nothing addresses what an underlying model provider may retain from the medical files and demand strategy that pass through the system.

The advice line is never drawn, though the vendor writes about professional conduct elsewhere. The Master Service Agreement has no statement that the service is not legal advice. Marketing presents the product as a drafting and workflow service rather than in terms of advice, and it is sold only to plaintiff firms. Every draft passes through the vendor's reviewers before it reaches the attorney, so lawyer review is built in and stated.

A vendor article on billing for AI powered services tells firms their use of technology must not compromise duties of loyalty and communication. Nothing states what the product is and is not, who may rely on it, or how it supports competence and supervision, and no jurisdiction limits are named.

No governance position is published for a system that drafts the document a claimant's recovery is negotiated from. Nothing identifies who inside the vendor is accountable for the models. No testing or evaluation before release is described, no results are disclosed, no policy or principles statement exists, and no certification such as ISO 42001 is claimed. Nothing addresses uneven output across injury types, jurisdictions or claimant demographics.

The security page does carry a section headed AI Safety with real content, but what it describes is the product's quality controls, source links and expert review. Those govern the quality of a draft. Governance is a different matter, namely who answers for how the system is built, tested and corrected, and that is not published.

Data handling is documented in substance, and incident response is the gap. Encryption is AES-256 at rest and TLS 1.2 or better in transit with perfect forward secrecy. Access inside a firm runs on roles, retention is set by the customer rather than the vendor, and permanent deletion is available. Client files are kept out of model improvement, and health data is handled under a design built for HIPAA. All of that is published policy rather than marketing.

No incident or breach notification practice appears on any page, on a platform that takes in complete medical files and holds health records for every case it works.

A real liability position is published, and it stops short of wrong output. The Master Service Agreement sets out mutual indemnification against third party claims arising from negligence, material breach, legal violations and other listed causes, with prompt notice and cooperation required. Aggregate liability is capped at amounts paid in the preceding twelve months, infringement claims excepted, and neither party bears indirect, consequential or punitive damages.

The vendor warrants its authority to perform and that it does not infringe registered US copyrights, patents and trademarks. Nothing a buyer can invoke applies when the output itself is wrong. No warranty covers the accuracy or completeness of a demand package, clause 6.3 disclaims all warranties beyond the limited one, and no insurance is referenced. One clause says the vendor has no liability for failing to identify or notify the client of any demand, on a service that sends demand letters to carriers for the firm.

The published agreement is an abridged summary. Fuller clause language appears in search results, and the full limitation wording, which could not be read, may say more.

Integrations reach the case management systems this buyer runs, and their depth is not documented. Three are named, each with its own page. In SmartAdvocate, Demand Composer is said to run directly inside the platform. In Clio, demand creation is described as streamlined within Clio Manage, and in Litify demands are generated and managed in the firm's matter system. For plaintiff personal injury, those three cover most of the case management market.

The vendor was a finalist for Best New App in the 2025 Clio Integration Awards, an assessment of the integration itself, and a dedicated integrations index page exists. The three integration pages were not opened, so what syncs, in which direction and what a firm must configure are not known, and the pages may say more. No API or developer documentation was found, and no document management or electronic signature connection is named.

Residency is stated at country level and nothing below it. The vendor states that all data processing and storage occur only in the United States and that client data never leaves US soil, framing this as data sovereignty. Tenancy is stated as logical isolation between firms. No cloud provider, region or data center is named, and no failover or secondary location is described. There is one cloud service, with no private, dedicated or on premises version.

Residency is the vendor's architecture rather than a customer choice, and a firm has no way to require or verify placement.

SOC 2 Type II is claimed, and nothing lets a buyer see the evidence. The vendor states it is SOC 2 Type II certified on the strength of annual audits by independent third parties covering security, availability and confidentiality. Its architecture is said to be designed for HIPAA compliance, and it offers to sign a business associate agreement for firms handling Protected Health Information. The security page is the vendor's own and is substantive.

No auditor is named, no audit period or report date is given, and the scope is not described. There is no download, no stated request path and no security review process. No other attestation is claimed, and no penetration testing or vulnerability program is described.

Models are referred to generically, and nothing underneath them is identified. The one trace of the supply chain is the security page's training statement, which mentions public foundational models and so shows that foundational models are in the architecture. It names no model, provider or version, and nothing states whether the generative layer is built by the vendor or supplied by a third party. The Closed Loop is described without saying what generates inside it.

No commitment to notify customers of a model change is published, and with nothing named, there is nothing such a notice could cover.

Pricing is public for the flagship only, and the marketing and the agreement disagree about commitment. Demand Composer's rate, trial and fee terms are all published, so one demand can be priced up front, while the rest of the platform has no published rate. The home page states there are no contracts, and the security page that there are no long term contracts. Clause 9.2 of the Master Service Agreement provides for automatic renewal for a further twelve months with a 7 percent fee increase, unless the agreement is canceled in writing thirty days before the service end date. Both statements are published, and the agreement is the binding text.

Coverage is deep within plaintiff personal injury and narrow by design, and its limits are not stated. The segment is plaintiff personal injury law firms, positioned explicitly against the carrier side. The vendor says it serves all firm sizes and handles small and large cases alike. Workflow coverage runs across the work before litigation, from claim setup and record retrieval to demand drafting and adjuster preparation.

Named customers range from regional practices to firms that advertise heavily. Nothing says which case types, injury categories or jurisdictions fall outside coverage, or whether the product suits work once litigation starts. A testimonial refers to requirements specific to a jurisdiction, and no jurisdictional scope is published.