Buying an applied-AI product studio in Canada

Buying an applied-AI product studio means evaluating two businesses stitched into one: a services agency that bills for delivery, and, in the better cases, a small portfolio of retained product interests sitting alongside it. The two behave completely differently as assets — one is a repeatable, if founder-dependent, income stream, and the other is a set of illiquid or semi-liquid positions whose value depends entirely on documentation you have not seen yet. A studio’s asking price usually reflects an optimistic read of both; your job before you commit to anything is to work out how much of that price is actually the second kind of asset, and how solid it really is.

What a good opportunity looks like versus a weak one

The stronger studios can point to specific shipped products still generating usage or royalty revenue today, a documented internal AI stack — evaluation harnesses, prompt libraries, reusable fine-tuning pipelines — that measurably shortens delivery on new engagements, and named technical staff beyond the founders who can credibly lead a project without them. The weaker version bills the same revenue purely through work-for-hire delivery with every contract assigning full IP to the client, has no retained products or equity worth counting, and depends entirely on one or two founders for both delivery quality and the reputation that generates new leads. Both can describe themselves identically as an 'AI product studio' in a listing; only one of them is actually selling you a product asset rather than a services pipeline with a founder attached.

What a seller may not volunteer

Ask specifically, project by project, whether the studio’s contract with each client assigned full IP to the client or left something with the studio — sellers describe their work as 'building AI products' far more often than their actual contracts support any retained ownership. Ask how the studio’s evaluation or testing process actually works for shipped AI features, since 'we test everything' in conversation and a documented process a buyer can review are different things, and the gap between them is a real quality-risk exposure you would be inheriting. And ask directly which client products are still running against a foundation-model API key or cloud account held under the studio’s own name, because that is an operational dependency that follows you as the new owner until it is formally transferred.

What you personally need to be able to step into

There is no licence to hold as the buyer of a product studio — the qualification bar here is about capability and relationships rather than regulation. The real question is whether you, or the team coming with the deal, can credibly lead an existing engagement if a named founder is unavailable, since client trust in this business often attaches to specific people rather than the studio’s brand. If the studio holds retained equity positions in client companies, find out whether those positions transfer to you automatically on a purchase of the studio’s shares, or whether each one requires the underlying client’s separate consent — the answer depends on how each stake was actually documented, not on how the seller describes it.

The vendor-account dependency that is easy to miss

A surprising number of applied-AI studios ship client products that still call a foundation-model API under the studio’s own account rather than the client’s, because it was faster to set up that way during delivery and nobody circled back to formalize the hand-off. As the buyer, you are inheriting that arrangement, including the ongoing cost and the operational risk that a client’s product silently breaks if the studio’s account is ever suspended, changed, or simply closed after your purchase. Confirm, engagement by engagement, which client products still depend on studio-held credentials, and get a plan in place to transfer or formalize each one, ideally before you close rather than as a post-closing cleanup item nobody owns.

Reading the case-study portfolio like a buyer, not a marketing page

A studio’s website portfolio is written to generate inbound leads, not to disclose risk, so read it with that in mind rather than as a neutral list of assets. Ask how many of the flagship case studies are still active, paying clients today versus historic projects kept on the site for credibility alone, and ask whether the same one or two projects are doing most of the work of generating new inquiries. A studio whose entire reputation rests on a small number of high-profile builds is more fragile than the portfolio page suggests, because losing or souring one of those relationships does not just cost the revenue — it can meaningfully slow the pipeline of new work that the case study was generating.