Who you already know
Owners and IT decision makers at US SMB and mid-market clients. You know which systems they run and how much history they keep.
Why an introduction can fit your work
You understand where a client's proprietary data assets live. You can spot well-maintained knowledge bases and ticket histories without ever touching the content.
What a suitable US client looks like
- Long-running internal knowledge base or ticketing history
- Documented IT and operational runbooks
- An owner open to new revenue from existing proprietary data assets
Relationship and disclosure
- Never access or export client data for a referral. Your admin access does not give you permission to share.
- Tell your contact that you may receive a referral reward from SourceX.
- Never share client files or data yourself. The company decides what proprietary data to share, directly with SourceX.
Qualification checklist
- ☐Established business in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE or Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English) with documented operations and valuable proprietary data
- ☐You can reach the owner, executive or authorized decision-maker
- ☐The material is likely the company's own, not its clients'
- ☐The contact is open to a short assessment of their data's licensing potential
Example of an owner-led introduction (illustrative)
"Your team keeps one of the best-maintained knowledge bases among our clients. SourceX licenses approved business data directly from companies for AI training and evaluation. As your direct licensing partner, it manages the agreement, rights review, data preparation, delivery and payout, subject to acceptance at Closing and agreed terms. Your company controls what proprietary data it approves for licensing. Want me to introduce you? I may receive a referral reward."
Rewards are calculated as the greater of $50,000 plus 5% and 15% of the Actual Supplier Payout (eligible licensing compensation SourceX actually pays the referred company, excluding separately itemized taxes and expense reimbursements), with no cap, subject to any signed Schedule A or addendum. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details. SourceX funds rewards separately; they do not reduce the company's payout. A lead, meeting or signed agreement alone does not trigger payment. See the program terms.
Admin access is a permission your client granted for defined service work. It is not a right to copy, share or license anything in the client's systems. Only the company can decide to license its records, and its CEO authorizes that conversation. Your part is to notice a fit, tell the CEO, and introduce them if they want it, using metadata the CEO approves. For a referral, no file, export, sample, screenshot or login ever leaves the tenant.
These sections turn the relationship rules above into something a service desk can follow: a training sheet for technicians and account managers, and a no-export workflow for Microsoft 365 clients.
Access, service duty and licensing authority are three different things
Each is held by a different party, and only one of them can start a licensing conversation.
| Term | What it is | Who holds it | What it permits for a referral |
|---|---|---|---|
| Access | Technical permissions in the client's systems, such as admin roles in a Microsoft 365 tenant | The MSP's technicians, as granted by the client | Noticing what you already see in your work, nothing more |
| Service duty | The work your master services agreement and statements of work describe | The MSP, under contract | Nothing: a referral is not a service task |
| Licensing authority | The right to license records the company owns, and the decision to explore it | The company; its CEO authorizes the conversation | Everything that follows, starting with whether to talk at all |
| Technical custodian | Whoever runs and administers the systems day to day | Often the MSP | Carrying out a written client instruction after the company signs, within the agreed scope |
| Sponsor | An executive who champions the idea inside the company, such as the COO or IT director | Varies by client | Carrying the idea to the CEO, not authorizing it |
Microsoft's partner model draws the same line. Its Partner Center documentation describes granular delegated admin privileges (GDAP) as least-privileged access to customer tenants: the partner requests specific built-in roles for a set period, from 1 to 730 days, and the customer must explicitly grant them. NIST states the principle in general form in control AC-6 of SP 800-53: allow only the authorized accesses necessary to accomplish assigned organizational tasks. An introduction is not an assigned task, so admin rights add nothing to it.
Which system events open the conversation, and who sponsors it?
Events you are already paid to handle: migrations, retirements and retention reviews. The person who asks you to handle them is often a sponsor, not the decision-maker.
| System event you see | Metadata it gives you | Likely sponsor | What you do not do |
|---|---|---|---|
| Tenant-to-tenant migration after an acquisition | Which tenant holds the older history, and when cutover is due | IT director or integration lead | Copy or stage data for anyone outside the migration scope |
| Retiring an on-premises file server or Exchange | Years of project folders or mail, and the shutdown date | COO or office manager | Keep a spare copy before decommissioning |
| Replacing a ticketing or PSA tool | How many years of resolved tickets sit in the old tool | Service manager | Export closed tickets to show what exists |
| Retention policy review | What is kept, for how long, and what will be deleted | Compliance lead or CFO | Run content searches to size anything for a referral |
| License true-up | Seat counts, which are not headcount | Finance | Present seat counts as full-time employees |
A dated cutover or deletion is a reason to raise the topic sooner, never a reason to skip the CEO. Related guides: tenant-to-tenant migration after an acquisition, Exchange Server end of support, the Microsoft 365 retention policy checklist and why a license count is not a headcount.
The access-versus-authority training sheet
Use it in a 15-minute team briefing. Each row is a situation a technician or account manager will meet; the two middle columns are the lesson.
| Situation | Your access lets you | Your authority lets you | The right move |
|---|---|---|---|
| You see 12 years of resolved tickets in a client's helpdesk | Read them for support work | Mention to the CEO that the history exists | Tell the CEO; share "helpdesk, about 12 years" only if they approve |
| The COO asks you to send SourceX a sample to show quality | Export a mailbox or site, if you hold an eDiscovery role | Nothing: the COO can sponsor, not authorize | Decline and offer to introduce the CEO; the MSP guidance above says never to export client data for a referral |
| An account manager wants proof of 50+ employees | Pull a license report | Pass on the headcount the client gives you | Ask for peak full-time headcount from payroll, contractors excluded |
| Someone asks for read-only credentials so the data can be assessed | Create an account | Nothing | Refuse; SourceX's own export guidance says admin logins are not shared |
| The IT director wants to keep it from the CEO until it looks promising | What you had before | Nothing new | Wait; if the CEO does not know, the introduction is usually not a fit |
| You host portals whose content belongs to the client's customers | Administer them | Nothing over the customers' material | Leave it out; client-owned material is usually not a fit |
| The CEO says yes and asks you to join the first call | Attend | Describe systems and years, as the CEO approved | Join; still no files |
| The client signs with SourceX and instructs you in writing to run the agreed export | Run it | Act as the client's technical custodian for that scope | Follow the written instruction and the agreed scope; this is service work, separate from the referral |
| Your own MSP holds 15 years of tickets and runbooks | Everything | Your own CEO decides | A different question: see which MSP records fit |
Method and assumptions. The sheet draws on SourceX's terms (version 2026-10-22.2, since replaced by version 2026-11-04), its who-qualifies page and Microsoft 365 export guidance, Microsoft's GDAP documentation, NIST SP 800-53 control AC-6 and the CISA advisory below, all checked 2026-10-26. It assumes your services agreement says nothing about referrals; where your agreement or a client's security policy is stricter, that governs. It is not legal advice. The recommendation changes in only two cases: after the client signs with SourceX and instructs you in writing, and when the records are your own company's.
Why shouldn't a Microsoft 365 administrator export files for a referral?
Because nobody has asked for an export, and an export is visible. At the referral stage there is nothing to deliver: the company applies, SourceX reviews it, and any export comes later under the company's signed agreement and its own approval.
The capability is real. SourceX's own Microsoft 365 guidance notes that admins can search and export content with Microsoft Purview eDiscovery, and Microsoft's documentation lists exporting from a search among the eDiscovery activities recorded in the audit log. A quick sample therefore leaves a record of an export the client never requested, in the log the client's security reviewer reads.
Client security teams are told to look for exactly that. A joint advisory from CISA and its UK, Australian, Canadian and New Zealand counterparts (AA22-131A, May 2022) urges MSP customers to make contracts assign security responsibilities clearly, to keep visibility into MSP activity, and to hold MSP accounts to least privilege. An unrequested export puts the MSP on the wrong side of all three.
The no-export introduction workflow
| Step | MSP (technical custodian) | Client CEO and company (owner) | SourceX |
|---|---|---|---|
| 1. Notice | Spot the event in normal work; write a metadata note from what you already know: system, record types, years, rough volume, administrator. Run no new searches or reports for it | Not yet involved | Not involved |
| 2. Raise | Tell the CEO, or ask the sponsor to bring you to the CEO; say you may receive a referral reward | Hears it first from you | Not involved |
| 3. Decide | Wait | Says yes, no or later; approves what the note may say | Not involved |
| 4. Introduce | Submit through your partner link, having signed the SourceX Channel Partner Agreement | The company applies itself | Receives the introduction |
| 5. Qualify | Answer system questions only as far as the CEO allows | Answers SourceX's questions directly | Reviews fit, rights and current data needs |
| 6. Deliver, only if signed | Run an export only on the company's written instruction, for the agreed scope | Approves the scope; runs or directs the export | Guides the export; no admin logins |
Step 1 is the discipline most teams miss. Writing the note from the migration plan or asset register you already hold is metadata; opening a content search to count mailboxes or folders for a referral is not. How data actually moves once a company signs is explained in does a data buyer need access to our systems, and SourceX's Microsoft 365 export guidance shows the company-run steps.
Introduce the owner without exports or unverified claims
A conversation that stays inside your authority (Illustrative):
"You're retiring the old file server in June, and it holds about 15 years of project folders. Some companies license records like these directly to SourceX for AI training and evaluation. You decide whether to explore it, and nothing leaves your systems unless you approve it later. I can introduce you if you'd like. I may receive a referral reward from SourceX if it goes ahead, and I'll share nothing beyond what you approve."
Keep four claims out of it: a value or price for the records, any promise that SourceX will take them, any named AI developer as a buyer, and any suggestion that your access makes the records easy to license. Rights are reviewed separately, by SourceX, with the company. The MSP email templates follow the same rules in writing.
One migration, two technicians (Illustrative)
Illustrative: a generic client and invented facts; no outcome is implied.
The right way. An MSP is moving a 260-person engineering consultancy from an on-premises file server to SharePoint, with the server due off in four months. The service manager sees 18 years of project folders. He writes a metadata note from the migration plan already on file (file server, project documents from 2007 to 2025, about 4 TB, administered by the MSP), and the account lead raises it with the CEO at the monthly review, mentioning the possible reward. The CEO wants a conversation and approves the note. The introduction goes through the partner link, the company applies, the migration plan does not change, and no copy is kept just in case.
The failure. Same client, different technician. Before the CEO knows anything, a technician exports three project folders through an eDiscovery case to show quality. The client's next access review finds an export nobody requested in the audit log. The MSP now has a security question to answer under its contract, the CEO first hears about licensing as an incident rather than an option, and the introduction is one SourceX's own guidance treats as usually not a fit, because it was made without the decision maker's knowledge.
Limits of the sheet
- Your contract may be stricter. Some agreements bar any use of client information outside the services; then even sharing the metadata note needs the client's written approval.
- Regulated clients. Health, finance and public-sector clients may treat system names and volumes as sensitive. Ask before writing them down.
- Rights stay open. Who owns the records, whether customer contracts limit reuse and whether they match current data needs are settled in SourceX's review, not by anything an MSP can see. Selling an MSP is a separate question, covered in how to sell an MSP business.
A measurable next step. Add one line to your technician runbook: "No exports, samples or credentials for referrals; raise fits with the account lead." Over the next quarter count four numbers: system events noted, CEOs told, introductions made with the CEO's approval, and exports made for a referral. The last should stay at zero. SourceX has not published MSP referral results; these counts are how you would measure your own. More partner guides are in the guides.
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.
When a system event surfaces a client whose CEO is open to the conversation, sign up on the registration page for a partner link, test that client against who qualifies, go through the program terms, and introduce the CEO with nothing more than the metadata they approved.