Referral opportunities for managed service providers

Short answer

Managed service providers often work closely with owners and operating leaders of established businesses in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English). If a client has well-documented proprietary data assets and may be open to licensing that knowledge, an introduction to SourceX can create value for them and earn you a referral reward.

Visual briefFull-size diagram
Three columns for the MSP as technical custodian, the client CEO as owner and SourceX: the MSP spots an event and writes a metadata note, the CEO decides and approves what is shared, then the company applies and SourceX reviews. A direct path from the MSP to SourceX is crossed out: no export, sample or login for a referral.
Who does what in an MSP introduction. Any export comes later, only on the company's written instruction after it signs.

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.

TermWhat it isWho holds itWhat it permits for a referral
AccessTechnical permissions in the client's systems, such as admin roles in a Microsoft 365 tenantThe MSP's technicians, as granted by the clientNoticing what you already see in your work, nothing more
Service dutyThe work your master services agreement and statements of work describeThe MSP, under contractNothing: a referral is not a service task
Licensing authorityThe right to license records the company owns, and the decision to explore itThe company; its CEO authorizes the conversationEverything that follows, starting with whether to talk at all
Technical custodianWhoever runs and administers the systems day to dayOften the MSPCarrying out a written client instruction after the company signs, within the agreed scope
SponsorAn executive who champions the idea inside the company, such as the COO or IT directorVaries by clientCarrying 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 seeMetadata it gives youLikely sponsorWhat you do not do
Tenant-to-tenant migration after an acquisitionWhich tenant holds the older history, and when cutover is dueIT director or integration leadCopy or stage data for anyone outside the migration scope
Retiring an on-premises file server or ExchangeYears of project folders or mail, and the shutdown dateCOO or office managerKeep a spare copy before decommissioning
Replacing a ticketing or PSA toolHow many years of resolved tickets sit in the old toolService managerExport closed tickets to show what exists
Retention policy reviewWhat is kept, for how long, and what will be deletedCompliance lead or CFORun content searches to size anything for a referral
License true-upSeat counts, which are not headcountFinancePresent 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.

SituationYour access lets youYour authority lets youThe right move
You see 12 years of resolved tickets in a client's helpdeskRead them for support workMention to the CEO that the history existsTell the CEO; share "helpdesk, about 12 years" only if they approve
The COO asks you to send SourceX a sample to show qualityExport a mailbox or site, if you hold an eDiscovery roleNothing: the COO can sponsor, not authorizeDecline 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+ employeesPull a license reportPass on the headcount the client gives youAsk for peak full-time headcount from payroll, contractors excluded
Someone asks for read-only credentials so the data can be assessedCreate an accountNothingRefuse; SourceX's own export guidance says admin logins are not shared
The IT director wants to keep it from the CEO until it looks promisingWhat you had beforeNothing newWait; if the CEO does not know, the introduction is usually not a fit
You host portals whose content belongs to the client's customersAdminister themNothing over the customers' materialLeave it out; client-owned material is usually not a fit
The CEO says yes and asks you to join the first callAttendDescribe systems and years, as the CEO approvedJoin; still no files
The client signs with SourceX and instructs you in writing to run the agreed exportRun itAct as the client's technical custodian for that scopeFollow the written instruction and the agreed scope; this is service work, separate from the referral
Your own MSP holds 15 years of tickets and runbooksEverythingYour own CEO decidesA 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

StepMSP (technical custodian)Client CEO and company (owner)SourceX
1. NoticeSpot 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 itNot yet involvedNot involved
2. RaiseTell the CEO, or ask the sponsor to bring you to the CEO; say you may receive a referral rewardHears it first from youNot involved
3. DecideWaitSays yes, no or later; approves what the note may sayNot involved
4. IntroduceSubmit through your partner link, having signed the SourceX Channel Partner AgreementThe company applies itselfReceives the introduction
5. QualifyAnswer system questions only as far as the CEO allowsAnswers SourceX's questions directlyReviews fit, rights and current data needs
6. Deliver, only if signedRun an export only on the company's written instruction, for the agreed scopeApproves the scope; runs or directs the exportGuides 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.

How can managed service providers earn referral income from AI data licensing?

Managed service providers can earn referral income by introducing qualified clients to SourceX. When a referred company licenses approved data directly to SourceX, partners can receive 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). Rewards are 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. Partners never handle any client data directly, ensuring a clean process.

SourceX offers managed service providers a clear referral program. Partners introduce clients who may benefit from licensing their proprietary data to SourceX. 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. The reward is 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. SourceX funds rewards separately; they do not reduce the company's payout. Partners avoid handling client data directly at any point in the process. This maintains security and simplifies the partner's role, focusing on client introductions.

Which clients should managed service providers consider for an AI data referral?

Consider US-based clients with 50 or more full-time employees at their peak. These companies should possess years of well-documented proprietary records and confirm they hold licensing rights. An authorized owner or executive sponsor must be ready to engage with SourceX. Focus on established businesses with valuable, structured data assets.

Managed service providers should screen clients against specific criteria for an optimal referral. Ideal clients are US-based companies that have employed 50 or more full-time employees at any point in their history. They must possess years of well-documented, proprietary data assets. It is crucial that the company holds clear rights to license this data. An authorized owner or executive sponsor must be prepared to oversee the data licensing process. These foundational elements ensure the client is well-positioned for AI data licensing opportunities through SourceX.

How can managed service providers raise data licensing during renewals and client technology reviews?

During renewals or technology reviews, MSPs can introduce data licensing as an optional, company-controlled revenue opportunity. Emphasize that the client approves data scope, anonymization, and delivery. SourceX will never deliver any data without the client’s explicit approval. This highlights client autonomy throughout the process.

Managed service providers can strategically introduce data licensing during regular client interactions like renewals or technology reviews. Position it as an additional, optional revenue stream for the company. It is vital to emphasize that the client retains full control over the entire process. This includes approving the scope of data to be shared and any anonymization steps. SourceX will only proceed with data delivery after receiving explicit authorization from the client. This approach assures clients that their data privacy and business interests remain paramount, making the discussion productive and transparent.

What do managed service providers do before and after a SourceX introduction?

Before an introduction, partners identify qualified companies and confirm their interest. After introducing, the partner’s role is complete. SourceX manages all subsequent steps, directly engaging the company. Partners never handle company data. The company retains approval rights over data scope and any final data delivery to buyers.

Before making an introduction, a managed service provider identifies a qualified US company client. The partner confirms the client's interest in exploring data licensing. Once the introduction to SourceX is made, the partner's direct involvement in the process concludes. SourceX takes over, engaging directly with the referred company. Partners never handle any company data at any stage. The referred company maintains full control, approving the scope of data extraction and granting final consent for any data delivery to buyers. This ensures a streamlined, secure, and partner-friendly referral process.

How do referral fees work for managed service providers?

Referral rewards for MSPs are 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 90-day attribution window applies from the initial introduction.

Referral fees for managed service providers are straightforward. The partner receives 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). Rewards are with no cap across all transactions, 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. An attribution window of 90 days applies, starting from the initial introduction of the company to SourceX. This system ensures clarity and fairness in partner compensation.

What ownership and disclosure questions arise for managed service providers making data referrals?

MSPs must confirm the client's data licensing rights and the executive sponsor's authority. Partners should disclose the referral reward to the client. Crucially, the referred company always controls the scope of data licensed. This transparency ensures trust and proper governance throughout the referral process and data transaction.

When making data referrals, managed service providers address key ownership and disclosure questions. Partners should confirm that the client company holds the explicit rights to license its data. It is also important to ensure that the designated executive sponsor has the authority to make decisions regarding data licensing. Partners must clearly inform the client about the referral reward they may receive from SourceX. This transparency builds trust. The referred company retains complete control over defining the scope of any data that is licensed, ensuring their business interests are protected at all times.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. 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.

Common questions

What is the referral program for managed service providers?

It's a program where managed service providers can refer businesses in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English) with well-documented proprietary data assets to SourceX. If the client is open to licensing their knowledge, an introduction can create value for them and earn the MSP a referral reward.

What types of clients are suitable for this referral program?

Suitable US clients have a long-running internal knowledge base or ticketing history and documented IT/operational runbooks. They must also have an owner open to new revenue from existing proprietary data assets, and the material should be the company's own.

How are referral rewards calculated?

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.

What should I tell clients about my referral?

You must inform your contact that you may receive a referral reward from SourceX for the introduction. Always ensure the client decides what proprietary data to share directly with SourceX, and never access or export their data yourself.

Can I tell SourceX how much data a client has?

Only what the CEO approves, at metadata level: the system, record types, years and a rough volume you already know from your work. Do not run searches, reports or eDiscovery cases to measure it for a referral.

What if the client later asks us to run the export?

That is service work under the client's written instruction, after it has signed with SourceX and approved the scope. SourceX's Microsoft 365 guidance has the company run or direct the export itself, and admin logins are not shared.

Do our own MSP records count?

Your own tickets, runbooks and project documents are your company's records, so your CEO decides. The MSP records page explains which ones fit and why client-owned environment data stays out.

Sources

  1. csrc.nist.gov/CSRC/media/Projects/risk-management/800-53 D…
  2. learn.microsoft.com/en-us/partner-center/customers/gdap-introduc…
  3. learn.microsoft.com/en-us/purview/edisc-ref-audit-log
  4. refer.sourcex.si/terms
  5. refer.sourcex.si/who-qualifies
  6. sourcex.si/export/microsoft-365
  7. cisa.gov/news-events/cybersecurity-advisories/aa22-131a

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment