Ascente Business Consulting, LLC v. DR myCommerce

CourtDistrict Court, D. Minnesota
DecidedApril 8, 2019
Docket0:18-cv-00138
StatusUnknown

This text of Ascente Business Consulting, LLC v. DR myCommerce (Ascente Business Consulting, LLC v. DR myCommerce) is published on Counsel Stack Legal Research, covering District Court, D. Minnesota primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Ascente Business Consulting, LLC v. DR myCommerce, (mnd 2019).

Opinion

UNITED STATES DISTRICT COURT DISTRICT OF MINNESOTA

ASCENTE BUSINESS CONSULTING, LLC Case No. 0:18-cv-00138-JNE-KMM d/b/a LIBERTYID,

Plaintiff,

v. ORDER

DR MYCOMMERCE d/b/a ESELLERATE; and DIGITAL RIVER, INC.;

Defendants.

This matter is before the Court on Ascente Business Consulting LLC’s (“Ascente”) motion for leave to amend the complaint. (ECF No. 54.) Ascente seeks permission to add claims for fraud, fraudulent inducement, and reckless misrepresentation against the defendants, DR MyCommerce (“DRM”) and Digital River, Inc. (“Digital River”), which is DRM’s parent company. In an Order dated July 26, 2018, the District Court granted the defendants’ motion to dismiss a fraud claim that Ascente included in its original Complaint. (7/26/2018 Order, ECF No. 36.) Now that the parties have engaged in discovery, Ascente argues that it can adequately plead fraud and fraudulent-inducement claims as well as a reckless-misrepresentation claim. DRM and Digital River argue that Ascente’s motion to amend should be denied because the proposed claims are futile— , they would not survive a motion to dismiss for failure to state a claim. For the reasons that follow, the motion to amend is granted in part and denied in part. I. Background1 Ascente provides identity-theft protection products to consumers. DRM is a software development company and a wholly owned subsidiary of Digital River. Ascente approached DRM in January 2014 to develop a web portal so that individual consumers

1 This recitation of the facts is drawn from Ascente’s Proposed Amended Complaint. ( ECF No. 57-2; ECF No. 60-2 (Defs.’ Redline).) could go online and purchase an identity-monitoring subscription service from Ascente. The parties negotiated and, in May 2014, agreed to a “Statement of Work,” by which Ascente would pay DRM $44,822 to develop the web portal. The parties also entered a “Publisher Agreement,” which provided that DRM would receive 10 percent of the revenue that was generated by the web portal. The development of the web portal was to be completed in approximately five months, by October 2014. In October, DRM told Ascente that it exceeded projected costs in developing and building the portal. On October 28, 2014, Jennifer Manwarren and Thomas Peterson, both of DRM, exchanged an email indicating that the web portal was “on schedule” to be launched before the end of the month. (Proposed Am. Compl. ¶ 27.) On October 28th and 29th, Chad Johnson and Cory Husfeldt of DRM told Ascente employee Bret Busse that the portal was ready for launch and “ready for commerce” as required by the parties’ agreement. ( ¶ 28.) Around the same time, DRM delivered the web portal to Ascente. Unfortunately, when it went live on October 29, 2014, the web portal did not function as intended. (Proposed Am. Compl. ¶ 34.) Several months later, on January 20, 2015, DRM employee Christine Roe emailed her coworker, Jim Swenson, and stated that certain work on the portal had not been completed. ( ¶¶ 29–31.) Ms. Roe also stated that the software that was delivered was not the end product, and she believed that Ascente was “getting a little screwed.” ( ) Ascente informed DRM of the problems it was having with the web portal and representatives of both sides met in Denver on January 28, 2015 to negotiate a new agreement. (Proposed Am. Compl. ¶¶ 35, 38.) According to Ascente, prior to the meeting in Denver, DRM employees Matthew Kleinsasser and Stefan Weber exchanged internal messages regarding the need to bring the web portal software up to compliance with security standards to protect credit card information. Recognizing that this would take a considerable amount of work, Mr. Weber stated: “I wish we could get rid of Ascente[.]” ( ¶ 65.) Ascente claims that the Defendants then “hatched a plan to dump the web portal,” claiming that they would complete the web portal if they received additional money from Ascente, but really “had no intention to do so.” ( ¶ 66.) On January 28, 2015, Mr. Weber emailed Swenson, Kleinsasser, and other DRM personnel indicating that DRM employee Rodney Salazar would “try to get out of the contract with Ascente today.” ( ¶ 67.) However, at the January 28, 2015 Denver meeting, Ascente and DRM did not break off their business relationship. Chad Johnson (DRM) told Ascente representatives that DRM had outstanding development costs of $187,336.25, which they had incurred in working on the project. (Proposed Am. Compl. ¶¶ 39–40.) Mr. Johnson offered that the defendants would complete the work necessary to get the web portal up and running in exchange for Ascente’s agreement to pay the outstanding development costs. ( ¶ 40.) Based on the internal DRM communications before the Denver meeting and several others that occurred afterward, Ascente asserts that DRM never intended to do any additional work on the portal. ( ¶¶ 68–71, 74–85.) For example, in early February 2015, several DRM employees internally discussed getting rid of or “divesting” from Ascente as well as placing a hold on development work. ( ¶¶ 68–71.) Moreover, Ascente alleges that the $187,3362 the Defendants said they incurred as DRM’s outstanding development costs was not the actual amount. Ascente alleges: On February 17, 2015, [Chad] Johnson [of DRM] reviewed a draft [bill] and pointed out that Ascente’s “most recent contract/SOW call[s] for $73 hour versus the $75 that’s called out in the invoice.” [Jennifer] Manwarren [of DRM] responded, “Are you serious?” Johnson wrote “Yep. We can try to submit to them as is but they will likely question it.” Manwarren: “No. They agreed to a dollar amount-, so you saw the wild math I had to do to get there.” ... Instead, Johnson suggested, “What if I deleted the rate and just left the total?” (Proposed Am. Compl. ¶ 72.) The defendants did not tell Ascente that the $187,336 “was not an accurate figure, nor did they ever tell Ascente the true amount of their alleged cost overruns.” ( ¶ 73.) Ascente eventually paid $187,336 to DRM, with the last installment payment occurring on May 4, 2016. ( ¶¶ 41, 44.) Out of the agreement reached at the Denver meeting, the parties reached a new contractual arrangement. In July 2015, the parties executed a Software Development

2 At times in the record, the alleged cost overruns are identified as $187,336 or $187,335. This $1 difference appears to be immaterial. The court will use the $187,336 figure in this Order. Agreement (“SDA”), which formalized Ascente’s agreement to pay an additional $187,336 in exchange for the defendants delivering a web portal that met certain specifications laid out in an Appendix A that was attached to the agreement. (Proposed Am. Compl. ¶ 52.) According to Ascente, it never received a web portal that worked as intended, and the defendants’ communications that followed the SDA’s execution allegedly show that the defendants did not intend to provide a functioning portal after DRM was paid the $187,336. ( ¶¶ 80–87.) For example, in an August 27, 2015 email, Christine Roe suggested to a colleague that “Ascente access can probably be dropped.... We’re not planning any additional coding changes....” ( ¶ 80.) Other internal messages among the defendants’ personnel from April, June, and October of 2016 allegedly confirm that DRM never intended to do additional work on the project, but instead falsely claimed to have delivered a working portal. ( ¶¶ 81–82, 84–85.) Ascente claims it has not been able to launch its business-to-consumer marketing campaign as a result of the defendants’ failure to provide a functioning web portal, costing it millions of dollars in revenue. ( ¶ 88.) II. Futility Standard Federal courts should freely give leave to a party moving to amend its pleadings “when justice so requires.” Fed. R. Civ. P. 15(a)(2).

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

Related

Blankenship v. USA Truck, Inc.
601 F.3d 852 (Eighth Circuit, 2010)
Ashcroft v. Iqbal
556 U.S. 662 (Supreme Court, 2009)
Porous Media Corporation v. Pall Corporation
186 F.3d 1077 (Eighth Circuit, 1999)
Vandeputte v. Soderholm
216 N.W.2d 144 (Supreme Court of Minnesota, 1974)
Specialized Tours, Inc. v. Hagen
392 N.W.2d 520 (Supreme Court of Minnesota, 1986)
Florenzano v. Olson
387 N.W.2d 168 (Supreme Court of Minnesota, 1986)
Martens v. Minnesota Mining & Manufacturing Co.
616 N.W.2d 732 (Supreme Court of Minnesota, 2000)
Cohen v. Appert
463 N.W.2d 787 (Court of Appeals of Minnesota, 1990)
Lunsford v. RBC DAIN RAUSCHER, INC.
590 F. Supp. 2d 1153 (D. Minnesota, 2008)
Christensen v. Metropolitan Life Insurance
542 F. Supp. 2d 935 (D. Minnesota, 2008)
Flora v. Firepond, Inc.
260 F. Supp. 2d 780 (D. Minnesota, 2003)
U.S. Bank N. A. v. Cold Spring Granite Co.
802 N.W.2d 363 (Supreme Court of Minnesota, 2011)
Triple Five of Minnesota, Inc. v. Simon
213 F.R.D. 324 (D. Minnesota, 2002)

Cite This Page — Counsel Stack

Bluebook (online)
Ascente Business Consulting, LLC v. DR myCommerce, Counsel Stack Legal Research, https://law.counselstack.com/opinion/ascente-business-consulting-llc-v-dr-mycommerce-mnd-2019.