Signal Hound Inc v. Expandable Software Inc

CourtDistrict Court, W.D. Washington
DecidedMarch 25, 2022
Docket3:21-cv-05448
StatusUnknown

This text of Signal Hound Inc v. Expandable Software Inc (Signal Hound Inc v. Expandable Software Inc) is published on Counsel Stack Legal Research, covering District Court, W.D. Washington primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Signal Hound Inc v. Expandable Software Inc, (W.D. Wash. 2022).

Opinion

1 2 3

5 UNITED STATES DISTRICT COURT 6 WESTERN DISTRICT OF WASHINGTON AT TACOMA 7 SIGNAL HOUND, INC., CASE NO. C21-5448 BHS 8 Plaintiff, ORDER 9 v. 10 EXPANDABLE SOFTWARE, INC., 11 Defendant. 12

13 This matter comes before the Court on Defendant Expandable Software, Inc.’s 14 Motion to Dismiss, Dkt. 17. The Court has considered the briefing filed in support of and 15 in opposition to the motion and the remainder of the file and grants in part and denies in 16 part the motion for the reasons stated below. 17 I. BACKGROUND 18 Plaintiff Signal Hound, Inc. is a global corporation in Battle Ground, Washington 19 that designs and builds spectrum analyzers and signal generators for engineers and radio 20 frequency professionals. Dkt. 14, ¶ 5. In 2019, Signal Hound was looking to upgrade its 21 Enterprise Resource Planning (“ERP”) software, which it uses to do things such as 22 calculate pricing discounts. Id. ¶¶ 6–7. Signal Hound sent a Request for Information 1 (“RFI”), Dkt. 14-1, to software companies to determine their respective capabilities and 2 to create a short list of vendors who would be asked to provide full proposals. Dkt. 14, 3 ¶ 7. Expandable responded to the RFI and was ultimately selected to provide a full

4 proposal. Id. ¶¶ 8–13; see also Dkt. 14-1. 5 Signal Hound’s RFI informed vendors that it sought an integrated system that 6 could accomplish the same tasks of the multiple software programs it was then using. 7 Dkt. 14-1 at 4. It wanted to increase efficiency and accuracy by limiting manual 8 manipulation and data entry. Id. The first part of the RFI prompted respondents to

9 indicate whether they could support certain programs. Id. at 6. Respondents could also 10 write comments about the requirements and were prompted to respond to other open- 11 ended questions in the second part of the RFI. See id. at 7–18. 12 Expandable responded that most of Signal Hound’s requirements were supported 13 “out of the box.” See id. at 7–13. Among the things Expandable said were supported out

14 of the box was the requirement labeled “Price Lists Defined with Multiple Criteria; 15 Matrix Based Pricing for Volume Buying; Contract Specific Pricing Capabilities; 16 Promotional Codes for Marketing Purposes.” Id. at 11. Expandable also stated that 17 “[s]oftware customization is rarely needed because Expandable ERP software is 18 extensively configurable” and that “workflow can be tailored to match the unique

19 business processes of [the] organization.” Id. at 14. It also represented that its customers 20 receive “a full-blown, proven ERP system that is easy to use, well-supported and will 21 meet their needs far into the future.” Id. at 15. 22 1 The companies met at Signal Hound’s office in Battle Ground to discuss Signal 2 Hound’s requirements and Expandable’s capabilities. Dkt. 14, ¶¶ 13–14. During those 3 meetings, Expandable indicated that it “could not currently handle Signal Hound’s

4 current pricing model, because it was based on the quantity of items purchased rather 5 than the dollar volume of the purchase.” Id. ¶ 14. Signal Hound’s CEO responded that he 6 would work on developing a dollar-volume pricing model, which Expandable assured 7 him they could work with. Id. Expandable’s executives assured Signal Hound that if 8 Expandable “could not make its software work to Signal Hound’s satisfaction,” it would

9 fully refund the purchase price as it had done for another customer. Id. ¶ 16. 10 Expandable then sent Signal Hound a quote totaling $158,709 which included the 11 “Expandable ERP Software Base Module” for $95,500, third-party products for $7,590, 12 the “Expandable Implementation, Training & Professional Services” for $50,170 based 13 on an estimated 286 hours of professional services, annual maintenance for $20,499, and

14 a $15,050 discount. Id. ¶ 18; see also Dkt. 14-2 at 2–3. Signal Hound accepted that offer 15 and signed the Software Licensing Agreement (“SLA”) and the Software Maintenance 16 Agreement (“SMA”) on November 26, 2019. See Dkt. 14-2 at 4–10. The SLA contained 17 a warranty waiver stating “[t]his warranty is in lieu of all other warranties expressed or 18 implied, including, but not limited to, the implied warranties of merchantability and

19 fitness for a particular purpose.” Dkt. 14-2 at 4. Both the SLA and SMA included choice 20 of law provisions stating: “This agreement will be governed by the laws of the State of 21 California” and a provision stating: “This agreement . . . is the complete and exclusive 22 statement of the agreement between the parties, and supersedes all proposals or prior 1 agreements, oral or written, and all other communications between the parties relating to 2 the subject matter of the agreement.” Id. at 5, 9. (emphasis omitted). Signal Hound paid 3 all amounts due under the contracts. Dkt. 14, ¶ 21.

4 Expandable and Signal Hound tried for months to implement the software. Id. 5 ¶ 22. Ultimately, Expandable was unable to provide automated pricing based on Signal 6 Hound’s new pricing model. Id. Expandable offered to customize the software to handle 7 the pricing model, apprising Signal Hound that the customization would cost over 8 $200,000 and take more than a year to implement. Id. ¶ 23. Signal Hound rejected that

9 offer and Expandable’s alternative solution to continue to run the software Signal Hound 10 had previously used, Microsoft Access, alongside Expandable’s software. Id. ¶¶ 23–24. 11 Signal Hound requested a refund which Expandable rejected. Id. ¶ 24. Signal Hound 12 never finished implementing Expandable’s software. Id. 13 Signal Hound sued Expandable for intentional misrepresentation, negligent

14 misrepresentation, breach of implied warranty of fitness for particular purpose, breach of 15 implied covenant of good faith and fair dealing, and failure of consideration. Dkt. 14. 16 Expandable moves to dismiss for failure to state a claim, arguing that Signal Hound did 17 not plead its misrepresentation claims with the particularity required for fraud claims, 18 Signal Hound is attempting to add new contract terms, and the contract waived implied

19 warranties. Dkt. 17. Signal Hound argues that it effectively pled its misrepresentation 20 claims with particularity, the warranty waiver in the contract was not conspicuous, and 21 Expandable’s failure to provide usable software prevented the purpose of the contract 22 from being realized and made the contract fail in a material respect. Dkt. 20. 1 II. DISCUSSION 2 A. Legal Standard 3 Dismissal under Federal Rule of Civil Procedure 12(b)(6) may be based on either

4 the lack of a cognizable legal theory or the absence of sufficient facts alleged under a 5 cognizable legal theory. Balistreri v. Pacifica Police Dep’t, 901 F.2d 696, 699 (9th Cir. 6 1988). A plaintiff’s complaint must allege facts to state a claim for relief that is plausible 7 on its face. See Ashcroft v. Iqbal, 556 U.S. 662, 678 (2009). A claim has “facial 8 plausibility” when the party seeking relief “pleads factual content that allows the court to

9 draw the reasonable inference that the defendant is liable for the misconduct alleged.” Id. 10 Although the Court must accept as true the complaint’s well-pled facts, conclusory 11 allegations of law and unwarranted inferences will not defeat an otherwise proper Rule 12 12(b)(6) motion to dismiss. Vazquez v. Los Angeles Cnty., 487 F.3d 1246, 1249 (9th Cir. 13 2007); Sprewell v. Golden State Warriors, 266 F.3d 979, 988 (9th Cir. 2001). “[A]

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)
Wyler v. Feuer
85 Cal. App. 3d 392 (California Court of Appeal, 1978)
Pasadena Live, LLC v. City of Pasadena
8 Cal. Rptr. 3d 233 (California Court of Appeal, 2004)
Erwin v. Cotter Health Centers, Inc.
161 Wash. 2d 676 (Washington Supreme Court, 2007)
McKee v. AT&T Corp.
164 Wash. 2d 372 (Washington Supreme Court, 2008)
Sprewell v. Golden State Warriors
266 F.3d 979 (Ninth Circuit, 2001)

Cite This Page — Counsel Stack

Bluebook (online)
Signal Hound Inc v. Expandable Software Inc, Counsel Stack Legal Research, https://law.counselstack.com/opinion/signal-hound-inc-v-expandable-software-inc-wawd-2022.