# Multiple IT providers, one data referral: the map | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-handle-a-client-with-several-it-providers
Last updated: 2026-11-05

Treat it as one company with one decision-maker and several custodians. The MSP, the ERP partner, the hosting provider and the security firm each run a slice of the client's systems; none of them owns the records, none can license them, and none should compare notes with the others to piece together a picture of the client's data. Ask the client's CEO whether she wants a conversation with SourceX, let her name one provider to make the introduction, or none, and leave every other provider's work untouched.

Mid-sized companies rarely have one IT supplier. Two firms knowing the same customer is covered in [reseller and SaaS vendor overlaps](/guides/when-a-reseller-and-a-saas-vendor-both-know-the-customer), and a workflow spread across several internal owners in [cross-system workflow histories](/guides/cross-system-workflow-histories-one-introduction-several-owners). This page is about the provider estate itself: four or five outside firms, each with keys to part of the house.

## Four providers, one estate, no shared view

A typical estate at a 250-person company might look like this. An MSP runs the help desk, laptops and identity. An ERP partner configures and supports the finance and operations system. A hosting provider keeps servers and backups. A security firm watches the logs. A line-of-business software vendor holds the CRM.

Each provider's access was granted for its own scope. Microsoft's granular delegated admin privileges show how that works in one large ecosystem: partners get least-privileged access, which the customer must explicitly grant, following a Zero Trust approach, and they request specific administrative roles for a definite period (paraphrase of Microsoft's GDAP documentation). Whatever the platform, the result is the same. Every provider sees its slice through a role the client approved, and no provider sees the whole.

That is not a gap the referral needs to fill. The client is the only party that holds the full map of its systems, and the only one entitled to describe it. SourceX's own first step asks the company to list its systems, years of history and what can be exported, with no files and no records shared, and SourceX then checks fit, completes the inventory with the company and runs the rights check. Nothing in that process asks a provider for anything.

## Moments when several providers notice the same history

Provider estates change, and the changes are when years of history come into view, often for more than one provider at once:

- **A provider transition.** The client replaces its MSP or its host, and the outgoing and incoming firms both handle the cutover.
- **Consolidation.** Several tools are folded into one platform, and the old ones are set to read-only.
- **An ERP upgrade.** The old system is kept for reference, with a retirement date someone has to choose.
- **A hosting contract ending.** The archive on the old servers needs a decision: move it, keep it or delete it.
- **The client is acquired.** Every provider hears about it, and from closing the acquirer's CEO decides for the company.

Inside the client, the person who hears about these events is usually the IT manager, or the CFO who signs the provider contracts. Either can sponsor a conversation internally. Neither replaces the CEO, who decides whether the company discusses licensing at all.

Timing deserves care when providers are changing. An outgoing provider that raises data licensing during its own exit can sound like a parting sales pitch, and an incoming one like it is reaching past its brief. Let the client choose the moment, and if the answer is "after the cutover," treat it the way [a 'not now' from an owner](/guides/how-to-handle-not-now-objection) is treated: agree the trigger and step back.

## The provider-owner coordination map

The map is one table the client keeps, with one row per system. Providers contribute only to their own row, and only what the client asks of them.

| Column | What goes in it |
|---|---|
| System | The client's name for it: "ERP", "help desk", "file servers" |
| Provider that runs it | The custodian, with the scope of its contract in a few words |
| Owner inside the client | The person who decides how the system is used day to day |
| What the provider may tell the client, if asked | Only metadata about its own system: what it is, since when, roughly how much. It stays with the client; the introduction carries the CEO's words |
| Has this provider mentioned SourceX? | Yes, with the date, or no; this is what prevents duplicate approaches |
| Introducer | One line for the whole map: the provider the CEO named, or "none, the company applies itself" |

Four rules keep the map safe to use:

1. **The client fills it in or confirms it.** Providers do not compile it from their consoles.
2. **Each provider sees its own row.** The whole map stays with the client.
3. **Providers do not compare notes.** Nobody pools what they know about the client's systems for a referral, in a joint call or in a shared document.
4. **The map ends in one name.** The CEO picks the introducer, or picks none.

An Illustrative map for a 260-person building products distributor:

| System | Provider that runs it | Owner inside the client | What the provider may tell the client, if asked | Has it mentioned SourceX? |
|---|---|---|---|---|
| ERP, in use since 2011 | ERP partner, configuration and support | CFO | Which modules, since when, that the old instance goes read-only next spring | No |
| Help desk and laptops | MSP, managed services contract | IT manager | That the ticket system dates from 2014 | Yes, at the last quarterly review |
| File servers and backups | Hosting provider, infrastructure contract | IT manager | Nothing yet; the client has not asked | No |
| Security monitoring | Security firm, monitoring contract | IT manager | Not part of this conversation | No |
| CRM | Software vendor, subscription | VP of sales | Not part of this conversation | No |

Introducer: the MSP, named by the CEO in writing. The map itself holds no record counts, no storage figures and no screenshots, and it never leaves the client.

## Every provider's keys, contract and limits

Holding admin access, a service contract and a referral relationship are three different positions, and a provider can be in all three for one client.

- **Keys.** Delegated access covers the provider's scope and nothing else. Using it to measure the client's records for a referral turns a service credential into something the client never approved. The [question about MSPs and admin credentials](/questions/msp-wont-give-admin-credentials) looks at the same boundary from the client's side.
- **Contract.** Each statement of work describes service duties. A licensing introduction is not one of them, so it sits outside the invoice and the client should hear that the introducer may receive a reward; the [MSP disclosure answer](/questions/msp-vendor-referral-fees-disclosure) covers the wording.
- **Licensing authority.** The CEO decides whether to talk; SourceX's rights review decides what can be licensed. The partner agreement gives a partner no authority to share a company's inventory, records, raw data or personal information, or to reach its extraction systems, and SourceX sets the processing route in the company's own deal. No provider is drafted into extraction by making an introduction.

Ticket data held by an MSP raises its own questions about whose records they are, covered in [whether an MSP can share client ticket data](/questions/can-msp-share-client-ticket-data). Records that belong to the client's own customers are usually not a fit in any case.

## Two providers, one company, one credit

When more than one provider wants to make the introduction, the program's answer is simple and the coordination is not. Credit goes to one partner per company, the one holding the first valid introduction on record, and only if the company, unknown to SourceX until then, files a verified application within 90 days. SourceX reads that order from dated records. Where two providers both submit, SourceX works out the overlap in duplicate review, and nothing in the terms ranks providers by contract size, tenure or who noticed first.

So do not race. Before raising SourceX, a provider asks the client one question: has anyone else already mentioned it? If the answer is yes, that provider stands down unless the CEO asks otherwise. If the company itself has ever applied to SourceX, or exchanged leads, accounts or emails with it, it is a duplicate under section 3 and no partner is credited. When the client belongs to a group, whether the parent and a subsidiary count as one referred company, whose first qualifying transaction alone carries the USD 50,000 floor, and how an earlier introduction of a sister company bears on credit are matters SourceX settles in duplicate review.

## A distributor with five IT providers (Illustrative)

Illustrative: the distributor from the map, with invented facts and no outcome implied.

The ERP partner learns during upgrade planning that the old ERP instance, with fifteen years of orders, returns and supplier claims, will go read-only next spring. Its consultant asks the CFO whether the CEO would want to hear about licensing that history. The CFO checks with the IT manager, who says the MSP mentioned SourceX at the last quarterly review.

The CFO takes both facts to the CEO. She wants the conversation and names the MSP to make the introduction, because its account manager raised it first and she already speaks to him monthly. She asks the ERP partner to stand down, and the ERP partner does, offering to answer her questions about the old system's history if she ever asks. The hosting provider and the security firm are never involved.

The MSP writes one introduction carrying the CEO's own description: an ERP in use since 2011, the order, return and claims history it holds, and the read-only date. If the distributor's eventual deal paid it $40,000, it would fall below the USD 100,000 Minimum Transaction and pay the MSP no reward unless SourceX agreed in writing; if it paid USD 200,000, the MSP's reward would be USD 60,000 (the greater of USD 50,000 plus 5% and 15%), paid by SourceX and never subtracted from what the distributor signed for; the ERP partner would receive nothing from SourceX. All figures are Illustrative.

## The introduction note with nothing from anyone's console

The note names the introducer and its relationship to the company, says the CEO asked for the introduction, gives the CEO's description of the records and any limits she set, and says SourceX may contact the company directly, which the terms allow without affecting attribution.

It leaves out console screenshots, storage or ticket counts, anything another provider said about its own systems, and any view on what the records might be worth. Fit is the CEO's to describe: a full-time workforce that peaked at 50 or more, contractors excluded; years of its own operating records; authority to license what it produced; and her own interest in the conversation. 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.

## Where the coordination map falls short

- **Contracts can restrict talk.** A provider's agreement may limit what it says about the client, or about other suppliers, even to the client's own staff. Read it first; this page is not legal advice.
- **Rivalry.** Providers competing for more of the account may treat the introduction as a prize. The map cannot stop that; the CEO's written choice can at least make it visible.
- **The sponsor may hold back.** An IT manager who would rather the CEO did not hear about it can stall the map. The program still needs the CEO's own yes.
- **Hidden earlier contact.** Only SourceX can see whether the company has already been in touch with it.
- **Demand and rights.** Whether the records suit SourceX's current data needs, and whether customer contracts restrict them, is settled in SourceX's review.

## 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 the CEO names you as the one provider to make the introduction, [set up your partner account](/register), run the company past the [screening criteria](/who-qualifies) and read the attribution and duplicate sections of the [program terms](/terms) before you write; the [guides library](/guides) holds more partner playbooks.

## Sources

- https://refer.sourcex.si/who-qualifies
- https://refer.sourcex.si/terms
- https://learn.microsoft.com/en-us/partner-center/customers/gdap-introduction
- https://learn.microsoft.com/en-us/graph/api/resources/delegatedadminrelationships-api-overview?view=graph-rest-1.0
- https://sourcex.si/how-it-works
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
