Contract analysis

I. Executive Summary This memorandum provides a comprehensive analysis of the material provisions and critical issues identified in Meridian Credit intelligence, Inc.'s ("Meridian") form Master Data License Agreement (the "MDLA"), drafted by Meridian's outside counsel, Kessler Pruitt & Ashe LLP, and delivered to Calderwood & Harkness LLP ("C&H") on November 4, 2022. The purpose of this memorandum is to identify and a

2. Absence of Most Favored Nation Pricing Protection. The Meridian form MDLA contains no most favored nation ("MFN") pricing clause, despite Quorum's explicit proposal of a broad MFN in its counter-term sheet. Given the scale of the financial commitment ($60 million over five years) and the competitive dynamics of the insurance data-licensing market, the absence of any pricing protection mechanism is a critical gap.

3. Meridian's License-Back and Revenue-Sharing Mechanisms on Derived Data Commercialization. Even apart from the IP ownership question, Meridian's demand for a perpetual, sublicensable license-back on all Derived Data, combined with the 15% revenue share and sole-discretion transformation standard, creates a comprehensive economic claim by Meridian on Quorum's downstream analytics business that is commercially unacce

II. Background and Context A. The Transaction Quorum Insurance Holdings Corp. is a Delaware corporation listed on the Nasdaq Stock Market (ticker: QIHC), with its principal executive offices located at 1200 Atlantic Street, Suite 3400, Stamford, Connecticut 06901. Quorum is a diversified insurance holding company operating through subsidiaries in the property and casualty, life, and specialty insurance segments, with

1. MCI Consumer Credit File™: This product encompasses approximately 310 million consumer credit records, including traditional credit bureau data (trade lines, payment histories, public records, credit inquiries, and credit scores). Delivery is available via daily batch processing through Secure File Transfer Protocol ("SFTP") and in real time through a REST API interface. This is the largest and most commercially s

2. MCI CommercialView™: This product encompasses approximately 42 million business entity records, including commercial credit profiles, payment behavior data, financial statement data, and business demographic information. Delivery is available via weekly batch processing through SFTP. Quorum intends to use this product primarily in connection with its commercial lines underwriting and its specialty insurance operat

3. MCI AltSignal™: This product encompasses approximately 85 million consumer alternative-data records, including utility payment histories, telecommunications payment data, and rental payment information. This alternative data is intended to supplement traditional credit file data and is particularly valuable for underwriting applicants with thin credit files. Delivery is available via daily batch processing through

1. Full Ownership of Derived Data. Quorum seeks to own all intellectual property rights in Derived Data — that is, blended risk scores, propensity models, enriched datasets, and other analytics outputs — created by Quorum or on its behalf using Meridian data as one of multiple inputs. Quorum views this as a foundational requirement, without which the transaction does not achieve its strategic purpose.

2. Protection of QuorumScore™. Quorum has developed QuorumScore™, a proprietary predictive underwriting model that incorporates machine-learning algorithms trained on multiple data sources, including (but not limited to) Meridian consumer credit data. A United States Patent and Trademark Office application for QuorumScore™ is pending (Serial No. 97/482,116). Quorum projects that B2B licensing of QuorumScore™ and rela

3. Most Favored Nation Pricing Protection. Given the magnitude of the financial commitment ($60 million over five years), Quorum seeks assurance that it will not pay more, on a per-record or aggregate basis, than competing insurance-industry licensees of comparable scale. Quorum's counter-term sheet proposed a broad MFN covering all U.S.-domiciled insurance carriers, managing general agents, and insurtech firms with

4. Court Jurisdiction for Dispute Resolution. Quorum prefers to resolve disputes in court rather than through binding arbitration, for reasons discussed in detail in Section XI below. These objectives have guided our analysis throughout this memorandum and will inform the positions taken in Quorum's redline.

III. Deal Economics — Pricing and Payment Terms A. License Fee Structure (Article III of MDLA)

Article III of the Meridian form MDLA sets forth the license fee structure for the five-year initial term. The total aggregate consideration recited in the MDLA is $60,000,000, allocated as follows: • Year 1: $10,800,000 annual license fee, payable in equal quarterly installments of $2,700,000 (equivalent to $900,000 per month). The reduced Year 1 fee reflects the six-month implementation and ramp period during which

Section 3.6 of the Meridian form MDLA provides that any amounts not paid when due shall accrue interest at a rate of 1.5% per month (equivalent to 18% per annum), compounding monthly. This interest begins to accrue on the day following the applicable due date and continues until full payment is received. This rate is aggressive and exceeds the prevailing market standard for enterprise data-licensing and technology tr

Section 3.4 of the MDLA establishes a tiered pricing structure based on monthly data-consumption volume: • Base Tier: Up to 500 million records per month (consumer, commercial, and alternative-data records combined). The base tier license fees are included in the annual license fee amounts set forth in Section 3.1. • Overage Rate: For each record consumed in excess of the 500 million base tier threshold in any given

1. Confidentiality obligations. Meridian asserts that disclosing pricing terms offered to other licensees would breach confidentiality provisions in those agreements.

2. Bespoke data packages. Meridian contends that each licensee's data package is customized in terms of product mix, delivery frequency, volume, and integration support, making apples-to-apples pricing comparisons impractical.

3. IPO-related margin concerns. Breckenridge Capital and Whitmore Zanthor have expressed concern that an MFN obligation could compress Meridian's margins on future deals, adversely affecting Meridian's financial profile ahead of the planned 2025–2026 IPO.

4. Antitrust sensitivities. Meridian has raised the possibility that MFN provisions in credit-data markets could attract antitrust scrutiny, particularly given the concentrated nature of the credit-data industry. We have considered each of these arguments and believe they are either manageable or unpersuasive. The confidentiality concern can be addressed through a pricing audit mechanism (discussed below). The bespok

IV. Intellectual Property Ownership — Derived Data (Article VII) A. Overview of Meridian's Proposed Framework

Article VII of the Meridian form MDLA is, in our assessment, the most commercially significant and problematic provision in the entire agreement. It governs the creation, ownership, and exploitation of "Derived Data," a term defined in Section 7.1 and discussed in detail below. The economic and strategic implications of Article VII pervade the entire commercial relationship and directly affect Quorum's ability to rea

Section 7.3 of the Meridian form MDLA provides that Quorum "hereby grants to Meridian a perpetual, royalty-free, fully paid-up, irrevocable, worldwide, sublicensable license to access, use, reproduce, distribute, display, perform, create derivative works of, and otherwise exploit all Derived Data for Meridian's internal business purposes and for commercial purposes, including without limitation the right to incorpora

Section 7.4 of the MDLA provides that Quorum "shall not sell, sublicense, distribute, or otherwise make available any Derived Data to any third party" unless the Derived Data has been "sufficiently transformed" such that "no Licensed Data can be identified, extracted, reverse-engineered, or otherwise derived from such Derived Data." While a restriction on redistribution of Meridian's raw data is reasonable and expect

1. No objective standard. The term "sufficiently transformed" is not defined with any precision. There is no quantitative threshold (e.g., minimum k-anonymity level, minimum differential privacy epsilon, or minimum number of independent data sources blended), no reference to industry-accepted de-identification standards (e.g., HIPAA Safe Harbor, NIST guidelines), and no technical criteria against which Meridian's det

2. Meridian sole discretion. By vesting sole discretion in Meridian, the provision effectively gives Meridian an absolute veto over Quorum's ability to commercialize any Derived Data. This veto is unconstrained: Meridian need not act reasonably, in good faith, or in accordance with any articulated standard. Meridian's commercial incentives are directly adverse to Quorum's — Meridian has every reason to deny approval,

3. No time limit on restriction. The restriction applies for the duration of the MDLA and, by implication under the survival provisions, in perpetuity after termination.

4. Direct impact on QuorumScore™. As noted above, the broad definition of Derived Data would encompass QuorumScore™ outputs. Quorum's planned B2B licensing of QuorumScore™ would therefore require Meridian's advance approval under Section 7.4 — approval that Meridian has no obligation to grant and every incentive to withhold. This provision, if accepted as drafted, would directly impede Quorum's planned B2B licensing

1. Narrow the definition of "Derived Data." The definition should be revised to exclude (a) machine-learning model weights and parameters that do not contain or reproduce identifiable Licensed Data; (b) inference outputs generated by models using non-Meridian inputs; and (c) any data, score, or output that does not contain, reproduce, or enable the identification or extraction of Licensed Data in its original or a su

2. Vest all IP ownership of Derived Data in Quorum. The MDLA should provide an express, unambiguous assignment of all intellectual property rights in Derived Data to Quorum, with Meridian disclaiming any right, title, or interest therein.

3. Eliminate the license-back provision entirely. The perpetual, royalty-free, sublicensable license-back in Section 7.3 should be deleted in its entirety. Quorum may consider, as a concession, granting Meridian a limited right to receive aggregated, anonymized, non-reverse-engineerable usage statistics for product-improvement purposes only, but any such grant should be narrowly scoped and non-sublicensable.

4. Eliminate the 15% revenue share. The revenue-sharing provision in Section 7.5 should be deleted in its entirety. Meridian's compensation for the Licensed Data is the $60 million license fee; it should not receive additional compensation for Quorum's independent creation of value using that data.

5. Permit Quorum to commercialize Derived Data without Meridian's consent. Section 7.4's sole-discretion approval mechanism should be replaced with an objective de-identification and non-reverse-engineering standard. We recommend a standard based on accepted data-anonymization methodologies (e.g., requiring that Derived Data made available to third parties be processed such that Licensed Data cannot be identified or

6. Include a specific carve-out protecting QuorumScore™. Given the strategic importance of QuorumScore™, the MDLA should include an express provision confirming that QuorumScore™ and all outputs thereof are the exclusive property of Quorum, are not Derived Data, and are not subject to any of Meridian's rights under Article VII.

V. Grant of License and Scope (Article II) A. License Grant

Article II of the Meridian form MDLA grants Quorum "a non-exclusive, non-transferable, non-sublicensable license to access and use the Licensed Data solely for Licensee's internal business purposes during the Term." While the non-exclusive nature of the license is appropriate and consistent with Quorum's expectations, the restrictions embedded in the license grant raise two significant issues. Internal business purpo

Section 2.2 of the MDLA restricts Quorum's use of the Licensed Data to the following three categories: (a) underwriting, (b) policy administration, and (c) claims management. While these three categories cover a portion of Quorum's intended use cases, they do not encompass the full range of purposes for which Quorum intends to use the Licensed Data. Specifically, the following use cases are omitted from the permitted

VI. Representations and Warranties (Article IV) A. Meridian's Representations

Article IV of the Meridian form MDLA contains several representations made by Meridian, which we address in turn. Right to license. Meridian represents that it has the right, power, and authority to grant the license set forth in the MDLA and to make the Licensed Data available to Quorum in accordance with the terms of the agreement. This representation is fundamental and appropriate. Compliance with applicable law.

VII. Data Security Obligations (Article V) This section is addressed in substantially greater detail in a forthcoming memorandum from David Cartwright and Lisa Johannsen, who are leading the data privacy and security workstream for this engagement. The observations provided below are summary-level only and are intended to flag the key issues for the attention of the commercial negotiating team. Quorum's full data-sec

VIII. Indemnification (Article IX) A. Meridian's Indemnification Obligations

Section 9.1 of the Meridian form MDLA provides that Meridian shall indemnify, defend, and hold harmless Quorum and its officers, directors, employees, and agents from and against any third-party claims, damages, losses, and expenses (including reasonable attorneys' fees) arising from claims that Quorum's use of the Licensed Data in accordance with the terms of the MDLA infringes or misappropriates any third-party int

1. Modification carve-out. Meridian excludes indemnification for any claims arising from Quorum's "modification, alteration, enhancement, or transformation" of Licensed Data. Given that virtually all of Quorum's intended uses involve processing, blending, and analyzing Licensed Data in combination with other data sources — all of which could be characterized as "modification" or "transformation" — this carve-out woul

2. Combination carve-out. Meridian excludes indemnification for any claims arising from the "combination of Licensed Data with data, software, systems, or materials not provided by Meridian." Since Quorum's core use case involves combining Meridian data with data from multiple other sources (internal policyholder data, third-party data feeds, public records, etc.), this carve-out would exclude indemnification for cla

3. Regulatory enforcement carve-out. Meridian excludes indemnification for any claims arising from "regulatory investigations, enforcement actions, or proceedings brought by any governmental authority." This carve-out is particularly problematic given the regulatory sensitivity of consumer credit data. If Meridian's data-collection practices are found to violate the FCRA, GLBA, or state consumer-protection laws, and