1008-00007 · Lumos Analytics Inc · Internal Memoranda

contractual-limitations-memo.docx DOCUMENT Litigation

4 / 12 ← → ✕

Contract analysis Extract to table

PRIVILEGED AND CONFIDENTIAL — ATTORNEY-CLIENT COMMUNICATION ATTORNEY WORK PRODUCT

CALDERWOOD & HARKNESS LLP 101 California Street, Suite 3200 San Francisco, CA 94111

MEMORANDUM

TO: Linda Osei, Responsible Partner Adriana Voss, General Counsel, Lumos Analytics Inc.

FROM: Simone Laroche, Lead Associate

DATE: June 20, 2023

RE: Contractual Limitations Defenses — Pinnacle Financial Holdings LLC SLA Credit Dispute

Matter No.: 1008-00007

MSA Reference: MSA-PFH-2021-0015

I. Executive Summary

The purpose of this memorandum is to analyze the three principal contractual defenses available to Lumos Analytics Inc. ("Lumos" or the "Company") in response to the demand for $2,870,000 in damages and credits asserted by Pinnacle Financial Holdings LLC ("Pinnacle") through its counsel, Hargrove, Tillman & Burch LLP (Katherine Hargrove, lead partner; Daniel Yun, associate), as set forth in Pinnacle's demand letter dated May 1, 2023. The three defenses are:

1. The SLA Credit Cap under Exhibit C, Section 3.4, of the Master Services Agreement dated January 15, 2021, between Lumos and Pinnacle (the "MSA"), which caps total SLA credits at 30% of the annual subscription fee ($432,000) over any rolling 12-month period;

2. The Mutual Waiver of Consequential Damages under MSA Section 11.3, which bars both parties from recovering indirect, incidental, consequential, special, or exemplary damages — including lost profits, lost revenue, loss of goodwill, and business interruption — arising out of or in connection with the MSA; and

3. The Timeliness Defense under Exhibit C, Section 3.5, which requires Pinnacle to submit any credit request within 30 calendar days of the end of the affected calendar month and which, by its express terms, deems a failure to submit a timely request a waiver of the right to receive credits for the applicable month. Pinnacle's credit request for Incident INC-4471 (October 12–13, 2022) was submitted on December 14, 2022 — 14 days beyond the November 30, 2022 deadline.

Summary Conclusion. These three contractual defenses, taken together, substantially limit Lumos's maximum exposure in this dispute. The SLA credit cap of $432,000 forecloses the possibility of credits exceeding that amount under any circumstances during any rolling 12-month period. The consequential damages waiver bars $2,750,000 of Pinnacle's demand — specifically, the lost-revenue, internal remediation, and reputational-harm claims that constitute the overwhelming majority of Pinnacle's asserted damages. The timeliness defense further reduces Lumos's credit exposure by eliminating the INC-4471 credit claim entirely (valued at $36,000 per Pinnacle's calculation, or $24,000 per Lumos's internal data). Even absent the timeliness defense, Lumos's maximum contractual exposure for SLA credits alone does not exceed $432,000, and the aggregate liability cap under MSA Section 11.2 limits total liability of either party to $1,440,000 (equal to 12 months of fees paid). Our analysis of the most likely exposure range places Lumos's realistic liability between $66,000 and $120,000.

Scope Limitations. This memorandum does not address the separate and ongoing dispute regarding uptime measurement methodology — specifically, the divergence between Pinnacle's claimed outage durations and the uptime data recorded by Lumos's third-party monitoring vendor, Sentinel Uptime Services Inc. That dispute is the subject of the companion Uptime Data Analysis Memorandum currently in preparation. Nor does this memorandum address in detail the third-party causation defense available to Lumos with respect to Incident INC-5033 (March 3–5, 2023), which Lumos attributes in substantial part to an infrastructure failure at Brindoval Cloud Infrastructure LLC and Pinnacle's own failure to activate its contractually available failover to the US-West-2 availability region. Those defenses are being analyzed separately and will be presented in a supplemental memorandum.

The MSA. The Master Services Agreement (agreement number MSA-PFH-2021-0015) was executed on January 15, 2021, between Lumos Analytics Inc. and Pinnacle Financial Holdings LLC. The MSA has an initial three-year term running from January 15, 2021 through January 14, 2024. The annual subscription fee is $1,440,000, yielding a total contract value of $4,320,000 over the initial term. The SLA, credit schedule, credit cap, and credit request procedures are set forth in Exhibit C to the MSA. The limitation of liability and consequential damages waiver are contained in MSA Sections 11.2 and 11.3, respectively. The MSA is governed by the laws of the State of California.

II. Background and Pinnacle's Demand

A. The MSA and SLA Framework

The MSA was executed on January 15, 2021 (Lumos agreement number MSA-PFH-2021-0015). Under the MSA, Lumos provides Pinnacle with access to and use of Lumos's enterprise software-as-a-service ("SaaS") platform for real-time financial analytics, risk scoring, and regulatory compliance dashboards. The platform is deployed in a multi-tenant cloud environment and is accessed by Pinnacle's personnel through secure web-based and API-based interfaces.

Pinnacle Financial Holdings LLC is a mid-market commercial lending and wealth management platform with approximately $4.2 billion in assets under management ("AUM"). Pinnacle's principal offices are located at 200 West Adams Street, Suite 3100, Chicago, Illinois 60606. Pinnacle's primary contacts for purposes of this dispute are Sandra Keppler, Senior Vice President of Technology Operations, and Naveen Mistry, Director of Vendor Management.

The annual subscription fee under the MSA is $1,440,000 per year, payable in monthly installments of $120,000. The initial three-year term yields a total contract value of $4,320,000. The MSA contemplates renewal for successive one-year terms unless either party provides written notice of non-renewal at least 90 days prior to the end of the then-current term.

The service levels applicable to Lumos's platform are set forth in Exhibit C to the MSA (the "Service Level Agreement" or "SLA"). The key terms of the SLA are as follows:

Uptime Commitment. Lumos commits to maintaining 99.95% availability of the platform, measured on a monthly basis. For a 30-day calendar month (43,200 minutes), this commitment translates to maximum allowable downtime of approximately 21.6 minutes per month. Uptime is measured by Lumos's designated third-party monitoring vendor, currently Sentinel Uptime Services Inc. The uptime calculation excludes scheduled maintenance windows (which must be noticed at least 72 hours in advance), force majeure events, and downtime attributable to Customer's systems, networks, or third-party services not provided by Lumos.

P1 Incident Response Times. For Priority 1 ("P1") incidents — defined as complete platform unavailability or degradation affecting core functionality for all users — Lumos commits to initial acknowledgment within 15 minutes and resolution or deployment of a reasonable workaround within 2 hours.

SLA Credit Tiers (Exhibit C, §3.2). If Lumos fails to meet the 99.95% uptime commitment in any given calendar month, Pinnacle is entitled to SLA credits according to the following graduated schedule:

SLA Credit Cap (Exhibit C, §3.4). The maximum aggregate SLA credits that may be issued in any rolling 12-month period shall not exceed 30% of the annual subscription fee. At Pinnacle's annual fee of $1,440,000, this cap equals $432,000.

Limitation of Liability (MSA §11.2). The aggregate liability of either party under the MSA — whether arising in contract, tort, strict liability, or otherwise — shall not exceed the total fees paid by Customer during the 12-month period immediately preceding the event giving rise to the claim. For Pinnacle, this cap equals $1,440,000.

Mutual Waiver of Consequential Damages (MSA §11.3). Neither party shall be liable to the other for any indirect, incidental, consequential, special, or exemplary damages, including but not limited to damages for lost profits, lost revenue, loss of goodwill, loss of data, or business interruption, arising out of or in connection with the MSA, regardless of the cause of action or the theory of liability, even if such party has been advised of the possibility of such damages.

Credit Request Procedure (Exhibit C, §3.5). Customer must submit a written credit request within 30 calendar days of the end of the affected calendar month, specifying the affected services and the observed downtime. Failure to submit a timely credit request shall constitute a waiver of Customer's right to receive SLA credits for the applicable month. Credit requests must be submitted to Lumos's designated support portal or via email to the assigned Customer Success Manager.

Governing Law (MSA §14.1). The MSA is governed by and construed in accordance with the laws of the State of California, without regard to its conflict-of-laws principles.

Dispute Resolution (MSA §14.3). Prior to initiating any litigation, the parties agree to participate in good-faith mediation in San Francisco, California. If mediation does not resolve the dispute within 60 days of the initial mediation session, either party may pursue litigation. The parties consent to the exclusive jurisdiction of the state and federal courts located in San Francisco County, California.

B. The Four Alleged Incidents

Pinnacle's demand letter identifies four incidents that it asserts triggered SLA credit obligations. The following table summarizes Pinnacle's claimed outage durations, its calculated monthly uptime percentages, and the corresponding credit amounts Pinnacle demands:

Pinnacle's total SLA credit claim: $120,000.

We note that Lumos's own uptime data, as recorded by Sentinel Uptime Services Inc. — Lumos's designated third-party monitoring vendor under Exhibit C — reflects materially shorter outage durations for several of these incidents. Under Lumos's data, the total credit obligation would be approximately $90,000 rather than $120,000. As noted above, the divergence between Pinnacle's and Lumos's uptime measurements is the subject of a separate Uptime Data Analysis Memorandum and is not addressed in detail here. For purposes of this memorandum's liability-cap and contractual-defenses analysis, we present exposure ranges based on both Pinnacle's data and Lumos's data.

C. Pinnacle's Full Demand

Pinnacle's demand, as set forth in the May 1, 2023 letter from Katherine Hargrove of Hargrove, Tillman & Burch LLP, is as follows:

The demand was communicated via letter from Katherine Hargrove (lead partner) and Daniel Yun (associate) of Hargrove, Tillman & Burch LLP, dated May 1, 2023. The letter characterizes the demand as reflecting both "contractual credit obligations and direct and consequential damages arising from Lumos's repeated and material breaches of its service level commitments." Pinnacle's counsel asserts that the SLA credit schedule represents a minimum remedy rather than an exclusive one, and that Pinnacle is entitled to recover the full measure of its actual losses. As analyzed below, this characterization is incorrect and contradicted by the express terms of the MSA and Exhibit C.

III. Defense No. 1: SLA Credit Cap (Exhibit C, §3.4)

A. The Contractual Provision

Section 3.4 of Exhibit C to the MSA provides:

"Notwithstanding anything to the contrary in this Exhibit C, the maximum aggregate SLA credits that may be issued to Customer in any rolling twelve (12) month period shall not exceed thirty percent (30%) of the annual subscription fee then in effect. Any credits that would otherwise be owed in excess of such maximum shall be forfeited, and Provider shall have no obligation to issue such excess credits."

At Pinnacle's annual subscription fee of $1,440,000, the SLA credit cap equals $432,000 per rolling 12-month period. This cap operates as an absolute ceiling on the credit remedy available under Exhibit C, regardless of the number, frequency, or severity of qualifying incidents during the applicable measurement period.

The credit cap provision is unambiguous. It uses mandatory language ("shall not exceed") and expressly addresses the consequence of credits exceeding the cap ("shall be forfeited"). There is no exception, carve-out, or escalation mechanism that would permit credits in excess of the cap under any circumstances.

B. Application to Pinnacle's Claims

All four incidents identified in Pinnacle's demand letter — INC-4471 (October 2022), INC-4602 (November 2022), INC-4815 (January 2023), and INC-5033 (March 2023) — occurred within a single rolling 12-month period (October 2022 through March 2023). Even if every incident were credited at the maximum 30% tier ($36,000 per month), the four incidents would produce $144,000 in total credits ($36,000 × 4 months), which is well within the $432,000 cap.

Pinnacle's own SLA credit claim of $120,000 is itself below the $432,000 cap, so the cap does not, as a mechanical matter, reduce Pinnacle's SLA credit claim in this particular dispute. However, the credit cap defense remains critically important for two reasons.

First, the cap is essential as a defense against Pinnacle's broader litigation theory. Pinnacle's demand letter, through its counsel at Hargrove, Tillman & Burch, suggests entitlement to damages above and beyond the credit schedule set forth in Exhibit C. Pinnacle appears to treat SLA credits as a floor — a minimum amount of compensation — rather than as the exclusive and capped remedy the MSA contemplates. The credit cap, read in conjunction with the exclusive remedy clause in Section 3.2 and the aggregate liability cap in Section 11.2, refutes this characterization.

Second, the credit cap provides certainty regarding the outer boundary of Lumos's SLA-specific exposure. Even in a hypothetical scenario in which Lumos experienced prolonged or repeated outages over a 12-month period, the credit cap would limit total credit obligations to $432,000. This is a meaningful and commercially significant protection that the parties specifically negotiated at the time of contracting.

Section 3.4 should be read in conjunction with MSA Section 11.2 (the aggregate liability cap) as establishing a layered framework of liability limitations. The SLA credit cap limits the credit-specific remedy; the aggregate cap limits total liability under the MSA irrespective of the form of claim or theory of recovery.

C. SLA Credits as Exclusive Remedy

The credit cap defense is reinforced by the exclusive remedy clause in Exhibit C, Section 3.2, which provides:

"The service credits set forth in this Section 3.2 shall constitute Customer's sole and exclusive remedy for any failure by Provider to meet the service levels set forth in this Exhibit C."

This language is clear and unequivocal. The SLA credit schedule is not merely one of several potential remedies for uptime failures; it is the only remedy. By its terms, the exclusive remedy clause channels all claims arising from SLA non-compliance — including claims that might otherwise sound in breach of contract, negligence, or breach of warranty — into the credit framework established by Section 3.2. And because the credit framework is, in turn, subject to the credit cap in Section 3.4, the maximum exposure for any and all SLA-related claims is $432,000 per rolling 12-month period.

Under California law, "sole and exclusive remedy" clauses in commercial SaaS agreements are generally enforceable between sophisticated parties who have negotiated their contracts at arm's length. California courts have consistently recognized that commercial parties are free to allocate risk and limit remedies through their agreements, and that such allocations will be upheld absent unconscionability, fraud, or a failure of essential purpose.

Pinnacle is a sophisticated commercial entity. As a financial services firm with approximately $4.2 billion in assets under management, Pinnacle possesses substantial bargaining power and commercial sophistication. Pinnacle was represented by experienced counsel during the negotiation of the MSA, and there is no indication that Pinnacle was deprived of the opportunity to negotiate the credit schedule, the credit cap, or the exclusive remedy clause. The MSA was the product of arm's-length negotiation between two well-resourced commercial entities, and the exclusive remedy clause reflects their mutual agreement regarding the allocation of risk associated with service-level failures.

Interaction with MSA §11.2 Aggregate Liability Cap. Even if a court or arbitrator were to determine that the exclusive remedy clause in Section 3.2 is inapplicable — an unlikely outcome given the clarity of the contractual language — the aggregate liability cap in MSA Section 11.2 provides a secondary ceiling on Lumos's total liability. Section 11.2 limits the aggregate liability of either party to the total fees paid during the 12-month period immediately preceding the event giving rise to the claim, which equals $1,440,000. This cap applies to all claims under the MSA, regardless of the form of action or theory of liability, and operates as an independent limitation that does not depend on the enforceability of the exclusive remedy clause.

D. California Law on SLA Credit Caps

California courts generally enforce contractual limitations on remedies in arm's-length commercial transactions between sophisticated parties. This principle is well established in both California common law and the California Commercial Code.

California Commercial Code Section 2719. Although the California Commercial Code's Article 2 provisions apply most directly to transactions in goods, California courts have frequently applied Section 2719 by analogy in the context of software licensing and technology services agreements. Section 2719(1)(a) permits parties to provide for remedies "in addition to or in substitution for those provided in this division and may limit or alter the measure of damages recoverable under this division, as by limiting the buyer's remedies to return of the goods and repayment of the price or to repair and replacement of non-conforming goods or parts." Section 2719(1)(b) further provides that "[r]esort to a remedy as provided is optional unless the remedy is expressly agreed to be exclusive, in which case it is the sole remedy."

The critical limitation on exclusive remedy clauses is found in Section 2719(2), which provides that "[w]here circumstances cause an exclusive or limited remedy to fail of its essential purpose, remedy may be had as provided in this code." The "failure of essential purpose" doctrine is the principal legal basis on which a party might challenge an SLA credit cap.

The Credit Remedy Does Not Fail of Its Essential Purpose. The credit schedule in Exhibit C, Section 3.2, provides graduated relief that is proportional to the severity of the service-level failure. Credits range from 5% of the monthly fee for minor shortfalls (uptime between 99.90% and 99.94%) to 30% of the monthly fee for significant outages (uptime below 99.00%). The credit cap of $432,000 per rolling 12-month period represents 30% of the annual subscription fee — a substantial sum that provides meaningful financial compensation for service-level failures. The credit mechanism is functional: it has been available to Pinnacle throughout the term of the MSA, credits have been calculated and issued for qualifying incidents, and the graduated structure ensures that more severe outages yield proportionally greater credits. There is no basis for concluding that the remedy has failed of its essential purpose.

If Pinnacle argues that the remedy fails of its essential purpose because its alleged losses ($2,870,000) far exceed the credit cap ($432,000), Lumos can respond that the failure-of-essential-purpose doctrine focuses on whether the remedy mechanism itself functions as intended — not on whether the remedy is sufficient to compensate for all conceivable losses. The credit cap was the product of negotiation between sophisticated parties, it was reflected in the subscription pricing (which Pinnacle negotiated knowing the scope of the available remedy), and both parties are sophisticated commercial actors who understood the risk allocation the contract embodied. The fact that a party's actual losses may exceed a contractual limitation does not, standing alone, render the limitation unenforceable under California law.

E. Conclusion on SLA Credit Cap

The SLA credit cap of $432,000 per rolling 12-month period, combined with the exclusive remedy clause in Exhibit C, Section 3.2, limits Lumos's exposure for all SLA-related claims to a maximum of $432,000. This is far below Pinnacle's total demand of $2,870,000 and, indeed, well above even Pinnacle's own SLA credit calculation of $120,000. The credit cap does not reduce Pinnacle's SLA credit claim on its own terms in this dispute — Pinnacle's $120,000 claim is within the cap — but it forecloses Pinnacle's broader argument that it is entitled to damages beyond the credit schedule. The credit cap, exclusive remedy clause, and aggregate liability cap operate together as a comprehensive framework limiting Lumos's contractual exposure.

Risk Level: Low. The SLA credit cap defense is well-supported by the plain language of Exhibit C, Section 3.4, the exclusive remedy clause in Section 3.2, and California law governing the enforceability of contractual limitation-of-remedies provisions between sophisticated commercial parties.

IV. Defense No. 2: Mutual Waiver of Consequential Damages (MSA §11.3)

A. The Contractual Provision

Section 11.3 of the MSA provides, in relevant part:

"IN NO EVENT SHALL EITHER PARTY BE LIABLE TO THE OTHER PARTY FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL, OR EXEMPLARY DAMAGES, INCLUDING BUT NOT LIMITED TO DAMAGES FOR LOST PROFITS, LOST REVENUE, LOSS OF GOODWILL, LOSS OF DATA, OR BUSINESS INTERRUPTION, ARISING OUT OF OR IN CONNECTION WITH THIS AGREEMENT, REGARDLESS OF THE CAUSE OF ACTION OR THE THEORY OF LIABILITY, EVEN IF SUCH PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES."

Several features of this provision merit emphasis. First, the waiver is mutual — it applies equally to both Lumos and Pinnacle. This mutuality is significant because it negates any argument that the provision was imposed unilaterally by the party with superior bargaining power. Both parties accepted the same limitation on their respective rights to recover consequential damages.

Second, the waiver is broadly drafted. It encompasses "indirect, incidental, consequential, special, or exemplary damages," and the illustrative list — "lost profits, lost revenue, loss of goodwill, loss of data, or business interruption" — directly targets precisely the categories of damages that Pinnacle now seeks to recover.

Third, the waiver applies "regardless of the cause of action or the theory of liability." This language was included to prevent a party from circumventing the waiver by recasting its claims in tort (e.g., negligence, negligent misrepresentation) rather than contract. The waiver applies irrespective of how Pinnacle frames its claims.

Fourth, the waiver applies "even if such party has been advised of the possibility of such damages." This language eliminates any argument based on Hadley v. Baxendale foreseeability — i.e., that Lumos should be liable for consequential damages because it knew or should have known that its service failures would cause downstream business losses to Pinnacle.

This type of mutual consequential damages waiver is standard in enterprise SaaS agreements and reflects a well-understood commercial allocation of risk. The SaaS provider limits its exposure to the fees it receives; the customer accepts the limitation in exchange for pricing that reflects the provider's reduced risk. Both parties benefit from certainty regarding the scope of potential liability.

B. Application to Pinnacle's Non-Credit Claims

Pinnacle's total demand of $2,870,000 includes $2,750,000 in damages beyond SLA credits. Each of these non-credit damage categories falls squarely within the scope of the consequential damages waiver in Section 11.3.

Lost Revenue from Delayed Loan Originations and Missed Trading Windows ($1,950,000). This is a textbook consequential damages or lost-profits claim. Pinnacle alleges that platform outages caused downstream business losses in its commercial lending and trading operations — specifically, that Pinnacle was unable to originate certain loans and missed trading windows during the periods of platform unavailability. These are classic indirect damages: they flow from the alleged service interruption but are not damages for the cost of the service itself. They are, instead, damages for the impact of the service interruption on Pinnacle's separate business activities. Section 11.3 expressly lists "lost profits," "lost revenue," and "business interruption" among the categories of excluded damages. The $1,950,000 lost-revenue claim is barred in its entirety by Section 11.3.

Internal Remediation Costs ($340,000). Pinnacle claims $340,000 in costs for manual workarounds, employee overtime, and the temporary licensing of a competitor platform — TrueNorth Data Systems Inc. — to provide substitute analytics services during the outage periods. This category requires closer analysis because some remediation or "cover" costs might, in certain circumstances, be characterized as direct rather than consequential damages.

However, the bulk of these claimed costs — including overtime labor reallocation, the cost of retraining personnel on a temporary substitute platform, and the licensing fees for TrueNorth Data Systems — are consequential in nature. They flow from the alleged breach but are not the cost of the contracted-for service itself. The direct cost of the service is the $120,000 monthly subscription fee that Pinnacle pays to Lumos; remediation costs that Pinnacle incurs to address the downstream effects of an outage are consequential damages arising from the breach, not direct damages for the value of the service not received. Section 11.3's reference to "business interruption" damages further supports the conclusion that internal remediation costs — which are, by definition, costs incurred to mitigate business interruption — fall within the scope of the waiver.

Even if a court were to characterize a portion of the remediation costs as direct damages — for example, the cost of licensing TrueNorth as "cover" — those costs would still be subject to the aggregate liability cap of $1,440,000 under MSA Section 11.2 and, to the extent they arise from uptime failures, would be channeled into the exclusive SLA credit remedy under Exhibit C, Section 3.2. In any event, the remediation costs cannot exceed the aggregate cap, and Pinnacle cannot use a remediation-costs theory to circumvent the contractual framework.

Reputational Harm / Client Attrition ($460,000). Pinnacle claims $460,000 representing the estimated value of two wealth-management clients that allegedly left Pinnacle due to service disruptions caused by platform outages. This claim is squarely consequential: it involves loss of goodwill, loss of business relationships, and indirect revenue impact from the departure of clients who were not parties to the MSA and whose decisions to leave Pinnacle involved intervening factors entirely outside Lumos's control. Section 11.3 expressly bars "loss of goodwill" damages. Moreover, the $460,000 figure is inherently speculative — it is based on Pinnacle's estimate of the future revenue it would have earned from two clients whose actual reasons for departing are unknown and unverified. This claim is clearly barred by Section 11.3.

Total Amount Barred by Section 11.3: $2,750,000. The consequential damages waiver eliminates the entirety of Pinnacle's non-credit demand, leaving only the SLA credit claim of $120,000 (as reduced or modified by the other defenses discussed in this memorandum).

C. Enforceability Under California Law

California courts consistently enforce mutual consequential damages waivers in commercial contracts between sophisticated parties. The enforceability of such provisions is well established under both California common law and the California Commercial Code.

California Commercial Code Section 2719(3). Section 2719(3) provides that "[c]onsequential damages may be limited or excluded unless the limitation or exclusion is unconscionable. Limitation of consequential damages for injury to the person in the case of consumer goods is prima facie unconscionable but limitation of damages where the loss is commercial is not." This provision creates a clear presumption: in commercial transactions between business entities, the limitation or exclusion of consequential damages is not unconscionable. Pinnacle bears the burden of overcoming this presumption, and the circumstances of this transaction make it exceedingly unlikely that Pinnacle could do so.

No Indicia of Procedural Unconscionability. Procedural unconscionability requires a showing of oppression or surprise — circumstances indicating that one party lacked meaningful choice or was subjected to unfair bargaining tactics. None of those circumstances exist here. The MSA was negotiated at arm's length between two sophisticated commercial entities with substantial resources and experienced counsel. Pinnacle, with $4.2 billion in AUM and a dedicated vendor management team, had bargaining power commensurate with its status as a significant enterprise customer paying $1,440,000 per year. There is no evidence of surprise — the consequential damages waiver appears in a conspicuous, capitalized provision in Article 11 of the MSA, and there is no indication that it was hidden, obscured, or presented on a take-it-or-leave-it basis. There is no evidence of oppression — Pinnacle was free to negotiate the terms of the MSA, and indeed the negotiation process involved multiple rounds of redlining and revision over a period of approximately three months prior to execution.

No Indicia of Substantive Unconscionability. Substantive unconscionability requires a showing that the contractual terms are unreasonably favorable to one party. The mutual nature of the consequential damages waiver in Section 11.3 negates this argument. The waiver applies equally to both parties: Lumos cannot recover consequential damages from Pinnacle any more than Pinnacle can recover consequential damages from Lumos. The mutuality of the provision reflects a balanced and commercially reasonable allocation of risk. Moreover, the consequential damages waiver is standard in the enterprise SaaS industry — it appears in the vast majority of negotiated SaaS agreements between enterprise vendors and their customers. The provision is not unusual, unexpected, or commercially unreasonable.

D. Potential Counterarguments and Responses

We have identified four potential counterarguments that Pinnacle or its counsel might advance in an effort to defeat or circumvent the consequential damages waiver. None of these arguments is likely to succeed, but each merits brief analysis.

1. Remediation Costs Are Direct Damages, Not Consequential. Pinnacle may argue that its $340,000 in remediation costs — including overtime, manual workarounds, and the temporary licensing of TrueNorth Data Systems — constitute direct damages rather than consequential damages and therefore fall outside the scope of the Section 11.3 waiver. This argument has some surface plausibility with respect to the TrueNorth licensing costs, which might be analogized to "cover" damages under UCC Section 2-712.

Response: Even if a court were to characterize some portion of the remediation costs as direct damages, this would not assist Pinnacle materially. Direct damages for uptime failures are channeled into the exclusive SLA credit remedy under Exhibit C, Section 3.2, and are subject to the $432,000 credit cap under Section 3.4. To the extent any remediation costs are deemed direct damages not subject to the exclusive SLA credit remedy — an analytical stretch — they would still be subject to the aggregate liability cap of $1,440,000 under Section 11.2. The direct/consequential distinction does not provide Pinnacle a path to recovering the full $2,870,000 demand.

2. The Consequential Damages Waiver Is Unconscionable. Pinnacle may argue that the waiver is unconscionable under California Commercial Code Section 2719(3) or under general California unconscionability doctrine.

Response: As discussed above, this argument is very unlikely to succeed. The waiver is mutual, was negotiated at arm's length between sophisticated parties with comparable bargaining power, and is standard in enterprise SaaS agreements. California Commercial Code Section 2719(3) creates a presumption that limitations on consequential damages in commercial transactions are not unconscionable, and Pinnacle bears the heavy burden of overcoming that presumption. Given the absence of any indicia of either procedural or substantive unconscionability, this argument should fail.

3. Willful Breach Vitiates the Consequential Damages Waiver. Pinnacle may argue that Lumos's service-level failures were so frequent or severe as to constitute willful or intentional breach, and that a party should not be permitted to shield itself from consequential damages for deliberate or willful misconduct.

Response: There is no evidence of willful or intentional breach. The service outages at issue were unintentional infrastructure events — they involved database failover delays (INC-4471), API gateway congestion (INC-4602), a data-center power excursion (INC-4815), and a cloud-infrastructure failure at Brindoval Cloud Infrastructure LLC (INC-5033). None of these incidents was caused by deliberate misconduct, and there is no basis for characterizing Lumos's conduct as willful. Moreover, even if willful breach were established (which it cannot be on these facts), Section 11.3 applies "regardless of the cause of action or the theory of liability." This broad language indicates that the parties intended the waiver to apply to all claims, including claims based on theories that might implicate intentionality. While there is a minority line of authority in some jurisdictions suggesting that consequential damages waivers should not apply to willful breach, California courts have not adopted such a rule as a per se matter, and the contractual language here supports application of the waiver regardless of the nature of the breach.

4. The SLA Credit Remedy Fails of Its Essential Purpose, Unlocking Full Damages. Pinnacle may argue that because the SLA credit remedy is capped at $432,000 while its actual losses exceed $2,870,000, the remedy has "failed of its essential purpose" under California Commercial Code Section 2719(2), and that the failure of essential purpose should vitiate not only the exclusive remedy clause but also the consequential damages waiver.

Response: As discussed in Part III.D above, the credit remedy has not failed of its essential purpose. The credit mechanism is functional, provides graduated relief proportional to the severity of the failure, and permits up to $432,000 in annual credits — a substantial sum. The failure-of-essential-purpose doctrine applies when the contractual remedy mechanism is inoperative or otherwise unable to fulfill its intended function (e.g., when a repair-or-replace warranty fails because the seller is unable or unwilling to repair or replace the defective product). It does not apply merely because a party's actual losses exceed the cap on the contractual remedy. Furthermore, even in jurisdictions that have held that a failure of essential purpose vitiates the exclusive remedy clause, courts are divided on whether such failure also eliminates the consequential damages waiver. Under the better-reasoned approach, these are independent provisions: the exclusive remedy clause and the consequential damages waiver serve different functions, were separately negotiated, and should be enforced independently. Section 11.3 is not dependent on the enforceability of the exclusive remedy clause in Section 3.2.

E. Conclusion on Consequential Damages Waiver

Section 11.3 of the MSA bars Pinnacle's claims for lost revenue ($1,950,000), internal remediation costs ($340,000), and reputational harm ($460,000) — totaling $2,750,000. This defense eliminates approximately 95.8% of Pinnacle's total demand ($2,750,000 of $2,870,000), leaving only the SLA credit claim of $120,000 at issue.

The consequential damages waiver is the single most impactful defense available to Lumos in this dispute. It is supported by clear and unambiguous contractual language, the mutual nature of the provision, the sophistication of the parties, and well-established California law. The potential counterarguments — unconscionability, willful breach, failure of essential purpose — are weak on these facts and unlikely to succeed.

Risk Level: Low. This is a strong defense with robust contractual language and favorable California case law. We assess the likelihood of a court or mediator invalidating Section 11.3 on these facts as very low.

V. Defense No. 3: Timeliness of Credit Request for INC-4471 (Exhibit C, §3.5)

A. The Contractual Provision

Section 3.5 of Exhibit C to the MSA establishes the procedural requirements for SLA credit requests:

"Customer must submit a written credit request within thirty (30) calendar days of the end of the affected calendar month, specifying the affected services and the observed downtime. Failure to submit a timely credit request shall constitute a waiver of Customer's right to receive SLA credits for the applicable month."

Two features of this provision are significant. First, it uses mandatory language — "must submit" — that leaves no discretion regarding the filing deadline. Second, it includes an express waiver consequence: failure to submit a timely request "shall constitute a waiver" of the right to credits for that month. The provision does not use permissive or discretionary language (such as "may" or "should"), nor does it provide for extensions, exceptions, or a cure period. The consequence of untimely submission is automatic forfeiture of the credit for the applicable month.

B. Facts Relevant to INC-4471

Incident INC-4471 occurred on October 12–13, 2022. Pinnacle alleges that the incident resulted in 7 hours and 42 minutes of downtime, reducing October 2022 uptime to 98.93% and triggering the maximum 30% credit tier ($36,000). Lumos's data from Sentinel Uptime Services Inc. indicates a shorter outage duration, corresponding to a 99.43% uptime level and the 20% credit tier ($24,000). The discrepancy in uptime measurement is addressed in the companion Uptime Data Analysis Memorandum.

For purposes of the timeliness defense, the relevant facts are as follows:

• The affected calendar month is October 2022.

• The end of October 2022 is October 31, 2022.

• The 30-calendar-day deadline under Section 3.5 is November 30, 2022.

• Pinnacle submitted its credit request for INC-4471 on December 14, 2022.

• The submission was therefore made 44 days after the end of October 2022, exceeding the 30-day deadline by 14 days.

The December 14, 2022 submission date is confirmed by the timestamp on Pinnacle's credit request as logged in Lumos's customer support portal. There is no dispute regarding the date of submission; Pinnacle's own demand letter acknowledges the December 14 submission date and does not contend that the request was submitted earlier through any alternative channel.

C. Enforceability of Contractual Deadlines Under California Law

California law generally enforces contractual notice and claim deadlines in commercial agreements. The legal analysis of the Section 3.5 deadline depends on its characterization: Is it a procedural notice requirement subject to substantial-compliance and prejudice standards, or is it a condition precedent to the right to receive the credit remedy?

The language of Section 3.5 supports characterization as a condition precedent. The provision does not merely require Pinnacle to "notify" Lumos of an outage or to "report" an incident within a particular timeframe. Instead, it requires Pinnacle to "submit a written credit request" — i.e., to invoke its right to the credit remedy — within 30 calendar days. And the provision expressly states that failure to comply "shall constitute a waiver" of the right to credits. A waiver is the intentional relinquishment of a known right. By deeming untimely submission a "waiver," Section 3.5 makes timely submission an essential precondition to the credit remedy, not merely a procedural formality.

Courts draw a meaningful distinction between notice provisions — which are often subject to substantial-compliance analysis and may require a showing of prejudice before non-compliance results in forfeiture — and claim-filing provisions that operate as conditions precedent to a remedy. Section 3.5 falls squarely in the latter category. It conditions Pinnacle's entitlement to credits on the timely submission of a credit request, and it attaches an express forfeiture consequence to non-compliance.

The 30-day window is reasonable and commercially standard. Enterprise SaaS agreements commonly include credit-request deadlines of 30 to 60 days, and the 30-day period provides Pinnacle ample time to review its monthly service performance data, identify qualifying incidents, calculate the applicable credit tier, and submit a written request. There is nothing unusual or unduly restrictive about the deadline.

D. Potential Counterarguments and Responses

1. Waiver by Lumos

Pinnacle may argue that Lumos waived the Section 3.5 deadline by engaging with Pinnacle on the INC-4471 incident without raising the timeliness objection, or by a course of dealing in which late credit submissions were previously accepted without objection.

Response: Whether this argument has any factual basis depends on the historical record of Lumos's enforcement of the Section 3.5 deadline. If Lumos has consistently enforced the 30-day deadline and has previously rejected or objected to late credit requests — whether from Pinnacle or from other customers under similar MSAs — the waiver argument fails. If, on the other hand, Lumos has a history of accepting late credit requests without objection, Pinnacle may have a stronger argument that Lumos waived strict compliance with the deadline through a course of dealing.

Additionally, the MSA likely contains an anti-waiver or "no waiver" clause — typically found in Article 14 or Article 15 (General Provisions) — providing that the failure of either party to enforce any provision of the MSA shall not constitute a waiver of such provision or of the right to enforce it in the future. If such a clause exists, it reinforces Lumos's ability to enforce the Section 3.5 deadline even if there were prior instances of lax enforcement.

Recommendation: We recommend confirming with Adriana Voss (General Counsel) and Rachel Dominguez (VP of Customer Success) whether there is any history of Lumos accepting late credit requests from Pinnacle or from other customers. We also recommend confirming the existence and precise language of any anti-waiver clause in the MSA's general provisions.

2. Estoppel. Pinnacle may argue that Lumos is equitably estopped from enforcing the Section 3.5 deadline if Lumos made representations — express or implied — that the deadline would not be strictly enforced, and Pinnacle reasonably relied on such representations to its detriment.

Response: Equitable estoppel requires (a) a representation by Lumos that the deadline would not be enforced; (b) reasonable reliance by Pinnacle on that representation; and (c) detriment to Pinnacle resulting from the reliance. In the absence of an affirmative representation by Lumos — whether in writing, orally, or through a clear pattern of conduct — estoppel should not apply. The mere fact that Lumos engaged with Pinnacle on the substance of the INC-4471 incident (e.g., discussing root cause or incident response) does not constitute a representation that the credit-request deadline would be waived.

Recommendation: We recommend reviewing all correspondence between Lumos personnel (specifically Thomas Kwan, Director of Technical Support, and Rachel Dominguez, VP of Customer Success) and Pinnacle personnel (Sandra Keppler and Naveen Mistry) regarding the INC-4471 incident and credit request. If any Lumos representative made a statement suggesting that the late submission would be accepted or that the deadline was flexible, the estoppel risk increases, and we would need to reassess the strength of this defense.

3. Substantial Compliance

Pinnacle may argue that its December 14, 2022 submission was in "substantial compliance" with the spirit of Section 3.5, or that the 14-day delay beyond the 30-day window was de minimis and should not result in forfeiture of the credit.

Response: The substantial-compliance doctrine is generally inapplicable where the contract includes express, mandatory language with a specified consequence for non-compliance. Section 3.5 uses the word "must," specifies a 30-day deadline, and provides that failure to comply "shall constitute a waiver." This is not a provision that invites a substantial-compliance analysis. The express waiver clause eliminates any argument that approximate or near-compliance is sufficient.

Moreover, the delay was not de minimis. A 14-day overshoot on a 30-day deadline represents a 47% overrun beyond the contractual window. This is not a case of a credit request submitted one or two days late; it is a case of a request submitted nearly two weeks after the deadline. While the characterization of any particular delay as "de minimis" is inherently subjective, a 47% overrun significantly undermines any claim that Pinnacle substantially complied with the deadline.

4. Prejudice Requirement

Pinnacle may argue that Lumos must demonstrate that it was prejudiced by the late submission — i.e., that the 14-day delay caused Lumos some concrete harm — before the forfeiture consequence should apply.

Response: Where the contract expressly provides that untimely submission "shall constitute a waiver" of the right to credits, California courts generally enforce the provision as written, without requiring a separate showing of prejudice by the non-breaching party. The prejudice requirement is more commonly applied in the insurance-law context, where courts have held that an insurer must demonstrate prejudice from late notice before it can deny coverage based on a late-notice defense. The insurance-law prejudice rule reflects policy considerations specific to the insured-insurer relationship and does not apply to arm's-length commercial SaaS credit-claim procedures.

Section 3.5 is not a general notice provision — it is a claim-filing deadline with an express forfeiture consequence. The parties specifically agreed that untimely submission would constitute a waiver, and there is no basis for grafting a judicially created prejudice requirement onto the provision. Requiring a showing of prejudice would effectively rewrite the parties' agreement and deprive Lumos of the benefit of the bargain it negotiated.

E. Impact on Overall Exposure

If the timeliness defense succeeds, Pinnacle loses the INC-4471 credit entirely. This reduces Pinnacle's SLA credit claim as follows:

• Under Pinnacle's data: From $120,000 to $84,000 ($120,000 minus $36,000)

• Under Lumos's Sentinel data: From $90,000 to $66,000 ($90,000 minus $24,000)

While the dollar amount at stake — $24,000 to $36,000 — is relatively modest in the context of the overall dispute, the timeliness defense is strategically significant for several reasons. First, it demonstrates that Pinnacle failed to comply with the very contractual procedures it now seeks to enforce, undermining Pinnacle's broader narrative that Lumos is the party in breach. Second, it reduces Lumos's total credit exposure, potentially to as little as $66,000 under Lumos's own uptime data. Third, it provides additional leverage in mediation and settlement discussions by narrowing the scope of Pinnacle's credible claims.

F. Conclusion on Timeliness Defense

Pinnacle's credit request for INC-4471 was submitted on December 14, 2022 — 44 days after the end of the affected calendar month (October 2022) and 14 days beyond the 30-calendar-day deadline established by Exhibit C, Section 3.5. The express waiver language in Section 3.5 supports forfeiture of the INC-4471 credit in its entirety.

The potential counterarguments — waiver by Lumos, estoppel, substantial compliance, and a prejudice requirement — are weak given the express terms of the contract and the sophistication of the parties. However, we recommend confirming the factual record regarding Lumos's prior enforcement practices to ensure the absence of any course of dealing that might support a waiver or estoppel argument.

Risk Level: Low to Moderate. The defense is well-grounded in the contract language and California law, but there is some residual risk that a mediator or court might give weight to equitable considerations, particularly if there is any evidence of inconsistent enforcement by Lumos. We rate this risk as manageable, and the defense should be asserted.

VI. Interaction of Defenses with Aggregate Liability Cap (MSA §11.2)

Separate from the three principal defenses analyzed above, the aggregate liability cap in MSA Section 11.2 provides an additional, independent layer of protection for Lumos. Section 11.2 provides:

"IN NO EVENT SHALL THE AGGREGATE LIABILITY OF EITHER PARTY UNDER THIS AGREEMENT EXCEED THE TOTAL FEES PAID BY CUSTOMER DURING THE TWELVE (12) MONTH PERIOD IMMEDIATELY PRECEDING THE EVENT GIVING RISE TO THE CLAIM, REGARDLESS OF THE FORM OF ACTION OR THEORY OF LIABILITY."

At Pinnacle's annual subscription fee of $1,440,000, the aggregate liability cap equals $1,440,000.

Pinnacle's total demand of $2,870,000 exceeds this cap by $1,430,000. Even if the consequential damages waiver in Section 11.3 were struck down — an outcome we assess as highly unlikely — the aggregate cap would independently limit Pinnacle's maximum recovery to $1,440,000. And Pinnacle would still need to prove its alleged damages (including the speculative lost-revenue and reputational-harm claims) to recover up to the cap.

The aggregate liability cap and the consequential damages waiver operate as independent, layered protections. They serve different functions and are enforceable on different grounds. The consequential damages waiver limits the types of damages recoverable; the aggregate cap limits the total amount recoverable regardless of damage type. Even if one provision were invalidated, the other would remain in force. This layered structure is deliberate and reflects the parties' intent to create multiple independent protections against excessive liability exposure.

The aggregate liability cap is subject to the same enforceability analysis as the other contractual limitations discussed in this memorandum. It was negotiated at arm's length between sophisticated parties, is mutual in nature, and is standard in enterprise SaaS agreements. California courts consistently enforce such caps in commercial transactions. The cap is not unconscionable, and Pinnacle has no basis for challenging it.

VII. Summary of Maximum Exposure Analysis

The following analysis presents Lumos's maximum exposure under four scenarios, ranging from the best-case scenario (all defenses upheld, Lumos's uptime data applied, and the INC-5033 third-party causation defense successful) to the absolute worst-case scenario (all contractual defenses fail).

A. Best-Case Scenario for Lumos

Under the best-case scenario, all three contractual defenses analyzed in this memorandum are upheld, Lumos's Sentinel uptime data is used for credit calculations, and the separate INC-5033 third-party causation defense succeeds:

• INC-4471 credit request time-barred under §3.5: $0

• INC-4602 credit per Sentinel data (99.77% uptime, 5% tier): $6,000

• INC-4815 credit per Sentinel data (99.43% uptime, 20% tier): $24,000

• INC-5033 excluded under §2.3 (third-party cause — Brindoval Cloud Infrastructure LLC failure and Pinnacle's failure to activate US-West-2 failover): $0

• All consequential/indirect damages barred under §11.3: $0

Best-case maximum exposure: $30,000

B. Worst-Case Scenario for Lumos (All Contractual Defenses Upheld, Pinnacle's Uptime Data)

Under this scenario, all three contractual defenses are upheld but Pinnacle's uptime data is used for credit calculations (i.e., Lumos does not prevail on the uptime measurement dispute), and the INC-5033 third-party causation defense is not applied:

• INC-4471 time-barred under §3.5: $0

• INC-4602 credit per Pinnacle's data (99.54% uptime, 10% tier): $12,000

• INC-4815 credit per Pinnacle's data (98.47% uptime, 30% tier): $36,000

• INC-5033 credit per Pinnacle's data (96.32% uptime, 30% tier): $36,000

• All consequential/indirect damages barred under §11.3: $0

Worst-case with defenses: $84,000

C. Scenario Without Timeliness Defense

Under this scenario, the timeliness defense for INC-4471 is not asserted or does not succeed, but the SLA credit cap and consequential damages waiver are upheld, and Pinnacle's uptime data is used:

• INC-4471 credit per Pinnacle's data (98.93% uptime, 30% tier): $36,000

• INC-4602 credit per Pinnacle's data: $12,000

• INC-4815 credit per Pinnacle's data: $36,000

• INC-5033 credit per Pinnacle's data: $36,000

• Total SLA credits: $120,000 (within $432,000 SLA credit cap)

• All consequential/indirect damages barred under §11.3: $0

Maximum exposure without timeliness defense: $120,000

D. Absolute Maximum (All Defenses Fail)

Under the absolute worst-case scenario — in which the consequential damages waiver is invalidated, the SLA credit cap is struck, and the exclusive remedy clause is deemed unenforceable — Lumos's exposure would be capped by the aggregate liability cap in MSA Section 11.2 at $1,440,000. Even in this scenario, Pinnacle would need to prove its actual damages, including the speculative lost-revenue claim ($1,950,000, which exceeds the aggregate cap on its own) and the highly speculative reputational-harm claim ($460,000). We assess the likelihood of all contractual defenses failing as extremely low.

Absolute maximum: $1,440,000 (subject to proof of damages)

E. Summary Table

The most likely range of Lumos's exposure, assuming the contractual defenses are upheld as we expect, is $66,000 to $432,000, with a realistic range of $66,000 to $120,000 depending on the resolution of the uptime measurement dispute and the timeliness defense.

VIII. Recommendations

A. Immediate Actions

Based on the analysis set forth in this memorandum, we recommend that Lumos take the following immediate steps:

1. Confirm Credit Request History. Adriana Voss (General Counsel) and Rachel Dominguez (VP of Customer Success) should confirm whether there is any prior history of Lumos accepting late SLA credit requests from Pinnacle — or from other customers under similar MSAs — without raising timeliness objections. If late credit requests have been accepted in the past without objection, the timeliness defense for INC-4471 is weakened. Conversely, if Lumos has consistently enforced the 30-day deadline, the defense is strengthened. This fact-finding is the single most important open item for the timeliness defense.

2. Confirm Anti-Waiver Clause. We recommend confirming the existence and precise language of the anti-waiver (or "no waiver") clause in the MSA's general provisions (likely in Article 14 or Article 15). Such a clause typically provides that the failure of either party to enforce any provision of the MSA shall not constitute a waiver of that provision or of the right to enforce it in the future. If this clause is present, it provides additional support for the timeliness defense and for Lumos's enforcement of the contractual limitations generally.

3. Review INC-4471 Correspondence. We recommend reviewing all internal and external correspondence between Lumos personnel (specifically Thomas Kwan, Director of Technical Support, and Rachel Dominguez, VP of Customer Success) and Pinnacle personnel (Sandra Keppler, SVP of Technology Operations, and Naveen Mistry, Director of Vendor Management) regarding the INC-4471 incident, the credit request, and the December 14, 2022 submission. We are specifically looking for any statements by Lumos representatives suggesting that the 30-day deadline was flexible, that the late submission would be accepted, or that Lumos was waiving strict compliance with Section 3.5. If any such statements exist, they would need to be addressed in our timeliness defense analysis.

4. Preserve Records. All records relevant to the Pinnacle dispute should continue to be preserved in accordance with the Litigation Hold Memorandum issued on May 15, 2023. We remind Adriana Voss and the Lumos team that the litigation hold applies to all documents, communications, and data related to the four incidents, the MSA, the SLA, and the Pinnacle relationship generally. Any questions about the scope of the litigation hold should be directed to this firm.

B. Strategic Recommendations

1. Lead with All Three Defenses. In any response to Pinnacle's counsel at Hargrove, Tillman & Burch LLP, we recommend emphasizing all three contractual defenses as the primary basis for rejecting the $2,870,000 demand. The response should make clear that Pinnacle's demand is contractually foreclosed and that Lumos's maximum exposure is limited to a fraction of the claimed amount.

2. Prioritize the Consequential Damages Waiver. The consequential damages waiver in Section 11.3 is the single most powerful defense available to Lumos. It eliminates 95.8% of Pinnacle's total demand ($2,750,000 of $2,870,000). The response to Pinnacle's counsel should lead with this defense, as it reframes the entire dispute from a $2.87 million claim to, at most, a $120,000 credit dispute.

3. Frame the Dispute as a Modest Credit Obligation. The SLA credit cap and timeliness defense should be used to frame the dispute as involving, at most, a modest credit obligation well within the ordinary course of the MSA's SLA framework. The response should convey that Lumos takes its service-level commitments seriously, that the SLA credit mechanism is functioning as intended, and that Lumos is prepared to address legitimate credit claims through the contractual framework — but that Pinnacle's demand for $2.87 million in damages is unsupported by the contract and barred by the MSA's liability-limitation provisions.

4. Reserve Additional Defenses. The third-party causation defense for INC-5033 (attributable to Brindoval Cloud Infrastructure LLC) and the mitigation-failure defense (Pinnacle's failure to activate its contractually available failover to the US-West-2 availability region) should be reserved as additional leverage. These defenses are being analyzed in a separate memorandum and, if viable, would further reduce Lumos's credit exposure by eliminating or reducing the INC-5033 credit. We recommend disclosing these defenses strategically — potentially in mediation — rather than in the initial response letter.

5. Prepare for Mediation. In anticipation of mandatory mediation under MSA Section 14.3, we recommend developing a settlement posture that recognizes some credit obligation while firmly defending against consequential damages. A reasonable settlement range, based on our exposure analysis, would be in the range of $66,000 to $120,000. Any settlement should include a full release of all claims related to the four incidents and, ideally, a reaffirmation of the MSA's liability-limitation provisions going forward. We should discuss s

PRIVILEGED AND CONFIDENTIAL — ATTORNEY-CLIENT COMMUNICATION ATTORNEY WORK PRODUCT
CALDERWOOD & HARKNESS LLP 101 California Street, Suite 3200 San Francisco, CA 94111
MEMORANDUM
TO: Linda Osei, Responsible Partner Adriana Voss, General Counsel, Lumos Analytics Inc.
FROM: Simone Laroche, Lead Associate
DATE: June 20, 2023
RE: Contractual Limitations Defenses — Pinnacle Financial Holdings LLC SLA Credit Dispute
Matter No.: 1008-00007
MSA Reference: MSA-PFH-2021-0015
I. Executive Summary
The purpose of this memorandum is to analyze the three principal contractual defenses available to Lumos Analytics Inc. ("Lumos" or the "Company") in response to the demand for $2,870,000 in damages and credits asserted by Pinnacle Financial Holdings LLC ("Pinnacle") through its counsel, Hargrove, Tillman & Burch LLP (Katherine Hargrove, lead partner; Daniel Yun, associate), as set forth in Pinnacle's demand letter dated May 1, 2023. The three defenses are:
1. The SLA Credit Cap under Exhibit C, Section 3.4, of the Master Services Agreement dated January 15, 2021, between Lumos and Pinnacle (the "MSA"), which caps total SLA credits at 30% of the annual subscription fee ($432,000) over any rolling 12-month period;
2. The Mutual Waiver of Consequential Damages under MSA Section 11.3, which bars both parties from recovering indirect, incidental, consequential, special, or exemplary damages — including lost profits, lost revenue, loss of goodwill, and business interruption — arising out of or in connection with the MSA; and
3. The Timeliness Defense under Exhibit C, Section 3.5, which requires Pinnacle to submit any credit request within 30 calendar days of the end of the affected calendar month and which, by its express terms, deems a failure to submit a timely request a waiver of the right to receive credits for the applicable month. Pinnacle's credit request for Incident INC-4471 (October 12–13, 2022) was submitted on December 14, 2022 — 14 days beyond the November 30, 2022 deadline.
Summary Conclusion. These three contractual defenses, taken together, substantially limit Lumos's maximum exposure in this dispute. The SLA credit cap of $432,000 forecloses the possibility of credits exceeding that amount under any circumstances during any rolling 12-month period. The consequential damages waiver bars $2,750,000 of Pinnacle's demand — specifically, the lost-revenue, internal remediation, and reputational-harm claims that constitute the overwhelming majority of Pinnacle's asserted damages. The timeliness defense further reduces Lumos's credit exposure by eliminating the INC-4471 credit claim entirely (valued at $36,000 per Pinnacle's calculation, or $24,000 per Lumos's internal data). Even absent the timeliness defense, Lumos's maximum contractual exposure for SLA credits alone does not exceed $432,000, and the aggregate liability cap under MSA Section 11.2 limits total liability of either party to $1,440,000 (equal to 12 months of fees paid). Our analysis of the most likely exposure range places Lumos's realistic liability between $66,000 and $120,000.
Scope Limitations. This memorandum does not address the separate and ongoing dispute regarding uptime measurement methodology — specifically, the divergence between Pinnacle's claimed outage durations and the uptime data recorded by Lumos's third-party monitoring vendor, Sentinel Uptime Services Inc. That dispute is the subject of the companion Uptime Data Analysis Memorandum currently in preparation. Nor does this memorandum address in detail the third-party causation defense available to Lumos with respect to Incident INC-5033 (March 3–5, 2023), which Lumos attributes in substantial part to an infrastructure failure at Brindoval Cloud Infrastructure LLC and Pinnacle's own failure to activate its contractually available failover to the US-West-2 availability region. Those defenses are being analyzed separately and will be presented in a supplemental memorandum.
The MSA. The Master Services Agreement (agreement number MSA-PFH-2021-0015) was executed on January 15, 2021, between Lumos Analytics Inc. and Pinnacle Financial Holdings LLC. The MSA has an initial three-year term running from January 15, 2021 through January 14, 2024. The annual subscription fee is $1,440,000, yielding a total contract value of $4,320,000 over the initial term. The SLA, credit schedule, credit cap, and credit request procedures are set forth in Exhibit C to the MSA. The limitation of liability and consequential damages waiver are contained in MSA Sections 11.2 and 11.3, respectively. The MSA is governed by the laws of the State of California.
II. Background and Pinnacle's Demand
A. The MSA and SLA Framework
The MSA was executed on January 15, 2021 (Lumos agreement number MSA-PFH-2021-0015). Under the MSA, Lumos provides Pinnacle with access to and use of Lumos's enterprise software-as-a-service ("SaaS") platform for real-time financial analytics, risk scoring, and regulatory compliance dashboards. The platform is deployed in a multi-tenant cloud environment and is accessed by Pinnacle's personnel through secure web-based and API-based interfaces.
Pinnacle Financial Holdings LLC is a mid-market commercial lending and wealth management platform with approximately $4.2 billion in assets under management ("AUM"). Pinnacle's principal offices are located at 200 West Adams Street, Suite 3100, Chicago, Illinois 60606. Pinnacle's primary contacts for purposes of this dispute are Sandra Keppler, Senior Vice President of Technology Operations, and Naveen Mistry, Director of Vendor Management.
The annual subscription fee under the MSA is $1,440,000 per year, payable in monthly installments of $120,000. The initial three-year term yields a total contract value of $4,320,000. The MSA contemplates renewal for successive one-year terms unless either party provides written notice of non-renewal at least 90 days prior to the end of the then-current term.
The service levels applicable to Lumos's platform are set forth in Exhibit C to the MSA (the "Service Level Agreement" or "SLA"). The key terms of the SLA are as follows:
Uptime Commitment. Lumos commits to maintaining 99.95% availability of the platform, measured on a monthly basis. For a 30-day calendar month (43,200 minutes), this commitment translates to maximum allowable downtime of approximately 21.6 minutes per month. Uptime is measured by Lumos's designated third-party monitoring vendor, currently Sentinel Uptime Services Inc. The uptime calculation excludes scheduled maintenance windows (which must be noticed at least 72 hours in advance), force majeure events, and downtime attributable to Customer's systems, networks, or third-party services not provided by Lumos.
P1 Incident Response Times. For Priority 1 ("P1") incidents — defined as complete platform unavailability or degradation affecting core functionality for all users — Lumos commits to initial acknowledgment within 15 minutes and resolution or deployment of a reasonable workaround within 2 hours.
SLA Credit Tiers (Exhibit C, §3.2). If Lumos fails to meet the 99.95% uptime commitment in any given calendar month, Pinnacle is entitled to SLA credits according to the following graduated schedule:
SLA Credit Cap (Exhibit C, §3.4). The maximum aggregate SLA credits that may be issued in any rolling 12-month period shall not exceed 30% of the annual subscription fee. At Pinnacle's annual fee of $1,440,000, this cap equals $432,000.
Limitation of Liability (MSA §11.2). The aggregate liability of either party under the MSA — whether arising in contract, tort, strict liability, or otherwise — shall not exceed the total fees paid by Customer during the 12-month period immediately preceding the event giving rise to the claim. For Pinnacle, this cap equals $1,440,000.
Mutual Waiver of Consequential Damages (MSA §11.3). Neither party shall be liable to the other for any indirect, incidental, consequential, special, or exemplary damages, including but not limited to damages for lost profits, lost revenue, loss of goodwill, loss of data, or business interruption, arising out of or in connection with the MSA, regardless of the cause of action or the theory of liability, even if such party has been advised of the possibility of such damages.
Credit Request Procedure (Exhibit C, §3.5). Customer must submit a written credit request within 30 calendar days of the end of the affected calendar month, specifying the affected services and the observed downtime. Failure to submit a timely credit request shall constitute a waiver of Customer's right to receive SLA credits for the applicable month. Credit requests must be submitted to Lumos's designated support portal or via email to the assigned Customer Success Manager.
Governing Law (MSA §14.1). The MSA is governed by and construed in accordance with the laws of the State of California, without regard to its conflict-of-laws principles.
Dispute Resolution (MSA §14.3). Prior to initiating any litigation, the parties agree to participate in good-faith mediation in San Francisco, California. If mediation does not resolve the dispute within 60 days of the initial mediation session, either party may pursue litigation. The parties consent to the exclusive jurisdiction of the state and federal courts located in San Francisco County, California.
B. The Four Alleged Incidents
Pinnacle's demand letter identifies four incidents that it asserts triggered SLA credit obligations. The following table summarizes Pinnacle's claimed outage durations, its calculated monthly uptime percentages, and the corresponding credit amounts Pinnacle demands:
Pinnacle's total SLA credit claim: $120,000.
We note that Lumos's own uptime data, as recorded by Sentinel Uptime Services Inc. — Lumos's designated third-party monitoring vendor under Exhibit C — reflects materially shorter outage durations for several of these incidents. Under Lumos's data, the total credit obligation would be approximately $90,000 rather than $120,000. As noted above, the divergence between Pinnacle's and Lumos's uptime measurements is the subject of a separate Uptime Data Analysis Memorandum and is not addressed in detail here. For purposes of this memorandum's liability-cap and contractual-defenses analysis, we present exposure ranges based on both Pinnacle's data and Lumos's data.
C. Pinnacle's Full Demand
Pinnacle's demand, as set forth in the May 1, 2023 letter from Katherine Hargrove of Hargrove, Tillman & Burch LLP, is as follows:
The demand was communicated via letter from Katherine Hargrove (lead partner) and Daniel Yun (associate) of Hargrove, Tillman & Burch LLP, dated May 1, 2023. The letter characterizes the demand as reflecting both "contractual credit obligations and direct and consequential damages arising from Lumos's repeated and material breaches of its service level commitments." Pinnacle's counsel asserts that the SLA credit schedule represents a minimum remedy rather than an exclusive one, and that Pinnacle is entitled to recover the full measure of its actual losses. As analyzed below, this characterization is incorrect and contradicted by the express terms of the MSA and Exhibit C.
III. Defense No. 1: SLA Credit Cap (Exhibit C, §3.4)
A. The Contractual Provision
Section 3.4 of Exhibit C to the MSA provides:
"Notwithstanding anything to the contrary in this Exhibit C, the maximum aggregate SLA credits that may be issued to Customer in any rolling twelve (12) month period shall not exceed thirty percent (30%) of the annual subscription fee then in effect. Any credits that would otherwise be owed in excess of such maximum shall be forfeited, and Provider shall have no obligation to issue such excess credits."
At Pinnacle's annual subscription fee of $1,440,000, the SLA credit cap equals $432,000 per rolling 12-month period. This cap operates as an absolute ceiling on the credit remedy available under Exhibit C, regardless of the number, frequency, or severity of qualifying incidents during the applicable measurement period.
The credit cap provision is unambiguous. It uses mandatory language ("shall not exceed") and expressly addresses the consequence of credits exceeding the cap ("shall be forfeited"). There is no exception, carve-out, or escalation mechanism that would permit credits in excess of the cap under any circumstances.
B. Application to Pinnacle's Claims
All four incidents identified in Pinnacle's demand letter — INC-4471 (October 2022), INC-4602 (November 2022), INC-4815 (January 2023), and INC-5033 (March 2023) — occurred within a single rolling 12-month period (October 2022 through March 2023). Even if every incident were credited at the maximum 30% tier ($36,000 per month), the four incidents would produce $144,000 in total credits ($36,000 × 4 months), which is well within the $432,000 cap.
Pinnacle's own SLA credit claim of $120,000 is itself below the $432,000 cap, so the cap does not, as a mechanical matter, reduce Pinnacle's SLA credit claim in this particular dispute. However, the credit cap defense remains critically important for two reasons.
First, the cap is essential as a defense against Pinnacle's broader litigation theory. Pinnacle's demand letter, through its counsel at Hargrove, Tillman & Burch, suggests entitlement to damages above and beyond the credit schedule set forth in Exhibit C. Pinnacle appears to treat SLA credits as a floor — a minimum amount of compensation — rather than as the exclusive and capped remedy the MSA contemplates. The credit cap, read in conjunction with the exclusive remedy clause in Section 3.2 and the aggregate liability cap in Section 11.2, refutes this characterization.
Second, the credit cap provides certainty regarding the outer boundary of Lumos's SLA-specific exposure. Even in a hypothetical scenario in which Lumos experienced prolonged or repeated outages over a 12-month period, the credit cap would limit total credit obligations to $432,000. This is a meaningful and commercially significant protection that the parties specifically negotiated at the time of contracting.
Section 3.4 should be read in conjunction with MSA Section 11.2 (the aggregate liability cap) as establishing a layered framework of liability limitations. The SLA credit cap limits the credit-specific remedy; the aggregate cap limits total liability under the MSA irrespective of the form of claim or theory of recovery.
C. SLA Credits as Exclusive Remedy
The credit cap defense is reinforced by the exclusive remedy clause in Exhibit C, Section 3.2, which provides:
"The service credits set forth in this Section 3.2 shall constitute Customer's sole and exclusive remedy for any failure by Provider to meet the service levels set forth in this Exhibit C."
This language is clear and unequivocal. The SLA credit schedule is not merely one of several potential remedies for uptime failures; it is the only remedy. By its terms, the exclusive remedy clause channels all claims arising from SLA non-compliance — including claims that might otherwise sound in breach of contract, negligence, or breach of warranty — into the credit framework established by Section 3.2. And because the credit framework is, in turn, subject to the credit cap in Section 3.4, the maximum exposure for any and all SLA-related claims is $432,000 per rolling 12-month period.
Under California law, "sole and exclusive remedy" clauses in commercial SaaS agreements are generally enforceable between sophisticated parties who have negotiated their contracts at arm's length. California courts have consistently recognized that commercial parties are free to allocate risk and limit remedies through their agreements, and that such allocations will be upheld absent unconscionability, fraud, or a failure of essential purpose.
Pinnacle is a sophisticated commercial entity. As a financial services firm with approximately $4.2 billion in assets under management, Pinnacle possesses substantial bargaining power and commercial sophistication. Pinnacle was represented by experienced counsel during the negotiation of the MSA, and there is no indication that Pinnacle was deprived of the opportunity to negotiate the credit schedule, the credit cap, or the exclusive remedy clause. The MSA was the product of arm's-length negotiation between two well-resourced commercial entities, and the exclusive remedy clause reflects their mutual agreement regarding the allocation of risk associated with service-level failures.
Interaction with MSA §11.2 Aggregate Liability Cap. Even if a court or arbitrator were to determine that the exclusive remedy clause in Section 3.2 is inapplicable — an unlikely outcome given the clarity of the contractual language — the aggregate liability cap in MSA Section 11.2 provides a secondary ceiling on Lumos's total liability. Section 11.2 limits the aggregate liability of either party to the total fees paid during the 12-month period immediately preceding the event giving rise to the claim, which equals $1,440,000. This cap applies to all claims under the MSA, regardless of the form of action or theory of liability, and operates as an independent limitation that does not depend on the enforceability of the exclusive remedy clause.
D. California Law on SLA Credit Caps
California courts generally enforce contractual limitations on remedies in arm's-length commercial transactions between sophisticated parties. This principle is well established in both California common law and the California Commercial Code.
California Commercial Code Section 2719. Although the California Commercial Code's Article 2 provisions apply most directly to transactions in goods, California courts have frequently applied Section 2719 by analogy in the context of software licensing and technology services agreements. Section 2719(1)(a) permits parties to provide for remedies "in addition to or in substitution for those provided in this division and may limit or alter the measure of damages recoverable under this division, as by limiting the buyer's remedies to return of the goods and repayment of the price or to repair and replacement of non-conforming goods or parts." Section 2719(1)(b) further provides that "[r]esort to a remedy as provided is optional unless the remedy is expressly agreed to be exclusive, in which case it is the sole remedy."
The critical limitation on exclusive remedy clauses is found in Section 2719(2), which provides that "[w]here circumstances cause an exclusive or limited remedy to fail of its essential purpose, remedy may be had as provided in this code." The "failure of essential purpose" doctrine is the principal legal basis on which a party might challenge an SLA credit cap.
The Credit Remedy Does Not Fail of Its Essential Purpose. The credit schedule in Exhibit C, Section 3.2, provides graduated relief that is proportional to the severity of the service-level failure. Credits range from 5% of the monthly fee for minor shortfalls (uptime between 99.90% and 99.94%) to 30% of the monthly fee for significant outages (uptime below 99.00%). The credit cap of $432,000 per rolling 12-month period represents 30% of the annual subscription fee — a substantial sum that provides meaningful financial compensation for service-level failures. The credit mechanism is functional: it has been available to Pinnacle throughout the term of the MSA, credits have been calculated and issued for qualifying incidents, and the graduated structure ensures that more severe outages yield proportionally greater credits. There is no basis for concluding that the remedy has failed of its essential purpose.
If Pinnacle argues that the remedy fails of its essential purpose because its alleged losses ($2,870,000) far exceed the credit cap ($432,000), Lumos can respond that the failure-of-essential-purpose doctrine focuses on whether the remedy mechanism itself functions as intended — not on whether the remedy is sufficient to compensate for all conceivable losses. The credit cap was the product of negotiation between sophisticated parties, it was reflected in the subscription pricing (which Pinnacle negotiated knowing the scope of the available remedy), and both parties are sophisticated commercial actors who understood the risk allocation the contract embodied. The fact that a party's actual losses may exceed a contractual limitation does not, standing alone, render the limitation unenforceable under California law.
E. Conclusion on SLA Credit Cap
The SLA credit cap of $432,000 per rolling 12-month period, combined with the exclusive remedy clause in Exhibit C, Section 3.2, limits Lumos's exposure for all SLA-related claims to a maximum of $432,000. This is far below Pinnacle's total demand of $2,870,000 and, indeed, well above even Pinnacle's own SLA credit calculation of $120,000. The credit cap does not reduce Pinnacle's SLA credit claim on its own terms in this dispute — Pinnacle's $120,000 claim is within the cap — but it forecloses Pinnacle's broader argument that it is entitled to damages beyond the credit schedule. The credit cap, exclusive remedy clause, and aggregate liability cap operate together as a comprehensive framework limiting Lumos's contractual exposure.
Risk Level: Low. The SLA credit cap defense is well-supported by the plain language of Exhibit C, Section 3.4, the exclusive remedy clause in Section 3.2, and California law governing the enforceability of contractual limitation-of-remedies provisions between sophisticated commercial parties.
IV. Defense No. 2: Mutual Waiver of Consequential Damages (MSA §11.3)
A. The Contractual Provision
Section 11.3 of the MSA provides, in relevant part:
"IN NO EVENT SHALL EITHER PARTY BE LIABLE TO THE OTHER PARTY FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL, OR EXEMPLARY DAMAGES, INCLUDING BUT NOT LIMITED TO DAMAGES FOR LOST PROFITS, LOST REVENUE, LOSS OF GOODWILL, LOSS OF DATA, OR BUSINESS INTERRUPTION, ARISING OUT OF OR IN CONNECTION WITH THIS AGREEMENT, REGARDLESS OF THE CAUSE OF ACTION OR THE THEORY OF LIABILITY, EVEN IF SUCH PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES."
Several features of this provision merit emphasis. First, the waiver is mutual — it applies equally to both Lumos and Pinnacle. This mutuality is significant because it negates any argument that the provision was imposed unilaterally by the party with superior bargaining power. Both parties accepted the same limitation on their respective rights to recover consequential damages.
Second, the waiver is broadly drafted. It encompasses "indirect, incidental, consequential, special, or exemplary damages," and the illustrative list — "lost profits, lost revenue, loss of goodwill, loss of data, or business interruption" — directly targets precisely the categories of damages that Pinnacle now seeks to recover.
Third, the waiver applies "regardless of the cause of action or the theory of liability." This language was included to prevent a party from circumventing the waiver by recasting its claims in tort (e.g., negligence, negligent misrepresentation) rather than contract. The waiver applies irrespective of how Pinnacle frames its claims.
Fourth, the waiver applies "even if such party has been advised of the possibility of such damages." This language eliminates any argument based on Hadley v. Baxendale foreseeability — i.e., that Lumos should be liable for consequential damages because it knew or should have known that its service failures would cause downstream business losses to Pinnacle.
This type of mutual consequential damages waiver is standard in enterprise SaaS agreements and reflects a well-understood commercial allocation of risk. The SaaS provider limits its exposure to the fees it receives; the customer accepts the limitation in exchange for pricing that reflects the provider's reduced risk. Both parties benefit from certainty regarding the scope of potential liability.
B. Application to Pinnacle's Non-Credit Claims
Pinnacle's total demand of $2,870,000 includes $2,750,000 in damages beyond SLA credits. Each of these non-credit damage categories falls squarely within the scope of the consequential damages waiver in Section 11.3.
Lost Revenue from Delayed Loan Originations and Missed Trading Windows ($1,950,000). This is a textbook consequential damages or lost-profits claim. Pinnacle alleges that platform outages caused downstream business losses in its commercial lending and trading operations — specifically, that Pinnacle was unable to originate certain loans and missed trading windows during the periods of platform unavailability. These are classic indirect damages: they flow from the alleged service interruption but are not damages for the cost of the service itself. They are, instead, damages for the impact of the service interruption on Pinnacle's separate business activities. Section 11.3 expressly lists "lost profits," "lost revenue," and "business interruption" among the categories of excluded damages. The $1,950,000 lost-revenue claim is barred in its entirety by Section 11.3.
Internal Remediation Costs ($340,000). Pinnacle claims $340,000 in costs for manual workarounds, employee overtime, and the temporary licensing of a competitor platform — TrueNorth Data Systems Inc. — to provide substitute analytics services during the outage periods. This category requires closer analysis because some remediation or "cover" costs might, in certain circumstances, be characterized as direct rather than consequential damages.
However, the bulk of these claimed costs — including overtime labor reallocation, the cost of retraining personnel on a temporary substitute platform, and the licensing fees for TrueNorth Data Systems — are consequential in nature. They flow from the alleged breach but are not the cost of the contracted-for service itself. The direct cost of the service is the $120,000 monthly subscription fee that Pinnacle pays to Lumos; remediation costs that Pinnacle incurs to address the downstream effects of an outage are consequential damages arising from the breach, not direct damages for the value of the service not received. Section 11.3's reference to "business interruption" damages further supports the conclusion that internal remediation costs — which are, by definition, costs incurred to mitigate business interruption — fall within the scope of the waiver.
Even if a court were to characterize a portion of the remediation costs as direct damages — for example, the cost of licensing TrueNorth as "cover" — those costs would still be subject to the aggregate liability cap of $1,440,000 under MSA Section 11.2 and, to the extent they arise from uptime failures, would be channeled into the exclusive SLA credit remedy under Exhibit C, Section 3.2. In any event, the remediation costs cannot exceed the aggregate cap, and Pinnacle cannot use a remediation-costs theory to circumvent the contractual framework.
Reputational Harm / Client Attrition ($460,000). Pinnacle claims $460,000 representing the estimated value of two wealth-management clients that allegedly left Pinnacle due to service disruptions caused by platform outages. This claim is squarely consequential: it involves loss of goodwill, loss of business relationships, and indirect revenue impact from the departure of clients who were not parties to the MSA and whose decisions to leave Pinnacle involved intervening factors entirely outside Lumos's control. Section 11.3 expressly bars "loss of goodwill" damages. Moreover, the $460,000 figure is inherently speculative — it is based on Pinnacle's estimate of the future revenue it would have earned from two clients whose actual reasons for departing are unknown and unverified. This claim is clearly barred by Section 11.3.
Total Amount Barred by Section 11.3: $2,750,000. The consequential damages waiver eliminates the entirety of Pinnacle's non-credit demand, leaving only the SLA credit claim of $120,000 (as reduced or modified by the other defenses discussed in this memorandum).
C. Enforceability Under California Law
California courts consistently enforce mutual consequential damages waivers in commercial contracts between sophisticated parties. The enforceability of such provisions is well established under both California common law and the California Commercial Code.
California Commercial Code Section 2719(3). Section 2719(3) provides that "[c]onsequential damages may be limited or excluded unless the limitation or exclusion is unconscionable. Limitation of consequential damages for injury to the person in the case of consumer goods is prima facie unconscionable but limitation of damages where the loss is commercial is not." This provision creates a clear presumption: in commercial transactions between business entities, the limitation or exclusion of consequential damages is not unconscionable. Pinnacle bears the burden of overcoming this presumption, and the circumstances of this transaction make it exceedingly unlikely that Pinnacle could do so.
No Indicia of Procedural Unconscionability. Procedural unconscionability requires a showing of oppression or surprise — circumstances indicating that one party lacked meaningful choice or was subjected to unfair bargaining tactics. None of those circumstances exist here. The MSA was negotiated at arm's length between two sophisticated commercial entities with substantial resources and experienced counsel. Pinnacle, with $4.2 billion in AUM and a dedicated vendor management team, had bargaining power commensurate with its status as a significant enterprise customer paying $1,440,000 per year. There is no evidence of surprise — the consequential damages waiver appears in a conspicuous, capitalized provision in Article 11 of the MSA, and there is no indication that it was hidden, obscured, or presented on a take-it-or-leave-it basis. There is no evidence of oppression — Pinnacle was free to negotiate the terms of the MSA, and indeed the negotiation process involved multiple rounds of redlining and revision over a period of approximately three months prior to execution.
No Indicia of Substantive Unconscionability. Substantive unconscionability requires a showing that the contractual terms are unreasonably favorable to one party. The mutual nature of the consequential damages waiver in Section 11.3 negates this argument. The waiver applies equally to both parties: Lumos cannot recover consequential damages from Pinnacle any more than Pinnacle can recover consequential damages from Lumos. The mutuality of the provision reflects a balanced and commercially reasonable allocation of risk. Moreover, the consequential damages waiver is standard in the enterprise SaaS industry — it appears in the vast majority of negotiated SaaS agreements between enterprise vendors and their customers. The provision is not unusual, unexpected, or commercially unreasonable.
D. Potential Counterarguments and Responses
We have identified four potential counterarguments that Pinnacle or its counsel might advance in an effort to defeat or circumvent the consequential damages waiver. None of these arguments is likely to succeed, but each merits brief analysis.
1. Remediation Costs Are Direct Damages, Not Consequential. Pinnacle may argue that its $340,000 in remediation costs — including overtime, manual workarounds, and the temporary licensing of TrueNorth Data Systems — constitute direct damages rather than consequential damages and therefore fall outside the scope of the Section 11.3 waiver. This argument has some surface plausibility with respect to the TrueNorth licensing costs, which might be analogized to "cover" damages under UCC Section 2-712.
Response: Even if a court were to characterize some portion of the remediation costs as direct damages, this would not assist Pinnacle materially. Direct damages for uptime failures are channeled into the exclusive SLA credit remedy under Exhibit C, Section 3.2, and are subject to the $432,000 credit cap under Section 3.4. To the extent any remediation costs are deemed direct damages not subject to the exclusive SLA credit remedy — an analytical stretch — they would still be subject to the aggregate liability cap of $1,440,000 under Section 11.2. The direct/consequential distinction does not provide Pinnacle a path to recovering the full $2,870,000 demand.
2. The Consequential Damages Waiver Is Unconscionable. Pinnacle may argue that the waiver is unconscionable under California Commercial Code Section 2719(3) or under general California unconscionability doctrine.
Response: As discussed above, this argument is very unlikely to succeed. The waiver is mutual, was negotiated at arm's length between sophisticated parties with comparable bargaining power, and is standard in enterprise SaaS agreements. California Commercial Code Section 2719(3) creates a presumption that limitations on consequential damages in commercial transactions are not unconscionable, and Pinnacle bears the heavy burden of overcoming that presumption. Given the absence of any indicia of either procedural or substantive unconscionability, this argument should fail.
3. Willful Breach Vitiates the Consequential Damages Waiver. Pinnacle may argue that Lumos's service-level failures were so frequent or severe as to constitute willful or intentional breach, and that a party should not be permitted to shield itself from consequential damages for deliberate or willful misconduct.
Response: There is no evidence of willful or intentional breach. The service outages at issue were unintentional infrastructure events — they involved database failover delays (INC-4471), API gateway congestion (INC-4602), a data-center power excursion (INC-4815), and a cloud-infrastructure failure at Brindoval Cloud Infrastructure LLC (INC-5033). None of these incidents was caused by deliberate misconduct, and there is no basis for characterizing Lumos's conduct as willful. Moreover, even if willful breach were established (which it cannot be on these facts), Section 11.3 applies "regardless of the cause of action or the theory of liability." This broad language indicates that the parties intended the waiver to apply to all claims, including claims based on theories that might implicate intentionality. While there is a minority line of authority in some jurisdictions suggesting that consequential damages waivers should not apply to willful breach, California courts have not adopted such a rule as a per se matter, and the contractual language here supports application of the waiver regardless of the nature of the breach.
4. The SLA Credit Remedy Fails of Its Essential Purpose, Unlocking Full Damages. Pinnacle may argue that because the SLA credit remedy is capped at $432,000 while its actual losses exceed $2,870,000, the remedy has "failed of its essential purpose" under California Commercial Code Section 2719(2), and that the failure of essential purpose should vitiate not only the exclusive remedy clause but also the consequential damages waiver.
Response: As discussed in Part III.D above, the credit remedy has not failed of its essential purpose. The credit mechanism is functional, provides graduated relief proportional to the severity of the failure, and permits up to $432,000 in annual credits — a substantial sum. The failure-of-essential-purpose doctrine applies when the contractual remedy mechanism is inoperative or otherwise unable to fulfill its intended function (e.g., when a repair-or-replace warranty fails because the seller is unable or unwilling to repair or replace the defective product). It does not apply merely because a party's actual losses exceed the cap on the contractual remedy. Furthermore, even in jurisdictions that have held that a failure of essential purpose vitiates the exclusive remedy clause, courts are divided on whether such failure also eliminates the consequential damages waiver. Under the better-reasoned approach, these are independent provisions: the exclusive remedy clause and the consequential damages waiver serve different functions, were separately negotiated, and should be enforced independently. Section 11.3 is not dependent on the enforceability of the exclusive remedy clause in Section 3.2.
E. Conclusion on Consequential Damages Waiver
Section 11.3 of the MSA bars Pinnacle's claims for lost revenue ($1,950,000), internal remediation costs ($340,000), and reputational harm ($460,000) — totaling $2,750,000. This defense eliminates approximately 95.8% of Pinnacle's total demand ($2,750,000 of $2,870,000), leaving only the SLA credit claim of $120,000 at issue.
The consequential damages waiver is the single most impactful defense available to Lumos in this dispute. It is supported by clear and unambiguous contractual language, the mutual nature of the provision, the sophistication of the parties, and well-established California law. The potential counterarguments — unconscionability, willful breach, failure of essential purpose — are weak on these facts and unlikely to succeed.
Risk Level: Low. This is a strong defense with robust contractual language and favorable California case law. We assess the likelihood of a court or mediator invalidating Section 11.3 on these facts as very low.
V. Defense No. 3: Timeliness of Credit Request for INC-4471 (Exhibit C, §3.5)
A. The Contractual Provision
Section 3.5 of Exhibit C to the MSA establishes the procedural requirements for SLA credit requests:
"Customer must submit a written credit request within thirty (30) calendar days of the end of the affected calendar month, specifying the affected services and the observed downtime. Failure to submit a timely credit request shall constitute a waiver of Customer's right to receive SLA credits for the applicable month."
Two features of this provision are significant. First, it uses mandatory language — "must submit" — that leaves no discretion regarding the filing deadline. Second, it includes an express waiver consequence: failure to submit a timely request "shall constitute a waiver" of the right to credits for that month. The provision does not use permissive or discretionary language (such as "may" or "should"), nor does it provide for extensions, exceptions, or a cure period. The consequence of untimely submission is automatic forfeiture of the credit for the applicable month.
B. Facts Relevant to INC-4471
Incident INC-4471 occurred on October 12–13, 2022. Pinnacle alleges that the incident resulted in 7 hours and 42 minutes of downtime, reducing October 2022 uptime to 98.93% and triggering the maximum 30% credit tier ($36,000). Lumos's data from Sentinel Uptime Services Inc. indicates a shorter outage duration, corresponding to a 99.43% uptime level and the 20% credit tier ($24,000). The discrepancy in uptime measurement is addressed in the companion Uptime Data Analysis Memorandum.
For purposes of the timeliness defense, the relevant facts are as follows:
• The affected calendar month is October 2022.
• The end of October 2022 is October 31, 2022.
• The 30-calendar-day deadline under Section 3.5 is November 30, 2022.
• Pinnacle submitted its credit request for INC-4471 on December 14, 2022.
• The submission was therefore made 44 days after the end of October 2022, exceeding the 30-day deadline by 14 days.
The December 14, 2022 submission date is confirmed by the timestamp on Pinnacle's credit request as logged in Lumos's customer support portal. There is no dispute regarding the date of submission; Pinnacle's own demand letter acknowledges the December 14 submission date and does not contend that the request was submitted earlier through any alternative channel.
C. Enforceability of Contractual Deadlines Under California Law
California law generally enforces contractual notice and claim deadlines in commercial agreements. The legal analysis of the Section 3.5 deadline depends on its characterization: Is it a procedural notice requirement subject to substantial-compliance and prejudice standards, or is it a condition precedent to the right to receive the credit remedy?
The language of Section 3.5 supports characterization as a condition precedent. The provision does not merely require Pinnacle to "notify" Lumos of an outage or to "report" an incident within a particular timeframe. Instead, it requires Pinnacle to "submit a written credit request" — i.e., to invoke its right to the credit remedy — within 30 calendar days. And the provision expressly states that failure to comply "shall constitute a waiver" of the right to credits. A waiver is the intentional relinquishment of a known right. By deeming untimely submission a "waiver," Section 3.5 makes timely submission an essential precondition to the credit remedy, not merely a procedural formality.
Courts draw a meaningful distinction between notice provisions — which are often subject to substantial-compliance analysis and may require a showing of prejudice before non-compliance results in forfeiture — and claim-filing provisions that operate as conditions precedent to a remedy. Section 3.5 falls squarely in the latter category. It conditions Pinnacle's entitlement to credits on the timely submission of a credit request, and it attaches an express forfeiture consequence to non-compliance.
The 30-day window is reasonable and commercially standard. Enterprise SaaS agreements commonly include credit-request deadlines of 30 to 60 days, and the 30-day period provides Pinnacle ample time to review its monthly service performance data, identify qualifying incidents, calculate the applicable credit tier, and submit a written request. There is nothing unusual or unduly restrictive about the deadline.
D. Potential Counterarguments and Responses
1. Waiver by Lumos
Pinnacle may argue that Lumos waived the Section 3.5 deadline by engaging with Pinnacle on the INC-4471 incident without raising the timeliness objection, or by a course of dealing in which late credit submissions were previously accepted without objection.
Response: Whether this argument has any factual basis depends on the historical record of Lumos's enforcement of the Section 3.5 deadline. If Lumos has consistently enforced the 30-day deadline and has previously rejected or objected to late credit requests — whether from Pinnacle or from other customers under similar MSAs — the waiver argument fails. If, on the other hand, Lumos has a history of accepting late credit requests without objection, Pinnacle may have a stronger argument that Lumos waived strict compliance with the deadline through a course of dealing.
Additionally, the MSA likely contains an anti-waiver or "no waiver" clause — typically found in Article 14 or Article 15 (General Provisions) — providing that the failure of either party to enforce any provision of the MSA shall not constitute a waiver of such provision or of the right to enforce it in the future. If such a clause exists, it reinforces Lumos's ability to enforce the Section 3.5 deadline even if there were prior instances of lax enforcement.
Recommendation: We recommend confirming with Adriana Voss (General Counsel) and Rachel Dominguez (VP of Customer Success) whether there is any history of Lumos accepting late credit requests from Pinnacle or from other customers. We also recommend confirming the existence and precise language of any anti-waiver clause in the MSA's general provisions.
2. Estoppel. Pinnacle may argue that Lumos is equitably estopped from enforcing the Section 3.5 deadline if Lumos made representations — express or implied — that the deadline would not be strictly enforced, and Pinnacle reasonably relied on such representations to its detriment.
Response: Equitable estoppel requires (a) a representation by Lumos that the deadline would not be enforced; (b) reasonable reliance by Pinnacle on that representation; and (c) detriment to Pinnacle resulting from the reliance. In the absence of an affirmative representation by Lumos — whether in writing, orally, or through a clear pattern of conduct — estoppel should not apply. The mere fact that Lumos engaged with Pinnacle on the substance of the INC-4471 incident (e.g., discussing root cause or incident response) does not constitute a representation that the credit-request deadline would be waived.
Recommendation: We recommend reviewing all correspondence between Lumos personnel (specifically Thomas Kwan, Director of Technical Support, and Rachel Dominguez, VP of Customer Success) and Pinnacle personnel (Sandra Keppler and Naveen Mistry) regarding the INC-4471 incident and credit request. If any Lumos representative made a statement suggesting that the late submission would be accepted or that the deadline was flexible, the estoppel risk increases, and we would need to reassess the strength of this defense.
3. Substantial Compliance
Pinnacle may argue that its December 14, 2022 submission was in "substantial compliance" with the spirit of Section 3.5, or that the 14-day delay beyond the 30-day window was de minimis and should not result in forfeiture of the credit.
Response: The substantial-compliance doctrine is generally inapplicable where the contract includes express, mandatory language with a specified consequence for non-compliance. Section 3.5 uses the word "must," specifies a 30-day deadline, and provides that failure to comply "shall constitute a waiver." This is not a provision that invites a substantial-compliance analysis. The express waiver clause eliminates any argument that approximate or near-compliance is sufficient.
Moreover, the delay was not de minimis. A 14-day overshoot on a 30-day deadline represents a 47% overrun beyond the contractual window. This is not a case of a credit request submitted one or two days late; it is a case of a request submitted nearly two weeks after the deadline. While the characterization of any particular delay as "de minimis" is inherently subjective, a 47% overrun significantly undermines any claim that Pinnacle substantially complied with the deadline.
4. Prejudice Requirement
Pinnacle may argue that Lumos must demonstrate that it was prejudiced by the late submission — i.e., that the 14-day delay caused Lumos some concrete harm — before the forfeiture consequence should apply.
Response: Where the contract expressly provides that untimely submission "shall constitute a waiver" of the right to credits, California courts generally enforce the provision as written, without requiring a separate showing of prejudice by the non-breaching party. The prejudice requirement is more commonly applied in the insurance-law context, where courts have held that an insurer must demonstrate prejudice from late notice before it can deny coverage based on a late-notice defense. The insurance-law prejudice rule reflects policy considerations specific to the insured-insurer relationship and does not apply to arm's-length commercial SaaS credit-claim procedures.
Section 3.5 is not a general notice provision — it is a claim-filing deadline with an express forfeiture consequence. The parties specifically agreed that untimely submission would constitute a waiver, and there is no basis for grafting a judicially created prejudice requirement onto the provision. Requiring a showing of prejudice would effectively rewrite the parties' agreement and deprive Lumos of the benefit of the bargain it negotiated.
E. Impact on Overall Exposure
If the timeliness defense succeeds, Pinnacle loses the INC-4471 credit entirely. This reduces Pinnacle's SLA credit claim as follows:
• Under Pinnacle's data: From $120,000 to $84,000 ($120,000 minus $36,000)
• Under Lumos's Sentinel data: From $90,000 to $66,000 ($90,000 minus $24,000)
While the dollar amount at stake — $24,000 to $36,000 — is relatively modest in the context of the overall dispute, the timeliness defense is strategically significant for several reasons. First, it demonstrates that Pinnacle failed to comply with the very contractual procedures it now seeks to enforce, undermining Pinnacle's broader narrative that Lumos is the party in breach. Second, it reduces Lumos's total credit exposure, potentially to as little as $66,000 under Lumos's own uptime data. Third, it provides additional leverage in mediation and settlement discussions by narrowing the scope of Pinnacle's credible claims.
F. Conclusion on Timeliness Defense
Pinnacle's credit request for INC-4471 was submitted on December 14, 2022 — 44 days after the end of the affected calendar month (October 2022) and 14 days beyond the 30-calendar-day deadline established by Exhibit C, Section 3.5. The express waiver language in Section 3.5 supports forfeiture of the INC-4471 credit in its entirety.
The potential counterarguments — waiver by Lumos, estoppel, substantial compliance, and a prejudice requirement — are weak given the express terms of the contract and the sophistication of the parties. However, we recommend confirming the factual record regarding Lumos's prior enforcement practices to ensure the absence of any course of dealing that might support a waiver or estoppel argument.
Risk Level: Low to Moderate. The defense is well-grounded in the contract language and California law, but there is some residual risk that a mediator or court might give weight to equitable considerations, particularly if there is any evidence of inconsistent enforcement by Lumos. We rate this risk as manageable, and the defense should be asserted.
VI. Interaction of Defenses with Aggregate Liability Cap (MSA §11.2)
Separate from the three principal defenses analyzed above, the aggregate liability cap in MSA Section 11.2 provides an additional, independent layer of protection for Lumos. Section 11.2 provides:
"IN NO EVENT SHALL THE AGGREGATE LIABILITY OF EITHER PARTY UNDER THIS AGREEMENT EXCEED THE TOTAL FEES PAID BY CUSTOMER DURING THE TWELVE (12) MONTH PERIOD IMMEDIATELY PRECEDING THE EVENT GIVING RISE TO THE CLAIM, REGARDLESS OF THE FORM OF ACTION OR THEORY OF LIABILITY."
At Pinnacle's annual subscription fee of $1,440,000, the aggregate liability cap equals $1,440,000.
Pinnacle's total demand of $2,870,000 exceeds this cap by $1,430,000. Even if the consequential damages waiver in Section 11.3 were struck down — an outcome we assess as highly unlikely — the aggregate cap would independently limit Pinnacle's maximum recovery to $1,440,000. And Pinnacle would still need to prove its alleged damages (including the speculative lost-revenue and reputational-harm claims) to recover up to the cap.
The aggregate liability cap and the consequential damages waiver operate as independent, layered protections. They serve different functions and are enforceable on different grounds. The consequential damages waiver limits the types of damages recoverable; the aggregate cap limits the total amount recoverable regardless of damage type. Even if one provision were invalidated, the other would remain in force. This layered structure is deliberate and reflects the parties' intent to create multiple independent protections against excessive liability exposure.
The aggregate liability cap is subject to the same enforceability analysis as the other contractual limitations discussed in this memorandum. It was negotiated at arm's length between sophisticated parties, is mutual in nature, and is standard in enterprise SaaS agreements. California courts consistently enforce such caps in commercial transactions. The cap is not unconscionable, and Pinnacle has no basis for challenging it.
VII. Summary of Maximum Exposure Analysis
The following analysis presents Lumos's maximum exposure under four scenarios, ranging from the best-case scenario (all defenses upheld, Lumos's uptime data applied, and the INC-5033 third-party causation defense successful) to the absolute worst-case scenario (all contractual defenses fail).
A. Best-Case Scenario for Lumos
Under the best-case scenario, all three contractual defenses analyzed in this memorandum are upheld, Lumos's Sentinel uptime data is used for credit calculations, and the separate INC-5033 third-party causation defense succeeds:
• INC-4471 credit request time-barred under §3.5: $0
• INC-4602 credit per Sentinel data (99.77% uptime, 5% tier): $6,000
• INC-4815 credit per Sentinel data (99.43% uptime, 20% tier): $24,000
• INC-5033 excluded under §2.3 (third-party cause — Brindoval Cloud Infrastructure LLC failure and Pinnacle's failure to activate US-West-2 failover): $0
• All consequential/indirect damages barred under §11.3: $0
Best-case maximum exposure: $30,000
B. Worst-Case Scenario for Lumos (All Contractual Defenses Upheld, Pinnacle's Uptime Data)
Under this scenario, all three contractual defenses are upheld but Pinnacle's uptime data is used for credit calculations (i.e., Lumos does not prevail on the uptime measurement dispute), and the INC-5033 third-party causation defense is not applied:
• INC-4471 time-barred under §3.5: $0
• INC-4602 credit per Pinnacle's data (99.54% uptime, 10% tier): $12,000
• INC-4815 credit per Pinnacle's data (98.47% uptime, 30% tier): $36,000
• INC-5033 credit per Pinnacle's data (96.32% uptime, 30% tier): $36,000
• All consequential/indirect damages barred under §11.3: $0
Worst-case with defenses: $84,000
C. Scenario Without Timeliness Defense
Under this scenario, the timeliness defense for INC-4471 is not asserted or does not succeed, but the SLA credit cap and consequential damages waiver are upheld, and Pinnacle's uptime data is used:
• INC-4471 credit per Pinnacle's data (98.93% uptime, 30% tier): $36,000
• INC-4602 credit per Pinnacle's data: $12,000
• INC-4815 credit per Pinnacle's data: $36,000
• INC-5033 credit per Pinnacle's data: $36,000
• Total SLA credits: $120,000 (within $432,000 SLA credit cap)
• All consequential/indirect damages barred under §11.3: $0
Maximum exposure without timeliness defense: $120,000
D. Absolute Maximum (All Defenses Fail)
Under the absolute worst-case scenario — in which the consequential damages waiver is invalidated, the SLA credit cap is struck, and the exclusive remedy clause is deemed unenforceable — Lumos's exposure would be capped by the aggregate liability cap in MSA Section 11.2 at $1,440,000. Even in this scenario, Pinnacle would need to prove its actual damages, including the speculative lost-revenue claim ($1,950,000, which exceeds the aggregate cap on its own) and the highly speculative reputational-harm claim ($460,000). We assess the likelihood of all contractual defenses failing as extremely low.
Absolute maximum: $1,440,000 (subject to proof of damages)
E. Summary Table
The most likely range of Lumos's exposure, assuming the contractual defenses are upheld as we expect, is $66,000 to $432,000, with a realistic range of $66,000 to $120,000 depending on the resolution of the uptime measurement dispute and the timeliness defense.
VIII. Recommendations
A. Immediate Actions
Based on the analysis set forth in this memorandum, we recommend that Lumos take the following immediate steps:
1. Confirm Credit Request History. Adriana Voss (General Counsel) and Rachel Dominguez (VP of Customer Success) should confirm whether there is any prior history of Lumos accepting late SLA credit requests from Pinnacle — or from other customers under similar MSAs — without raising timeliness objections. If late credit requests have been accepted in the past without objection, the timeliness defense for INC-4471 is weakened. Conversely, if Lumos has consistently enforced the 30-day deadline, the defense is strengthened. This fact-finding is the single most important open item for the timeliness defense.
2. Confirm Anti-Waiver Clause. We recommend confirming the existence and precise language of the anti-waiver (or "no waiver") clause in the MSA's general provisions (likely in Article 14 or Article 15). Such a clause typically provides that the failure of either party to enforce any provision of the MSA shall not constitute a waiver of that provision or of the right to enforce it in the future. If this clause is present, it provides additional support for the timeliness defense and for Lumos's enforcement of the contractual limitations generally.
3. Review INC-4471 Correspondence. We recommend reviewing all internal and external correspondence between Lumos personnel (specifically Thomas Kwan, Director of Technical Support, and Rachel Dominguez, VP of Customer Success) and Pinnacle personnel (Sandra Keppler, SVP of Technology Operations, and Naveen Mistry, Director of Vendor Management) regarding the INC-4471 incident, the credit request, and the December 14, 2022 submission. We are specifically looking for any statements by Lumos representatives suggesting that the 30-day deadline was flexible, that the late submission would be accepted, or that Lumos was waiving strict compliance with Section 3.5. If any such statements exist, they would need to be addressed in our timeliness defense analysis.
4. Preserve Records. All records relevant to the Pinnacle dispute should continue to be preserved in accordance with the Litigation Hold Memorandum issued on May 15, 2023. We remind Adriana Voss and the Lumos team that the litigation hold applies to all documents, communications, and data related to the four incidents, the MSA, the SLA, and the Pinnacle relationship generally. Any questions about the scope of the litigation hold should be directed to this firm.
B. Strategic Recommendations
1. Lead with All Three Defenses. In any response to Pinnacle's counsel at Hargrove, Tillman & Burch LLP, we recommend emphasizing all three contractual defenses as the primary basis for rejecting the $2,870,000 demand. The response should make clear that Pinnacle's demand is contractually foreclosed and that Lumos's maximum exposure is limited to a fraction of the claimed amount.
2. Prioritize the Consequential Damages Waiver. The consequential damages waiver in Section 11.3 is the single most powerful defense available to Lumos. It eliminates 95.8% of Pinnacle's total demand ($2,750,000 of $2,870,000). The response to Pinnacle's counsel should lead with this defense, as it reframes the entire dispute from a $2.87 million claim to, at most, a $120,000 credit dispute.
3. Frame the Dispute as a Modest Credit Obligation. The SLA credit cap and timeliness defense should be used to frame the dispute as involving, at most, a modest credit obligation well within the ordinary course of the MSA's SLA framework. The response should convey that Lumos takes its service-level commitments seriously, that the SLA credit mechanism is functioning as intended, and that Lumos is prepared to address legitimate credit claims through the contractual framework — but that Pinnacle's demand for $2.87 million in damages is unsupported by the contract and barred by the MSA's liability-limitation provisions.
4. Reserve Additional Defenses. The third-party causation defense for INC-5033 (attributable to Brindoval Cloud Infrastructure LLC) and the mitigation-failure defense (Pinnacle's failure to activate its contractually available failover to the US-West-2 availability region) should be reserved as additional leverage. These defenses are being analyzed in a separate memorandum and, if viable, would further reduce Lumos's credit exposure by eliminating or reducing the INC-5033 credit. We recommend disclosing these defenses strategically — potentially in mediation — rather than in the initial response letter.
5. Prepare for Mediation. In anticipation of mandatory mediation under MSA Section 14.3, we recommend developing a settlement posture that recognizes some credit obligation while firmly defending against consequential damages. A reasonable settlement range, based on our exposure analysis, would be in the range of $66,000 to $120,000. Any settlement should include a full release of all claims related to the four incidents and, ideally, a reaffirmation of the MSA's liability-limitation provisions going forward. We should discuss s

PRIVILEGED AND CONFIDENTIAL — ATTORNEY-CLIENT COMMUNICATION ATTORNEY WORK PRODUCT

MEMORANDUM

Record

Parties

Dates

Amounts