TREADSTONE LAW · ONTARIO · DIGITAL LEGAL SERVICES · EST. MMXXI ·TSL
Home/Case Studies/Mergers & Acquisitions
№ 137 Case Study — Mergers & Acquisitions

The Buyout That Almost Closed on an Unsigned Patent Assignment

Three managers agreed to buy the Thunder Bay company they had spent years building. Diligence found the patent behind its equipment and the code behind its scheduling app had never been formally signed over to the business at all.

Mergers & Acquisitions6 min readThunder Bay, OntarioClean IP title
All Mergers & Acquisitions case studies
ClientYasmin, Lan and Jing, buying out the Thunder Bay company they managed
The issueA patent and in-house software were never formally assigned to the company
ServiceManagement buyout, share purchase, and IP due diligence
ResolutionAssignments recorded and clean title confirmed before signing; deal closed on schedule

The situation

The company had grown out of an odd but workable combination of services: personal support work for seniors living independently, paired with grounds maintenance and snow clearing for the same client base, sold together as one contract so families dealt with a single provider instead of two. Yasmin had joined years earlier as a personal support worker, doing home visits before moving into scheduling and then operations. Lan had started on the landscaping side, cutting grass and clearing walkways before taking over that division. Jing came in later to run the books and had ended up as the company's de facto finance lead. Between the three of them, they had been running the day-to-day of the business for several years while the founder, who was ready to retire, stayed on mostly as an owner in name.

When the founder decided to sell, the three managers put together an offer to buy the company themselves rather than see it go to an outside buyer who might change how it operated. They arranged financing through a combination of their own savings, a loan against the business's assets, and a modest vendor take-back from the founder, and settled on a purchase price of roughly $5.4 million for the whole company. It was, on paper, a straightforward management buyout: the people running the business already knew its operations, its clients, and its staff better than any outside purchaser could. What none of the three had thought carefully about was what, exactly, the company owned.

What the review found

Two pieces of the company's value sat outside its day-to-day service contracts. The first was a patent covering a folding ramp attachment the founder had designed years earlier for clearing snow and ice from narrow walkways at senior clients' homes, a small but genuinely useful piece of equipment that the company now manufactured in a small batch through a local machine shop and used across its landscaping crews. The second was a scheduling and dispatch application, built years earlier by a contract developer and refined since by an in-house hire, that coordinated personal support worker visits and landscaping crews across the same client roster. Both were treated internally as company property. Neither actually was, on paper.

A patent is registered to whoever invents it unless that person formally assigns their rights to someone else in writing. The founder had applied for and held the patent personally, in their own name, and had never signed a document transferring it to the company. Software works the same way under Canadian copyright law: the person who writes code owns the copyright in it unless they are an employee acting within the scope of their job, or they have signed an assignment. The original developer had been an independent contractor, not an employee, and the contract under which they had been engaged said nothing about who would own the resulting code. The in-house hire who had since modified and extended the software was an employee, so that portion was less exposed, but the foundation the whole application was built on had a gap in its ownership.

In an outright asset sale, this kind of gap can sometimes be patched up quietly after the fact. In a share purchase, where the buyers are acquiring the company itself rather than a list of assets, it matters more, because the buyers are paying for a business that is supposed to already own everything it uses. If the patent and the core of the software were never the company's to begin with, the purchase price was being calculated on value the company did not, strictly speaking, hold clean title to. Worse, because the founder was both the seller and the unrecorded owner of the patent, closing the sale without fixing the assignment would have left the founder personally holding rights to a piece of equipment the buyers believed they were paying for as part of the business.

What we did

  1. Ran a targeted intellectual property search before touching the purchase agreement. We pulled the patent's registration details directly from the federal patent register and confirmed the inventor and owner of record. The mismatch between who legally owned the patent and who the buyers believed owned it was visible within the first day of diligence, well before any deposit changed hands.
  2. Traced the software's history contractor by contractor. We asked for every agreement, invoice, and email connected to the original build of the scheduling application, and pieced together who had touched the code and under what terms. This confirmed the gap: no assignment from the original independent contractor, and only an implied but undocumented ownership claim over later work done by the employee.
  3. Located the original developer and negotiated a retroactive assignment. Years had passed, but the developer was still reachable and, after some negotiation over a modest payment to formally sign away any claim, agreed to execute a written assignment transferring all rights in the original code to the company. This closed the single biggest hole in the software's ownership chain.
  4. Had the founder execute a formal patent assignment before signing. Rather than leave this as a closing condition to be sorted out later, we prepared the assignment document and had the founder sign it as a precondition to signing the share purchase agreement itself, and arranged for it to be recorded with the patent office so the company's ownership was a matter of public record, not just a private agreement between the parties.
  5. Added confirming representations and a holdback to the purchase agreement. Even with the assignments in hand, we built in seller representations confirming the company owned all the intellectual property used in its business, along with a modest holdback of the purchase price for a period after closing, giving the buyers a remedy if any other undisclosed ownership gap surfaced later.
  6. Confirmed the employee-created code was properly covered. We reviewed the employment agreement for the staff member who had extended the software after the original build, confirming it contained language assigning work product to the employer, so that portion of the intellectual property required no further fix.

The outcome

Both assignments were signed and, in the patent's case, recorded before the share purchase agreement itself was signed, so by the time Yasmin, Lan, and Jing committed to the roughly $5.4 million purchase price, the company they were buying actually owned the patent and the software they were paying for. The transaction closed on the timeline the three had originally planned, without a renegotiation of price and without the founder needing to be brought back in after closing to sign documents they might, by then, have had less incentive to sign quickly or for free.

The retroactive assignment from the original software developer cost the company a modest one-time payment, well under $10,000, to formally close out a claim that could otherwise have complicated the deal or, years later, resurfaced as a dispute over who owned the core of a tool the business depended on every day. That was a small price against a $5.4 million transaction, but only because it was paid deliberately, as part of clearing title, rather than extracted later by someone who realized their leverage after the fact. The recorded patent assignment meant the folding ramp attachment, and the company's exclusive right to make and use it, belonged to the business the three now owned outright, not to their former boss.

What made this a clean result rather than a near miss was timing. The gap in ownership existed the entire time the company operated, unnoticed, because nobody had reason to test it until a sale put real money on the fine print of who owned what. Diligence caught it early enough that fixing it was a matter of paperwork and a modest negotiated payment, done calmly before signing, rather than a scramble against a closing date or a fight after the fact between new owners and a seller who no longer had much reason to cooperate.

What you can learn from this

  • In a share purchase, buyers are paying for a company that is supposed to already own everything it uses. Confirm that ownership with a patent office or copyright search rather than assuming internal use equals legal title.
  • A patent belongs to its inventor personally until they sign a formal assignment, even if the invention has been used by their company for years. Check the register, not the org chart.
  • Software written by an independent contractor is owned by that contractor unless a written agreement says otherwise. Employees are different, but only if their employment agreement actually assigns work product to the employer.
  • Fix gaps in intellectual property ownership before signing, not as a promise to sort out after closing. Sellers and former contractors have far less incentive to cooperate once the money has changed hands.
  • A modest holdback on the purchase price gives buyers a practical remedy if an undisclosed ownership gap surfaces after closing, even after careful diligence.
This case study is entirely fictional. It does not describe any real client, file, or matter handled by Treadstone Law, and it is not a real file with details changed. All names, people, properties, businesses, dollar amounts, dates, and events are invented, and any resemblance to a real person, business, or situation is coincidental. Fictional scenarios like this one illustrate the kinds of legal issues people in Ontario commonly face and how a lawyer can help. They are general information, not legal advice — no two matters unfold the same way, and nothing here predicts the outcome of any real case. Reading a case study does not create a lawyer-client relationship. If you are facing something similar, speak with a lawyer about your specific circumstances.

This is a mergers & acquisitions problem we handle

Start a file online — flat, published fees, reviewed by a licensed lawyer before a dollar is owed.

ContactStart a File →