Acclaim Systems Inc v. Infosys Limited

679 F. App'x 207
CourtCourt of Appeals for the Third Circuit
DecidedFebruary 9, 2017
Docket16-1770
StatusUnpublished
Cited by3 cases

This text of 679 F. App'x 207 (Acclaim Systems Inc v. Infosys Limited) is published on Counsel Stack Legal Research, covering Court of Appeals for the Third Circuit primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Acclaim Systems Inc v. Infosys Limited, 679 F. App'x 207 (3d Cir. 2017).

Opinion

OPINION *

GREENAWAY, JR., Circuit Judge.

Acclaim Systems, Inc. (“Acclaim”) appeals a grant of summary judgment in favor of Infosys Ltd, (“Infosys”) in this business dispute. Acclaim asserts that In-fosys intentionally interfered with non-compete contracts governing four IT consultants when it contracted to work with them. Because the record does not show that Infosys actually knew of the non-compete clauses, we will affirm.

I. FACTUAL BACKGROUND

Acclaim and Infosys are providers of IT services. Both consult with Time Warner Cable (“TWC”). This dispute concerns the two companies’ work with TWC on a particular project related to the Sales Force Dot Com (“SFDC”) client relationship platform. In the spring of 2013, Acclaim (and another company, Acumen, which is not a party to this litigation) was working with TWC on the SFDC project. But TWC *209 reached out to Infosys, asking it to present on its own SFDC capabilities. 2 Looking for cost savings—made larger by Infosys’s new pricing strategy, which offered volume discounts to TWC—TWC decided to transfer the SFDC project from Acclaim and Acumen to Infosys.

TWC began the transition process from Acclaim to Infosys in the summer of 2013. Infosys originally proposed using two on-site consultants located in Charlotte, North Carolina, with the rest of its team based in India. TWC again approached Infosys and asked it to consider retaining four SFDC team members: Acclaim employee Timothy Blackwell and three subcontractors, Santhosh Nellutla, Pavan Jas-thi, and Leslie Mendonca. Each of the four had non-compete agreements in place restricting their ability to work on this project for Infosys. Infosys knew that these four had previously worked for Acclaim, but did not know at the time that they were subject to non-competes.

Blackwell was hired directly by Infosys. In an initial email to Infosys, Blackwell stated directly “I do not have a non-compete clause with Acclaim.” App. 189a. He also filled out an online employment application which asked whether he was subject to any contractual restrictions, including non-compete covenants, that might prevent him from working for Infosys in this role; he answered, “No.” Id. 3 He began his employment in early September, 2013.

Nellutla, Jasthi, and Mendonca remained subcontractors, in part for immigration reasons, and remained with their direct employers, Global InfoTech, Inc. and Syslntelli, Inc. Their hiring process, therefore, took a different path. First, an Infosys hiring mapager, Sushobhan Su-prabhat, spoke with the subcontractors, telling them, among other things, to verify that they were not subject to any non-compete agreements, and to report this to Raj Srinivasan, the Infosys project manager for the TWC SFDC work. Each of the three told Srinivasan that they were not subject to any non-compete. Srinivasan also asked Global and Syslntelli whether the subcontractors were contractually bound not to work for Infosys, and those employers likewise failed to inform Infosys of the non-competes.

With this information in hand, Infosys began to bring the subcontractors on board. It did so by routing the subcontracts through an approved Infosys vendor, Vedalnfo, Inc., with which it had an ongoing relationship and contract. It is disputed whether Vedalnfo conducted its own determination of whether the subcontractors were subject to non-competes. *210 The subcontractors began working through Infosys as of October 1, 2013.

Meanwhile, TWO cancelled its contract with Acclaim, having now transferred the SFDC project to Infosys. The Acclaim contract could be cancelled at-will and TWO did not breach the contract.

On October 24, 2013, Acclaim filed suit in state court against Blackwell, Global and Syslntelli. Only after the state court litigation commenced did Infosys first learn of the non-compete agreements at issue.

II.PROCEDURAL HISTORY

In the course of motion practice, this suit has been substantially narrowed. On a 12(b)(6) motion, the District Court dismissed plaintiffs claims of aiding and abetting a contractual breach. That decision is not challenged on appeal. Next, all claims against Vedalnfo were dismissed by stipulation. Acclaim also withdrew its claims of civil conspiracy. Finally, the District Court granted summary judgment for Infosys on the remaining claim of tortious interference with contractual relations, finding for Infosys on three separate grounds. This appeal, which is limited to the tortious interference claim, followed.

III.STANDARD OF REVIEW 4

The Court of Appeals’ review of a grant of summary judgment is “plenary” and the court should “apply the same test the district court should have utilized initially.” Giles v. Kearney, 571 F.3d 318, 322 (3d Cir. 2009). Summary judgment should be granted only when “there is no genuine dispute as to any material fact and the movant is entitled to judgment as a matter of law.” Fed. R. Civ. P. 56(a). “ ‘[A]U justifiable inferences are to be drawn in [the nonmovant’s] favor,’ ” but the “mere existence of some evidence in support of the nonmovant is insufficient to deny a motion for summary judgment; enough evidence must exist to enable a jury to reasonably find for the nonmovant on the issue.” Giles, 571 F.3d at 322 (quoting Anderson v. Liberty Lobby, Inc., 477 U.S. 242, 255, 106 S.Ct. 2505, 91 L.Ed.2d 202 (1986)).

IV.ANALYSIS

Appellant’s only remaining claim is for tortious interference with contractual relations. Under Pennsylvania law, 5 this cause of action has four elements: “(1) the existence of a contractual relationship between the plaintiff and a third party; (2) purposeful action by the defendant, specifically intended to harm the contractual relationship; (3) the absence of privilege or justification on the part of the defendant; and (4) damages to the plaintiff as a result of the defendant’s conduct.” Burton v. Teleflex Inc., 707 F.3d 417, 433 (3d Cir. 2013) (citation omitted). Pennsylvania follows the Restatement (Second) of Torts in its analysis of tortious interference claims. Acumed LLC v. Advanced Surgical Servs., Inc., 561 F.3d 199, 215 (3d Cir. 2009). The District Court granted summary judgment in this case on three independent grounds, finding that Appellant could not show a genuine dispute of material fact as to the second, third, or fourth elements of a tortious interference claim. Our analysis begins, and *211

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

Related

Cite This Page — Counsel Stack

Bluebook (online)
679 F. App'x 207, Counsel Stack Legal Research, https://law.counselstack.com/opinion/acclaim-systems-inc-v-infosys-limited-ca3-2017.