Insurer–Funder Collaboration on Litigated Claims

Two different relationships, often confused as one

When a litigation funder backs a plaintiff pursuing a claim against an insured defendant, the funder and the defendant's liability insurer are on opposite sides of the underlying dispute — their interests genuinely conflict, and no amount of shared data changes that. That is the relationship most commonly discussed, and it is not the collaboration opportunity this guide addresses. The collaboration opportunity sits in a different, less-discussed relationship: an insurer evaluating its own reserve adequacy and litigation strategy on a claim it is defending, and a funder evaluating whether to fund a related position, are both trying to answer a structurally identical question — what is the calibrated outcome distribution for this claim, in this jurisdiction, before this judge, given this fact pattern.

A second genuine alignment exists in bad-faith and coverage-dispute financing, where a funder backs a policyholder's claim against an insurer for wrongful denial — here the funder's and the insured's interests align against the insurer, and the underwriting question (how does this jurisdiction and this judge typically resolve bad-faith claims of this fact pattern) is the same type of question an insurer's own claims organization should be asking about its own denial decisions before they are made, not after they are challenged.

Where the underwriting problem is shared

Reserve-setting and case-selection underwriting are the same statistical exercise performed by two different institutions for two different purposes. An insurer setting reserves on a litigated claim needs the same calibrated outcome distribution, duration estimate, and jurisdiction-specific base rate that a funder evaluating whether to back an adverse claim needs — the direction of the position differs, the underlying intelligence does not. This is the practical basis for insurers and outcomes-intelligence providers working directly together on reserve modeling, independent of any specific funder relationship: an actuarial department applying jurisdiction-specific, judge-aware outcome models to open litigated claims is doing the same work a sophisticated funder does when it screens deal flow, just pointed at the insurer's own book instead of an acquisition opportunity.

Where a genuine three-party structure emerges — for example, structured settlement financing, or portfolio transactions where an insurer transfers a book of litigated claims and a funder or specialty capital provider prices the transfer — a shared, jurisdiction-specific outcomes framework gives both sides a common reference point for negotiation, which reduces the information asymmetry that otherwise makes these transactions slow and expensive to structure.

What does not change

None of this collapses the underlying adversarial relationship in a defended claim into a cooperative one. An insurer's reserve model and a funder's underwriting model can both be built on the same calibrated outcome infrastructure and still produce opposite trading decisions on the same claim, because the two institutions are evaluating the position from opposite sides of the payout. The value of a shared intelligence layer is that both sides are arguing from the same distribution rather than from incompatible, privately-held estimates — which changes the quality of the negotiation without changing whose interests are on which side of it.

Data-sharing arrangements need their own governance, not an informal handshake

Where an insurer and an outcomes-intelligence provider work together on reserve modeling, or where a funder and an insurer share a common analytical framework in a structured settlement or portfolio-transfer context, the data-sharing arrangement itself needs explicit governance: scope of what is shared, confirmation that shared claim-level data is not used to price adverse positions against the same insured whose data was shared, and a clear boundary between the underwriting methodology, which can reasonably be common, and any specific client's proprietary claim data, which should not cross between engagements without explicit consent.

This is not a hypothetical compliance concern. It is the specific issue that determines whether an insurer's own claims organization can safely engage a shared intelligence provider without creating conflicts with its existing reinsurance, litigation, or regulatory relationships, and it should be resolved in the engagement agreement before any data changes hands, not discovered afterward when a conflict actually surfaces.

A useful test for whether a proposed data-sharing arrangement is well governed: could the underwriting methodology be published or shared with a third party without disclosing anything about any specific client's book? If the answer is yes, the arrangement is sharing method, which is generally safe to share broadly. If extracting the methodology from the specific data would reveal something about a particular insured's claims history or a particular fund's portfolio, the arrangement has not actually separated the two, and the governance work described above has not been finished yet.

What to ask for from an intelligence provider

• 01The same jurisdiction- and judge-aware outcome model applied consistently to reserve-setting on the underwriting side and to case-selection on the funding side.
• 02Reserve-adequacy scoring for litigated claims that flags positions diverging materially from the calibrated distribution.
• 03A shared reference framework for structured settlement financing or claims-portfolio transactions between insurers and capital providers.
• 04Clear separation of engagements that would create a genuine conflict of interest from those that share only a common underwriting method.
• 05Written confirmation that the underwriting methodology can be described without disclosing anything about any specific client's claims history or portfolio — the practical test for whether data governance is actually in place.