Stopping a Departing Salesperson From Taking the Client List

The situation

Manuel built his Sudbury software company over eleven years, growing it from a two-person contract shop into an incorporated firm with about 60 staff and roughly $14 million in annual revenue, delivering custom systems for mining, healthcare and logistics clients across northern Ontario. He had trained as a software developer and still reviewed architecture decisions personally. Ines, a university professor on partial leave from her teaching appointment, held equity in the company and sat on its two-person board, focused on governance and long-term strategy while Manuel ran day-to-day operations.

Their strongest revenue driver was not code. It was a single senior salesperson, Parisa, who had spent six years building relationships with the company's twenty largest accounts. Parisa carried nearly all of the institutional knowledge about who made purchasing decisions at each client, what those clients paid, when their contracts renewed and what problems kept them up at night. That knowledge lived partly in her head and partly in a shared client relationship spreadsheet the company maintained internally, which Manuel and Ines treated as one of the business's most valuable assets, alongside the software itself.

The legal problem

Parisa resigned on a Friday afternoon, citing a new opportunity. She gave the standard two weeks' notice and was, on paper, cooperative. What Manuel did not know until the following Monday was that she had already accepted a sales role at a smaller competing firm, and that in her final days she had exported the full client relationship spreadsheet to a personal email account.

By the second week of her notice period, three of the company's largest clients had received calls from Parisa introducing her new employer and suggesting they consider switching providers when their current contracts came up for renewal. One client forwarded the email to Manuel directly, confused about why a salesperson still technically employed by his company was pitching a competitor. That email was the first concrete evidence of what was happening, and it arrived four days before Parisa's employment was due to end.

Manuel called our team the same afternoon. The core legal question was what the company could actually stop. Ontario's Employment Standards Act, 2000 generally prohibits non-compete clauses for most employees, and Parisa did not hold an executive title that would fall within the narrow exceptions to that rule, so an outright ban on her working for a competitor was not realistic. But her employment contract, which our team reviewed within hours, contained two separate provisions that did not depend on any non-compete: a confidentiality clause covering client information, and a non-solicitation clause preventing her from soliciting the company's clients or prospective clients for twelve months after leaving. Non-solicitation covenants of that kind remain enforceable in Ontario, provided they are reasonable in scope and duration, because they restrict specific conduct rather than the ability to work at all. Separately, taking the spreadsheet itself raised a breach of confidence claim independent of the contract, since Ontario common law protects confidential business information regardless of what any agreement says.

What we did

1. Preserved the evidence before making contact. Before anyone approached Parisa, we had Manuel secure the forwarded client email, the company's IT logs showing the spreadsheet export, and a timeline of which clients had been contacted and when. A demand made without solid evidence behind it invites denial; a demand backed by a specific export log and a forwarded email is much harder to dismiss.
2. Sent a cease-and-desist letter the same week. The letter went to Parisa directly, with a copy to her new employer's owner, setting out the confidentiality and non-solicitation clauses, the evidence of the export, and a demand that she stop contacting the company's clients, return or destroy the spreadsheet, and confirm in writing that she had done so. Speed mattered here: the longer solicitation continues unchallenged, the more clients get contacted and the harder it becomes to establish that any resulting business loss flowed from the breach rather than ordinary competition.
3. Prepared, but did not yet file, an application for an injunction. An injunction is a court order requiring someone to stop specific conduct immediately, available before a full trial when a party can show real and urgent harm. We drafted the supporting materials in parallel with the letter so that if Parisa or her new employer ignored the demand, the company could move to the Superior Court within days rather than starting from a blank page under time pressure.
4. Contacted the affected clients directly. With Manuel's approval, we advised the company to reach out proactively to the three clients Parisa had already contacted, not to disparage her, but to reaffirm the company's ongoing commitment to their accounts and confirm nothing about their service was changing. Clients who feel abandoned during a dispute are the ones most likely to actually switch providers; clients who hear promptly from ownership usually stay put.
5. Negotiated a signed undertaking rather than pushing straight to court. Parisa's new employer, once it understood the exposure it faced by knowingly benefiting from a departing employee's breach of confidence, had no interest in a lawsuit either. Within ten days, Parisa signed a formal undertaking confirming she had deleted all copies of the spreadsheet, agreeing to make no further contact with the twenty listed accounts for the remainder of the twelve-month period, and acknowledging that any breach would entitle the company to seek the injunction already drafted and waiting.

The outcome

All three contacted clients stayed with the company; none moved their business during the dispute or in the months afterward. Parisa's new employer kept her in a role covering different accounts and did not solicit the restricted client list again during the undertaking period. Manuel estimated the twenty accounts covered by the non-solicitation clause represented roughly $3.8 million of the company's annual revenue, and the case resolved without any of it moving.

The company avoided a courtroom fight entirely. A signed undertaking, backed by a fully prepared injunction application the other side knew was ready to file, produced the same practical result as a court order at a fraction of the cost and delay, closing the matter within three weeks of the first warning email reaching Manuel's inbox. Manuel had braced himself for a drawn-out fight measured in months, and was relieved to learn that a well-documented breach, addressed immediately, rarely needs to reach that stage at all.

Afterward, Ines pushed the board to formalize what had been informal practice. The company adopted a written policy requiring departing employees to complete an exit checklist confirming return of company property and data before their final paycheque issued, and began restricting export access to the client relationship spreadsheet to a smaller group of senior staff, with activity logging turned on for anyone who could download it in full. Manuel also asked our team to review the standard employment agreement used for every new sales hire going forward, to confirm the confidentiality and non-solicitation language would hold up the same way again if it was ever tested.

The review turned up one gap worth fixing: the twelve-month non-solicitation period applied only to clients a salesperson had personally serviced, not to prospective clients still in the sales pipeline when they left. Parisa's departure had not exposed that gap, since every account she contacted was one she had personally managed, but the next departure might involve someone further along in courting a client who had not yet signed. The company updated its template to close that gap before it mattered.

What you can learn from this