FR EA

Contract analysis

Clause-by-clause risk read on any document of the firm. Pick a contract, or open any document from a matter.

Contract analysis / contractual-limitations-memo.docx
contractual-limitations-memo.docx
1008-00007 · 34 clauses
High · 7 Medium · 2 Standard · 3
I. Executive Summary
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 Pinna
1. The SLA Credit Cap under Exhibit C, Section 3.4, of the Master Services Agreement date Standard
⚑ Commercial term
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 par
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 Medium
⚑ Liability cap to check against exposure
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, 20
II. Background and Pinnacle's Demand High
⚑ Non-compete / exclusivity restraint
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 environme
III. Defense No. 1: SLA Credit Cap (Exhibit C, §3.4)
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: High
⚑ Non-compete / exclusivity restraint
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 obligatio
Section 3.4 should be read in conjunction with MSA Section 11.2 (the aggregate liability c High
⚑ Non-compete / exclusivity restraint
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 cl
IV. Defense No. 2: Mutual Waiver of Consequential Damages (MSA §11.3)
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: High
⚑ Non-compete / exclusivity restraint
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
1. Remediation Costs Are Direct Damages, Not Consequential. Pinnacle may argue that its $3 High
⚑ Non-compete / exclusivity restraint
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 licen
2. The Consequential Damages Waiver Is Unconscionable. Pinnacle may argue that the waiver
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 i
3. Willful Breach Vitiates the Consequential Damages Waiver. Pinnacle may argue that Lumos
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 uninten
4. The SLA Credit Remedy Fails of Its Essential Purpose, Unlocking Full Damages. Pinnacle High
⚑ Non-compete / exclusivity restraint
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
Section 11.3 of the MSA bars Pinnacle's claims for lost revenue ($1,950,000), internal rem
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
V. Defense No. 3: Timeliness of Credit Request for INC-4471 (Exhibit C, §3.5)
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
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.
1. Waiver by Lumos
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 L
2. Estoppel. Pinnacle may argue that Lumos is equitably estopped from enforcing the Secti
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 Pin
3. Substantial Compliance
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
4. Prejudice Requirement
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, wi
Section 3.5 is not a general notice provision — it is a claim-filing deadline with an expr Standard
⚑ Commercial term
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 th
VI. Interaction of Defenses with Aggregate Liability Cap (MSA §11.2) Standard
⚑ Commercial term
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
VII. Summary of Maximum Exposure Analysis High
⚑ Non-compete / exclusivity restraint
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
VIII. Recommendations
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 (V
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 w
2. Confirm Anti-Waiver Clause. We recommend confirming the existence and precise language
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 pres
3. Review INC-4471 Correspondence. We recommend reviewing all internal and external corre
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,
4. Preserve Records. All records relevant to the Pinnacle dispute should continue to be p
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 lit
1. Lead with All Three Defenses. In any response to Pinnacle's counsel at Hargrove, Tillm Medium
⚑ Liability cap to check against exposure
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 Secti
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 def
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
4. Reserve Additional Defenses. The third-party causation defense for INC-5033 (attributa
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
5. Prepare for Mediation. In anticipation of mandatory mediation under MSA Section 14.3,
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 incid