Where client introductions fit in a CSP practice
Most CSP revenue comes from three places: margin on Microsoft subscriptions, managed services layered on the tenant, and projects such as migrations, security hardening and Copilot readiness. A SourceX introduction is a fourth, occasional source.
The fit comes from what you administer. Exchange Online mailboxes, inactive mailboxes kept for departed staff, Teams chats and channel conversations, SharePoint and OneDrive libraries with version history, Planner boards and often Dynamics 365: together they record years of how a company actually worked. AI developers building agents need exactly that kind of material, showing how requests moved between people, what was decided and what happened next. Researchers at Epoch AI have projected that, if current trends continue, language models will fully use the stock of public human-written text sometime between 2026 and 2032, a forecast with wide uncertainty, which is why permissioned, non-public records draw attention.
The client licenses; you introduce. That division is the whole model, and the next section explains why it is not optional.
Why tenant admin rights never equal authority to license
Whether you hold granular delegated admin roles or a break-glass global admin account, your access exists to run the services you were hired for. It gives you no say over what the company does with its records.
| What your admin role can do technically | What it does not authorize | Who decides |
|---|---|---|
| Run content searches and eDiscovery across mailboxes | Reviewing content for any purpose outside your service scope | The client's legal or compliance owner |
| Export mailboxes, Teams data or SharePoint libraries | Sending any record to a third party, SourceX included | The owner, CEO, CFO or authorized representative, under a signed agreement |
| Change retention policies and holds | Deleting history the client may want to license or must preserve | The client, ideally with its counsel |
| See tenant age, storage use and active users | Describing the client's records to anyone outside the engagement | The client |
| Assign licenses and manage accounts | Representing the company in a licensing decision | The company's authorized sponsor |
Your services agreement with the client and the Microsoft partner terms you operate under define what you may do with tenant access, and a data license sits outside both. So the partner role stays narrow: notice, ask, introduce. With the client's permission you can pass along basic fit information such as approximate headcount and years in operation. Everything else comes from the client.
Which CSP clients fit
| Signal | What to look for in the tenant | Why it matters to buyers |
|---|---|---|
| People, not seats | 50+ full-time employees at peak, contractors excluded | Enough people working together create connected records |
| Tenant age | A tenant running for many years, or on-premises Exchange history and PST archives migrated in | Longer histories show how work and decisions changed |
| Teams and SharePoint depth | Active project channels and document libraries with version history | Threads and drafts show reasoning, not just final documents |
| Departed staff mailboxes | Inactive or converted mailboxes kept for former employees | Decisions made by people who have left often survive only there |
| Line-of-business systems | Dynamics 365, a CRM, a ticketing tool or an ERP alongside Microsoft 365 | Workflows that cross systems are the most useful to agent builders |
| Ownership | Content created by the company's own staff for its own work | Material held for the company's clients usually cannot be licensed |
Seat counts mislead. Shared mailboxes, room and service accounts and contractor licenses inflate the user list, so the page on Microsoft 365 seats versus full-time employees explains how to get the real number.
The tenant-depth screen
Five questions, answerable from what you already know about the client without opening any content.
- ☐History: do the tenant and any migrated archives cover several years of operations?
- ☐Breadth: are mail, Teams and SharePoint in real daily use, plus at least a few line-of-business systems?
- ☐Retention: have retention settings kept history, or have auto-delete rules removed it?
- ☐Ownership: was the content created by the company's own staff for its own operations?
- ☐Sponsor: can you reach the owner, CEO or CFO, not only the IT contact?
Four yeses is a good reason to raise it. The who qualifies page covers the full baseline, and the network opportunity finder helps you sort a client list.
When to raise it in the CSP year
| Moment | Why it works | What to ask the client |
|---|---|---|
| Copilot readiness or data governance assessment | You are already mapping where data lives and who can see it | Beyond Copilot, has anyone looked at this history as an asset? |
| Annual subscription renewal and license review | Cost and usage are on the agenda | Which archives are you paying to keep, and why? |
| Former employee mailbox cleanup | Inactive mailboxes are being reviewed to cut cost | Before anything is deleted, do you want to know whether this history has value? |
| Tenant-to-tenant migration after an acquisition | Two companies' histories are being merged or retired | What happens to the acquired company's mail and files after cutover? |
| File server to SharePoint migration | Decades of shared drives are being sorted | Are the oldest folders going to be migrated, archived or deleted? |
Mailbox cleanup deserves care: the page on former employee email accounts walks through the keep, archive or delete decision.
How an introduction moves from you to SourceX
- You register and either send the owner your referral link or submit the company with the referral form.
- SourceX confirms fit with the company's sponsor: headcount, years of operation, range of systems and rights.
- The company itself describes its systems and the years they cover in a data inventory; no records move at this stage.
- SourceX and the company settle one net payout and the license terms, and the company is free to walk away until it signs.
- Interested AI labs and data buyers evaluate what is on offer.
- After signing, SourceX manages data preparation and delivery under the company's agreed de-identification and redaction rules, subject to acceptance at Closing and agreed terms. 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.
What to say to the owner
"During the Copilot work we mapped how much history sits in your mail, Teams and SharePoint. Some companies now license records like that to SourceX for a one-time payment, keeping ownership and approving exactly what is included. SourceX is your direct licensing partner and manages the agreement, rights review, data preparation, delivery and payout, subject to acceptance at Closing and agreed terms. Would you like an introduction to see if you qualify?"
Ready-to-edit wording for a follow-up email is in the client introduction email templates.
How rewards work for CSP partners
Partners earn the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap. Actual Supplier Payout is the eligible licensing compensation SourceX actually pays the referred company, excluding separately itemized taxes and expense reimbursements. The USD 50,000 floor applies once per referred company, to its first qualifying transaction; each further qualifying transaction first agreed within 12 months of that first Closing pays 15% of its Actual Supplier Payout, and a transaction qualifies when its Actual Supplier Payout is at least USD 100,000 unless SourceX agrees otherwise in writing. All of this is 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. An introduction, a meeting or even a signed license does not trigger a reward on its own, and rewards are not guaranteed. SourceX funds rewards separately, so they do not reduce the client's payout.
Tell the client you are paid for the introduction, and check your own customer agreements and Microsoft partner terms for anything that limits outside referral arrangements. If you also implement business applications, the Dynamics 365 partner page covers ERP and CRM history in more depth.
When not to bother
- The tenant belongs to a small holding company, or the operating business falls short of 50+ full-time employees at peak (contractors excluded).
- Most content belongs to the client's own clients, as at agencies and many professional firms bound by client confidentiality.
- Aggressive retention settings have already deleted most history.
- The client is a clinic or health business whose records are mainly patient information.
- Your only contact is an office manager with no route to the owner.
Next step
At your next renewal or Copilot assessment, run the tenant-depth screen on that client. If it clears, register as a partner and make the introduction to the owner, never through the tenant.