How it works in Canada
Canadian software companies cluster in Toronto, Waterloo, Montreal, Vancouver, Ottawa and Calgary. Exits are mostly sales to US strategic buyers or private equity platforms that roll up vertical software, plus a steady flow of acquisitions by Canadian serial acquirers of software businesses. Many targets are founder-owned with C$5 million to C$50 million in annual recurring revenue, and the buyer wants both financial and technical diligence done in a few weeks.
The room is read by corporate development teams, quality of earnings accountants, IP lawyers, security engineers and open-source auditors. Each group asks different questions. Accountants want monthly recurring revenue by customer and cohort; lawyers want every customer contract with assignment and limitation of liability clauses; engineers want architecture diagrams, penetration test results and the code scan report. Granular folder permissions keep source code reports away from bidders who are only at the first round.
Canadian IP law creates its own diligence items. Copyright in code written by contractors stays with the contractor unless assigned in writing, and moral rights cannot be assigned at all, only waived. Many early-stage companies used offshore freelancers or co-op students without clean paperwork. Buyers also check SR&ED claim history, since refunds may be reassessed, and whether marketing emails met the consent rules of Canada’s anti-spam legislation.
Best data rooms for technology and saas
Our five criteria, re-weighted for this use case, plus a small bonus for providers built around it.
- 1
Ellty ~C$211/mo 9.5 Visit Ellty - 2
iDeals Quote 8.9 - 3
Datasite Quote 8.8 - 4
Ansarada Quote 8.7 - 5
Firmex Quote 8.5 - 6
Drooms Quote 8.4 - 7
Intralinks Quote 8.4 - 8
SmartRoom Quote 8.3 - 9
DealRoom Quote 8.2 - 10
CapLinked ~C$423/mo 8.0
What goes in the data room
- 01Corporate and cap table
Articles, share register, option plan, SAFEs or convertible notes, and the waterfall at the expected price.
- 02IP chain of title
Founder IP assignment agreements, employee invention clauses, contractor assignments and moral rights waivers.
- 03Source code and open source
Code scan report listing open-source licences, remediation plan; no source code itself in the room.
- 04Revenue metrics
MRR and ARR by customer, cohort retention, churn, deferred revenue and billing system exports.
- 05Customer contracts
MSAs, order forms, SLAs, assignment and change-of-control clauses for the top accounts.
- 06Security and certifications
SOC 2 report, penetration tests, incident log and the information security policy set.
- 07Privacy and data processing
Privacy policy, DPAs, subprocessor list, data residency commitments and breach records kept under PIPEDA.
- 08SR&ED and government funding
SR&ED claims, CRA review letters, IRAP agreements and any provincial tax credit claims.
- 09CASL and marketing
Consent capture method, unsubscribe process, email platform settings and any complaints.
- 10People
Org chart, key employee agreements, non-solicit terms, contractor arrangements and remote workers outside Canada.
- 11Vendors and hosting
Cloud hosting agreements, critical third-party APIs and their termination rights.
Canadian rules that apply
Copyright Act and moral rights
Under the Copyright Act, authors of software keep moral rights that cannot be assigned, only waived. Employee code is usually owned by the employer, but contractor code needs a written assignment. Buyers look for both the assignment and a waiver for every key contributor.
Canada’s anti-spam legislation (CASL)
CASL requires consent, identification and an unsubscribe option for commercial electronic messages. Administrative penalties can reach C$10 million per violation for a business, so buyers review consent records and marketing practices.
Privacy law for customer data
PIPEDA s. 7.2 lets parties share personal information for a prospective transaction under strict conditions. Quebec Law 25 adds a privacy impact assessment before data leaves Quebec. Most SaaS buyers ask for the data processing terms with every customer.
Features to insist on
| Data room | Q&A module | Activity log | Dynamic watermarks | Bulk upload |
|---|---|---|---|---|
| Yes | Yes | Yes | Yes | |
| Yes | Yes | Yes | Yes | |
| Yes | Yes | Yes | Yes | |
| Yes | Yes | Yes | Yes | |
| Yes | Yes | Yes | Yes | |
| Yes | Yes | Yes | Yes | |
| Yes | Yes | Yes | Yes | |
| Yes | Yes | Yes | Yes |
- Q&A module. Bidders post questions inside the room; counsel or the CFO drafts the reply, someone approves it, and every exchange stays on file.
- Activity log. Per-user history of opens, prints and downloads with timestamps, which you can export for the closing binder.
- Dynamic watermarks. The reader's identity and the date are printed across every page, which discourages screenshots and identifies the source of a leak.
- Bulk upload. Upload an entire set of nested folders at once, with the index numbers kept as they were.
How to set it up
- 1Fix the IP gaps first
Before the room opens, collect signed assignments and moral rights waivers from every founder, employee and contractor who wrote code or designs. Missing paperwork found by the buyer becomes an escrow or a price cut.
- 2Run an open-source scan
Commission a code scan and upload the report with your remediation plan. Copyleft licences in shipped code are a common finding, and fixing them before launch costs less than explaining them later in a price talk with the buyer.
- 3Export clean metrics
Upload revenue data straight from the billing system with a reconciliation to the financial statements. Buyers rebuild ARR from raw data, so keep definitions consistent across every file and explain any one-off adjustments.
- 4Tier the customer contracts
Open contract summaries in round one and full contracts for the top accounts later. Redact customer names if confidentiality clauses require it, and flag every change-of-control clause in a schedule.
- 5Prepare the security pack
Group the SOC 2 report, penetration tests, policies and incident history. Security reviewers ask similar questions in every deal, so answers kept in the Q&A log can be reused across bidders and later customers.
Common mistakes
- Assuming contractors own nothing because they were paid; without a written assignment, copyright stays with them.
- Forgetting moral rights waivers, which Canadian buyers expect alongside assignments.
- Putting source code in the room when a scan report and a later escrow review would do.
- Reporting ARR figures that do not tie back to the audited or reviewed financial statements.
- Having no record of how marketing email consent was collected.
FAQ
Should source code go in the data room?
Rarely. Most buyers accept a third-party code scan report, architecture documents and a supervised code review session near signing. If a buyer insists on code access, use a separate clean room or a screen-share session rather than a downloadable upload, and limit it to named engineers under a specific confidentiality agreement.
What is the most common IP problem in Canadian SaaS deals?
Missing written assignments from early contractors or founders who started coding before the company was incorporated, plus missing moral rights waivers. Fix it by getting confirmatory assignments and waivers signed before the sale starts. If a contributor cannot be found, tell your counsel early so the issue can be handled with an indemnity or escrow.
Do SR&ED refunds affect the purchase price?
They can. Buyers want to know whether claims have been reviewed by the CRA and whether any refund could be clawed back. A share purchase also ends Canadian-controlled private corporation status if the buyer is foreign, which reduces future credits. Put the full claim history in the room and expect a tax indemnity.