What a January 2026 lawsuit revealed about Liberty Mutual's claims-tech stack.

TL;DR

• Ryan v. Liberty Mutual, filed in the Western District of Virginia in January 2026, identifies Snapsheet, CCC Intelligent Solutions, and Claim Assist as the vendor stack Liberty Mutual uses for auto virtual appraisals.
• The disclosure isn't strategic — it's an artifact of how product-liability and bad-faith claims work. Plaintiffs' counsel names every entity in the workflow because liability theories often turn on which entity made which decision.
• For Phidea's carrier × vendor matrix, this is one of the cleanest sources of operational vendor relationships available. Court filings name what carriers and vendors won't.
• The technique is reusable. Federal court records (PACER, RECAP) for bad-faith, product-liability, UDAP, and FCRA claims against carriers routinely surface vendor names that no other source documents.
• The implication for carriers: your tech stack is structurally less private than your procurement team thinks. Litigation discovery, regulatory examinations, and certain DOI complaints all force partial disclosure.

What the lawsuit names

The case is Ryan v. Liberty Mutual, filed January 2026 in the U.S. District Court for the Western District of Virginia. The complaint relates to virtual-appraisal practices in auto claims. Material to Phidea's purposes, the complaint names:

Snapsheet. Identified as the vendor handling Liberty Mutual's virtual appraisals — the workflow in which a claimant uploads photos of vehicle damage and a remote estimator scopes the loss without an in-person inspection. Snapsheet's claims platform is the underlying tech.

CCC Intelligent Solutions. Identified as a separate vendor in the same workflow, with its own role in damage estimation and parts pricing. CCC is the dominant US auto-claims estimating platform; its named involvement here is operational evidence.

Claim Assist. Identified as a third-party adjusting and inspection partner in the workflow.

The combination — Snapsheet + CCC + Claim Assist — sketches an operational architecture: claimant-facing intake (Snapsheet), estimating engine (CCC), human-in-the-loop appraisal (Claim Assist). Each of these relationships would likely appear individually in vendor case studies if disclosed, but the combination — and Liberty Mutual specifically named — would not.

Why court filings are this useful

Three structural reasons:

1. Plaintiffs' counsel names everyone. Modern bad-faith and product-liability theories often turn on the chain of decision-making. If a claim was denied, plaintiffs need to identify which entity (carrier, claims platform, estimating engine, third-party adjuster, AI model) made the decision being challenged. Naming everyone in the stack is the default starting position.

2. Defendants confirm relationships in answers and motions. Even when plaintiffs guess wrong, defendants' responses confirm or deny the relationship. Either way, the public docket ends up with operational vendor disclosures.

3. The discovery layer adds more detail than the complaint. Discovery production logs, deposition exhibits, and summary-judgment briefs surface internal communications and contracts. PACER access is paid; RECAP and Court Listener mirror much of it for free.

For carrier-vendor research, this is materially different from what vendors and carriers themselves disclose:

How Phidea is using this

We've added court-filing review as an explicit research channel for the carrier × vendor matrix. Specifically:

• Federal-court PACER searches for top US carriers as defendants in bad-faith, UDAP, and FCRA actions.
• State DOI consent orders that name third-party processors involved in alleged misconduct.
• NAIC market-conduct examination summaries when made public.
• Class-action complaint mining — class-action plaintiffs' bars in insurance routinely name vendor entities as part of liability theories.

The Liberty Mutual / Snapsheet relationship surfaced through this approach. It would not have surfaced through vendor-side research.

What it means for carriers

If you're at a US carrier, the operational implication is uncomfortable:

Your tech stack is structurally less private than you think. Anything load-bearing in your claims, underwriting, fraud-detection, or pricing workflow can be named in litigation. Once named, it's public on PACER, in regulatory examinations, in DOI complaint summaries.

This isn't a reason to disclose proactively — there are real competitive reasons not to. But it is a reason to have an explicit posture on:

• Which vendor relationships your communications, legal, and PR teams know about and have rehearsed responses for.
• Which AI-model decisions in your claims workflow you can defend in deposition (the model's design rationale, validation evidence, override rules).
• Which third-party adjusting and inspection partners are in scope for your bad-faith preparedness review.

The implicit model in most carrier procurement is "this contract is private until we say otherwise." Litigation pressure makes that an aspirational position, not a practical one.

What it means for vendors

For B2B insurance-tech vendors, the lesson is simpler: carriers' worst case for your involvement in their workflow is being named in a complaint. That's a sales-objection you can address explicitly:

• Documented model design and validation procedures that survive discovery.
• Clear delineation of who-decides-what between your platform and the carrier's adjusters.
• Contractual liability allocation that doesn't surprise the carrier in litigation.

Vendors that treat litigation preparedness as a sales asset will increasingly have it as one. The carriers that have been named in bad-faith claims involving virtual-appraisal automation (which is several, by 2026) are paying attention.

The longer pattern

This is part of a broader truth Phidea has been documenting: carrier tech stacks are systematically opaque in normal commercial channels but systematically forced open in adversarial channels (litigation, regulation, journalism). The Travelers × Nearmap relationship surfaced through an NBC Connecticut investigation of claim-denial methodology. The State Farm × Cape Analytics governance posture surfaced through corporate-venture disclosures. The Liberty Mutual stack surfaced through a federal complaint.

For research purposes, the lesson is straightforward: you can't only mine vendor websites. You have to mine where the relationships are forced into the open.