1 2 3 IN THE UNITED STATES DISTRICT COURT 4 FOR THE NORTHERN DISTRICT OF CALIFORNIA 5 IN RE STEM, INC. 6 SECURITIES LITIGATION Case No. 23-cv-02329-MMC 7 8 This Document Relates To: O FI R R D S E T R A D M I E S N M D IS E S D I N C G O N P S LA O I L N ID TI A F T F E S D ’ 9 ALL ACTIONS COMPLAINT
11 Before the Court is defendants’1 Motion, filed December 20, 2024, “to Dismiss 12 Plaintiffs’ First Amended Consolidated Complaint” pursuant to Rules 12(b)(6), 8(a), and 13 9(b) of the Federal Rules of Civil Procedure. Plaintiffs, who are identified below, have 14 filed opposition, to which defendants have replied. Having read and considered the 15 papers filed in support of and in opposition to the motion,2 the Court rules as follows.3 16 BACKGROUND 17 As set forth in the Court’s order filed August 30, 2024 (see Order Granting 18 Defendants’ Mot. to Dismiss Pls.’ Consol. Compl. (“August 30 Order”) at 1:19-4:7), 19 plaintiffs plead the following factual allegations, which, for purposes of the instant motion, 20 the Court accepts as true. 21
22 1 Defendants are, in the order set forth in the First Amended Consolidated Complaint (“FACC”), Stem, Inc. (“Stem”), John Carrington (“Carrington”), William Bush 23 (“Bush”), Larsh Johnson (“Johnson”), Prakesh Patel (“Patel”), Alan Russo (“Russo”), Bryan Ho (“Ho”), Star Peak Energy Transition Corp. (“Star Peak”), Eric Scheyer 24 (“Scheyer”), Michael C. Morgan (“Morgan”), Alec Litowitz (“Litowitz”), and Adam E. Daley (“Daley”). (See FACC ¶¶ 14-31.) 25 2 “Defendants’ Request for Judicial Notice” (Doc. No. 129) is hereby DENIED as 26 moot for the reason that the Court, in making the findings set forth herein, has not relied on any of the documents as to which such request is made. 27 1 Star Peak Energy Transition Corp. (“Star Peak”) is a special purpose acquisition 2 company (“SPAC”), i.e., a “blank check company with no business operations of its own” 3 (see FACC ¶ 27), which went public through an IPO completed August 20, 2020 (see id. 4 ¶ 54). 5 A SPAC, after “listing [itself] on a public exchange,” seeks to “acquire” a “private 6 company” as a means to “‘go public.’” (See id. ¶¶ 50-51.) The SPAC’s shareholders 7 must approve the acquisition at a specified price per share in “a vote on the so-called ‘de- 8 SPAC transaction’” and, at that time, have the option to “sell [their shares] on the 9 secondary market or have their shares redeemed” at the price specified. (See id. ¶ 51.) 10 After the transaction, the target company “carries on its operations as a public company,” 11 and the SPAC dissolves. (See id.) 12 Stem is a Delaware corporation that “provide[s] customers with energy storage 13 systems, primarily . . . batteries and related hardware, and software-enabled services to 14 operate those energy storage systems.” (See id. ¶ 15.) Stem’s software services include 15 its “Athena artificial intelligence (‘AI’) software,” which “purportedly allows its customers to 16 ‘automatically’ maximize [energy] storage assets.” (See id. ¶ 1.) Stem sells its products 17 to two types of customers: “behind-the-meter” (“BTM”) and “front-of-the-meter” (“FTM”). 18 (See id. ¶¶ 1, 24.) BTM customers are typically “individual business[es]” seeking to 19 “reduc[e] energy costs and enhanc[e] energy resiliency,” whereas projects for FTM 20 customers are “more complex” because they “use technology and data analysis to 21 balance supply and demand, manage outages, and maintain the stability and reliability of 22 the [electrical] grid.” (See id. ¶ 69.) 23 On September 28, 2020, Star Peak chose Stem as its acquisition “target” (see id. 24 ¶ 55), and, on December 3, 2020, the parties signed a merger agreement by which Star 25 Peak agreed to acquire Stem (see id. ¶ 102), after which Star Peak filed a prospectus4 on 26
27 4 A prospectus is an “offering document describing the company, the IPO terms 1 December 17, 2020 (hereinafter, the “Prospectus”). (See id. ¶ 107.) 2 On April 27, 2021, after the Prospectus was filed, Star Peak’s shareholders 3 approved the merger, and, on April 28, 2021, the companies merged. (See id. ¶¶ 109- 4 10.) Stem survived “as a wholly owned subsidiary of Star Peak,” and Star Peak 5 “renamed itself ‘Stem, Inc.’ and began operating [Stem’s] business.” (See id. ¶ 110.) On 6 April 29, 2021, Stem “went public with a closing price of $27.05” per share. (See id. ¶ 1.) 7 As of the filing of the FACC on November 8, 2024, the stock was “trad[ing] below one 8 dollar per share.” (See id.) 9 Lead plaintiffs Vishal Lawale and Vishale Thakkar held Star Peak shares5 as of 10 the March 4, 2021, record date, and were “entitled to vote on the [m]erger [between Stem 11 and Star Peak] at the [April 27, 2021] special meeting of shareholders.” (See id. ¶¶ 12- 12 13.) Plaintiffs allege “certain of [Stem’s] senior executives and directors . . . engag[ed] in 13 a host of activities that reaffirmed the purported viability” of Stem’s “defective business 14 model” and “ma[de] false and misleading statements” in several categories, including 15 statements about said business model, statements about “risks to Stem’s business,” 16 statements about the success of “Stem’s Massachusetts FTM project,” and statements 17 about “Stem’s key software Athena,” which plaintiffs allege “was neither automated nor 18 viable for FTM projects.” (See id. ¶ 2.) 19 On behalf of themselves and a putative class “of all persons who purchased Stem 20 securities between” December 4, 2020, and April 3, 2023 (hereinafter, the “Class Period”) 21 (see id.), plaintiffs assert five claims for relief, titled, respectively, (1) “Violation of Section 22 14(a) of the Exchange Act of 1934 and SEC Rule 14a-9 against the 14(a) Defendants,”6 23 (2) “Violation of § 20(a) of the Exchange Act Against the 14(a) Individual Defendants,” 24
25 5 After the April 28, 2021, merger, Star Peak, as noted, re-named itself “Stem, Inc.,” and, consequently, individuals who held “Star Peak” shares prior to the merger 26 became “Stem” shareholders on that date. (See FACC ¶ 14.) 27 6 The 14(a) Defendants are Stem, Star Peak, Bush, Carrington, Daley, Litowitz, 1 (3) “Violation of § 10(b) of the Exchange Act and SEC Rule 10b-5 Against the Fraud 2 Defendants,”7 (4) “Violation of § 20(a) of the Exchange Act Against the Individual Fraud 3 Defendants,” and (5) “Violation of § 20A of the Exchange Act Against Defendants Bush, 4 Carrington, Daley, Johnson, and Russo for Insider Selling.” (See id. ¶¶ 432-74.) 5 By its August 30 Order, the Court dismissed all of the above-listed claims as set 6 forth in plaintiffs’ initial Consolidated Complaint (“CC”). (See August 30 Order at 27:6-8.) 7 By the instant motion, defendants again move to dismiss those claims. 8 LEGAL STANDARD 9 Dismissal under Rule 12(b)(6) of the Federal Rules of Civil Procedure “can be 10 based on the lack of a cognizable legal theory or the absence of sufficient facts alleged 11 under a cognizable legal theory.” See Balistreri v. Pacifica Police Dep’t., 901 F.2d 696, 12 699 (9th Cir. 1990). Rule 8(a)(2), however, “requires only ‘a short and plain statement of 13 the claim showing that the pleader is entitled to relief.’” See Bell Atlantic Corp. v. 14 Twombly, 550 U.S. 544, 555 (2007) (quoting Fed. R. Civ. P. 8(a)(2)); see also Fed. R. 15 Civ. P. 8(d)(1) (providing “[e]ach allegation must be simple, concise, and direct”). 16 Consequently, “a complaint attacked by a Rule 12(b)(6) motion to dismiss does not need 17 detailed factual allegations.” See Twombly, 550 U.S. at 555. Nonetheless, “a plaintiff’s 18 obligation to provide the grounds of his entitlement to relief requires more than . . . a 19 formulaic recitation of the elements of a cause of action . . . .” See id. (internal quotation, 20 citation, and alteration omitted). 21 In analyzing a motion to dismiss, a district court must accept as true all material 22 allegations in the complaint and construe them in the light most favorable to the 23 nonmoving party. See NL Indus., Inc. v. Kaplan, 792 F.2d 896, 898 (9th Cir. 1986). “To 24 survive a motion to dismiss,” however, “a complaint must contain sufficient factual matter, 25 accepted as true, to ‘state a claim to relief that is plausible on its face.’” Ashcroft v. Iqbal, 26
27 7 The Fraud Defendants are Stem, Star Peak, Bush, Carrington, Daley, Ho, 1 556 U.S. 662, 678 (2009) (quoting Twombly, 550 U.S. at 570). “Factual allegations must 2 be enough to raise a right to relief above the speculative level,” Twombly, 550 U.S. at 3 555, and courts “are not bound to accept as true a legal conclusion couched as a factual 4 allegation,” see Iqbal, 556 U.S. at 678 (internal quotation and citation omitted). 5 Rule 9(b) applies to claims based on “misrepresentation,” see In re GlenFed, Inc. 6 Sec. Litig., 42 F.3d 1541, 1553 (9th Cir. 1994) (en banc), and requires a plaintiff to 7 “identify the who, what, when, where, and how of the misconduct charged, as well as 8 what is false or misleading about [the purportedly fraudulent] statement, and why it is 9 false,” see Cafasso, U.S. ex rel. v. Gen. Dynamics C4 Sys., Inc., 637 F.3d 1047, 1055 10 (9th Cir. 2011) (internal quotation and citation omitted; alteration in original). 11 DISCUSSION 12 I. Challenged Statements 13 Plaintiffs allege the Fraud Defendants violated section 10(b) of the Securities and 14 Exchange Act of 1934 (hereinafter, the “Exchange Act”) and Securities and Exchange 15 Commission Rule 10b-5 by “disseminat[ing] or approv[ing] the materially false and 16 misleading statements . . . which they knew, or were deliberately reckless in not knowing, 17 were misleading.” (See FACC ¶ 450.) 18 To state a claim under section 10(b) and Rule 10b-5, a plaintiff must allege: “(1) a 19 material misrepresentation or omission; (2) scienter; (3) a connection between the 20 misrepresentation or omission and the purchase or sale of a security; (4) reliance; 21 (5) economic loss; and (6) loss causation.” See Oregon Pub. Emps. Ret. Fund v. Apollo 22 Grp. Inc., 774 F.3d 598, 603 (9th Cir. 2014). 23 Allegations of fraud must also “satisfy the dual pleading requirements of Federal 24 Rule of Civil Procedure 9(b) and the [Private Securities Litigation Reform Act of 1995 25 (‘PSLRA’)].” See Zucco Partners, LLC v. Digimarc Co., 552 F.3d 981, 990 (9th Cir. 26 2009). A plaintiff must, under Rule 9(b), “state with particularity the circumstances 27 constituting fraud,” see Fed. R. Civ. P. 9(b), and must, under the PSLRA, “specify each 1 statement is misleading,” and “state with particularity facts giving rise to a strong 2 inference that the defendant acted with the required state of mind,” see Zucco Partners, 3 552 F.3d at 990-91 (quoting 15 U.S.C. §§ 78u-4(b)(1)-(2)). 4 Here, plaintiffs allege defendants made ninety-four false or misleading 5 statements.8 In their briefing, the parties divide these statements into two groups: 6 (1) statements regarding Athena’s automation and (2) statements regarding Athena’s 7 success in the FTM market. (See Mot. at 7-11; Opp. at 9-11.) The Court first sets forth 8 below the statements in those two groupings. 9 A. Statements Regarding Athena’s Automation 10 Plaintiffs identify fifty-four statements regarding Athena’s automated functions. 11 (See Statement Nos. 1-14, 19-36, 41-47, 50, 54, 57-58, 63-65, 67-68, 73, 77, 81-82, and 12 89-90.) Plaintiffs argue the statements falsely represented Athena as “fully automated” 13 (see Opp. at 10:14), whereas defendants argue the statements “represent[ed] that 14 Athena automated only certain functions” (see Mot. at 7:12) (emphasis in original).9 15 Thirty of the challenged statements in this grouping include the following language: 16 “By combining advanced energy storage solutions with Athena™, a worldclass AI- 17 powered analytics platform, Stem enables customers and partners to optimize 18 energy use by automatically switching between battery power, onsite generation 19 8 All challenged statements referenced herein are set forth in Exhibit A to the 20 FACC (hereinafter, “Exhibit A”) (see Doc. No. 127-1), which plaintiffs submitted in compliance with the Court’s prior order that plaintiffs “set out in chart form their securities 21 fraud allegations” (see August 30 Order at 27:11-15). 22 9 As set forth in the Prospectus, Athena’s functions include “predict[ing] customer facility and system peaks,” “collecting data from meters, breakers, storage systems and 23 solar generation systems,” processing “1 terabyte of data every day . . . along with weather, energy prices and grid information” to ensure such data is “complete and 24 accurate and that anomalies are detected,” providing “an interactive user interface for partners and customers to understand the operation of the energy storage systems along 25 with the insights Athena provides,” enabling “customers to participate in markets and grid programs with automated dispatching,” “observ[ing] asset and system health to manage 26 charging and discharging cycles,” “provid[ing] transparent performance reporting” to customers, “supporting data collection and transfer between diverse software 27 applications,” and “employ[ing] state-of-the-art informational safeguards and security 1 and grid power.” (See Statement Nos. 3-4, 6-11, 19-20, 22-23, 26-27, 29-34, 42-43, 2 45-47, 50, 58, 63, 73, and 77) (emphasis in original). Plaintiffs contend said language 3 would mislead a reasonable investor to believe Athena was “fully automated.” (See Opp. 4 at 10:14.) By identifying the particular function that is asserted to be automated, 5 however—“switching between battery power, onsite generation and grid power” (see, 6 e.g., Statement No. 3)—the statement limits the scope of automation to that function. 7 Two challenged statements include the following language: “Athena automates 8 system discharges across multiple different utility territories, collaborating with 9 the utilities to provide instant grid support when and where it is needed. . . . And 10 when power prices drop at night Athena automates their recharging.” (See Statement 11 Nos. 2 and 25) (emphasis in original). Again, by identifying the particular function that is 12 asserted to be automated—“system discharges” and “recharging” (see id.)—the 13 statements limit the scope of automation to that function.10 14 Two challenged statements pertain to the development of Athena Bidder11 and 15 include the following language:
16 Athena is also executing in Massachusetts with its fully automated energy dispatch platform called Athena 17 Bidder, where this past quarter Stem began AI automated bidding into the ISO New England energy and frequency 18 regulation markets using real time price forecasting algorithms. 19 (See Statement No. 54) (emphasis in original). 20 Last month, we introduced new advanced applications for 21 wholesale energy markets [including] . . . Athena Bidder, which incorporates an owner’s asset strategy and continuously 22 generates market bids to maximize wholesale market revenues. 23 . . . Athena continuously forecast solar generation, the 24
25 10 Stem bundles “large lithium-ion batteries” with its Athena software. (See FACC ¶ 388.) The above-referenced function is the charging and discharging of those 26 batteries. 27 11 Athena Bidder is an “application” that was introduced in October 2021. (See battery state of charge, energy and frequency regulation 1 prices, market options and incentive goals.
2 With this information, Athena optimizes executing millions of scenarios per hour to determine the best 3 operation for each site and then automatically generates bids for each market interval over the coming hours and 4 days.
5 (See Statement No. 57) (emphasis in original). 6 As with the above-referenced statements, the statements pertaining to Athena 7 Bidder identify the function asserted to be automated—“automatically generat[ing] bids 8 for each [energy] market interval” (see id.)—and thereby limit the scope of automation to 9 that function. 10 Two challenged statements read as follows: “Company generates revenue by 11 providing customers with integrated energy storage systems, long-term recurring 12 software services and energy market participation through its proprietary software 13 platform, called Athena™, which enables AI-automated system operations.” (See 14 Statement Nos. 1 and 24) (emphasis in original). In describing Athena, the FACC uses 15 the terms “operations” and “functions” interchangeably (see FACC ¶¶ 170-71), and, as 16 with the above-cited statements, there is no representation that all operations are 17 automated. 18 One challenged statement reads as follows: “Our shared vision [with AlsoEnergy] 19 is to empower clean energy asset owners and operators to scale their businesses by 20 leveraging AI-automated, data-driven operations enabled by Athena.” (See 21 Statement No. 64) (emphasis and alteration in original). As with the above-quoted 22 references to “operations,” there is no representation that all such operations are 23 automated. (See id.) 24 One challenged statement reads as follows:
25 Starting with the Stem energy storage business, our software drives exceptional economics for our customers. Athena 26 automates everything, including reducing costs, increasing revenues, complying with regulatory incentives and constraints 27 and minimizing greenhouse gas emissions. Our broad market value for our customers. 1 (See Statement No. 65) (emphasis in original). 2 Although it uses the word “everything,” the statement does not refer to a function 3 of Athena, let alone the entirety of its functions. Rather, it speaks to the results 4 customers can achieve by using a software program. 5 Lastly, one statement includes the following language: 6 This is a fully automated process lights out. There’s no 7 humans involved in this loop. Once we set it up, it just keeps running. And then second, we’re at the point of asset 8 performance management. All the time we’re doing this, we’re continually getting streaming data from these sites. Data that 9 can range from every second to every few minutes.
10 (See Statement No. 82) (emphasis in original). 11 Although plaintiffs point to Stem’s use of the phrase “is fully automated,” plaintiffs 12 omit any context for the preceding noun, “This,” and, consequently, again fail to show 13 Stem represented all of Athena’s functions as being automated. Indeed, the phrase “in 14 this loop” suggests the reference is only to a particular aspect of the program. 15 In sum, defendants’ statements clearly pointed out certain functions of Athena that 16 were automated. There is no language in any statement identified by plaintiffs, however, 17 that would lead a reasonable investor to believe Athena’s functions were exclusively 18 automated. 19 Accordingly, to the extent plaintiffs’ section 10(b) and Rule 10b-5 claims are based 20 on the allegation that defendants falsely represented Athena was fully automated, said 21 claims are subject to dismissal. 22 B. Statements Regarding Athena’s Success in the FTM Market 23 Plaintiffs identify forty allegedly false or misleading statements pertaining to 24 Athena’s success in the FTM market. (See Statement Nos. 15-18, 37-40, 48-49, 51-53, 25 55-56, 59-62, 66, 69-72, 74-76, 78-80, 83-88, and 91-94.) Unlike the statements in the 26 previous group, there is no disagreement as to their meaning. 27 // 1 Seven challenged statements concern Stem’s success and include the following 2 language:
3 As an early participant in the BTM market, we developed operational focus and technical capabilities that position 4 us to have multiple product offerings and services in the evolving market for FTM energy storage services. We 5 believe that Athena’s ability to optimize operations in both the BTM and FTM markets is unique in the industry and 6 provides us with a competitive advantage.
7 (See Statement Nos. 15, 37, 69, and 91) (emphasis in original).
8 I mean, ultimately, I think as we’ve always said and I think most have agreed, this is a software story. It’s not a sale of 9 somebody else’s hardware. It’s really what—the differentiating component of Stem is the Athena platform. 10 That’s always been true, and I think that’s going to continue to be true in the future. 11 (See Statement No. 66) (emphasis in original). 12 And then finally, on the front-of-the meter side, this is a 13 market, as I mentioned, that we really continue to have great success on. 14 And as I mentioned, really to go from 0 to leading market 15 share in 18 months in New England ISO is very impressive. And it says a lot about the software. 16 (See Statement No. 83) (emphasis in original). 17 While we went from 0 to over 50% market share in 18 18 months in the New England ISO.
19 So a real accomplishment that is very much attributable to our software platform because we could translate our 20 behind-the-meter software deck to that front-of-the-meter need. 21 (See Statement No. 84) (emphasis in original). 22 Twenty-seven challenged statements concern risk assessment and include, with 23 immaterial differences,12 the following language: 24 If Stem is unsuccessful in developing and maintaining its 25 proprietary technology, including the Athena platform, Stem’s ability to attract and retain partners could be 26
27 12 For example, Statement No. 86 begins with “If we are unsuccessful” and impaired, Stem’s competitive position could be adversely 1 affected and Stem’s revenue could be reduced. 2 (See Statement Nos. 16, 38, 51, 59, 70, 74, 78, 86, and 92) (emphasis in 3 original).
4 Stem’s technology, including the Athena platform, could have undetected defects, errors or bugs in hardware or 5 software which could reduce market adoption, damage Stem’s reputation with current or prospective customers 6 and/or expose Stem to product liability and other claims that could materially and adversely affect Stem’s 7 business. 8 (See Statement Nos. 17, 39, 52, 60, 71, 75, 79, 87, and 93) (emphasis in 9 original).
10 The distributed generation industry is an emerging market and our distributed generation offerings may not receive 11 widespread market acceptance.
12 . . . Enterprises may be unwilling to adopt our offerings over traditional or competing power sources for any number of 13 reasons, including the perception that our technology is unproven. . . . Because this is an emerging industry, broad 14 acceptance of our hardware and software-enabled services is subject to a high level of uncertainty and risk. 15 (See Statement Nos. 18, 40, 53, 61, 72, 76, 80, 88, and 94) (emphasis in 16 original). 17 The Court first turns to the question of falsity, i.e., whether a challenged statement 18 represents something different than what actually exists, or, alternatively, whether a 19 statement was misleading, i.e., gave an “impression of a state of affairs that differs in a 20 material way from the one that actually exists.” See Sneed v. Talphera, Inc., 147 F.4th 21 1123, 1131 (9th Cir. 2025) (internal quotation and citation omitted).13 22 C. Whether the Statements Were False or Misleading 23 In alleging claims under section 10(b) and Rule 10b-5, a plaintiff must “identify[ ] 24 the statements at issue and set[ ] forth what is false or misleading about the statement 25
26 13 Defendants do argue some of the statements in this grouping are “protected” as forward-looking or opinion. (See Mot. at 12:11, 13:13.) The Court, in light of its finding 27 below that plaintiffs have failed to plead any such statement is false or misleading, does 1 and why the statements were false or misleading at the time they were made.” See In re 2 Rigel Pharms., Inc. Sec. Litig., 697 F.3d 869, 876 (9th Cir. 2012). To determine whether 3 a statement is misleading, courts analyze the challenged statement from the perspective 4 of “a reasonable investor,” i.e., one that “acts with care and seeks out relevant 5 information.” See Sneed, 147 F.4th at 1131. “A reasonable investor cares about a 6 statement’s surrounding text, including hedges, disclaimers, and apparently conflicting 7 information.” Id. (internal quotation and citation omitted). Consequently, a plaintiff must 8 “demonstrate that a particular statement, when read in light of all the information then 9 available to the market, or a failure to disclose particular information, conveyed a false or 10 misleading impression.” See In re Convergent Techs. Sec. Litig., 948 F.2d 507, 512 (9th 11 Cir. 1991). By the instant motion, defendants argue plaintiffs have failed to plead a false 12 or misleading statement.14 13 Here, in arguing the statements set forth above were false or misleading, plaintiffs 14 rely on three sources of information: (1) reports from confidential witnesses (“CWs”); (2) a 15 statement made by Carrington after the Class Period; and (3) Stem’s financial results. 16 The Court analyzes each source in turn. 17 1. Confidential Witnesses 18 To satisfy the PSLRA, a complaint “relying on statements from confidential 19 witnesses” must describe the witnesses “with sufficient particularity to establish their 20 reliability and personal knowledge,” and the statements “must themselves be indicative of 21 scienter.” See Zucco Partners, 552 F.3d at 995. To describe a witness with “sufficient 22 particularity,” a plaintiff must “provide[ ] sufficient detail about [the] confidential witness’ 23
24 14 At the outset, defendants ask the Court to dismiss the FACC, as it did the CC (see August 30 Order at 8:21-23), on the asserted ground that the FACC constitutes 25 impermissible “puzzle pleading.” (See Mot. at 5:1-5.) While the Court agrees plaintiffs could have more precisely identified why each statement was false or misleading (see 26 Mot. at 5:14-26), plaintiffs have improved their pleading in general and have complied with the Court’s order “to set out in chart form their securities fraud allegations” (see 27 August 30 Order at 27:11-15). Consequently, the Court finds dismissal on said structural 1 position within the defendant company to provide a basis for attributing the facts reported 2 by that witness to the witness’ personal knowledge.” See id. Although hearsay is not 3 “automatically precluded from consideration,” a hearsay statement “may indicate that a 4 confidential witnesses’ report is not sufficiently reliable, plausible, or coherent to warrant 5 further consideration.” See id. at 997 n.4. 6 Here, by its August 30 Order, the Court found plaintiffs failed to show falsity based 7 on information provided by four CWs, namely, CW1, CW2, CW3, and CW4. (See August 8 30 Order at 8:24-11:2.) Specifically, as to CW1, CW2, and CW4, the Court held plaintiffs 9 failed to describe each such CWs’ job responsibilities “with sufficient specificity to 10 establish their reliability” (see id. at 10:1-2), and although the Court found plaintiffs 11 sufficiently pleaded CW3’s job responsibilities, it nonetheless held plaintiffs failed to 12 demonstrate “the information provided by CW3 [was] based on personal knowledge” (see 13 id. at 11:1-2). 14 In the FACC, plaintiffs, while abandoning CW4, replead information from CW1, 15 CW2, and CW3.15 As to all ninety-four challenged statements, plaintiffs allege each such 16 statement was false or misleading because of information provided by CW1, CW2, and 17 CW3.16 Defendants argue the CWs “lack reliability and personal knowledge.” (See Mot. 18 at 15:4.) In response, plaintiffs contend the FACC addresses the “deficiencies” identified 19 in the Court’s prior order “by adding allegations as to why these witnesses were in a 20 position to know the detailed information they provide.” (See Opp. at 6:7-9.) The Court 21 addresses each CW in turn. 22 15 The identities of the CWs in the FACC are the same as in the CC. For example, 23 CW1 in the FACC is the same individual as CW1 in the CC. (Compare CC ¶¶ 46-49 with FACC ¶¶ 46-49.) 24 16 For example, as to Statement Nos. 1 to 23, a range comprising statements from 25 both of the above-referenced two groupings, plaintiffs allege such statements were false or misleading because of, in part, the following: “CW1 and CW2 reported that the 26 Company did not have a working product for FTM projects because Athena was not automated for FTM” and “CW3 confirmed that when CW3 arrived in March 2021, Athena 27 lacked functionality with respect to FTM projects.” (See Exhibit A re: Statement Nos. 1- 1 a. CW1 2 The FACC sufficiently pleads CW1’s job responsibilities by alleging CW1 “worked 3 on FTM deals” and was responsible for “answering client questions, assisting the FTM 4 sales team with drafting” proposals, “sending proposals via emails to clients, managing 5 deal flow across the entire sales cycle,” and “serv[ing] as an expert on the entire sales 6 cycle.” (See FACC ¶ 46.) 7 Plaintiffs attribute the following information to CW1, who, as explained below, 8 appears to have acquired it from other individuals: “Athena did not work for the [FTM] 9 Massachusetts project because Stem’s Athena software was not automated and, thus, 10 required a Stem employee to use an Excel spreadsheet to manually perform functions 11 Athena was supposed to offer” (see id. ¶ 67); “Stem did not have a working product for 12 FTM projects because Athena was not fully automated for FTM” (see id. ¶ 70); “all of 13 Stem’s FTM clients CW1 worked with described Athena as an empty suit when it came to 14 the software for FTM projects because Stem simply did not have the software it said it 15 had” (see id. ¶ 71); and “many deals did not close because customers . . . realized 16 Athena did not work for FTM projects” (see id. ¶ 89). 17 With regard to the first two statements, there is no indication CW1 would have 18 personal knowledge, from a job in sales, as to which functions were performed manually 19 for FTM projects, and, to the extent CW1 reports information from other Stem employees, 20 there is no showing that any such employee(s) had personal knowledge as to such 21 information.17 With regard to the other information provided by CW1, there is no showing 22 the referenced “clients” had personal knowledge as to Athena’s technology, nor does 23 CW1 make clear whether he/she is conveying what any customer reported or, rather, 24 his/her own conclusions or assumptions based on what he/she was told. See In re 25
26 17 Additionally, as CW1 does not specify a particular function of Athena that was performed manually by an employee with “an Excel spreadsheet” (see FACC ¶ 67), such 27 information does not contradict defendants’ representation that certain functions are 1 Pivotal Sec. Litig., No. 3:19-CV-03589-CRB, 2020 WL 4193384, at *13 (N.D. Cal. July 21, 2 2020) (dismissing plaintiffs’ section 10(b) claim; finding “unreliable hearsay” and 3 “conclusory assertions” insufficient to support finding of falsity). 4 Plaintiffs also attribute the following information to CW1, who “explained that 5 [he/she] served as an expert on the entire sales cycle” (see FACC ¶ 46): CW1 “ask[ed] 6 the software team for a working Athena model” for FTM projects but “never received such 7 a model” (see id. ¶ 79); and “Stem’s FTM deal close rate for its eight account executives 8 was only 15% to 20%” (see id. ¶ 89). 9 Although the above-referenced information appears to be based on personal 10 knowledge, it does not demonstrate the falsity of any challenged statement, whether 11 pertaining to automation or success/risk, as the non-delivery of the model does not show 12 Athena lacked the automated functions it described and, in the absence of any context to 13 explain the significance of the above-referenced percentages, the above-referenced 14 close rate fails to show any statements concerning success or risk were false or 15 misleading. 16 Moreover, and with equal importance, CW1 provides no time frame for his/her 17 information, nor have plaintiffs otherwise included any allegations to show any challenged 18 statements were “false or misleading at the time they were made.” See In re Rigel, 697 19 F.3d at 876. 20 Accordingly, plaintiffs have not shown falsity based on the information provided by 21 CW1. 22 b. CW2 23 In the FACC, plaintiffs sufficiently plead CW2’s job responsibilities, in that they 24 allege, inter alia, he/she “held several positions . . . including as a Stem analyst,” was 25 “part of Stem’s Market Enablement Group that included approximately 20 individuals,” 26 reported “ultimately to [defendant] Russo,” and “worked with sales involving, among other 27 things, FTM projects.” (See FACC ¶ 48.) 1 spreadsheet to handle functions on the Massachusetts FTM project that were supposed 2 to be handled by Athena” and “hear[d] from a Stem senior sales associate that a Stem 3 operations manager had complained because the operations manager was annoyed at 4 having to do so many manual tasks.” (See id. ¶ 74.) 5 As with the information CW1 provided regarding Athena’s automation, there are no 6 allegations demonstrating the reliability of the information conveyed, namely, allegations 7 showing that the individuals who communicated the above-referenced information had 8 personal knowledge thereof. Moreover, as with CW1, CW2 provides no time frame for 9 his/her information, nor have plaintiffs otherwise included any allegations to show any 10 challenged statements were “false or misleading at the time they were made.” See In re 11 Rigel, 697 F.3d at 876. 12 Accordingly, plaintiffs have not shown falsity based on the information provided by 13 CW2. 14 c. CW3 15 The Court previously found the CC sufficiently pleaded CW3’s job responsibilities 16 (see August 30 Order at 10:3-18), and given that the FACC realleges the same 17 responsibilities (compare CC ¶ 49 with FACC ¶ 49), the Court again finds those 18 allegations suffice. 19 Plaintiffs repeat, however, the allegation that the Court previously found was not 20 shown to be based on personal knowledge (see August 30 Order at 10:15-18), namely, 21 that CW3 was “told that some of the content on Athena’s FTM software could not be used 22 because the products were still in development and were not functional” (see FACC 23 ¶ 81). Plaintiffs fail to cure said earlier-identified deficiency, such as by “specify[ing] 24 which members of the product team conveyed the above-alleged information to CW3, or 25 facts demonstrating their personal knowledge of the information conveyed.” (See August 26 30 Order at 10:19-21.) 27 Accordingly, plaintiffs have not shown falsity based on the information provided by 1 2. Carrington’s Statement 2 Plaintiffs allege Carrington, who served as Stem’s CEO from December 2013 until 3 September 2024, “admitted post-Class Period18 during Stem’s 02/28/24 earnings call 4 discussing the Company’s Q4/ 2023and FY 2023 results, Stem’s ‘program management 5 team adds a ‘human-in-the-loop’ to Athena’s operations.” (See FACC ¶¶ 16, 75) 6 (alteration omitted). Plaintiffs allege all ninety-four challenged statements were false or 7 misleading given Carrington’s statement.19 An after-the-fact statement, however, “does 8 not constitute an admission unless it contradicts the substance of an earlier statement 9 and essentially states ‘I knew it all along.’” See Lopes v. Fitbit, Inc., No. 18-CV-06665- 10 JST, 2020 WL 1465932, at *11 (N.D. Cal. Mar. 23, 2020), aff’d, 848 F. App’x 278 (9th Cir. 11 2021). Here, the most recent of the challenged statements were made on February 17, 12 2023 (see Statement Nos. 90-94), a year before Carrington’s statement, which describes 13 Athena in the present, not past, tense. Moreover, Carrington’s statement does not 14 contradict any of the above-referenced statements, as it does not make any 15 representation as to any particular specified function or Athena’s success in the FTM 16 market. Indeed, Carrington’s statement is in accord with the challenged statements 17 concerning automation, which, as discussed above, do not constitute representations that 18 Athena was fully automated. 19 Accordingly, plaintiffs have not show falsity based on Carrington’s statement. 20 3. Stem’s Financial Results 21 Plaintiffs allege defendants, on December 4, 2020, predicted “Stem would be 22
23 18 The Class Period, as noted, is from December 4, 2020, to April 3, 2023. (See FACC ¶ 2.) 24 19 For example, as to Statement Nos. 1 to 23, a range, as noted, comprising 25 statements from both of the above-referenced two groupings, plaintiffs allege such statements were false or misleading because “[d]efendant Carrington admitted during 26 Stem’s [February 28, 2024] earnings call that Stem’s ‘program management team adds a ‘human-in-the-loop’ to Athena’s operations, thereby confirming Athena was never fully 27 automated for FTM.” (See Exhibit A re: Statement Nos. 1-23) (emphasis in original; 1 profitable with adjusted EBITDA20 of $28 million” for FY 2022 (see FACC ¶¶ 99, 293), but 2 defendants did not “deliver as promised” and “reported adjusted EBITDA of negative $46 3 million for FY 2022” (see id. ¶¶ 101, 310). Plaintiffs characterize thirty-one challenged 4 statements as false or misleading in light of Stem’s financial results. (See Statement 5 Nos. 51-53, 59-61, 70-94.) As to statements pertaining to Athena’s automation, plaintiffs 6 allege those statements were false or misleading because “Stem was unable to convert 7 its business to a high-margin software Company, as reflected by its low gross margins 8 and earnings.” (See, e.g., Exhibit A re: Statement No. 73.) Plaintiffs fail, however, to 9 explain how Stem’s performance demonstrates Athena did not automate certain functions 10 for FTM projects. 11 As to challenged statements pertaining to Stem’s success/risk, plaintiffs allege 12 those statements were false or misleading because “[t]he warned-of risks had already 13 materialized as evidenced by the fact that Stem was unable to convert its business to a 14 profitable high-margin software Company, as reflected by the magnitude of its miss” in 15 forecasting earnings for FY 2022. (See, e.g., Exhibit A re: Statement No. 51.) The only 16 allegations on which plaintiffs rely to show Stem, at the time it predicted favorable results, 17 knew it would not do well are based on information provided by CW1, which information, 18 as discussed above, has not been shown to be reliable. 19 Accordingly, plaintiffs have not shown falsity based on Stem’s financial results. 20 4. Conclusion: False or Misleading 21 For all of the reasons set forth above, the Court finds the above-discussed three 22 sources of information, whether viewed separately or collectively, fail to demonstrate a 23 false or misleading representation or omission, and, accordingly, plaintiffs’ section 10(b) 24 claims are subject to dismissal.21 25 20 EBITDA is an acronym for “[e]arnings before interest, taxes, depreciation, and 26 amortization.” (See Opp. at ii.) 27 21 In light of the above finding, the Court does not address herein the other 1 II. Scheme Liability 2 Rules 10b-5(a) and (c) make it unlawful to “employ any device, scheme, or artifice 3 to defraud” or to “engage in any act, practice, or course of business which operates or 4 would operate as a fraud or deceit upon any person, in connection with the purchase or 5 sale of any security.” See 17 C.F.R. § 240.10b-5(a), (c). To state a claim for scheme 6 liability, a plaintiff must allege “each defendant committed a manipulative or deceptive act 7 in furtherance of the scheme.” See Cooper v. Pickett, 137 F.3d 616, 624 (9th Cir. 1997). 8 A scheme liability claim can be based on false or misleading statements that also 9 violate section 10(b), see Lorenzo v. Securities and Exchange Comm’n., 587 U.S. 71, 80 10 (2019), but where the “alleged scheme consists entirely of” failed section 10(b) 11 statements, a plaintiff likewise fails to adequately plead a scheme, see Kang v. PayPal 12 Holdings, Inc., 620 F.Supp.3d 884, 902 (N.D. Cal. 2022). Here, by its August 30 Order, 13 the Court dismissed plaintiffs’ claim alleging scheme liability to the extent said claim was 14 based on allegedly false or misleading statements, finding plaintiffs failed to plead any 15 such statement violated section 10(b). (See August 30 Order at 22:18-23.) As discussed 16 above, the Court again finds plaintiffs fail to plead an actionable section 10(b) statement. 17 Where, as here, a plaintiff additionally relies on conduct other than an allegedly 18 false statement, such plaintiff must allege a transaction or other event “the principal 19 purpose and effect of which is to create [a] false appearance of fact.” See Simpson v. 20 AOL Time Warner Inc., 452 F.3d 1040, 1048 (9th Cir. 2006), vacated on other grounds, 21 519 F.3d 1041 (9th Cir. 2008). “Conduct that is consistent with the defendants’ normal 22 course of business,” however, “would not typically be considered to have the purpose 23 and effect of creating a misrepresentation,” and thus, standing alone, does not suffice to 24 plead scheme liability. See id. at 1050 (collecting cases) (noting creation of “[s]ham 25 business transactions with no legitimate business purpose” would suffice to plead 26 scheme liability). 27 In its prior order, the Court found the scheme liability allegations in the CC, 1 and made certain remarks during earnings calls, were unavailing, as there was “nothing 2 in the CC to demonstrate any [such] acts [were] outside the defendants’ ‘normal course 3 of business.’” (See August 30 Order at 23:5-20) (quoting Simpson, 452 F.3d at 1050). 4 To the extent plaintiffs’ scheme liability claim relies on their failed section 10(b) 5 statements and repleading the above-referenced allegations from the CC (see, e.g., 6 FACC ¶ 255), said claim is subject to dismissal.22 The Court next turns to three new 7 theories of scheme liability as alleged in the FACC, each based on a particular event. 8 First, on December 16, 2021, “Stem announced its acquisition of AlsoEnergy, a 9 company that purportedly provides customers with solar asset performance monitoring 10 and control software, for $695 million.” (See id. ¶ 114.) Plaintiffs allege defendants 11 purchased AlsoEnergy “to combine the financial results of the two companies and not 12 report them separately,” thereby “muddling the financial results of the two companies” 13 and “masking Stem’s issues with Athena in the FTM market.” (See id. ¶ 256.) Plaintiffs 14 fail, however, to allege defendants’ acquisition of AlsoEnergy was outside defendants’ 15 normal course of business. Indeed, according to plaintiffs, AlsoEnergy was “‘a global 16 leader in solar asset management software’ with ‘60% gross margin across its software’ 17 and other service businesses” (see id. ¶ 114), which suggests defendants’ acquisition 18 was a business decision that did not have the “purpose and effect of creating a 19 misrepresentation,” see Simpson, 452 F.3d at 1050. 20 Second, on February 24, 2022, Stem announced its “flagship $500 million . . . FTM 21 project” with Available Power, a company that “purportedly designs, develops, and 22 deploys distributed energy resources and microgrid systems for commercial and 23 industrial real estate.” (See FACC ¶¶ 43, 84.) Plaintiffs allege defendants ordered 24 22 Additionally, to the extent plaintiffs again rely on their allegation that 25 “engagements listed in the [FTM] pipeline were not actual deals or even commitments on the part of the developer, rather, they represented just a chance with no guarantee of 26 getting a platform deal signed” (compare FACC ¶ 277 with CC ¶ 83), such reliance is unavailing, as there is no allegation to support a finding that reporting potential 27 engagements was outside defendants’ normal course of business, or that such 1 batteries “for the Available Power project” based on a “letter of intent” rather than a 2 “customer purchase order.” (See id. ¶¶ 85, 262.) While plaintiffs allege such act was “in 3 violation of Company policy” (see id. ¶ 85), their only basis for such allegation comes 4 from CW2, and plaintiffs fail to show how CW2 has personal knowledge of the above- 5 referenced policy given that CW2, as noted, worked in sales, a division not shown to be 6 involved in decisions concerning the equipment needed to accompany the software. 7 Moreover, even assuming, arguendo, CW2’s personal knowledge, CW2 “indicated it was 8 Stem’s standard procedure not to procure hardware without a customer purchase order 9 but that exceptions to this procedure were not uncommon.” (See id. ¶ 85) (emphasis 10 added). Consequently, plaintiffs fail to allege the timing of the order was outside the 11 course of normal business. 12 Lastly, plaintiffs allege defendants violated generally accepted accounting 13 principles in connection with an SEC form filed February 16, 2023. (See id. ¶¶ 264, 308.) 14 In that regard, plaintiffs allege that, after Available Power did not place a purchase order 15 for the batteries Stem acquired for the FTM project, “Stem unloaded the batteries on two 16 customers,” namely, REX and Lullwater, who agreed to resell the batteries “to an end- 17 user customer” (see id. ¶¶ 264-66), and Stem agreed to “bear responsibility for the 18 shortfall” if REX or Lullwater “resold the hardware for ‘less than the amount initially sold to 19 the customer’” (see id. ¶¶ 265-66). Plaintiffs allege Stem reported the revenue from 20 those contracts in the above-referenced SEC form and did not disclose the “contingent 21 nature” thereof until “[a] year later” when it “announced material revenue reduction 22 adjustments” in connection therewith. (See id. ¶¶ 264, 268.) According to the FACC, 23 defendants violated Financial Accounting Standards Board Accounting Standard 24 Codification (“ASC”) No. 606, as defendants “should never have recognized revenue” 25 from those contracts “because at the time of the sale, collection of substantially all of the 26 sales price was not probable.” (See id. ¶ 269.) Although plaintiffs have not responded to 27 defendants’ arguments countering this theory (see Mot. at 27:1-28:4; Opp. at 16:15- 1 ASC No. 606 provides that a business entity may “account for [revenue from] a 2 contract” if “[i]t is probable that the entity will collect substantially all of the consideration 3 to which it will be entitled in exchange for the goods or services that will be transferred to 4 the customer.” See ASC 606-10-05-1, 606-10-25-1. Here, plaintiffs do not show why, at 5 the time defendants filed the above-referenced SEC form, it was not “probable” Stem 6 would “collect substantially all” of the revenue from the REX and Lullwater deals. See id. 7 Although Plaintiffs allege defendants knew “the batteries were subpar” (see FACC 8 ¶ 266), that allegation relies solely on a lawsuit brought against Stem by Lullwater,23 9 which commenced after defendants filed the above-referenced SEC form (see id. ¶¶ 266- 10 67), and plaintiffs fail to show that, at the time defendants filed said form, they had any 11 knowledge that the batteries sold to one of the buyers were other than of satisfactory 12 quality. Indeed, plaintiffs have not pleaded any allegations demonstrating the actual 13 quality of those batteries. See Veal v. LendingClub Corp., 423 F. Supp. 3d 785, 812 14 (N.D. Cal. 2019) (holding “[p]laintiffs may not rely on facts alleged in [a separate action] 15 without providing any independent corroboration” of such facts). 16 Accordingly, plaintiffs’ claim alleging scheme liability is subject to dismissal. 17 III. Section 14(a) Claim 18 Section 14(a) of the Exchange Act makes it unlawful for “any person” to “solicit or 19 to permit the use of his name to solicit any proxy or consent or authorization” in 20 “contravention of [the] rules and regulations” prescribed by the Securities and Exchange 21 Commission. See 15 U.S.C. § 78n(a)(1). Rule 14a-9, in turn, provides that “[n]o 22 solicitation . . . shall be made by means of any proxy statement” containing any “false or 23 misleading [statement] with respect to any material fact.” See 17 C.F.R. § 240.14a-9. To 24 state a claim under section 14(a) and Rule 14a-9, a plaintiff must allege: “(1) the 25 defendant made a material misrepresentation or omission in a proxy statement, (2) the 26
27 23 According to plaintiffs, Lullwater’s lawsuit was filed July 20, 2023, and alleged 1 misrepresentation or omission was made with the requisite level of culpability,24 and (3) 2 the misrepresentation or omission was an essential link in the accomplishment of a 3 transaction proposed in the proxy solicitation.” See Kelley v. Rambus, Inc., No. C 07- 4 1238 JF (HRL), 2008 WL 5170598, at *3 (N.D. Cal. Dec. 9, 2008), aff’d, 384 F. App’x 570 5 (9th Cir. 2010). Although section 14(a) does not necessarily require a plaintiff to plead 6 fraud with particularity, “Rule 9(b) applies where a claim is ‘grounded in fraud’ or 7 ‘sound[s] in fraud,’ even if fraud is not an essential element of the cause of action.” See 8 In re Finjan Holdings, Inc., 58 F.4th 1048, 1057 (9th Cir. 2023) (alteration in original). 9 Here, by its August 30 Order, the Court dismissed plaintiffs’ section 14(a) claim, 10 for failure to comply with Rule 9(b). (See August 30 Order at 25:8-19.) Although plaintiffs 11 argue the FACC “cures the earlier pleading defect” by “detailing negligent conduct 12 separately” (see Opp. at 24:9-10), they continue to make only a “formalistic 13 differentiation” between their section 14(a) and section 10(b) claims (see August 30 14 Order at 25:13), in that their section 14(a) claim relies on the statements set forth above 15 that form the basis of their section 10(b) claim (compare FACC ¶¶ 156-182 (section 14(a) 16 statements) with ¶¶ 187-250 (section 10(b) statements)). In particular, the Ninth Circuit, 17 in the context of claims under section 11 of the Exchange Act, has held that, even where 18 a negligence claim “does not adopt all of the allegations contained in the rest of the 19 complaint,” if such claim “does not allege different misrepresentations” but “merely relies 20 on the same alleged misrepresentations . . . that are central to [plaintiffs’] section 10(b) 21 fraud claim,” Rule 9(b) is applicable, see In re Rigel, 697 F.3d at 886, and district courts 22 have applied that holding to claims under section 14(a), see, e.g., Mehedi v. View, No. 23 21-cv-06374-BLF, 2023 WL 3592098, at *14 (N.D. Cal. May 22, 2023) (holding “[t]he 24 same reasoning [in Rigel] applies to a Section 14 claim”). Consequently, given the 25 Court’s finding above that plaintiffs have not pleaded a false or misleading statement 26
27 24 The requisite level of culpability for a section 14(a) claim is negligence. See 1 under Rule 9(b), plaintiffs cannot sustain their claim under section 14(a).7° 2 Accordingly, plaintiffs’ section 14(a) claim is subject to dismissal. 3 || IV. Section 20(a) and Section 20A Claims 4 Plaintiffs’ remaining claims are brought pursuant to section 20(a) and section 20A 5 || of the Exchange Act. (See FACC [If] 443-47, 455-74.) To state a claim under either 6 || section, a plaintiff must first plead an independent violation of the Exchange Act. See 7 || Zucco Partners, 552 F.3d at 990 (holding “Section 20(a) claims may be dismissed 8 || summarily, however, if a plaintiff fails to adequately plead a primary violation of section 9 || 10(b)”); In re VeriFone Sec. Litig., 11 F.3d 865, 872 (9th Cir. 1993) (holding, where 10 || plaintiffs “failed to allege an actionable independent underlying violation” of the Exchange 11 Act, “the § 20A claim was properly dismissed”). Here, as plaintiffs have failed to allege 12 || anindependent violation of the Exchange Act, their section 20(a) and section 20A claims
£ 13 || are subject to dismissal.
CONCLUSION O 8 15 For the reasons stated above, defendants’ motion to dismiss is hereby GRANTED,
Q 16 and the FACC is hereby DISMISSED without further leave to amend. See Zucco
G 17 Partners, 552 F.3d at 1007 (affirming dismissal without leave to amend where district
18 || court advised plaintiff of pleading deficiencies and plaintiff failed to correct such 19 || deficiencies in amended pleading). 20 IT IS SO ORDERED. 21 22 Dated: December 17, 2025 ‘ : INE M. CHESNEY 23 United States District Judge 24 25 26 25 In light thereof, the Court does not address herein defendants’ additional arguments that plaintiffs have not sufficiently alleged (1) an “essential link” between “the 97 || Proxy and any harm” suffered by plaintiffs and (2) the 14(a) Defendants “solicited or permitted the use of their namef[s] to solicit votes.” (See Mot. at 29:22-30:11) (internal 23 quotation, citation, and alterations omitted).