This page is for the overlap itself: a software vendor and the reseller, implementer or managed service provider that sells or supports its product, both serving one customer company. If you are only deciding whether a SourceX introduction is a referral or a resale, the referral partner versus reseller comparison settles that first: a data licensing introduction is always a referral, because nothing is resold.
Two relationships, one customer, one introduction
The reseller usually holds the commercial paper: the order, the invoice, the first call when something breaks. The vendor holds the product relationship: the platform, the customer success manager, the roadmap calls. Each firm can believe, honestly, that it "owns" the customer. For a SourceX introduction, neither ownership claim matters as much as two program rules.
| Rule in the program terms | What it means when two firms know the customer |
|---|---|
| Credit belongs to whichever valid introduction of a new company lands first in the 90-day attribution window, provided that company goes on to submit a verified application | A race to send links first is the default outcome if nobody talks |
| Only one partner is credited per company | Two firms cannot both be paid for one customer |
| Attribution is decided from dated records, and an earlier link click alone does not decide credit | Written introduction evidence matters more than who clicked first |
| A company with an earlier lead, account or email with SourceX is a duplicate and not credited | If the customer had already contacted SourceX, neither firm is credited |
Established software ecosystems already handle overlapping partners this way. Microsoft's Partner Center, for instance, lets a partner invite another partner onto a co-sell deal with notes on why it is inviting them and what help it needs, and for IP co-sell deal registration it says only the partner that owns the end-customer contract with the included solutions should register the deal. The lesson carries over even though a SourceX introduction has no joint sale: settle who registers before the customer sees two pitches. The live note on two partners introducing the same company covers what happens when that conversation never takes place, and written introductions versus link attribution explains why the written record carries weight.
What the customer gains, and which of its people decides
The introduction is worth making only if the customer would want it. What it offers the customer is specific: a conversation about licensing its own operating records directly to SourceX, which pays the company under its own agreement. SourceX pays any referral reward separately and never deducts it from the company's compensation. The fit facts are SourceX's published baseline: roughly 50 or more full-time employees at peak, several years in operation, original records the company created and rights to license them.
The person who decides is rarely the person either firm talks to. The reseller's contact is often in IT or procurement; the vendor's is the product administrator or an operations champion. Under the program, the customer's CEO is the one who can authorize a licensing discussion and sign. So the real question between the two firms is not who knows the customer best, but whose contact can ask the CEO and be heard. However warm either firm's path, SourceX's screening usually counts an introduction the CEO knows nothing about as not a fit.
The customer relationship coordination protocol
Seven steps, in order. Steps 1 to 5 happen between the two firms and involve no customer contact.
| Step | Who acts | What gets written down | What must not happen |
|---|---|---|---|
| 1. Notice the overlap | Whichever firm spots it | The date, who noticed, and the conversation it came from | Picking the customer from usage data, admin consoles or support tickets |
| 2. Check each firm's contracts | Each firm, separately | Whether its customer agreement limits promotional outreach, and whether the reseller agreement limits the vendor's direct contact with the reseller's customers | Assuming the other firm's contract allows what yours does |
| 3. Check what already exists | Each firm, in its own partner dashboard | Whether either firm already shared a link or submitted the customer | Sending a link "just in case" while you talk |
| 4. Name one lead introducer | Both firms, in writing | The firm whose contact can ask the CEO, and the date agreed | Leaving it to whoever moves first |
| 5. Agree the other firm's role | Both firms, in writing | That it sends nothing about SourceX, refers questions to the lead and asks the customer nothing about progress | A side promise neither firm has checked against its partner agreement |
| 6. One message to the CEO | The lead introducer, through the contact who can ask | That both firms' roles and any referral interest were disclosed, and the CEO's answer | Two messages, or a message that hides who may be paid |
| 7. The customer applies itself | The customer | The date the CEO said yes and the introduction evidence | Either firm handling, describing or moving the customer's records |
Step 4 needs a tie-break the two firms agree before they ever disagree. Ours, in order: the firm whose contact already has the CEO's ear; then the firm whose customer contract clearly permits the outreach; then the firm the customer has trusted with sensitive conversations before. If neither firm has a path to the CEO, the answer is to wait, not to cold-email.
Step 5 covers money as well as messages. The program terms describe one credited partner per company and say nothing about dividing a reward between firms. Whatever the two firms agree between themselves is their own contract, outside the program; read your SourceX Channel Partner Agreement, which each firm signs before submitting introductions, before relying on one.
Step 6 is a disclosure as much as an introduction. The FTC's Endorsement Guides require a connection that might materially affect the weight of an endorsement, including the possibility of being paid, to be disclosed clearly and conspicuously when the audience would not expect it. A customer hearing about SourceX from its software supplier would not assume a reward is involved, so say so, and say it once: "We may receive a referral reward from SourceX if you license data with them; it is paid by SourceX and never comes out of your payment." The referral fee disclosure question has more wording.
Method note. The protocol was built on 2026-10-26 from SourceX's program terms (Version 2026-10-22.2, since replaced by version 2026-11-04) and screening page, Microsoft's Partner Center co-sell documentation and 16 CFR 255.5. The tie-break order is our design. Nothing here measures how often shared customers accept, how often duplicate review occurs or how customers react to coordinated outreach; SourceX has not published those figures.
Why neither firm may mine the product to choose customers
The vendor hosts the customer's records and the reseller may hold delegated admin rights to the same tenant. Both can see usage dashboards. None of that is the customer's permission. The customer owns its records, contracts with SourceX directly and decides the scope; a firm that uses its access to pick targets is using the customer's data for a purpose the customer never agreed to, and may be breaching its own customer agreement.
The signal for step 1 is what the customer told a person: an operations leader mentioning ten years of service history, a CEO asking what AI companies pay for business data. If the customer raises the question of whether its software vendor already has training rights over its records, that is worth answering before anything else, because a prior grant can conflict with an exclusive license later; the live guide on whether a SaaS vendor trains AI on customer data walks through the paperwork.
Three overlaps, worked through (Illustrative)
Illustrative. Generic firms and companies, invented facts, no outcome implied.
A. The reseller has the CEO. A 160-person owner-run building-products distributor buys its ERP through a regional reseller whose founder has known the distributor's CEO for fifteen years. The vendor's customer success manager knows only the operations manager. Step 4 names the reseller. The vendor sends nothing and, when the operations manager mentions SourceX on a support call, says the reseller is the right contact.
B. One contract forbids outreach. A 300-person field-services company's agreement with the vendor restricts promotional messages; its agreement with the reseller does not. The reseller leads, after confirming its own contract. Had both contracts restricted outreach, the protocol would have stopped at step 2, with no message from either firm.
C. The race that went wrong. A 220-person logistics company heard about SourceX from the vendor's partnerships team and from the reseller's account manager in the same week, each with its own link. The CEO paused, unsure who was selling what. Credit, if any, will be settled by SourceX from dated records in duplicate review. The two firms adopted the protocol afterward; the customer relationship took longer to repair.
If case A's distributor went on to license and its Actual Supplier Payout reached $160,000, the default reward would be $58,000, paid by SourceX to the reseller as the one credited partner, and only once the payment conditions in the terms were met. Illustrative; not a forecast or a quote.
Start with five shared customers, then decide
Do not roll the protocol out across a whole partner channel at once. Pick up to five shared customers where one firm clearly has a path to the CEO and both firms' contracts permit outreach. Before the first message, agree what you will count: CEOs who said yes, CEOs who said no, any customer complaint about being approached, hours spent by each firm, and whether any case reached duplicate review. After each conversation, the lead introducer asks the CEO one question: whether the approach felt like an option or like pressure from a supplier.
Pause the pilot after any complaint about being contacted by both firms, and fix the step that failed before the next customer. A shared customer is also a shared product relationship, and keeping it is worth more than any single introduction. The SaaS data partner overview and the guides library cover the wider program.
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.
Once the two firms have named one lead introducer in writing and the customer's CEO wants the conversation, the lead firm should register for a partner link, confirm the customer against who qualifies and read the program terms before sending the single message.