Contract analysis

I. Executive Summary The purpose of this memorandum is to evaluate the adequacy of the service-level commitments proposed by Meridian Credit intelligence, Inc. ("Meridian" or "MCI") in its counter-draft of the Service Level Agreement ("SLA") schedule to the Master Data License Agreement ("MDLA") currently under negotiation between Quorum Insurance Holdings Corp. ("Quorum" or "QIH") and Meridian. This memorandum is in

1. Uptime Commitments. Meridian's proposed 99.5% monthly uptime commitment falls materially below industry benchmarks for enterprise credit-data providers serving insurance and financial-services clients. The proposed blended measurement methodology further obscures the performance picture for individual data products and delivery channels.

2. Latency Commitments. Meridian's proposed REST API latency commitments are insufficiently defined and substantially below the thresholds required to support Quorum's real-time automated underwriting and claims-fraud detection operations. The omission of P99 latency commitments and API throughput guarantees creates unacceptable tail-latency and capacity risks.

3. Service Credit Remedies. The proposed service credit structure — a flat 2% credit capped at 5% of the monthly fee — fails to incentivize Meridian's compliance with its service-level obligations and provides Quorum with commercially negligible compensation in the event of significant outages or performance degradation.

4. Chronic Failure Termination. Meridian's counter-draft entirely deletes the chronic failure termination provision from Quorum's initial draft, effectively locking Quorum into a five-year, $60 million commitment with no meaningful exit right in the event of persistent service underperformance. We recommend that Quorum insist on strengthened provisions across all four areas before accepting the SLA schedule. The reco

II. Scope and Methodology A. Documents Reviewed In preparing this memorandum, we reviewed the following materials:

1. Quorum's Proposed SLA Schedule (C&H draft, January 2023), which sets forth Quorum's initial service-level requirements for uptime, latency, batch delivery windows, service credits, escalation procedures, and termination triggers.

2. Meridian's SLA Counter-Draft (KP&A markup, received approximately late February to early March 2023), which constitutes Meridian's response to Quorum's proposed SLA schedule and is the primary subject of this memorandum's analysis.

3. Relevant Provisions of the MDLA Draft (KP&A initial draft dated November 4, 2022, and C&H response draft), with particular attention to the data delivery and remedies provisions (Article 4, Data Delivery and Access), the limitation of liability clause (Section 11.2), the termination provisions (Article 12), the force majeure clause (Section 14.6), and the governing law and dispute resolution provisions (Article 15

4. Technical Schedule A — Data Delivery Specifications (C&H draft, February 2023), prepared by Omar Siddiqui with substantive input from Priya Nair, Director, Data Engineering, Quorum. Technical Schedule A sets forth the detailed specifications for data format, delivery cadence, API architecture, expected query volumes, error handling, and data-quality acceptance criteria.

5. Pinnacle Ridge Advisory LLC Benchmarking Materials, consisting of a pricing and terms benchmark study delivered February 14, 2023, prepared by Franklin Osei, Managing Director, Pinnacle Ridge Advisory LLC. The study benchmarks Meridian's proposed commercial terms — including SLA provisions — against comparable enterprise credit-data licensing arrangements in the insurance and financial-services sectors. B. Benchma

III. Analysis of Meridian's Proposed Uptime Commitments A. Quorum's Proposed Standard Quorum's January 2023 SLA draft proposed a 99.9% monthly uptime commitment for all data-delivery channels, encompassing both SFTP batch delivery and REST API access. Under this standard, 99.9% uptime translates to no more than approximately 43.8 minutes of unplanned downtime per calendar month (calculated as 0.1% of 43,800 minutes i

1. Reject the 99.5% standard. Quorum should insist on the 99.9% monthly uptime commitment as proposed in Quorum's January 2023 SLA draft. This threshold is consistent with industry benchmarks, with Quorum's existing data-vendor arrangements, and with the operational requirements of Quorum's real-time automated underwriting and claims-fraud detection systems. The 99.9% standard is not aspirational; it reflects the min

2. Require per-service, per-delivery-method measurement. Uptime must be calculated separately for each of the three data products (MCI Consumer Credit File, MCI CommercialView, MCI AltSignal) and separately for each delivery method (SFTP and REST API). This ensures that the uptime metric accurately reflects the performance of each individual service and prevents the dilution effect inherent in blended measurement.

3. Narrow the Downtime exclusions. Specifically: (a) Scheduled maintenance. Reduce the scheduled maintenance window from 8 hours to 4 hours per month, require 72 hours' advance written notice (increased from Meridian's proposed 48 hours), and add a requirement that all scheduled maintenance be conducted during off-peak hours, defined as Saturday 12:00 AM to 6:00 AM Eastern Time. (b) Total Service Outage threshold. Ti

4. Off-peak maintenance requirement. As noted above, require that all scheduled maintenance be conducted during the designated off-peak window (Saturday 12:00 AM to 6:00 AM ET) absent Quorum's prior written consent. Emergency maintenance outside the scheduled window should be permitted only in the event of a bona fide security vulnerability or imminent system failure, with immediate telephonic and email notice to Quo

IV. Analysis of Meridian's Proposed Latency Commitments A. Quorum's Proposed Standards Quorum's January 2023 SLA draft established specific latency commitments for both the REST API and SFTP batch delivery channels, calibrated to Quorum's operational requirements: REST API (MCI Consumer Credit File — Real-Time Access): • P95 response time: ≤200 milliseconds per query (i.e., 95% of all API queries in any calendar mont

1. Maintain the 200ms P95 / 500ms P99 REST API latency requirement. The 200ms P95 threshold is not discretionary; it reflects the operational constraints of Quorum's underwriting infrastructure as validated by the Data Engineering team. The 500ms P99 commitment is essential to managing tail-latency risk and preventing cascading failures in Quorum's downstream systems. If Meridian contends that it cannot meet these th

2. Require hard delivery deadlines for all SFTP batch feeds. Replace the "commercially reasonable efforts" language with firm, measurable delivery commitments: MCI Consumer Credit File by 6:00 AM ET daily, MCI AltSignal by 7:00 AM ET daily, and MCI CommercialView by 6:00 AM ET on the designated weekly delivery day. Define service credits for late delivery (see Section V below) to create a meaningful financial incenti

3. Add API throughput guarantees. Specify minimum sustained query rates (queries per second) and define burst capacity, consistent with the expected query volumes set forth in Technical Schedule A. The specific throughput thresholds should be validated with Ms. Nair's team but should, at a minimum, accommodate Quorum's projected peak query volumes with a reasonable margin of headroom (e.g., 125% of projected peak vol

4. Specify API error-rate thresholds. Define a maximum permissible error rate — we recommend that the error rate not exceed 0.1% of total API calls per calendar month — with defined consequences (service credits and, at higher thresholds, potential Downtime reclassification) for exceeding the threshold. Errors should be defined to include HTTP 5xx server errors, timeout errors, and any response that does not return a

V. Analysis of Service Credit Remedies A. Quorum's Proposed Service Credit Structure Quorum's January 2023 SLA draft proposed a tiered service credit structure calibrated to the severity and duration of SLA failures. The proposed credit tiers are as follows: Uptime-Based Credits (per data product, per delivery method, per month): Batch Delivery Credits: • Batch delivery delay exceeding 2 hours past the designated del

1. Insist on the tiered service credit structure proposed in Quorum's January 2023 draft. The tiered approach ensures that credits escalate proportionally with the severity of the performance failure, creating a graduated financial incentive for Meridian to maintain high service levels.

2. Increase the monthly service credit cap to at least 20% of the applicable monthly fee. At the Year 1 monthly rate, a 20% cap would yield a maximum monthly credit of $180,000; at the Years 2–5 rate, $205,000. While still modest relative to the potential downstream harm from a catastrophic outage, a 20% cap provides a materially more meaningful incentive than Meridian's proposed 5%. We note that several of the compa

3. Extend service credits to cover latency and batch-delivery failures as proposed in Quorum's draft. Every measurable SLA commitment must be backed by a defined financial consequence; otherwise, the commitment is meaningless as a contractual protection.

4. Require automatic application of service credits without any claim-submission requirement. Credits should be calculated based on the agreed monitoring data and applied automatically to the next invoice following the affected month. This is consistent with industry practice and eliminates the administrative burden and forfeiture risk associated with claim-based crediting.

5. Clarify that service credits are not Quorum's sole and exclusive remedy. The SLA should expressly preserve Quorum's right to pursue actual damages for SLA failures that cause material harm to Quorum's business, subject to the negotiated limitation-of-liability provisions in the MDLA (with appropriate carve-outs as discussed in Section VIII.A below). The SLA should also expressly preserve Quorum's termination right

VI. Termination Triggers for Chronic SLA Failures A. Quorum's Proposed Provisions Quorum's January 2023 SLA draft included a "chronic failure" termination right designed to provide Quorum with a meaningful exit mechanism in the event that Meridian's data services prove persistently unreliable. The proposed provision operates as follows: • If monthly uptime for any individual data product or delivery method falls belo

1. Reinstate the chronic failure termination provision from Quorum's January 2023 draft. The proposed uptime-based thresholds — below 99.0% in any three months within a rolling twelve-month period, or below 98.0% in any single month — are reasonable, represent a substantial buffer below the 99.9% target, and are consistent with market practice.

2. Add a termination trigger for persistent API latency failures. We propose that Quorum may exercise a termination right if P95 REST API latency exceeds 500 milliseconds for more than 5 business days in any calendar month, and such latency failures occur in three or more months within a rolling twelve-month period. This threshold provides a meaningful check on chronic latency degradation while allowing for isolated

3. Add a termination trigger for batch delivery failures. We propose that failure to deliver any batch feed within 8 hours of the designated delivery time on more than 10 occasions in a rolling twelve-month period should trigger a termination right. This threshold accommodates occasional delays while addressing a pattern of persistent late delivery.

4. Define the consequences of SLA-based termination. Upon Quorum's exercise of an SLA-based termination right: (i) No early termination fee. Quorum should not be required to pay any early termination fee, breakage fee, or similar charge, as the termination is a direct consequence of Meridian's failure to meet its service-level commitments. (ii) Pro rata refund of prepaid fees. All prepaid but unused license fees shou

5. Expressly define SLA failures as material breach. The MDLA should include a provision expressly stating that SLA failures meeting the defined chronic failure termination thresholds constitute "material breach" for purposes of all MDLA provisions, including the termination provisions, limitation of liability provisions, and indemnification provisions. This eliminates the ambiguity inherent in the general material b

6. Coordinate with post-termination data treatment provisions. An SLA-based termination would trigger the MDLA's post-termination obligations, including the 90-day return/destruction period for raw Meridian data. The transition assistance period should be aligned with this 90-day window to ensure continuity. We note that the treatment of Derived Data post-termination — including Quorum's QuorumScore™ and other derive

VII. Additional SLA Provisions Requiring Attention In addition to the four principal areas analyzed above, several other provisions in Meridian's SLA counter-draft require attention and revision. These issues, while individually less significant than the uptime, latency, service credit, and termination provisions, collectively have a material impact on the enforceability and practical effectiveness of the SLA. A. Mea

VIII. Interaction with Other MDLA Provisions The SLA schedule does not exist in isolation; it operates within the broader contractual framework of the MDLA. Several provisions of the MDLA interact with the SLA in ways that require careful coordination to ensure that Quorum's rights and remedies are consistent and enforceable. A. Limitation of Liability Meridian's form MDLA (KP&A draft dated November 4, 2022) includes