How can a Canadian MSP introduce an eligible operating company?
Treat it as a handoff with three owners: you spot and screen, the client's owner decides and applies, and SourceX reviews. Your part ends once an authorized person at the client has applied through your referral link.
The route below is specific to MSPs because of one awkward fact: you probably hold the technical keys to the very systems a licensing review would look at. That makes you a strong spotter and a poor courier. The program is designed so you never need to be the courier.
The handoff, step by step
| Step | Who acts | What happens | What the MSP keeps on file |
|---|---|---|---|
| 1. Sign up | MSP | Register as a partner and sign the Channel Partner Agreement | Signed agreement date |
| 2. Screen | MSP | Check headcount, record span, systems and ownership from existing knowledge | A one-page metadata note |
| 3. Ask | MSP and owner | Raise the idea in a scheduled account review, not a support ticket | Date and the owner's yes or no |
| 4. Opt in | Owner | The owner names who will speak for the company | Contact's name, title and business email |
| 5. Apply | Client | The authorized contact applies through your referral link | Date of the introduction |
| 6. Review | SourceX and client | Inventory, rights review, dataset fit, offer and agreement | Nothing; you are not in this loop |
Step 6 is where most of the uncertainty sits, and none of it is yours to resolve. What you control is the quality of steps 2 to 5.
What should the MSP check before raising it with the owner?
Check the program's company criteria using facts you already hold or can ask for, never by running a report against the client's tenant.
Headcount is not seat count
Your RMM and licensing dashboards show seats, mailboxes and devices. None of those is the program's test, which is 50+ full-time employees at peak, contractors excluded. Seat counts drift away from headcount in predictable ways:
| What your dashboard counts | Why it can overstate headcount | Better question for the owner |
|---|---|---|
| Licensed mailboxes | Shared, room and service mailboxes | "How many full-time staff at your busiest point?" |
| Endpoints under management | Spare and shared devices, kiosks | "Was that number ever above 50?" |
| Active directory users | Contractors, seasonal and departed staff not yet removed | "How many of those are contractors?" |
A 70-seat client might be a 45-person company with contractors. A 40-seat client might have peaked at 60 staff before a downturn. Ask; do not infer.
Records, span and system
Note what kind of operating records exist (tickets, project files, quotes, dispatch logs, quality reports), roughly how many years they cover, and which system holds them. You can usually answer "which system" and "how many years" from memory. Do not answer "how good is the content" by looking.
Ownership and authority
Who owns the business, and who can authorize a discussion about licensing its records? It is the CEO; in an owner-managed firm that is usually the owner. In a group, the operating company may not own the records its staff created; a parent or a client contract may. Write down what you know and flag what you do not.
Where does Canadian law change the conversation?
It mostly changes what the company and SourceX must review later, not what you do now. Two points are worth knowing before the first conversation.
Privacy law sits with the company. The Office of the Privacy Commissioner of Canada explains that PIPEDA governs private-sector commercial activity, that Alberta, British Columbia and Quebec have private-sector privacy laws deemed substantially similar, and that PIPEDA still applies when personal information crosses provincial or national borders. For a client with offices in Ontario and Quebec, that can mean more than one regime applies to the same records. You do not need to analyze it. You need to avoid creating a new disclosure by moving records yourself, which is one more reason discovery stays at metadata level.
Your introduction email may be a commercial message. The CRTC's CASL guidance says a commercial electronic message needs consent, identification of the sender and an unsubscribe mechanism, and that the sender bears the burden of proving consent. A note to an existing client inside an active account relationship is a different situation from a cold email to a stranger, but ask your own counsel how CASL applies to your practice before you build a campaign. The wider cross-border tax and professional-rule picture is in the guide for Canadian advisors referring US companies.
An illustrative screen: a two-province client
Illustrative. A fictional freight and warehousing company, 140 people today, with sites in Ontario and Quebec, a managed client for eight years.
| Question | What the MSP knows | Status |
|---|---|---|
| Full-time staff at peak | Owner confirmed about 150 in 2024, contractors excluded | Meets 50+ |
| Operating history | Founded 2009; dispatch and WMS records since 2014 | Documented |
| Systems | A TMS, a warehouse management system, a help desk, shared drives | Named, not opened |
| Language of records | Mixed English and French | SourceX assesses dataset fit |
| Who owns the records | The operating company; some customer contracts may restrict reuse | Flag for rights review |
| Who can authorize | The owner, who names the CFO as contact | Authorized contact identified |
| Location | Canada | Within the published geography |
Every cell is metadata. Nothing in the table required a login, a sample file or an export, and the two flagged rows are exactly the items SourceX and the company's counsel resolve during review.
Which companies qualify, and what stays unknown?
Introduced companies need 50+ full-time employees at peak (contractors excluded), a documented operating history, the rights to license the records, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.
The full criteria are on who qualifies, and the company fit checker gives the owner a preliminary, non-binding screen without contact details. Until SourceX reviews the company, nobody knows whether buyers want those records, what the rights review will conclude, what the company would be offered, or whether any reward will follow.
If the client pushes back on involving you at all, that is fine. The guide on clients who will not share admin credentials covers the trust side, and an MSP considering its own exit should read selling an MSP separately; it is a different decision.
How is the MSP credited and paid?
Credit goes to the first valid introduction within the 90-day attribution window, recorded when the company submits a verified application; one partner is credited per company, and duplicates are reviewed. The company's compensation and your reward are separate: SourceX pays the company under its own agreement, and funds any reward on top. The rewards page shows how statuses move from estimated to paid, and the first-month plan for MSPs covers how to fit this into a book of clients.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If one managed client passes the headcount-not-seats test and its owner says yes, register as a partner, check the details against who qualifies, and read the program terms before sending the referral link; the referral program overview summarizes the rest.