P

ProPlaintiff

The product is AI native by construction and says so. The vendor states it is built from the ground up as an AI native platform rather than layering AI onto outdated software, and the product bears that out. Every named feature is generative or analytical rather than a form with a model attached: demand letters, medical chronologies, document generation, summaries, review, media analysis, case analysis and a conversational assistant.

The agentic framing applies to case management itself rather than to one document type, so the model layer is the operating logic of the system rather than one capability within it. Remove the models and what remains is a file store with a calendar. The vendor also calls the AI a force multiplier and digital assistant handling repetitive, data heavy work, which is a centrality claim and a disclaimer of substitution at once.

Grounding is claimed clearly and nothing behind it is published. The vendor says demand letters cite specific medical records, bills and reports automatically, and that smart citations pull from the firm's uploaded files, which describes citation to the case file rather than invented sources. Its own practitioner guidance says good platforms log what data was used, what was generated and who approved it, and that this is the firm's defensibility.

Nothing measures or specifies its own implementation. There is no accuracy figure, extraction error rate or evaluation, and no description of what smart citations point to or how a user checks one. Nothing says how the product behaves when records are incomplete or provider names are inconsistent, a failure mode the vendor's own content says is where platforms fall apart. The citation mechanism is asserted rather than shown: no page level links, hyperlinked navigation or table of authorities is described.

The oversight position is stated as a rule rather than as reassurance. The vendor's guidance says attorney oversight is non negotiable, that AI drafts and attorneys approve, and that no compliant workflow skips that step. It says the firm owns the output and that a good platform logs what data was used, what was generated and who approved it. The product ships permission management and system activity logs, the mechanisms an approval record would run on.

The vendor also disclaims substitution, describing the AI as a force multiplier that frees paralegals and attorneys for client communication, negotiation and trial preparation. The rule is published as advice to the profession, not as a specification of this product. Nothing says ProPlaintiff enforces an approval step, whether any output can be sent without one, what the activity log captures, or whether the platform produces the approval record the vendor says firms need.

Nothing is published. No customer or firm is named anywhere in vendor material, and there is no case study, usage figure, time saving or outcome claim, funding announcement, independent analyst placement or award. A G2 listing exists, carrying a vendor supplied product description rather than verified customer outcomes. The vendor publishes a substantial practitioner content library, and none of it contains a customer result.

Checked the home page, the demand letters page, the case management page, the blog library, the G2 listing and the site navigation. This is a documented absence on those pages, not a judgment about adoption, which public material cannot show.

Basic protections are stated with one useful specific, and there is no privilege position. Published: HIPAA compliance with industry standard safeguards, encryption, storage in the United States, and access limited to authorized users at the firm, supported in the product by permission management, system activity logs and secure case sharing. Naming United States storage is a concrete commitment. Against that, no SOC 2 or other independent attestation is published.

No business associate agreement is offered, although the vendor's own guidance tells readers to choose HIPAA compliant platforms under a BAA. Attorney client privilege and work product are not addressed. The compliance posture is self declared, supported by product features.

The vendor publishes a real professional responsibility position, in its practitioner guidance. It says ABA Model Rules on competence and supervision apply to AI assisted drafting, that the firm owns the output, and that attorney oversight is non negotiable and no compliant workflow skips the approval step. It says firms must verify how damages language, statutory references and negligence framing vary by state. It also disclaims substitution, saying the AI does not replace human judgment and calling it a force multiplier.

Naming the rules that apply, who carries the obligation and that jurisdictional variation is the user's responsibility goes beyond a disclaimer. It is published as market education in a blog library, not as a product commitment or a term. Nothing binds the vendor to it, it is not surfaced in the product or any agreement located, and no bar authority beyond the ABA Model Rules is engaged.

Nothing is published on how the models are governed, evaluated or monitored. There is no AI policy, model card, bias or fairness testing, evaluation method, accuracy monitoring, drift statement, named governance body or ISO 42001. The vendor's content says accuracy of AI medical record analysis has improved for platforms trained on clinical and legal documents, which is a claim about the field rather than a disclosure about this system.

The risk is specific here. By the vendor's own description, the platform generates demand letters that anchor damages, including a justified pain and suffering valuation, and any systematic tendency in how that valuation is framed falls on claimants.

Protection is stated with one location specific, and use is not addressed. Published: data is encrypted, stored in the United States, accessible only to authorized users at the firm, with HIPAA compliance and industry standard safeguards. United States storage is a real commitment and the concrete element here. Not located: any statement on whether uploaded medical records, case files, generated chronologies or demand drafts are used to train or improve models, any retention period, any deletion right at matter close, and anything on what happens to saved templates and preferred language, which by the vendor's own description build up a firm's drafting patterns over time.

No exercisable control such as manual deletion and no independent attestation covering the handling claims is published.

No published position is published. Nothing covers liability for AI output, warranties, service levels or remedies. The vendor's own guidance says the firm owns the output. That allocates responsibility to the customer and is the closest thing to a liability position in public material, but it is advice to the profession, not a contract term. Nothing addresses what happens when a generated demand misstates a treatment, a citation points to the wrong record, or the AI calendar produces a wrong deadline. On a case management platform, that last one is a malpractice exposure, not a drafting one.

No integration is available, and the vendor says so. Published material describes API integration as planned rather than delivered, and data migration is offered, which is a one time import rather than an integration. No case management, document management or records retrieval integration is named. The reason is structural: the product is itself the case management platform, competing with Filevine, Litify, Clio and CasePeer rather than connecting to them.

That position is coherent, and it leaves a firm with no ongoing route to move data between this system and anything else.

A real residency statement has nothing behind it, and a deployment option is named without detail. The vendor says data is stored securely in the United States, a jurisdictional commitment rather than a gesture at secure cloud hosting. Custom deployment is named as available for firm wide automation supporting hundreds of attorneys, which implies something beyond standard shared hosting but is not described. No hosting provider, region or availability zone is named, nothing says whether custom deployment means dedicated infrastructure, a private instance or configuration, and no data processing description is given. A country is the start of a residency answer, not the whole of it.

No independent attestation of any kind is published, and the vendor's own guidance shows it knows the standard. Located: a HIPAA compliance claim with industry standard safeguards, encryption, United States storage, permission management, system activity logs and a stated secure, HIPAA compliant workflow. Not located: any SOC 2 report, ISO certification, named auditor, examination scope or date, business associate agreement, trust center, security page or route to request documentation.

The artifact is absent, not gated. The vendor's own advice tells buyers to look for SOC 2 Type II, HIPAA compliance and GDPR adherence, and to protect privileged communications by choosing HIPAA compliant platforms under a BAA. On its own criteria, this vendor would not clear the bar it sets for others.

Nothing located. No foundation model provider, model family or version is named, no distinction is drawn between proprietary and third party models, and no subprocessor list was found. The vendor's own practitioner content discusses general assistants including named commercial models and advises that firms require approved confidentiality controls before those touch case files, which demonstrates awareness that the identity of the model matters and stops short of identifying its own.

For a platform processing protected health information under a claimed HIPAA posture, every processor touching that data is a question a firm's diligence asks and none can be answered from public material.

No pricing is published at any level: no price, range, tier structure or unit of charge. Nothing shows how custom deployment for hundreds of attorneys is priced against a solo practitioner, although both are named as buyers. No independent estimate is published either. In contingency work, case costs are advanced against a claimant's recovery, so undisclosed cost is ultimately cost to an injured person.

Functional breadth is wide, practice scope is narrow and plainly stated, and the coverage that matters for a case management platform is not described. Functions run from intake through litigation: case management, calendaring and deadlines, document generation and review, media analysis, chronologies, demands and analytics in one system. The practice is plaintiff personal injury, with solo attorneys, paralegals and firms of hundreds of attorneys named as buyers.

Nothing is described at the level a buyer checks. No jurisdictional coverage is stated, although the vendor's own guidance warns that damages language, statutory references and negligence framing vary by state. Nothing says which record types or formats the medical analysis handles, or whether areas such as mass tort or medical malpractice are covered. For the firm's system of record, coverage claims need boundaries, and none are given.