Opal Labs Inc. v. Sprinklr, Inc.

CourtDistrict Court, D. Oregon
DecidedAugust 19, 2021
Docket3:18-cv-01192
StatusUnknown

This text of Opal Labs Inc. v. Sprinklr, Inc. (Opal Labs Inc. v. Sprinklr, Inc.) is published on Counsel Stack Legal Research, covering District Court, D. Oregon primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Opal Labs Inc. v. Sprinklr, Inc., (D. Or. 2021).

Opinion

IN THE UNITED STATES DISTRICT COURT

FOR THE DISTRICT OF OREGON

OPAL LABS INC., No. 3:18-cv-01192-HZ

Plaintiff, OPINION & ORDER

v.

SPRINKLR, INC.,

Defendant.

Chad M. Colton Adam M. Starr Stanton R. Gallegos Daniel J. DiCicco Kathryn P. Roberts MARKOWITZ HERBOLD PC 1455 SW Broadway, Suite 1900 Portland, OR 97101

Attorneys for Plaintiff Robert L. Carey Christopher J. Pallanch Michael Willes Sadie Concepcion Paul M. Balmer TONKON TORP LLP 888 SW Fifth Avenue, Suite 1600 Portland, OR 97204

Attorneys for Defendant

HERNÁNDEZ, District Judge: This trade secrets dispute arises out of a failed collaboration between two software companies. Plaintiff Opal Labs Inc. alleges that Defendant Sprinklr, Inc., stole its trade secrets after the parties collaborated for a joint customer. Plaintiff brings claims for breach of contract, breach of the implied covenant of good faith and fair dealing, fraud, tortious interference with economic relations, and violation of the Oregon Uniform Trade Secrets Act. Both parties move for summary judgment on some of Plaintiff’s claims and Defendant’s affirmative defenses. At oral argument, the Court resolved part of the parties’ motions and reserved ruling on Defendant’s first, third and fourth motions, and Plaintiff’s first and fifth motions. Hr’g Tr., ECF 289. For the reasons that follow, the now Court grants in part and denies in part the remaining motions. BACKGROUND Plaintiff and Defendant are software companies with complementary products geared toward the creation and publishing of marketing content. At the beginning of the parties’ working relationship, Defendant’s primary product enabled marketing teams to publish content across different “channels,” including social media platforms like Facebook and Twitter. Plaintiff’s product helps marketing teams plan and create marketing campaigns. Using both systems together, a marketing team could plan and create a marketing campaign with Plaintiff’s product and then publish that campaign on various platforms with Defendant’s product. And that is exactly what was intended when the parties worked for Nike in 2013. Giannini Decl. ¶ 3, ECF 263. Defendant and Plaintiff each had independent relationships with Nike that pre-existed the parties’ collaboration. Herman Decl. ¶¶ 2–3, ECF 227. In mid-2013, Nike suggested to Plaintiff

and Defendant that they explore “integration” of both of their platforms. Giannini Decl. ¶ 4. The parties subsequently executed a nondisclosure agreement to share information with each other. Pallanch Decl. Ex. 12, ECF 226; Giannini Decl. ¶ 5. As the parties began working together, Defendant showed its platform to Plaintiff, and Plaintiff granted some of Defendant’s employees access to Plaintiff’s software. Pallanch Decl. Exs. 13–14. Both parties also continued to provide services to Nike. Soon after, Defendant began to consider further development of its own content planning software. See Starr Decl. Ex. 3, ECF 265. In early 2014, Nike asked Defendant to estimate the cost and time to build a “functional equivalent” of Plaintiff’s platform. Pallanch Decl. Ex. 22 (email from Paul Herman asking

“[w]hat would it take for Sprinklr to build the functional equivalent of what we have in Opal today and what we require in the near future?”). Along with its request, Nike sent Defendant a document identifying its requirements for content planning software. Id. Defendant and Nike— through Nike employee Paul Herman—ultimately planned to work on building a platform together. Starr Decl. Exs. 7, 8. In April 2014, Herman provided a Sprinklr employee with access to Plaintiff’s platform through Nike’s Opal account, Starr Decl. Exs. 10, 11, 12, and a software developer for Defendant in India obtained access to Plaintiff’s platform and the list of requirements for Nike’s content planning software, id. at Exs. 11, 12. When Plaintiff discovered that Defendant had access to Plaintiff’s live environment, Plaintiff sent Defendant a cease-and-desist letter. Pallanch Decl. Ex. 36; Giannini Decl. ¶ 7. Two of Plaintiff’s executives then had a telephone conference with three of Defendant’s executives on May 1, 2014. Pallanch Decl. Ex. 37 (Giannini Dep.) 67:14–21; Giannini Decl. Ex. 1. During the call, Defendant’s CEO—Ragy Thomas—claimed that there had been a misunderstanding and

that the access had been for the purposes of the Nike integration. Giannini Decl. Ex. 1. He also stated that they were not interested in competing with Plaintiff and were only developing a platform with “baseline content planning capabilities.” Id. at 55:25–56:7, 39:16–18. Ultimately, Thomas proposed that the parties form a partnership to pitch their complementary software to their clients. Id. at 40:20–22. This discussion led to the Teaming Agreement, which allowed the parties to introduce clients or customers to one another while restricting the use of confidential information shared between the parties to activities in furtherance of their relationship under the Teaming Agreement. Pallanch Decl. Ex. 41. A few months later, Defendant began working on its Content Marketing module. Starr

Decl. Ex. 51 (Michaud Dep.) 8:1–17, 14:18–25. Defendant released a prototype of this platform to some customers in early 2015. Id. at 10:11–12:7, 13:20–14:17. Nike also embarked on a project to build a Unified Communications Platform—also called Beacon—to bring its marketing and analytics under one umbrella. Herman Decl. ¶ 4; Starr Decl. Ex. 47 (Herman Dep.) 39:11–12, 40:16–20, 41:3–42:8. In the fall of 2015, Defendant won a bid to program the “back end” of the Beacon platform. Herman Decl. ¶ 5; Starr Decl. Ex. 52 (Singh Dep.) 106:8– 107:13. During this time, Herman and others from Sprinklr accessed Plaintiff’s software. Second Gorman Decl. Exs. 3, 5, 6, ECF 264. In early 2016, Nike changed course and determined that its platform would not be entirely unified, and it would use Opal for planning and Adobe for asset management. Pallanch Decl. Ex. 44; Herman Decl. ¶ 6. Beacon would focus only on targeting, scheduling, publishing, engagement, and measurement functions. Id. Throughout 2016, Nike used Adobe, Opal, and Beacon together. Herman Decl. ¶ 6. Meanwhile, Plaintiff and Defendant entered into an

“Integration Agreement,” which contemplated integration of their platforms for customers like Nike. Pallanch Decl. Ex. 47. Ultimately, Nike and Defendant abandoned Beacon, and Defendant began developing Planner 2.0. Starr Decl. Ex. 55 (Shibahara Dep.) 5:16–52:7, 53:3–15; Starr Decl. Ex. 52 (Singh Dep.) 107:14–23. Defendant continued to access Plaintiff’s software in March, May and June of 2016. Gorman Decl. Ex. 6 at 10–18. Defendant then began to sell Planner 2.0, which it dubbed a “full replacement” of Opal. Starr Decl. Exs. 31, 25, 36. Plaintiff heard that Defendant was “undermining Opal in the market.” Giannini Decl. ¶ 11. Plaintiff’s CEO—Steve Giannini— spoke with Thomas about the parties’ relationship and was reassured that the sales team pitching

Sprinklr “was probably just not up to speed” on their relationship. Id. Giannini spoke with Sprinklr’s president, who echoed this sentiment. Id. But soon after this meeting, Nike—after working out a deal with Defendant—considered ending its relationship with Plaintiff to adopt Defendant’s new planning tool. Starr Decl. Exs. 29, 38, 26; Pallanch Decl. Ex. 48. Nike officially notified Plaintiff that it was terminating its contract with Plaintiff in May 2017. Pallanch Decl. Ex. 49. Nike and Plaintiff later agreed to extend their agreement to 2018. Pallanch Decl. Ex. 50. In March 2018, Nike sent Plaintiff another notice of termination, and Plaintiff’s work for Nike ended in mid-2018. Pallanch Dec. Ex. 51. Nike ultimately replaced Plaintiff’s platform with Defendant’s Planner 2.0.

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

Related

Earl v. Nielsen Media Research, Inc.
658 F.3d 1108 (Ninth Circuit, 2011)
Barackman v. Anderson
109 P.3d 370 (Oregon Supreme Court, 2005)
Bias v. Moynihan
508 F.3d 1212 (Ninth Circuit, 2007)
Eggiman v. Mid-Century Insurance
895 P.2d 333 (Court of Appeals of Oregon, 1995)
Best v. United States National Bank
739 P.2d 554 (Oregon Supreme Court, 1987)
Carrier v. Hicks
851 P.2d 581 (Oregon Supreme Court, 1993)
Suever v. Connell
579 F.3d 1047 (Ninth Circuit, 2009)
North Pacific Lumber Co. v. Oliver
596 P.2d 931 (Oregon Supreme Court, 1979)
Federal Trade Commission v. Stefanchik
559 F.3d 924 (Ninth Circuit, 2009)
Western Medical Consultants, Inc. v. Johnson
835 F. Supp. 554 (D. Oregon, 1993)
Klamath Off-Project Water Users, Inc. v. PacifiCorp
240 P.3d 94 (Court of Appeals of Oregon, 2010)
Acrymed, Inc. v. Convatec
317 F. Supp. 2d 1204 (D. Oregon, 2004)
02 Micro International Ltd. v. Monolithic Power System, Inc.
399 F. Supp. 2d 1064 (N.D. California, 2005)
HAYS GROUP, INC. v. Biege
193 P.3d 1028 (Court of Appeals of Oregon, 2008)
O2 Micro International Ltd. v. Monolithic Power Systems, Inc.
420 F. Supp. 2d 1070 (N.D. California, 2006)
Morrow v. Red Shield Insurance
159 P.3d 384 (Court of Appeals of Oregon, 2007)

Cite This Page — Counsel Stack

Bluebook (online)
Opal Labs Inc. v. Sprinklr, Inc., Counsel Stack Legal Research, https://law.counselstack.com/opinion/opal-labs-inc-v-sprinklr-inc-ord-2021.