Deavo
Due diligenceGuide · 5 min read

Due diligence on an AI business

Due diligence on an AI business starts with the usual small-business review, then adds questions for the seller: where the training data came from, who owns the model and code, how much depends on one person, and which outside services the product runs on.

Due diligence on an AI business starts with the review any small-business purchase needs — financials, leases, contracts — and then adds questions a buyer can put to the seller about data, ownership and dependency: where did the training data come from, who owns the model and the code, how much of the product depends on one person, and which outside services does it run on. The sources behind this page are Ontario law-firm articles on general acquisition diligence, the federal privacy statute and the federal privacy regulator, not AI-specific guidance, so treat what follows as questions to ask. This page covers Ontario; check the rules where you are.

Data provenance and privacy

Ask the seller to document where the training data came from: licensed, purchased, collected from users, gathered from public sources, or generated inside the business. Where any of it is personal information, ask how it was collected and what consent or terms applied at the time. The Office of the Privacy Commissioner of Canada lists the fair information principles of the federal Personal Information Protection and Electronic Documents Act (PIPEDA), which include accountability, identifying purposes, consent, limiting collection, use, disclosure and retention, and safeguards.

PIPEDA s.7.2(1) lets organizations that are parties to a prospective business transaction use and disclose personal information without the individual’s knowledge or consent if they have entered into an agreement requiring the organization that receives it to use and disclose it solely for purposes related to the transaction, to protect it with security safeguards appropriate to its sensitivity and, if the transaction does not proceed, to return or destroy it within a reasonable time, and if the information is necessary to decide whether to proceed and, if the decision is to proceed, to complete the transaction. Under s.7.2(4), this does not apply to a transaction whose primary purpose or result is the purchase, sale or other acquisition or disposition, or lease, of personal information, so ask your lawyer how it applies before any data is shared. In Ontario, ask what personal information the business collects and where it is stored, whether it has a written privacy policy and whether practice matches it, and which third-party vendors handle the data and what their agreements say about data protection. Ask specifically about past breaches, ransomware, phishing incidents and regulatory complaints, not only whether the business has ever been hacked.

If the seller cannot document the data trail, ask your lawyer how representations, warranties and an indemnity in the purchase agreement could address data issues that surface after closing. Ask those questions directly before closing rather than relying on recovering losses afterward.

IP ownership: model, weights, code

Ask who legally owns the model, the trained weights and the underlying code, not who built them but who holds documented rights. In Ontario, ask whether work created by an employee within their job duties belongs to the employer, and whether work created by an outside contractor may still belong to the contractor unless a written assignment transfers it to the business. For anything made by a freelancer, developer or agency, look for a signed agreement that assigns ownership to the seller’s business, and ask your lawyer whether an invoice or a verbal understanding alone would be enough.

Request the employment agreements and contractor agreements for everyone who worked on the core system, and ask what to do about any gap. Ask your lawyer about purchase agreement tools for this: representations and warranties that the seller owns or validly licenses all IP used in the business, a disclosure schedule listing every key contract and licence, specific assignment documents, and indemnities allocating the risk if an ownership problem appears after closing.

Key-person and technical dependency

An Ontario article on selling a business describes key-person dependency as a business that would struggle to operate without its owner personally, and lists pricing, quoting or key operational decisions living in the owner’s head rather than in written processes as a sign of it. That idea is about owners; for an AI product, also ask who built, tuned and maintains the model, whether technical documentation exists that a new team could work from, and whether that person intends to stay through and after the transition.

A buyer facing this dependency can ask whether the seller would stay involved after closing as a consultant, an employee or under a transition services arrangement, and can ask about a longer transition period or an earn-out tied to post-closing performance. Ask your lawyer whether a retention or transition arrangement fits the deal, and raise it early in negotiations.

Third-party and infrastructure dependency

Make a list, with the seller, of every outside service the product runs on: the underlying foundation model if it is not the seller’s own, cloud infrastructure, data vendors and specialized tooling. For each, request the contract or terms of service and ask about cost, notice periods, any exclusivity commitment and what happens if the provider changes its terms or price. In Ontario, an article on IP diligence notes that some software and technology licences are personal to the seller and do not automatically transfer to a new owner, so ask each provider whether the agreement can be assigned to you. Also ask the seller whether there is a documented fallback plan if a key provider became unavailable.

Open-source components

Ask the seller for a list of the open-source components in the product, including any open-source frameworks or open-weight models, with the licence that applies to each. Have your lawyer or a technical reviewer read each licence and explain what, if anything, it requires of the business before you rely on the product being usable commercially in its current form.

Financial and revenue questions to ask

  • Ask how compute and API costs are recorded in the financial statements, and whether any are treated as one-time items.
  • Ask for revenue split between recurring subscription or contract income and one-time implementation or pilot projects.
  • Ask for a customer list showing how much revenue each customer represents, to see whether a few customers account for most of it.
  • For usage-based pricing, ask the seller to show the cost of serving a customer alongside the revenue from that customer.
  • Ask which revenue comes from pilots or proof-of-concept engagements and whether any have converted to a standing contract.
  • Ask your accountant how a change in a key provider’s pricing would show up in the numbers.

Sources

Every requirement and figure referenced in this guide traces to a primary source. Links were last confirmed on the dates shown.

  1. 01
    Office of the Privacy Commissioner of CanadaGovernment
    The Personal Information Protection and Electronic Documents Act (PIPEDA)
    priv.gc.ca·Checked Aug 14, 2026
  2. 02
    Government of Canada (Department of Justice)Government
    Personal Information Protection and Electronic Documents Act, S.C. 2000, c. 5
    laws-lois.justice.gc.ca·Checked Oct 20, 2026
  3. 03
    Treadstone LawLegal commentary
    Intellectual Property Due Diligence When Buying a Business in Ontario
    treadstonelaw.ca·Checked Aug 14, 2026
  4. 04
    Treadstone LawLegal commentary
    Cybersecurity and Data Privacy Due Diligence When Buying a Business in Ontario
    treadstonelaw.ca·Checked Aug 14, 2026
  5. 05
    Treadstone LawLegal commentary
    How Long Does Due Diligence Take When Buying a Business in Ontario?
    treadstonelaw.ca·Checked Aug 14, 2026
  6. 06
    Treadstone LawLegal commentary
    Key-Person Dependency
    treadstonelaw.ca·Checked Aug 14, 2026

Deavo is an advertising and listings platform, not a brokerage, law firm or valuation firm. This page is general information, not legal, tax, accounting or valuation advice, and rules differ by province. Confirm anything you rely on with a qualified professional before you act on it.