A Consultant Took the Program Model to a Rival

The situation

What worried Zhen was not the principle of the thing. It was the annual report. Her organization, a small community group serving families in Wasaga Beach, had spent three years and a provincial grant building a structured mentorship curriculum with measurable outcomes, the kind of program that funders wanted to see renewed year after year because it actually worked. If a nearly identical program appeared somewhere else under someone else's name, the first question from the funding body would not be sympathetic. It would be about which organization actually owned the results being reported.

The board chair, Liang, an electrician who volunteered his evenings to the organization's governance, was the one who spotted it. A regional funders' newsletter profiled a new program at a competing agency two towns over, describing session structures, intake forms and a scoring rubric that were, paragraph for paragraph, close enough to the non-profit's own materials that Liang printed both documents and laid them side by side on his kitchen table.

The consultant who had built the original curriculum, Lesia, had been engaged on a modest contract two years earlier, paid in the low five figures, to design the intake process and training materials from scratch using the organization's client data and outcome history. Her engagement letter said the work product belonged to the organization. It said nothing, clearly, about what she could reuse from memory once the contract ended.

Zhen had reported the resemblance to the board within a week of Liang's discovery. The organization's revenue from that single grant program ran in the low hundred thousands annually, and a renewal cycle was approaching within months. The dispute, once it was framed in dollar terms for the purpose of a possible claim, sat somewhere between one and three years of that funding, depending on how directly the competing program could be shown to have displaced the non-profit's renewal prospects. Nobody on the board wanted a public fight. What they wanted was to know, quickly, whether the funder would see this as the non-profit's failure to protect its own work.

Zhen had been through funding reviews before, and she knew how quickly a funder's confidence could shift when something looked irregular, even when nothing improper had actually happened on the organization's end. A phone call asking her to explain a resemblance she had not chosen and could not fully control was the scenario that kept her up at night, more than any court process ever could. She wanted a plan for that phone call before it happened, not after.

What was actually at stake

The legal question underneath the board's worry was about confidential information and the limits of what a consultant is entitled to carry with her when a contract ends. Ontario law does not require every useful idea to be treated as a trade secret. A general skill or approach a consultant develops through her own experience is hers to use again elsewhere. What is not hers to reuse is a specific method built for and paid for by a client, using that client's data, kept internal and marked or treated as confidential, and now being deployed for a competitor's benefit.

The organization's engagement letter with Lesia helped, but only partly. It assigned ownership of the deliverables, meaning the actual documents, forms and training slides. It did not contain a clean non-use or non-disclosure clause covering the underlying method itself, and it said nothing about what happened if she went on to consult for a similar organization afterward. That gap mattered, because the competing program was not a photocopy of the non-profit's documents. It was a close reconstruction, evidently drawn from memory and notes, which is a harder thing to prove was taken improperly than a leaked file would have been.

What was genuinely at stake was narrower than the board first feared, and also more immediate. It was not a clean claim for stolen intellectual property with an obvious dollar value attached. It was reputational and financial exposure tied to one funding cycle, plus whatever legal cost would be spent chasing a claim that was, on the underlying facts, less than airtight. A demand letter sent too aggressively, without a realistic read on how strong the underlying claim actually was, risked provoking a public dispute that would do more damage to the funding relationship than the original resemblance ever would have.

There was also a quieter risk. If the funder learned of the dispute from someone other than the organization itself, the story would arrive already shaped by whoever told it first. Getting ahead of that, on the organization's own terms, mattered as much as any letter sent to Lesia or the rival agency.

There was a further complication in valuing what had actually happened. The rival program had only been running for a few months, so there was no full year of displaced funding to point to yet, only a projection. Overstating the loss in a demand letter, when the real figure was still speculative, would have undercut the organization's credibility in any negotiation that followed, and made a modest, achievable resolution harder to reach than it needed to be.

What we did

1. Took over a file already in motion. Zhen's organization had approached another lawyer first, who had drafted an aggressive cease-and-desist letter but not sent it before a scheduling conflict forced a handoff mid-file. We reviewed what had already been drafted, along with the correspondence already exchanged with Lesia, before deciding whether to send it, revise it or start over, since a half-sent aggressive letter can do more harm than either sending it properly or not sending it at all.
2. Assessed the strength of the underlying claim honestly. We compared the engagement letter's actual wording against what had happened, and concluded the claim for misuse of confidential information was real but not overwhelming, given the absence of an explicit non-use clause covering methods reused from memory rather than documents taken outright. Telling the board this plainly, rather than promising a stronger case than actually existed, shaped every decision that followed, including how firmly any demand letter could credibly be worded.
3. Rewrote the demand letter to fit the real leverage available. Instead of threatening litigation the organization was unlikely to pursue given its budget and the mixed strength of the underlying claim, the revised letter focused on the concrete, provable overlap between the two programs and asked for specific, achievable relief: an acknowledgment of the program's origin and a commitment not to further replicate the organization's proprietary materials. A letter the organization could not credibly back up would have cost more than it gained.
4. Opened a direct conversation with the rival agency's leadership. Because the competing organization had its own funding relationships to protect, its board had an interest in resolving this quietly too, without a public dispute drawing attention to either side. We proposed a short call between the two organizations' leadership rather than lawyer-to-lawyer correspondence alone, which moved the conversation faster than a formal exchange of letters would have and gave both boards room to find a resolution neither side had to be forced into.
5. Negotiated a written acknowledgment rather than damages. Because the underlying claim was not strong enough to justify a costly pursuit of monetary damages, and because a drawn-out fight over money risked the exact public exposure the board wanted to avoid, we focused the negotiation on a signed acknowledgment that the program had originated with Zhen's organization, plus a commitment that future materials from the rival program would be independently developed going forward.
6. Prepared a short, factual note for the funder. Before any renewal decision was made, we helped Zhen draft a brief, calm summary of what had happened and how it had been resolved, so the funder heard the organization's own account first rather than a secondhand version arriving through the regional newsletter or a rumour at a conference. Getting ahead of the story this way meant the renewal conversation started from confidence rather than from the organization explaining itself defensively.
7. Reviewed and rewrote the organization's future consultant contracts. Going forward, every contractor engagement now includes a clear non-use clause covering methods and approaches developed for the organization, not just the physical deliverables, closing the exact gap that had made this dispute harder to resolve than it needed to be. This turned a hard lesson into a standing protection, so the organization would not have to rely on goodwill or a rival's cooperation the next time a consultant's contract ended.
8. Documented the timeline for future reference. We put together a short internal memo recording the dates of Lesia's engagement, the terms of her original contract, and the sequence of events once the rival program surfaced, including who first spotted the resemblance and when the board was told. This gave the organization a ready record if a similar question ever arose with a different consultant down the line, rather than relying on memory to reconstruct a timeline years later.

The outcome

The dispute settled without litigation. Lesia's former colleague at the rival agency agreed, on behalf of that organization, to a written acknowledgment that the original program had been developed by Zhen's non-profit, along with a commitment to independently redevelop the disputed materials rather than continuing to run a near-copy. No money changed hands in either direction, and the organization did not recover the cost of Lesia's original contract or the value of the competitive advantage it had briefly lost.

That was, honestly, a partial outcome rather than a clean win. The board had hoped for a stronger statement or some form of compensation, and neither came, because the underlying claim was not strong enough to support a harder negotiating position without risking a costly and uncertain fight. What the organization gained instead was containment: a documented record of what happened, a clear paper trail showing it had acted responsibly and promptly, and language it could point to if the resemblance ever came up again.

The funder renewed the grant that cycle. Zhen's short written summary, sent before any question was raised, appeared to matter more than the underlying legal outcome did. The organization's new consultant contract template, with its non-use language, has since been used for two further engagements without incident. Liang still keeps the two side-by-side program documents in a folder, less as evidence of a fight won than as a reminder of what a properly worded contract would have prevented in the first place.

Lesia herself was never named in the eventual acknowledgment, and no formal claim was ever filed against her personally. The board debated that decision at length, since some members wanted a clearer statement of what she had done. In the end, the organization judged that a quiet resolution with the rival agency achieved everything a longer fight might have, without the cost or the public exposure, and that judgment has held up in the months since.

What you can learn from this