Outpost24 AB v. Laurel Health Care Company

CourtDistrict Court, D. Massachusetts
DecidedJanuary 24, 2024
Docket1:21-cv-10449
StatusUnknown

This text of Outpost24 AB v. Laurel Health Care Company (Outpost24 AB v. Laurel Health Care Company) is published on Counsel Stack Legal Research, covering District Court, D. Massachusetts primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Outpost24 AB v. Laurel Health Care Company, (D. Mass. 2024).

Opinion

UNITED STATES DISTRICT COURT DISTRICT OF MASSACHUSETTS

OUTPOST24 AB, * * Plaintiff, * * v. * * Civil Action No. 21-cv-10449-ADB LAUREL HEALTH CARE COMPANY, * * Defendant. * * *

MEMORANDUM AND ORDER

BURROUGHS, D.J. Plaintiff Outpost24 AB (“Outpost”) asserts claims for breach of contract, breach of the covenant of good faith and fair dealing, deceit, and unfair business practices against Defendant Laurel Health Care Company (“Laurel”) relating to the breakdown of a business relationship in which Laurel purchased cybersecurity services. [ECF No. 1 at 6–9; ECF No. 45 at 2]. Pending before the Court is Laurel’s motion for summary judgment on all claims. [ECF No. 44]. For the reasons set forth below, the motion is DENIED. I. BACKGROUND Except as otherwise noted, the following facts are not in dispute.1

1 Local Rule 56.1 provides that “[m]otions for summary judgment shall include a concise statement of the material facts of record as to which the moving party contends there is no genuine issue to be tried,” and that “[a] party opposing the motion shall include a concise statement of the material facts of record as to which it is contended that there exists a genuine issue to be tried.” L.R. 56.1. “Material facts of record set forth in the statement required to be served by the moving party will be deemed for purposes of the motion to be admitted by opposing parties unless controverted by the statement required to be served by opposing parties.” Id. Accordingly, facts set forth by Laurel, [ECF No. 45], that are not specifically controverted by Outpost’s opposition statement, [ECF No. 48], are deemed admitted for purposes of this motion. A. The Pwnie Agreement “On June 15, 2017, Laurel entered into an agreement with Rapid Focus Security, Inc. d/b/a Pwnie Express (‘Pwnie’) for the Pulse Platform Professional Edition (‘PPPE’), a cyber security software service” (the “Pwnie Agreement” or “Agreement”).2 [ECF No. 45 at 2

(“Mot.”)]. As explained below, the claims in this case generally arise from a dispute over whether Laurel terminated the Agreement in July 2019. See infra. Several provisions of the Pwnie Agreement are relevant to whether Laurel effectively terminated it. First, the license term was “thirty-six (36) months from the last shipment date,” [ECF No. 45-4 at 2], which was September 30, 2017, [id. at 3]; see also [Mot. at 2]. An annual subscription fee of $90,191.80 was “payable annually, in advance, upon the Effective Date of” the Pwnie Agreement, [ECF No. 45-4 at 2], “and on each Renewal Anniversary thereafter,” the first of which was October 7, 2018, [id. at 3]; see also [Mot. at 2]. Second, the two-page Pwnie Agreement states that [t]he end user customer or Licensee’s use or license of the Software, Sensors and Support Services set forth herein is governed by the terms and conditions of this Order Form and the then current Pwnie Express SaaS Terms and Conditions at https://www.pwnieexpress.com/saas-terms-and-conditions/ which are incorporated herein by reference. The person signing this Order Form represents that she/he is authorized to bind the end user customer or Licensee identified above and that end user customer or Licensee accepts all of the terms and conditions of this Order Form, including such then-current Pwnie Express SaaS Terms and Conditions. [ECF No. 45-4 at 3]; see also [Mot. at 2]. The hyperlink in the Agreement is blue and underlined. [Id.]; see also [Mot. at 2]. Laurel argues that “[a]t no point prior to signing the Pwnie Agreement did Laurel see or review the Terms and Conditions, nor did Pwnie ever send Laurel the Terms and Conditions separate from the hyperlink in the Pwnie Agreement.” [Mot. at

2 In August 2019, Outpost “acquired certain assets of Pwnie[,] including the Pwnie Agreement.” [Mot. at 3]; see also [ECF No. 48 at 1 (“Opp.”)]. 2]. Outpost, on the other hand, says, among other things, that the hyperlink was “conspicuous” in the contract and that testimony about whether a Laurel representative “read the terms and conditions, knew of them, and or agreed to them” is “not consistent.” [Opp. at 4–5]. In any event, Section 2.1 of the Terms and Conditions provides that “[t]he term of the

license for the use of the Software and Sensors will commence seven (7) days after the first shipment of the Order . . . and continue for the license term . . . unless terminated as provided herein . . . .” [ECF No. 45-7 at 2]. The termination provision, Section 2.2, provides that Licensee shall have no right to terminate the Agreement without cause. Either party may terminate this Agreement upon thirty (30) days prior written notice in the event of a material breach by the other party of any term and condition of this Agreement and a failure to cure such breach. In the event of any such expiration or termination of the Agreement, no refund of fees shall be due and owing to Licensee, and Licensee shall pay any fees then due and owing for the remainder of the applicable license term. Licensee shall cease all use of the Software and Sensors upon the expiration or termination of this Agreement. Any expiration or termination of this Agreement shall not modify any rights or obligations of a party hereto which arose prior to such expiration or termination. [Id. at 2–3]. Finally, the Agreement provided that Laurel would receive “forty-one (41) . . . sensors,” [ECF No. 45-4 at 2]; see also [Mot. at 2], which were “placed in each of Laurel’s facilities, and were supposed to scan Laurel’s wireless network for security threats,” [id. at 2]. The parties dispute whether Laurel or Outpost owned the sensors. See [Mot. at 2; Opp. at 4–5]. Laurel claims that “Pwnie represented to Laurel that Laurel owned the sensors,” [Mot. at 2], whereas Section 2.4 of the Terms and Conditions of the Pwnie Agreement provides that [a]ll equipment supplied by Pwnie Express for use pursuant to this Agreement shall be owned by Pwnie Express. Upon termination of this Agreement, unless Pwnie Express elects to disable or abandon all or any of the equipment owned by it, the Licensee, at the Licensee’s cost, agrees to return, within thirty (30) days of the termination of this Agreement, all equipment to Pwnie Express. Failure to return such equipment will result in a charge to the Licensee for the price of such equipment[,] [ECF No. 45-7 at 3]; see also [Opp. at 2]. B. The Disputed Termination of the Pwnie Agreement Laurel paid the annual subscription fee for the first two years that the Pwnie Agreement was in effect. [Opp. at 2]. Then, on July 9, 2019, Kelly Foster of Laurel emailed Kurt Lee of Pwnie stating, among other things, that [w]hile we have the devices installed and do monitor the data, we find it of little use, not very accurate, buggy, the devices temperamental and certainly not worth $100K per year. . . . Besides problems with the devices, which should have been documented in support calls, we simply do not need the Pwnie services, and never really did. We get the same information, and much more, and more accurately, with our other systems. Not a knock on Pwnie – it just doesn’t give us much that we need. Obviously, we will not be renewing our contract (September?). So, if any type of notice is required, please consider this it and do not bill us. Is there anything else Laurel needs to do to wind-down the contract? [ECF No. 45-8 at 2]. The parties dispute whether this email exchange showed an intent to terminate and/or sufficed to actually terminate the Agreement. [Mot. at 3; Opp. at 2, 5]. Approximately one month later, in August 2019, Outpost acquired the Agreement. [Mot. at 3]. Four months after that, on December 4, 2019, Ellinor Klingvall of Outpost emailed Nicholas Ries of Laurel stating that she was “[g]oing through our accounts receivables list [and] I noticed that [Laurel’s] invoice, year 3/3 for the Pulse Platform subscription purchased from Pwnie Express is still unpaid.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Carmona v. Toledo
215 F.3d 124 (First Circuit, 2000)
Cochran v. Quest Software, Inc.
328 F.3d 1 (First Circuit, 2003)
Hannon v. Beard
645 F.3d 45 (First Circuit, 2011)
Gomez v. Stop & Shop Supermarket Co.
670 F.3d 395 (First Circuit, 2012)
Nansamba v. North Shore Medical Center, Inc.
727 F.3d 33 (First Circuit, 2013)
Ocasio-Hernandez v. Fortuno-Burset
777 F.3d 1 (First Circuit, 2015)

Cite This Page — Counsel Stack

Bluebook (online)
Outpost24 AB v. Laurel Health Care Company, Counsel Stack Legal Research, https://law.counselstack.com/opinion/outpost24-ab-v-laurel-health-care-company-mad-2024.