City of Miami Fire Fighters' and Police Officers' Retirement Trust v. Cerence Inc.

CourtDistrict Court, D. Massachusetts
DecidedMarch 25, 2024
Docket1:22-cv-10321
StatusUnknown

This text of City of Miami Fire Fighters' and Police Officers' Retirement Trust v. Cerence Inc. (City of Miami Fire Fighters' and Police Officers' Retirement Trust v. Cerence Inc.) 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
City of Miami Fire Fighters' and Police Officers' Retirement Trust v. Cerence Inc., (D. Mass. 2024).

Opinion

UNITED STATES DISTRICT COURT DISTRICT OF MASSACHUSETTS

* CITY OF MIAMI FIRE FIGHTERS’ and * POLICE OFFICERS’ RETIREMENT * TRUST, Individually and on Behalf of All * Others Similarly Situated, * * Plaintiff, * Civil Action No. 22-cv-10321-ADB * v. * * CERENCE INC., SANJAY DHAWAN, and * MARK J. GALLENBERGER, * * Defendants. * *

MEMORANDUM AND ORDER

BURROUGHS, D.J. This is a federal securities class action lawsuit concerning alleged violations of Sections 10(b) and 20(a) of the Securities Exchange Act of 1934, 15 U.S.C. §§ 78j, 78t, and Rule 10b-5, 17 C.F.R § 240.10b-5, by Defendants Cerence Inc. (“Cerence”), Cerence’s former CEO Sanjay Dhawan and former CFO Mark Gallenberger. [ECF No. 37 (“Amended Complaint” or “Am. Compl.”)]. Plaintiff, on behalf of itself and others, claims that Cerence and its executives made false and misleading statements concerning demand for Cerence’s software and sales of its product. See [Id. ¶¶ 3–6]. Currently before the Court is Defendants’ motion to dismiss. [ECF No. 39]. For the reasons discussed below, the motion to dismiss is DENIED. I. FACTS AS ALLEGED For purposes of this motion to dismiss, the Court, as it must, “accept[s] as true all well-pleaded facts alleged in the complaint and draw[s] all reasonable inferences therefrom in the pleader’s favor.” A.G. ex rel. Maddox v. Elsevier, Inc., 732 F.3d 77, 80 (1st Cir. 2013) (quoting Santiago v. Puerto Rico, 655 F.3d 61, 72 (1st Cir. 2011)). A. The Parties Cerence is “an artificial-intelligence software company that operates almost exclusively in the automobile market . . . [selling] voice-operated virtual assistant software to . . .

approximately 60 automobile manufacturers, including Toyota, BMW, Daimler, and Ford.” [Am. Compl. ¶ 32]. Defendant Dhawan was the CEO and a board member of Cerence from June 7, 2019 to December 15, 2021. [Am. Compl. ¶ 29].1 As CEO, he ran Cerence’s day-to-day operations and was responsible for its financial performance. [Id.]. More specifically, he “personally reviewed and approved each [Cerence] contract for the sale of $1 million or more in licenses,” and “regularly spoke to investors and securities analysts regarding [Cerence]’s revenues.” [Id.]. Defendant Gallenberger was the CFO of Cerence from July 1, 2019 to February 7, 2022. [Am. Compl. ¶ 30].2 As CFO, he “personally reviewed and approved each [Cerence] contract for the sale of $1 million or more in licenses,” and “regularly spoke to investors and securities

analysts regarding [Cerence]’s revenues.” [Id.]. Both Dhawan and Gallenberger “directly participated in the management of Cerence’s operations, had direct and supervisory involvement in Cerence’s day-to-day operations, and had the ability to control and did control financial reporting and Cerence’s statements to investors.” [Am. Compl. ¶ 31]. Further, they “were involved in drafting, reviewing, publishing, and making

1 Dhawan was the CEO of Cerence’s predecessor, Nuance, from June 7, 2019 to October 1, 2019, when Cerence was spun off from Nuance. [Am. Compl. ¶ 29].

2 Gallenberger was the CFO of Cerence’s predecessor, Nuance, from July 1, 2019 to October 1, 2019, when Cerence was spun off from Nuance. [Am. Compl. ¶ 30]. [Cerence]’s statements to investors, including the false and misleading statements and omissions alleged” in the Amended Complaint. [Id.]. B. Cerence’s Business Cerence became a public company in 2019. [Am. Compl. ¶ 2]. From that date forward, Defendants told the public, investors, and analysts that the company was focused on growth and

had strong growth prospects. [Id.]. For example, on a February 11, 2020 earnings call for its first quarter as a public company, Dhawan said that Cerence was “laser-focused on profitably growing the business,” and Gallenberger stated that Cerence was “poised for strong revenue growth and profit performance for the fiscal year and beyond.” [Id. ¶ 33]. Shortly after, at Cerence’s first Analyst Day on February 18, 2020, Dhawan said the company was “very focused on growth,” and Gallenberger explained that one of the key takeaways that I want you to walk away from today with as it relates to Cerence is [how] the company historically has had a very good growth trajectory even in light of the fact that we’re part of an auto industry that has low-single-digit growth rates. We’ve been growing 10%, 15%. And so, there’s a secular tailwind that we have associated with the Cerence story. [Id. ¶ 34]; see also [id. (Gallenberger touting growth rates and the fact that company “expect[ed] that trend to continue,” with revenues nearly doubling by 2024). Gallenberger further said that Cerence had “‘visibility’ into future revenues . . . based on [a] ‘large amount of backlog’” (i.e. expected sales in the future). [Id.]. Analysts responded well to these comments and publicly noted confidence in the company’s prospects. [Id. ¶ 35]. To sell its software, Cerence enters “license agreements” with its customers, which give auto manufacturers the right to install Cerence’s software into their automobiles’ infotainment systems. See [Am. Compl. ¶¶ 3–4, 32]. The customer purchases an individual license for every automobile in which it installs the software, which allows the unlimited use of the software in that particular vehicle. See [id. ¶¶ 3–4]. In other words, a “license agreement” may give the auto manufacturer the right to many individual “licenses,” reflecting the fact that each vehicle requires its own license. See [id.] More than half of Cerence’s revenue comes from its license agreements. [Am. Compl. ¶ 35]. In 2021, for example, license revenue was 52% of the company’s total revenue. [Id.].

Relevant here, the license agreements come in two general forms. [Am. Compl. ¶ 37]. First, under variable license agreements, customers pay for each individual license when they actually install Cerence’s software in an automobile. [Id.]. When a variable license agreement is struck, the customer pays nothing up front. [Id.]. Rather, Cerence initially records expected revenue from the deal in its backlog (because it expects to get that revenue in the future in light of the agreement), and thereafter, as the customer puts the software into its vehicles, the customer sends a quarterly report to Cerence indicating the number of vehicles it produced and shipped with Cerence’s software. [Id.]. Based on those royalty reports, Cerence records revenue in the fiscal quarter during which the cars are produced. [Id. ¶ 38]. As it records that revenue, it also removes it from the backlog. [Id.]. It ultimately receives payment in the quarter after the

company records the revenue. [Id.]. Variable licenses generate steady quarterly revenue, [Am. Compl. ¶ 38], and are thus Cerence’s preferred license type, [id. ¶ 37]. Moreover, Plaintiff alleges that variable licenses are “an important barometer” of Cerence’s growth, [id. ¶ 38], apparently because the backlog shows expected future revenues. In contrast, the second type of agreements are fixed license agreements, which involve an upfront payment for a set number of licenses (i.e., cars that have Cerence’s technology). [Am. Compl. ¶ 39]. There are two types of fixed license agreements: “prepaid” and “minimum commitment” agreements. See, e.g., [id. ¶¶ 39, 67–68].

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

Related

Tellabs, Inc. v. Makor Issues & Rights, Ltd.
551 U.S. 308 (Supreme Court, 2007)
Bell Atlantic Corp. v. Twombly
550 U.S. 544 (Supreme Court, 2007)
Greebel v. FTP Software, Inc.
194 F.3d 185 (First Circuit, 1999)
Geffon v. Micrion Corporation
249 F.3d 29 (First Circuit, 2001)
Aldridge v. A.T. Cross Corp.
284 F.3d 72 (First Circuit, 2002)
Mesko v. Cabletron System, Inc.
311 F.3d 11 (First Circuit, 2002)
Hill v. Gozani
638 F.3d 40 (First Circuit, 2011)
Santiago v. Commonwealth of Puerto Rico
655 F.3d 61 (First Circuit, 2011)
A.G. Ex Rel. Maddox v. Elsevier, Inc.
732 F.3d 77 (First Circuit, 2013)
In Re SMITH & WESSON HOLDING CORP. SEC. LITIG
604 F. Supp. 2d 332 (D. Massachusetts, 2009)
Fitzer v. Security Dynamics Technologies, Inc.
119 F. Supp. 2d 12 (D. Massachusetts, 2000)
Brumbaugh v. Wave Systems Corp.
416 F. Supp. 2d 239 (D. Massachusetts, 2006)
Meyer v. Biopure Corp.
221 F. Supp. 2d 195 (D. Massachusetts, 2002)
In Re Allaire Corp. Securities Litigation
224 F. Supp. 2d 319 (D. Massachusetts, 2002)
Kader v. Sarepta Therapeutics, Inc.
887 F.3d 48 (First Circuit, 2018)

Cite This Page — Counsel Stack

Bluebook (online)
City of Miami Fire Fighters' and Police Officers' Retirement Trust v. Cerence Inc., Counsel Stack Legal Research, https://law.counselstack.com/opinion/city-of-miami-fire-fighters-and-police-officers-retirement-trust-v-mad-2024.