Selling an applied-AI product studio in Canada

Selling an applied-AI product studio starts with a question most founders have never had to answer precisely: for every product the studio has shipped, who actually owns the intellectual property in it today — the studio, the client, or some undocumented mix of the two? Studios that have operated for years on a project-by-project basis, sometimes under work-for-hire terms and sometimes with a retained-equity handshake, often cannot answer that question cleanly without going back through each engagement’s contract. A buyer’s lawyer will ask it project by project, so the earlier you answer it yourself, the less it costs you in negotiating leverage later.

Sort out IP ownership before you sort out anything else

Go through every shipped product and confirm, in writing, whether the studio retained any ownership, licence or royalty right, and whether that position is documented in a signed agreement rather than an understanding from a conversation years ago. Where contractors or freelance developers worked on client deliverables, confirm each of them signed an assignment covering their contribution — a gap here does not just affect one product, it can call into question whether the studio’s entire internal tooling stack, if built partly by the same contractors, is cleanly owned. Any retained equity position in a client’s company needs its own check: read the actual shareholder or option agreement to confirm the stake is real, vested, and transferable, rather than assuming it survives a change of the studio’s ownership just because nobody has challenged it yet.

What runs on its own timeline during the process

If any retained equity position is significant, transferring it as part of the sale can raise securities-law considerations depending on how the stake is structured and who is buying the studio — this is a genuine legal question to route through a lawyer early, not something to assume will sort itself out at closing. Where a client’s own contract requires their consent before the studio’s ownership changes, or before an equity position can be assigned, get that consent process started as soon as confidentiality allows, because a client’s internal approval process runs on the client’s clock, not yours.

Confidentiality with clients who don’t know you’re selling

Client relationships in this business are often carried by a small number of named technical people, which means the same reputation that drives inbound work is also what a client is trusting when they hand over a sensitive product build. Running a sale process that lets word reach a client before you have controlled the message risks the client wondering whether delivery quality survives a change of ownership, or whether their own product’s IP position is suddenly less certain. Use a properly scoped non-disclosure agreement with prospective buyers, and decide deliberately which clients need to be told before close versus after, based on which contracts actually require their consent.

What a buyer will ask for

• The underlying contract for every shipped product still generating revenue, showing exactly what IP or licence rights the studio retained.
• Signed IP assignments from every contractor who touched a client deliverable or the studio’s internal tooling.
• Cap table or option-agreement documentation for any retained equity stakes, including vesting and transferability terms.
• Evidence of the internal evaluation and testing process applied to shipped AI features, since a documented process reduces buyer-side quality-risk concerns.
• Confirmation of who currently controls the API keys and vendor accounts client products actually run on in production.

Handling engagements that are still in flight at closing

If the studio has active client engagements underway on your closing date, agree explicitly with the buyer who completes them and under what terms — a half-delivered product build is a worse outcome for everyone than a slightly delayed closing that lets you finish it properly first. Where a current engagement is the one most likely to generate a future retained-equity position, make sure the sale agreement is specific about who owns that position if it materializes after closing but the underlying work was substantially done before it: this is exactly the kind of detail that gets missed when a deal moves quickly, and it is far cheaper to specify in the purchase agreement than to argue about after the fact. The same logic applies to any compute or API costs already committed for in-flight projects — confirm who is responsible for them across the closing date.

What commonly delays a close

The most common delay is a client contract that turns out to require consent before assignment, discovered only once the buyer’s lawyer asks the client directly and the client takes a long time to respond through their own internal process. A close second is a retained equity stake that, on inspection of the actual agreement, turns out to be diluted, non-transferable, or simply never formally issued — worth far less than the studio’s own internal summary suggested, and a hard thing to renegotiate once a buyer has already built it into their price expectations. Sort out both before you list, not after a buyer has already discovered the gap themselves.