Contract analysis

I. EXECUTIVE SUMMARY Calderwood & Harkness LLP ("C&H") has been retained by Lumos Analytics Inc. ("Lumos" or the "Company") to defend against a breach-of-contract claim asserted by Pinnacle Financial Holdings LLC ("Pinnacle") arising from alleged failures to meet service level commitments under the Master Services Agreement dated January 15, 2021 (Agreement No. MSA-PFH-2021-0015) (the "MSA"). This memorandum sets for

II. BACKGROUND AND FACTUAL SUMMARY A. The Parties Lumos Analytics Inc. Lumos is a Delaware corporation headquartered at 580 Howard Street, Suite 400, San Francisco, California 94105. Lumos operates an enterprise software-as-a-service ("SaaS") platform that provides real-time financial analytics, risk scoring, and regulatory compliance dashboards to banks, asset managers, insurance companies, and other financial insti

III. ANALYSIS OF PINNACLE'S CLAIMS We turn now to a detailed analysis of each component of Pinnacle's demand, assessing the merits, applicable defenses, and risk of liability for each category of claimed damages. A. Breach of Contract — SLA Credit Claims ($120,000) Pinnacle's core contractual claim rests on the allegation that Lumos breached its uptime commitment of 99.95% in four separate calendar months and that Pi

IV. LUMOS'S AFFIRMATIVE DEFENSES In addition to the contractual limitations on liability analyzed above, Lumos has several affirmative defenses that could further reduce its exposure. We address each in turn. A. Disputed Uptime Measurements — Sentinel Telemetry Data A critical factual dispute exists regarding the actual duration of the four service disruptions. Pinnacle's demand letter relies on uptime measurements t

V. RISK EXPOSURE ASSESSMENT Based on the foregoing analysis, we present the following assessment of Lumos's potential exposure across a range of scenarios. A. Best Case Scenario In the best case, all of Lumos's defenses are successful: • All consequential damages ($2,750,000) are barred by the mutual waiver in §11.3, eliminating the lost-revenue, remediation, and reputational harm claims in their entirety. • The INC-

VI. INSURANCE COVERAGE CONSIDERATIONS On May 18, 2023, Lumos tendered the Pinnacle claim to Meridian Specialty Insurance Company ("Meridian") under its Technology Errors & Omissions / Cyber Liability insurance policy, Policy No. MSI-TECH-2022-07841. The tender was submitted through Lumos's insurance broker, Velthorn Risk Advisors LLC (primary contact: Neil Frazier, Senior Vice President). The relevant policy paramete

1. Maintain regular communication with Meridian and Patricia Engel regarding the status and progress of the matter, consistent with the policy's cooperation and reporting obligations.

2. Keep Velthorn Risk Advisors LLC and Neil Frazier informed of material developments.

3. Comply with all consent-to-settle requirements under the policy before entering into any settlement agreement.

4. Track and document all defense costs and indemnity-related expenses against the SIR.

5. Evaluate whether a settlement structured as service credits (rather than cash payments) may fall outside the scope of covered "loss" under the policy, and if so, whether that affects Lumos's strategic calculus regarding the form of any resolution.

VII. STRATEGIC RECOMMENDATIONS Based on the foregoing analysis, we recommend the following strategic approach to the defense and resolution of this matter. A. Immediate Actions The following actions should be completed on an expedited basis:

1. Complete Evidence Preservation. We must finalize implementation of the litigation hold issued on May 15, 2023 and verify that all relevant data and documents are being preserved. This includes, without limitation: Sentinel Uptime Services telemetry data and monitoring logs for the period September 2022 through April 2023; Lumos's internal incident management records, including incident tickets, root cause analyses

2. Sentinel Data Certification. We should promptly obtain a formal written certification from Brenda Hale at Sentinel Uptime Services Inc. confirming: (a) the monitoring methodology used to measure Lumos platform availability; (b) the data integrity and chain-of-custody protocols governing the capture, storage, and retrieval of telemetry data; (c) the specific outage start and end timestamps recorded for each of the

3. Root Cause Documentation for INC-5033. We should work with Thomas Kwan and his site reliability engineering team to compile a comprehensive root cause analysis package for INC-5033, documenting the Brindoval Cloud Infrastructure LLC configuration change as the triggering cause of the March 2023 incident. This package should include: (a) a written root cause analysis narrative; (b) supporting network logs, configur

4. Historical Credit Request Review. We must confirm with Rachel Dominguez, Lumos's Vice President of Customer Success, whether Lumos has ever accepted late credit requests from Pinnacle or from any other customer. This investigation is essential to assess the viability of the INC-4471 timeliness defense and to evaluate the risk of a waiver or course-of-dealing argument. Ms. Dominguez should be asked to review Lumos'