Health Cost IQ Incorporated v. BDG Benefits Design Group Incorporated

• Court: District Court, D. Arizona
• Decided: April 21, 2025
• Docket: 2:25-cv-00070
• Status: Unknown

Opinion

1 WO 2 3 4 5 6 IN THE UNITED STATES DISTRICT COURT 7 FOR THE DISTRICT OF ARIZONA

9 Health Cost IQ Incorporated, No. CV-25-00070-PHX-DWL

10 Plaintiff, ORDER

11 v.

12 BDG Benefits Design Group Incorporated,

13 Defendant. 14 15 Pending before the Court is a motion for default judgment filed by Plaintiff Health 16 Cost IQ, Inc. (“Plaintiff” or “HCIQ”). (Doc. 11.) The Court requires supplemental briefing 17 regarding Plaintiff’s anticipatory breach claim. 18 RELEVANT BACKGROUND 19 On January 8, 2025, Plaintiff filed the complaint. (Doc. 1.) The complaint alleges 20 that in May 2024, Plaintiff entered into a software-as-a-service license agreement (“the 21 Agreement”) with Defendant BDG Benefits Design Group, Inc. d/b/a 1850 Plan Services 22 (“Defendant” or “1850”). (Doc. 1 ¶¶ 1-2.) The Agreement had a “5 Year Initial Term.” 23 (Id. ¶ 21(a).) Under the Agreement, Plaintiff agreed to provide certain software—which is 24 described as “a comprehensive population health, risk profiling, cost and plan management 25 platform” (hereinafter, “the Software”)—and other services to Defendant in exchange for 26 quarterly payments of $73,500. (Id. ¶¶ 20-21.) Plaintiff “complied with its obligations 27 under the Agreement” and sent three quarterly invoices for $73,500 to Defendant—the first 28 on July 1, 2024, the second on October 1, 2024, and the third on January 7, 2025—but 1 Defendant failed to pay any of those invoices. (Id. ¶¶ 40, 45.) 2 The complaint further alleges that between August 2024 and October 2024, 3 Plaintiff’s representatives engaged in various communications with two of Defendant’s 4 principals (Ms. Norman and Mr. Smith) concerning the past-due invoices and other matters 5 related to the Agreement. (Id. ¶¶ 25-37.) During one meeting on August 26, 2024, “Ms. 6 Norman confirmed that [Defendant] would perform under the Agreement.” (Id. ¶ 26.) 7 However, Ms. Norman then failed to respond to multiple follow-up inquiries. (Id. ¶¶ 27- 8 32.) On October 2, 2024, Mr. Smith reached out to one of Plaintiff’s representatives “to 9 discuss the Agreement” (id. ¶ 33), and Plaintiff’s notes from that call reflect that Plaintiff 10 proposed two options for modifying the terms of the Agreement. (Doc. 1-3.) However, 11 Mr. Smith then ignored several follow-up communications from Plaintiff (Doc. 1 ¶¶ 34- 12 36) before writing on October 16, 2024 “that [Defendant] is a start up with no groups that 13 would benefit from the data stream, that they were considering their options, and that the 14 6,000 lives was a goal, but not likely until sometime in the future.” (Id. ¶ 36.) Afterward, 15 Plaintiff sent another follow-up inquiry but Mr. Smith failed to respond. (Id. ¶ 37.) 16 Based on those allegations, the complaint asserts two claims for relief: (1) a claim 17 for breach of contract in which Plaintiff seeks damages of $220,500 (i.e., the amount of the 18 three unpaid invoices), plus tax and interest at a monthly rate of 1.5% as specified in the 19 Agreement; and (2) a claim for “anticipatory breach of contract” in which Plaintiff seeks 20 damages of $1,249,500 (i.e., all of the future quarterly payments of $73,500 that would 21 have been owed during the remainder of the five-year term of the Agreement), plus tax and 22 interest. (Id. ¶¶ 41-62.) 23 On January 13, 2025, Defendant was served with process. (Doc. 6.) 24 On February 7, 2025, Plaintiff applied for entry of default. (Doc. 9.) 25 On February 10, 2025, the Clerk of Court entered a default. (Doc. 10.) 26 On February 26, 2025, Plaintiff filed the pending motion for default judgment. 27 (Doc. 11.) Defendant has not responded. 28 … 1 DISCUSSION 2 As noted, in Count One of the complaint, Plaintiff asserts a claim for breach of 3 contract. Under Arizona law, “in an action based on breach of contract, the plaintiff has 4 the burden of proving the existence of a contract, breach of the contract, and resulting 5 damages.” Chartone, Inc. v. Bernini, 83 P.3d 1103, 1111 (Ariz. Ct. App. 2004). In Count 6 Two, Plaintiff asserts a claim for anticipatory breach. Under Arizona law, “[a]nticipatory 7 breach of contract exists where the repudiating party expresses a positive and unequivocal 8 manifestation that he will not render the required performance when it is due.” 9 Oldenburger v. Del E. Webb Development Co., 765 P.2d 531, 533 (Ariz. Ct. App. 1988).1 10 In its motion for default judgment, Plaintiff provides the following argument as to 11 why the second and third Eitel factors are satisfied here:

12 HCIQ and 1850 entered into the Agreement on or about May 9, 2024. Pursuant to the terms of the Agreement, HCIQ agreed to provide the 13 Software and other services to 1850 in exchange for quarterly payments in the amount of $73,500.00 by 1850 over a five-year term. The Agreement is 14 valid, binding, and enforceable, and HCIQ has complied with its obligations under the Agreement. However, 1850 has failed to make any quarterly 15 payments as required by the Agreement, including for the Invoices, sent to 1850 by HCIQ on July 1, 2024, October 1, 2024, and January 7, 2025, which 16 total $220,500.00. 1850 has breached the Agreement by failing to pay the Invoices on receipt, thereby damaging HCI. . . . 1850 has [also] made clear 17 to HCIQ that it will continue to breach the Agreement, to HCIQ’s detriment, by failing to make any future quarterly payments for the remainder of the 18 five-year term of the Agreement. The Agreement remains in effect and has not been terminated. Thus, HCIQ is entitled to recover damages for 1850’s 19 anticipatory breach of the remainder of the five-year term of the Agreement, which amounts to $1,249,500.00 in damages to HCIQ. 20 21 (Doc. 11 at 5-6.) 22 The Court agrees with Plaintiff that the factual allegations in the complaint state a 23 plausible claim for relief as to Count One. The complaint plausibly alleges the existence 24 of a contract, a breach (i.e., Defendant’s failure to pay the first three $73,500 invoices), and 25 damages. 26 1 “[A]n anticipatory breach, by itself, does not entitle the injured party to damages. 27 To recover damages, in addition to proving repudiation, the non-breaching party need only show that he would have been ready and willing to have performed the contract, if the 28 repudiation had not occurred.” Thomas v. Montelucia Villas, LLC, 302 P.3d 617, 620 (Ariz. 2013). 1 The analysis is more complicated as to Count Two. As noted, anticipatory breach 2 “exists where the repudiating party expresses a positive and unequivocal manifestation that 3 he will not render the required performance when it is due.” Oldenburger, 765 P.2d at 533 4 (emphasis added). However, the complaint does not allege that any of Defendant’s 5 representatives expressed a positive and unequivocal intention not to comply with 6 Defendant’s future payment obligations under the Agreement. To the contrary, the only 7 direct statement on this topic referenced in the complaint is Ms. Norman’s statement in 8 August 2024 in which she “confirmed that [Defendant] would perform under the 9 Agreement.” (Doc. 1 ¶ 26.) Perhaps Plaintiff’s theory is that Defendant’s subsequent 10 conduct, which consisted of failing to pay the past-due invoices and ignoring multiple 11 follow-up inquiries, raises an inference that Defendant intended to violate future payment 12 obligations, but Plaintiff has not cited any authority—and the Court is aware of none— 13 holding that an inference arising from silence and inaction qualifies as a “positive and 14 unequivocal manifestation” of intent not to perform. See also United Cal. Bank v. 15 Prudential Ins. Co. of Am., 681 P.2d 390, 429 (Ariz. Ct. App. 1983) (“A statement by a 16 party to a contract merely implying that he will not perform is not the equivalent of a 17 positive and unequivocal refusal to perform.”) (citation omitted); Diamos v. Hirsch, 372 18 P.2d 76, 78-79 (Ariz. 1962) (affirming the trial court’s grant of a directed verdict in favor 19 of the defendant, where the plaintiff sought to assert a claim “for breach of contract based 20 upon the anticipatory repudiation by one of the parties to the contract,” because the 21 defendant merely “implied that he wanted plaintiff to sign the addendum or defendants 22 would not perform” and “never made a positive statement that defendants would not 23 perform unless plaintiff agreed to the addendum” and thus the evidence “f[ell] far short of 24 the requisite proof that in order to constitute a breach by anticipatory repudiation there must 25 be a positive and unequivocal refusal to perform”). For similar reasons, it is not obvious 26 why Mr. Smith’s final communication on October 16, 2024 could be deemed sufficient to 27 meet the “positive and unequivocal manifestation” standard—he simply stated that 28 Defendant “would [not] benefit” from Plaintiff’s modification proposals and that 1 Defendant was “considering [its] options.” (Doc. 1 ¶ 36.) 2 Additionally, the Agreement, which is appended to the complaint and is therefore 3 incorporated by reference, specifies that Defendant has the right to terminate the 4 Agreement “at any time following the second (3rd) anniversary of the Effective Date upon 5 ninety (90) days written notice to [Plaintiff].” (Doc. 1-1 at A-8 ¶ 11(a).) The parties’ 6 apparent typographical error in specifying that Defendant could terminate after the 7 “second” anniversary but placing “3rd” in parentheses makes this contractual term 8 ambiguous. When written and numerical terms are in conflict, the “general rule” is that 9 “the written number controls.” Fetch Interactive Television LLC v. Touchstream Techs. 10 Inc., 2019 WL 193921, *20 (Del. Ch. 2019); see also id. at *20 n.235. Further 11 complicating the analysis here, the Agreement incorporates by reference six “Schedules,” 12 one of which is “Schedule F – Order Form,” and specifies that “[i]n the event of a conflict 13 between the terms of this Agreement and any Order Form, the terms of this Agreement will 14 control.” (Doc. 1-1 at A-12 ¶ 17(e).) The Schedule F “Order Form” contains a clause near 15 the bottom of the first page specifying, in bold font, that the “Term” is “3 Years (April 16 29, 2024, through April 28, 2027).” (Id. at A-34.) To the extent this term designation 17 conflicts with the definition of the “Initial Term” in the Agreement, which is defined as “a 18 period of five (5) years” (id. at A-8 ¶ 11(a)), the definition in the Agreement “will control.” 19 But to the extent the three-year term specified in Schedule F could shed light on whether 20 Defendant had the right to terminate the Agreement following the “second” or “3rd” 21 anniversary of the effective date, this is a consideration to bear in mind when construing 22 the ambiguous term in the Agreement.2 23 At any rate, however the ambiguous contractual term is construed, Defendant was 24 not obligated to continue payments for the full five-year term. It is therefore difficult to 25 understand how Defendant could be liable for payments beyond the second or third 26 2 In an October 3, 2024 email from one of Plaintiff’s principals to one of Defendant’s 27 principals, Plaintiff referred to the Agreement as having a “3-year term” and proposed two “options” for Defendant’s consideration—keeping the three-year term or agreeing to a two- 28 year term. (Doc. 1-3 at 3-4.) Defendant neither agreed with nor objected to Plaintiff’s characterization of the Agreement’s term length. 1 anniversary of the Agreement’s effective date. An anticipatory breach applies only to a 2 “required performance,” Oldenburger, 765 P.2d at 533, and Defendant’s performance 3 under the Agreement does not appear to be “required” after the point when Defendant is 4 allowed to “terminate” the Agreement “at any time.” (Doc. 1-1 at A-8 ¶ 11(a).) Put 5 another way, it does not seem plausible that Defendant’s obligation to make $73,500 6 quarterly payments would have extended beyond two or three years, depending on how the 7 ambiguous term in the Agreement is construed (as opposed to the five-year term on which 8 Plaintiff bases its damage calculations in Count Two). 9 Furthermore, although the record is not developed on this point, it is possible that 10 Plaintiff would have incurred at least some costs in the course of providing the agreed-to 11 software and other services to Defendant pursuant to the Agreement (and that Plaintiff’s 12 anticipated quarterly profit was thus the agreed-to payment of $73,500 minus those 13 unspecified costs). However, once Defendant anticipatorily breached the Agreement, 14 Plaintiff would stop incurring those costs. Awarding $73,500 in damages to Plaintiff for 15 each future quarter following any anticipatory breach would thus result in a windfall to 16 Plaintiff. In anticipatory breach cases, courts often require an offset to avoid such a 17 windfall. See generally Arens Controls Co., L.L.C. v. Enova Sys., Inc., 2012 WL 18 13066501, *3 (N.D. Ill. 2012) (“Damages for anticipatory breach of contract include: (1) 19 the difference between the market price at the time and place for tender and the unpaid 20 contract price together with any incidental damages . . . but less expenses saved in 21 consequence of the buyer’s breach or, if this measure of damages is inadequate to put the 22 seller in as good a position as performance would have done then (2) the profit (including 23 reasonable overhead) which the seller would have made from full performance by the buyer 24 . . . .”) (cleaned up) (emphasis added). Accordingly, assuming Plaintiff is able to remedy 25 the other shortcomings regarding Count Two identified in this order, it must also provide 26 information regarding the costs it would have incurred when performing under the 27 Agreement and whether it would have avoided those costs in the case of an anticipatory 28 breach. 1 A final potential complication with Plaintiff’s damage calculation in Count Two is 2 that Plaintiff makes no effort to account for the time value of money. See generally Oliveri 3 v. Delta S.S. Lines, Inc., 849 F.2d 742, 745-46 (2d Cir. 1988) (“We have previously 4 explained in some detail the proper method of discounting a future income stream to 5 present value. Our approach takes into account two matters—inflation and the opportunity 6 to invest money. Because a dollar received in the future will almost surely have less 7 purchasing power than a dollar has today, we have required estimates of lost future earnings 8 to reflect the effect of inflation. In addition, because a dollar received today may be 9 invested and produce a larger sum of money in the future (even though that sum will have 10 less purchasing power than an equivalent sum has today), we have required that damages 11 for loss of earnings that would have been received in the future must be discounted to 12 reflect the fact that, even if there were no inflation, a dollar received today is worth more 13 than the right to receive a dollar in the future.”) (citations omitted). The $73,500 quarterly 14 payments owed over the remaining term of the Agreement (whatever the length of that 15 remaining term) would not be payable right now—instead, they would be payable over 16 time. In analogous situations, courts have required the plaintiff pursuing an anticipatory 17 breach claim to discount the value of the future payments to their present value. Great 18 Lakes Gas Transmission Ltd. P’ship v. Essar Steel Minnesota, LLC, 2014 WL 12597430, 19 *17 (D. Minn. 2014) (“[T]he general rule is that anticipatory repudiation of a contract 20 permits the aggrieved party to sue for damages resulting from future as well as past non- 21 performance. Awards of future damages generally require adjustment, or discounting, to 22 present value by the application of a discount rate. The discount rate performs two 23 functions: (i) it accounts for the time value of money; and (ii) it adjusts the value of the 24 cash flow stream to account for risk.”) (cleaned up); Long Island R. Co. v. Northville 25 Industries Corp., 362 N.E.2d 558, 566 (N.Y. Ct. App. 1977) (upholding award of damages 26 for anticipatory breach but clarifying that “[t]his does not mean, however, that the railroad 27 is presently entitled to the full $20,000 guaranteed minimum for those annual payments 28 not yet due” because “[s]ince these amounts will be collected in advance of their due date, || the respective installments should be discounted to their present value”). However, 2|| Plaintiff has not performed any such discounting here. 3 The Court will authorize Plaintiff to submit supplemental briefing on these issues. Alternatively, Plaintiff may withdraw the portion of the default judgment motion based on || Count Two. 6 Accordingly, 7 IT IS ORDERED that within 14 days of the issuance of this order, Plaintiff must 8 || either file (1) a supplemental memorandum addressing the perceived deficiencies in Count 9|| Two identified above; or (2) a memorandum confirming that Plaintiff does not wish to || further pursue Count Two and would be satisfied with the entry of a default judgment in 11 |} its favor on Count One. 12 Dated this 21st day of April, 2025. 13 14 fm ee” 15 f CC —— Dominic W. Lanza 16 United States District Judge 17 18 19 20 21 22 23 24 25 26 27 28

-8-