HARBOR BUSINESS COMPLIANCE CORPORATION v. FIRSTBASE.IO, INC.

CourtDistrict Court, E.D. Pennsylvania
DecidedApril 26, 2023
Docket5:23-cv-00802
StatusUnknown

This text of HARBOR BUSINESS COMPLIANCE CORPORATION v. FIRSTBASE.IO, INC. (HARBOR BUSINESS COMPLIANCE CORPORATION v. FIRSTBASE.IO, INC.) is published on Counsel Stack Legal Research, covering District Court, E.D. Pennsylvania primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
HARBOR BUSINESS COMPLIANCE CORPORATION v. FIRSTBASE.IO, INC., (E.D. Pa. 2023).

Opinion

UNITED STATES DISTRICT COURT EASTERN DISTRICT OF PENNSYLVANIA __________________________________________

HARBOR BUSINESS COMPLIANCE CORP., : Plaintiff, : : v. : No. 5:23-cv-00802 : FIRSTBASE.IO, INC., : Defendant. : __________________________________________

O P I N I O N Motions to Dismiss, ECF Nos. 18 and 22 – Granted in Part, Denied in Part

Joseph F. Leeson, Jr. April 26, 2023 United States District Judge

I. INTRODUCTION This case involves the unsuccessful business relationship of two companies. Plaintiff Harbor Business Compliance Corporation (“HC”) initiated the above-captioned action against Defendant FIRSTBASE.IO., INC. (“Firstbase”) alleging that Firstbase, after acquiring trade secrets of HC, breached the Partnership Agreement between the companies relating to the licensing, marketing, and sale of HC’s white-labeled registered agent service.1 Firstbase has filed a Motion to Dismiss four (4) of the six (6) counts in the Complaint. For the reasons set forth below, the Motion to Dismiss is granted in part as to the claim for Unjust Enrichment, which is dismissed with prejudice, and denied in all other respects.

1 A white-label product or service is produced by one company (producer) that other companies (marketers) rebrand to make it appear as if they had made it. See Compl. ¶ 14, n.2. II. BACKGROUND On March 1, 2023, HC filed a Complaint against Firstbase with six counts: (I) Breach of Contract; (II) Breach of Implied Covenant of Good Faith and Fair Dealing; (III) Misappropriation of Trade Secrets under Pennsylvania Law;2 (IV) Misappropriation of Trade Secrets under Federal Law;3 (V) Common Law Unfair Competition; and (VI) Unjust

Enrichment.4 See Compl., ECF No. 1.5 According to the Complaint: “Harbor Compliance is a software-focused provider of a wide array of compliance solutions for companies of all types and sizes.” Compl. ¶ 8. Since 2012, HC has worked with more than thirty-five thousand (35,000) account users to register for and maintain compliance by utilizing “its unique blend of highly confidential and proprietary reference data, entity data, technology, methodologies, and ‘know-how,’ which was obtained through many years of industry experience.” Id. Firstbase is a “new entity in the process of building an all-in-one Company [operating system (‘OS’)] to help define how founders across the globe launch, manage, and grow their businesses.” Id. ¶ 9 (internal quotations omitted).

On or about March 14, 2020, Firstbase purchased HC’s branded registered agent service. Id. ¶ 11. In February 2022, Firstbase contacted HC about wanting to license HC’s software to provide Firstbase’s customers the same (or substantially the same) services that HC brands and offers for sale under its own trade name to the consuming public. Id. ¶ 14. Firstbase sought an exclusive nationwide registered agent partner with HC. Id. ¶ 18.

2 Pennsylvania Uniform Trade Secrets Act (“PUTSA”) 3 Defend Trade Secrets Act (“DTSA”) 4 The Complaint includes two counts labeled “Count V.” The first Count V begins on page 47 of the Complaint and is for “Common Law Unfair Competition.” The second Count V begins on page 49 of the Complaint and is for “Unjust Enrichment.” For purposes of this Opinion and to avoid confusion, the second Count V for “Unjust Enrichment” will be referred to as Count VI. 5 An unredacted copy of the Complaint is filed under seal at ECF No. 3. By March 2022, as negotiations continued, Firstbase requested information concerning HC’s confidential business methodologies, such as the methodology through which HC processes mail on behalf of its customers, the names of third-party service providers in HC’s network, information on HC’s customer intake forms, the mechanisms and methodology through which HC’s API would be sending data to Firstbase, and how to leverage client-facing features

such as ongoing compliance reminders and filings through such mechanisms and methodologies for transferring data. Id. ¶ 23. Firstbase also requested HC’s proprietary, confidential, and trade secret compilations of detailed, state/commonwealth/territory-specific jurisdictional requirements and information, of internal and external processes, of “know how” utilized by HC in connection with performing efficient, expeditious, and consistent quality services to the consuming public at large, which HC had developed over the course of many years in the industry and through working and building relationships directly with contacts at the relevant agencies located in each of the states/commonwealths/territories throughout the United States (the “JX Databases”), and of HC’s marketing and sales data and information for effective

productization, pricing, packaging, and the like. Id. ¶¶ 24-25. HC provided the same pursuant to a Non-Disclosure Agreement (“NDA”). Id. ¶ 26. By the end of May 2022, HC had begun creating the white-labeled Firstbase Agent. Id. ¶ 53. On May 28, 2022, after negotiating the parameters for HC to become the exclusive nationwide registered agent of, and white-labeled solution for, Firstbase, HC and Firstbase signed a “Partnership Agreement.” Id. ¶ 29. The following month, Firstbase began marketing the HC white-label Firstbase Agent to its clients. Id. ¶ 58. However, HC alleges, Firstbase did not negotiate in good faith as required by the Partnership Agreement, and HC contributed a greater amount of work and money than it otherwise would have, such as processing between six hundred (600) and one thousand (1,000) new orders per month. Id. ¶¶ 62-66. On August 29, 2022, HC delivered its redesigned API (application programming interfaces) to Firstbase. Id. ¶ 68. Despite HC’s delivery, Firstbase never implemented the API as agreed, which prevented the system from becoming automated. Id. ¶ 68. Firstbase did not compensate HC for its work

done to automate the system. Id. ¶ 69. Between May 2022 and January 31, 2023, HC delivered two thousand eight hundred seventy-two (2,872) total filings on behalf of Firstbase customers, some of which were canceled by Firstbase. Id. ¶¶ 70-71. There were more than an additional one hundred (100) orders placed by Firstbase in which Firstbase failed to provide sufficient information. Id. ¶ 72. In September 2022, Firstbase, accusing HC of trying to charge additional costs, contacted HC to amend the Partnership Agreement. Id. ¶ 77. On or about November 1, 2022, during one of the Parties’ Status Meetings, a representative of Firstbase disclosed that Firstbase was attempting to exit the Partnership Agreement because one of its potential investors preferred

Firstbase to run the Firstbase Agent itself, rather than relying on a white-label arrangement with HC. Id. ¶ 91. The next day, Firstbase sent a letter to HC noticing its intent to terminate the Partnership Agreement based on HC’s alleged breaches. Id. ¶ 92. HC challenged the termination and attempted to negotiate with Firstbase, detailing the future potential of the partnership and advising Firstbase that HC was working on “automating CA, FL, NY and TX within the next two months.” Id. ¶ 94. The companies continued to communicate regarding alleged breaches, curing the same, and termination of the Partnership Agreement. Id. ¶¶ 95-107. On November 17, 2022, Firstbase sent an email to its clients and contacts announcing the the expansion of its Firstbase Agent to the same four states HC had mentioned: California, Florida, New York, and Texas. Id. ¶ 102. On or around November 22, 2022, Firstbase’s website pictured its new Firstbase Agent service, which HC alleges looked “remarkably similar” to the white-labeled Firstbase Agent that HC was obligated to provide under the Partnership Agreement. Id. ¶ 103. Two weeks prior, Firstbase had formed a new company called Firstbase Agent LLC, which was qualified/or registered to do business in several states. Id. ¶¶ 110-113.

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

Related

Bell Atlantic Corp. v. Twombly
550 U.S. 544 (Supreme Court, 2007)
Ashcroft v. Iqbal
556 U.S. 662 (Supreme Court, 2009)
Mayer v. Belichick
605 F.3d 223 (Third Circuit, 2010)
Bimbo Bakeries USA, Inc. v. Botticella
613 F.3d 102 (Third Circuit, 2010)
Larry R. Moore v. Kulicke & Soffa Industries, Inc
318 F.3d 561 (Third Circuit, 2003)
Phillips v. County of Allegheny
515 F.3d 224 (Third Circuit, 2008)
Rohm and Haas Co. v. Lin
992 A.2d 132 (Superior Court of Pennsylvania, 2010)
Alpart v. General Land Partners, Inc.
574 F. Supp. 2d 491 (E.D. Pennsylvania, 2008)
Schott v. Westinghouse Electric Corp.
259 A.2d 443 (Supreme Court of Pennsylvania, 1969)
Mitchell v. Moore
729 A.2d 1200 (Superior Court of Pennsylvania, 1999)
Wilson Area School District v. Skepton
895 A.2d 1250 (Supreme Court of Pennsylvania, 2006)
Gee v. Eberle
420 A.2d 1050 (Superior Court of Pennsylvania, 1980)
Styer v. Hugo
619 A.2d 347 (Superior Court of Pennsylvania, 1993)
Torchia on Behalf of Torchia v. Torchia
499 A.2d 581 (Supreme Court of Pennsylvania, 1985)
Harry Miller Corp. v. Mancuso Chemicals Limited
469 F. Supp. 2d 303 (E.D. Pennsylvania, 2007)

Cite This Page — Counsel Stack

Bluebook (online)
HARBOR BUSINESS COMPLIANCE CORPORATION v. FIRSTBASE.IO, INC., Counsel Stack Legal Research, https://law.counselstack.com/opinion/harbor-business-compliance-corporation-v-firstbaseio-inc-paed-2023.