E

EvenUp

The models are the entire product, and the company was built around a proprietary dataset to feed them. Piai is named as EvenUp's own AI engine, and the vendor's central technical claim is that it is trained on a large dataset specific to personal injury rather than adapted from a general model. Every deliverable is model output. Medical chronologies are generated from raw records with treatment timelines and ICD extraction, demand letters are generated end to end, case valuations come from a settlement repository, and analytics sit on top of the extracted data.

Remove the models and nothing remains but a document store the firm already had. Independent review material reaches the same conclusion, describing it as a vertical drafting engine trained on injury cases rather than a general legal assistant.

Grounding is built into the deliverable, and the vendor publishes no measured figure. Medical chronologies carry citations back to source documents, so a reviewer can check any entry against the underlying record, which suits output that is a factual account of someone's treatment. Demand packages cite comparable verdicts from the settlement repository, so the valuation argument traces to named prior outcomes, and a Thomson Reuters and Westlaw integration supports legal citation.

There are two gaps. Two accuracy figures circulate in third party material and neither is published in vendor material with a method attached: that chronologies capture over 90 percent of relevant medical information on first pass, and that demands are 69 percent more likely to reach policy limits. Neither comes with a sample, baseline or definition. And nothing says what the system does when a record is illegible, contradictory or missing, which in medical record work is the common case.

Oversight is sold as a product tier, which makes it visible rather than aspirational. Demands are offered in tiers from instant AI generation through Express Demands to an expert reviewed tier, where an in house team checks the document before delivery. Independent material notes that the human quality step adds turnaround time, a trade off made visible in the pricing structure. Output is consistently positioned as a draft that requires attorney review.

The mechanics are not published: nothing says what the in house reviewers check or against what standard, or what distinguishes the tiers beyond speed. No confidence indication is given on generated content, and nothing describes the instant tier, where no human sits between generation and the attorney's inbox.

Outcome claims are specific and named firms appear, but the best available source flags the whole class as vendor supplied. Lundy Law is reported to have increased output from about 30 to about 110 demand packages a month after adopting AI tooling without adding staff, and J. Chrisp Law to have reclaimed 80 hours of paralegal time per case. Those are named firms with quantified operational change. The vendor claim that demands are 69 percent more likely to reach policy limits is the most consequential figure, because it speaks to case outcome rather than throughput, and it carries no method, comparison group or sample.

The independent guide reporting these figures says most such benchmarks come from vendor marketing and that results depend on case complexity and record volume. The adoption story is credible and consistently reported, but none of it is published as a vendor case study with a method.

Confidentiality evidence here rests on a health specific credential. The product takes in complete medical records, billing statements and treatment histories for injured claimants, so the confidential material is not only the client's legal matter but a third party's protected health information. Against that sit an independently assessed HIPAA attestation validating safeguards for PHI and a SOC 2 Type 2 examination whose scope includes confidentiality and privacy as well as security and availability.

The vendor also says it supports customers handling sensitive information through contractual, technical, organizational and compliance measures, which acknowledges the business associate relationship a plaintiff firm needs. Nothing addresses legal professional privilege or attorney work product. A demand package is work product and the case strategy in a valuation is privileged, but the published posture covers health data protection and general security without reaching the legal side at all.

Not located in vendor material. The product generates the demand letter a firm sends to an insurer, which is an advocacy document making legal and valuation arguments on a client's behalf, and it generates the case valuation that shapes settlement advice. Independent material states consistently that output is a draft requiring attorney review, and that framing is not published as a vendor published position. Nothing addresses the supervising attorney's duty over machine drafted advocacy, the professional responsibility of relying on a machine generated valuation when advising a client whether to settle, or any bar guidance.

The gap matters more here than on a research tool because the output goes out under the firm's name to an adverse party.

Nothing published about how the models are governed or evaluated. No AI policy, no model card, no bias or fairness testing, no evaluation methodology or result, no accuracy monitoring, no drift statement, no named governance body and no ISO 42001. The untested risk on this product is specific and serious: case valuation is generated from a settlement repository of past outcomes, and historical personal injury settlements carry the demographic and geographic patterns of who was compensated well and who was not.

A valuation engine trained on that history can reproduce those patterns for a new claimant while presenting the result as a data backed figure, and nothing published indicates whether that has ever been examined.

Data handling is credentialed and the training question is unanswered. The HIPAA attestation and the SOC 2 Type 2 privacy and confidentiality scope show that safeguards over protected health information have been independently assessed, which is real stewardship evidence. No statement is published on whether medical records, demand drafts, case files or settlement outcomes submitted by firms are used to train or improve Piai, how long client content is kept, or whether a firm can require deletion.

The question is central for this vendor: its main technical claim is a proprietary model trained on a large personal injury dataset, and nothing published says where that dataset came from or whether customer matters continue to feed it. A credential covering how data is protected is not a statement about what it is used for.

No published position is published on liability for AI output, warranty, service levels or remedy. The exposure is concrete here. A missed injury, a misread treatment date or an omitted provider in a generated chronology flows straight into a demand letter and can understate a claim, and an understated demand that settles is a loss the claimant never learns about. A generated valuation that anchors a firm low has the same effect.

No published vendor position addresses any of it, so the risk sits with the firm and ultimately the injured claimant. Enterprise agreements govern this and are not public.

One substantive integration is named, and the connections this buyer needs most are not. A Thomson Reuters and Westlaw integration supports legal citation inside generated demand packages, a real integration for a plaintiff drafting tool that gives the citation layer an established source. No case management system integration is published, and for a personal injury firm that is the connection that matters, since the practice runs on a case management platform holding intake, treatment tracking and deadlines.

No API or export documentation is published either, and nothing describes how records get in or how a finished demand returns to the matter file. Independent comparisons in this market treat case management integration as a primary criterion, which makes its absence notable.

Nothing is published. No hosting provider is named, no region or data residency commitment is published, and no single tenant or dedicated instance option is described. For a platform holding protected health information for injured claimants, where that data sits and how it is separated is a question a firm's compliance review would ask directly. The HIPAA attestation shows that safeguards were assessed without saying where the data sits. The Trust Center's request access route was not used and may hold residency detail.

Scope, currency and a self serve route are all published. A Trust Center at trust.evenuplaw.com describes security, privacy and compliance practices and offers a request access route to documentation rather than a sales gate. The attestation is named with its scope: a SOC 2 Type 2 examination covering security, availability, confidentiality and privacy, four of the five Trust Services Criteria. Currency is dated, with recertification announced in April 2026.

Alongside it sits an independently conducted HIPAA compliance assessment and attestation, the credential this product needs given that it processes protected health information. The vendor correctly explains that HIPAA has no formal certification and that what exists is a third party attestation. The auditing firm is not named for either the SOC 2 or the HIPAA assessment.

Nothing located. Piai is named and claimed as proprietary, trained on a personal injury specific dataset, and that is a statement about ownership rather than about supply chain. No foundation model provider is named, nothing states whether third party models sit underneath Piai or process any part of the pipeline, no subprocessor list is published, and the Thomson Reuters and Westlaw integration establishes at least one external data relationship without any accompanying disclosure of what flows to it.

For a product handling protected health information, the identity of every party in the processing chain is a question a firm's HIPAA business associate review asks directly and it cannot be answered from public material.

No pricing is published at any level. Independent review material describes the model as charged per case rather than per seat, so cost scales with caseload rather than headcount, and notes that the platform pays off only at sufficient injury volume. None of that comes from the vendor: there is no price, range, per case figure or tier structure, and no indication of what a demand package costs. Every route is a sales conversation and an annual contract.

The absence weighs more for contingency fee firms, which carry case costs themselves, because a per case charge comes directly out of a claimant's eventual recovery.

Depth in one practice area, stated plainly, with the boundary acknowledged. The vendor says it builds for plaintiff personal injury and nothing else, and independent review confirms it is not a general legal assistant. Within that scope coverage is deep. Inputs include police reports, medical records, billing statements, photographs and intake notes, and outputs include demand letters, chronologies, case valuations, negotiation preparation and caseload analytics, with a settlement repository supporting comparables by jurisdiction.

Specializing in one practice is a design decision rather than a coverage failure. What is not described is the data behind the main differentiator. Nothing says how many verdicts or settlements the repository holds, which jurisdictions it covers, its date range, how often it updates, or whether it is deep enough in a given venue for a comparable to carry weight, which an attorney relying on that citation in negotiation needs to know.