A sale and an introduction run in opposite directions
Most enterprise sellers learned referrals from co-selling. Microsoft's partner documentation, for one, describes co-selling as working jointly with Microsoft sales teams and partners on customer deals, sharing leads and opportunities through a referrals workspace, with connectors that let sellers create and update co-sell referrals from their own CRM (our paraphrase of its co-sell overview). In that motion the customer is the buyer, and a referral is a purchase opportunity that two sellers share.
A SourceX introduction runs the other way. The customer becomes the supplier: it licenses selected records to SourceX under its own Master Supplier Licensing Agreement and Dataset Deal Confirmation, approves scope and terms before any data moves, and is paid by SourceX. The corporate buys nothing and sells nothing. At most it is the partner of record that passed on one CEO's request. Procurement access, a large contract or an equity stake gives the corporate no authority over a customer's records; the customer's CEO decides, and once a customer has been acquired, the acquirer's CEO does.
Every account therefore holds three roles that the training keeps apart:
- The corporate, as partner of record. The legal person named in the signed SourceX Channel Partner Agreement, usually reached through the venture or platform team that owns the program.
- The vendor relationship. The account seller and the account plan: renewals, pricing, support and disputes. It carries the corporate's commercial weight, which is exactly why it must not carry the ask.
- The operating company. The customer, whose CEO decides whether to talk and later signs with SourceX.
SourceX sits outside all three. It reviews the company, signs with it and pays it. The partner agreement's section 7.1 adds that a partner is not SourceX's agent and may not commit SourceX to prices, licenses or payouts, so a seller who quotes a number is speaking for nobody. The referral partner versus sales rep comparison covers the same split for independent partners.
The sales-team boundary training card
The card has two parts. The first translates habits that make a good seller into the rule that replaces each one for a SourceX introduction.
| Selling habit | Why it misfires here | Rule on the card |
|---|---|---|
| Log it in the CRM as an opportunity | It puts a customer's possible interest in licensing its records where the whole account team can read it | Log nothing about the customer until its CEO says yes in writing; the program owner keeps that note outside the account plan |
| Raise it with the renewal or a discount | It ties a decision about the customer's own records to its contract with you | Never in the same meeting, email or quarter as pricing, a renewal, a tender or a dispute |
| Qualify the account | Headcount, systems and record counts are the company's to describe, and partners never handle its records | Point the CEO to the published criteria and the company fit checker; the company describes itself to SourceX if it applies |
| Promise the outcome | Section 4.6 bars presenting an estimate, interest, a signature or an upload as a sure purchase or reward, and SourceX publishes no typical payouts | Say "SourceX decides after its own review", and stop there |
| Speak for the vendor | A partner is not SourceX's agent and cannot speak to its prices or terms | Send SourceX's public pages, never your own summary of a deal |
| Go to whoever picks up | Your usual contact may run IT, operations or purchasing, but only the CEO decides | Ask your contact only whether the CEO would want to hear about it |
| Chase to close | Pressure from a supplier reads as a condition of the relationship | One mention, one follow-up at most; a no closes it for that account |
The second part is what each seller actually carries, four lines long:
- Say: "We are a referral partner of SourceX, which licenses operating records from established companies for AI training and evaluation. If your CEO ever wants to look into it, I can pass on a request. It has nothing to do with our contract."
- Disclose: "If your company licenses records after we introduce it, SourceX may pay us a referral reward. It comes from SourceX and is never taken out of what your company is paid."
- Hand off: a CEO's written yes goes to the named program owner the same day, with nothing else about the customer attached.
- Stop when: a renewal, tender or dispute is open; anyone offers a file, sample or login; the customer asks whether this affects pricing; the CEO says no.
Before the "Say" line is used in anything public, such as a webinar slide or a customer newsletter, check it against section 4.5 of the agreement, which bars either side from publicly identifying the other as a partner without written authorization. The co-branding permission audit runs that check.
Map internal and company approvals
Seven approvals, in the order they are needed. The first five sit inside the corporate; the last two belong to the customer alone.
| Approval | Who gives it | Needed before | Evidence kept |
|---|---|---|---|
| The corporate takes part at all | The executive sponsor of the venture or platform team, with legal and compliance | Any training | A dated decision naming the program owner |
| Signing the partner agreement | An officer who can bind the corporate | Any introduction, under section 1 of the terms | The signed agreement and the signer's authority |
| Sellers may mention the program | Sales leadership | Training | A written rule that mentions earn no quota or sales credit and stay out of account plans |
| The words sellers use, disclosure included | Legal or compliance | The first mention | The approved card, with a version number |
| A mention to one customer | That account's owner | Each mention | A dated note, outside the CRM opportunity record |
| The company talks to SourceX | The customer's CEO | Any introduction | The CEO's written request, for that one company |
| The company licenses anything | The customer's CEO, in the company's own agreements with SourceX | Any data leaving the company | Nothing the corporate sees |
Three facts change none of the rows. If the customer belongs to a corporate group, the group shares one reward cap, whichever entity licenses. If the corporate holds a stake in the customer, the stake gives it no say. And if the customer has already applied to SourceX, held an account or simply exchanged email with it, section 3 of the terms makes it a duplicate, and no introduction is credited. Who inside a venture unit should be the named owner is settled in the relationship-owner RACI.
Train once, then pilot on a few accounts
Run a 30-minute session: walk through both parts of the card, then work the five scenarios below and have each seller name the stop list from memory. Then pilot with three to five sellers who volunteer, each choosing no more than two accounts where they know the CEO and nothing commercial is open. Over 90 days, count customers who asked whether it affected their contract (the target is zero), any mention that reached the CRM, CEO requests, declines and complaints to the account team. One customer who links the program to pricing pauses the pilot for review. SourceX has not published conversion figures, and the pilot's counts are too small to be rates; report them as counts. For a corporate that wants to tell its whole customer base at once, the targeted opt-in pilot is the safer design.
Five scenarios for the session (Illustrative)
Illustrative. Invented accounts and people.
| Scenario | Answer from the card |
|---|---|
| A customer's CFO raises data licensing in the middle of renewal talks | Park it: finish the renewal, then offer to pass a request from the CEO to the program owner |
| A seller wants to tell a CEO "you would definitely qualify" | No: SourceX decides after its own review; point to the published criteria |
| A customer offers a sample export so the seller can "take a look" | Decline: no files, samples or logins; the company describes its records to SourceX itself |
| A seller asks whether they personally earn anything | Any reward goes to the partner of record named in the agreement; whether any of it reaches staff is the corporate's policy, set before training |
| A customer the corporate partly owns asks whether the corporate must approve | No: the stake gives the corporate no say; the customer's CEO decides |
Where the card can fail
- Commercial weight. Even one careful mention from a supplier can feel like a condition. No published data measures how customers react; the pilot's first count is there to test it.
- Rights. A customer's most visible records may belong to its own clients, and SourceX's screening page lists client-owned material among cases that are usually not a fit.
- Earlier licensing. Records already licensed for AI training are out: on SourceX's process page, the company confirms its data has not been licensed for that purpose before.
- Demand. Relevance to SourceX's current data needs is checked in review, so a well-run mention can still end in a decline.
- Duplicates. A customer that has already corresponded with SourceX cannot be credited to anyone later.
- Incentives inside the corporate. If sellers are paid for mentions, the card cannot remove the pressure that creates. The approval map puts that decision before training for this reason.
Method note. The card and the approval map apply the program terms (Version 2026-10-22.2, since replaced by version 2026-11-04), the partner agreement sample (version 2026-10-19, sections 4.2, 4.5, 4.6 and 7.1), SourceX's screening and process pages and Microsoft's co-sell overview, all checked 2026-10-27. Nothing here measures customer reactions, how often mentions become requests, or any reward; none of those figures has been published.
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 approval map is signed off and the card has a version number, register the corporate as the partner, give every trained seller the published bar on who qualifies, and keep the program terms version with the card.
Training sellers on the referral role is one decision; judging whether SourceX is worth backing as a company is another, and readers weighing the second can ask for materials on the SourceX investor page.
This article is for information only and is not an offer to sell or a solicitation of an offer to buy securities. Any offering by SourceX is made only to verified accredited investors through its offering documents.