The situation covers hosting providers, managed service providers running a shared platform, resellers of a hosted system and anyone holding admin rights across many customers' environments. The temptation is the same in each: the vendor can see, at a glance, which tenants have deep histories. This page draws the line between seeing and deciding.
Pooled infrastructure, separate owners
NIST's definition of cloud computing describes resource pooling in one sentence: "The provider's computing resources are pooled to serve multiple consumers using a multi-tenant model." The same definition notes that the customer generally has no control or knowledge over the exact location of the provided resources. What is pooled is the machinery. Microsoft's shared responsibility page draws the other half of the picture: whatever the deployment type, the customer always keeps responsibility for its data, its endpoints, its accounts and its access management (paraphrase).
Put those together and a hosting vendor is a custodian of shared machinery holding many separate owners' records. SourceX's screening guidance looks at the same split from the licensing side. A company needs the right to license what it offers: the material has to be its own, or licensable without breaking a duty it owes clients, staff or a contract partner. Material that belongs to a company's clients rather than the company is usually not a fit. From the vendor's seat, every tenant's contents are its clients' material. The vendor cannot license them, and it cannot speak for the client that can.
The system events that put a tenant in view
A vendor usually learns that a client's history is in play through the service itself, not by looking. These are the common moments, what the vendor sees without opening anything, and whose decision follows.
| Event | What the vendor sees without opening contents | Who inside the client may sponsor | Who decides | A question for the client |
|---|---|---|---|---|
| Tenant leaving the platform | A cutover plan or an export request ticket | IT director or COO | The client's CEO | Will the history move with you, or stay behind and expire? |
| Platform end of life | The vendor's own sunset notice | Operations lead | The client's CEO | Which years do you still need, and who chooses? |
| Shorter retention or a cheaper storage tier | A change request | Controller or records owner | The client's CEO | What happens to records older than the new limit? |
| The client is acquired | A request to merge tenants | Integration lead | Before closing the target's CEO; after closing the acquirer's CEO | Which company's records are these now? |
| Contract renewal | A renewal quote | CFO | The client's CEO | Is the archive part of what you are renewing? |
Service metadata of this kind is enough to know a conversation might be timely. It is not permission to open a tenant's contents to size the opportunity. When records change hands in an acquisition, the tenant control and data ownership worksheet separates the two questions in detail.
The tenant-owner boundary map
Three parties, six questions. Read down a column to see one party's whole role; read across a row to see where a responsibility sits.
| Question | Technical custodian (the vendor) | Tenant owner (the client company) | SourceX |
|---|---|---|---|
| What does it hold? | Infrastructure, backups and the admin credentials it was issued | The records, and whatever rights it has to them | Nothing from the referral |
| What does it decide? | How the platform runs, within the service contract | Whether to discuss licensing, what is in scope, who acts for it | Whether the company and its records fit a current program, and on what terms |
| Who signs for it? | The vendor's own officers, for the vendor's own business | The client's CEO | SourceX |
| What may it say in an introduction? | That it serves the client, plus what the client asked it to pass on | Anything about its own records | Its published process and terms |
| What does it never do? | Open, export, sample or count tenant contents for a referral | Let a vendor speak for it in place of its own decision | Treat the vendor's word as the client's yes |
| Which papers govern it? | The client's service agreement; the Channel Partner Agreement for the referral | Its own contracts with customers and staff | A Master Supplier Licensing Agreement and Dataset Deal Confirmation signed with the client |
A vendor's platform usually carries three record families, and each points to a different introduction or none:
| Record family | Whose it is | Introduce whom | Unknown until SourceX reviews it |
|---|---|---|---|
| Tenant contents: each client's documents, tickets and transactions | That client | The client's CEO, if she wants it | Rights, customer contract limits, fit with a current program |
| The vendor's own operating records: runbooks, change logs, its own service history | The vendor | The vendor's own CEO, with the vendor as the company | Whether those records mention clients in ways contracts restrict |
| Mixed records, such as tickets describing a client's problems | Contested | Nobody, until the question goes to SourceX's rights review | Almost everything |
The second row is easy to overlook: a vendor with 50 or more full-time employees at its peak and years of its own operating history may be the company worth introducing. What service desk histories look like as a data type is described on the MSP ticket and time-entry page.
Admin rights, the service contract and the power to license
These are three different permissions, and holding the first two gives none of the third.
- Admin access is technical ability, issued by the client so the vendor can run the service. On Microsoft's account of shared responsibility, access management stays the customer's job even when the vendor holds the keys.
- The service duty is what the service agreement asks the vendor to do. A licensing introduction is not part of it; it is a separate relationship under a separate agreement, and clients deserve to hear that you may earn a reward. The MSP disclosure guide covers that conversation.
- Licensing authority belongs to the client's CEO, and whether the records can be licensed at all is settled in SourceX's rights review. The partner agreement gives a partner no authority to share a company's inventory, records, raw data or personal information, or to access extraction systems (4.2). It bars collecting or keeping dataset copies through the referral program without separate written authorization (4.4), and a partner is not SourceX's agent and cannot commit SourceX to prices, licenses or payouts (7.1).
One tenant, one company, one introduction
Every client on the platform is screened as its own company: 50 or more full-time employees at peak with contractors left out, documented operating history, rights to license, and a CEO who agrees. Each has its own 90-day attribution window, its own duplicate check and its own verified application. One partner is credited per company, so a client already introduced by its accountant is a duplicate when the vendor arrives second, and a client that once emailed SourceX is a duplicate for everyone.
Groups need one more rule. There is no cap on rewards, per company or per group, but the USD 50,000 floor applies once per referred company, to its first qualifying transaction, and not again on a repeat, renewal or amendment. Illustrative only: if SourceX credited one group company to the partner and its first qualifying transaction paid USD 500,000, the reward would be USD 75,000, and that company's floor would not apply again to its later transactions. Whether an earlier introduction of one group company changes the credit for its sister is not answered by the terms; SourceX works that out in duplicate review. The subsidiaries guide goes further into group structures.
Introducing a tenant's CEO with the client's facts, not yours
- Ask first. Through the client's sponsor or directly, ask the CEO whether she wants a conversation about licensing records her company created. Say that you may receive a reward if she goes ahead.
- Let the client describe the records. Record types, years covered, systems and rough volume, in the client's words. Never figures read off a console you administer.
- Write a short introduction. Who you are, that you host a system for the company, the CEO's own description, and nothing attached.
- Step back. SourceX may deal with the company directly without affecting valid attribution, so the vendor's part ends with the introduction.
An Illustrative screen of four tenants on a 70-person hosting provider's document management platform:
| Tenant (Illustrative) | What the vendor knows from running the service | Verdict | Reason |
|---|---|---|---|
| 320-person civil engineering firm | A May cutover ticket; the COO asked how far back project files go | Ask the CEO, through the COO | Its own project records, a dated event and a reachable CEO |
| Bookkeeping practice whose full-time staff peaked at 44 | A renewal quote | Do not raise it | Its peak full-time headcount never reached 50 |
| 260-person logistics subsidiary whose parent is also a tenant | One group administrator for both tenants | Raise it once, with the subsidiary's CEO, and note the once-per-company floor | Credit between sister companies is SourceX's call |
| 150-person claims administrator | Support tickets show it stores files for insurer clients | Do not pitch it as a fit; its CEO may still ask SourceX | Material belonging to its clients is usually not a fit |
What the boundary map cannot settle
The map shows roles, not contract terms. A service agreement may restrict what you can say about a client at all, even its name, so read yours before you raise anything. A client's own contracts with its customers decide much of what it may license, and only SourceX's review reaches those. And demand moves: a tenant that fits today's programs may not fit next year's, and the reverse. For the wider screen of which clients deserve a conversation, see how MSPs recognize suitable client businesses, the managed service provider overview and the parallel screen for staffing firms' business 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.
Pick the one tenant whose CEO has already raised the company's records with you, introduce that company on its own in the CEO's words, and leave every other tenant's contents untouched; register as a partner first, then check that client against who qualifies and the attribution sections of the program terms. The guides hub has more partner playbooks.