# Existing licensing provider referral: 9 questions | SourceX

Canonical: https://refer.sourcex.si/guides/when-a-referral-candidate-already-works-with-another-licensing-provider
Last updated: 2026-11-04

Do not drop the company, and do not pitch over the other provider. What matters is which records the existing deal covers and what it promised about the rest. SourceX asks suppliers to confirm their data has not been licensed for AI training before, and its own licenses are exclusive for AI training, so anything already licensed for that purpose elsewhere is out. Records the other deal never touched may still be offered if its contract allows it. Ask the CEO, let counsel read the contract, and introduce only on the CEO's yes.

## What the other provider's deal rules out, and what it leaves

It rules out the records it covered and, depending on its wording, possibly more. Everything else is a question for counsel and for SourceX's rights review, not for you.

SourceX's own process page lists what a supplier confirms when it signs: that it has the rights to license the data, and that the data has not been licensed for AI training before. The same page says SourceX's licenses are exclusive for AI training and cover only the selected data, with future data and unselected records outside them. Put those together and the screening question becomes concrete. The company is not asking "can we work with two providers?" but "which of our records has nobody licensed for AI training yet, and is anything in the other contract stopping us offering them?"

The other contract can reach further than its delivered files. It may be exclusive over a whole record type, extend to data created during its term, or give the provider notice or first-refusal rights over any later deal. Under U.S. copyright law, as the Copyright Office's Circular 12 explains, an exclusive license counts as a transfer of ownership and needs a signed writing, while a nonexclusive license is not a transfer at all. Where copyright protects the records, an exclusive grant can leave the company without the right to license them again. How much protection a given set of business records has is counsel's question. Yours is only whether counsel has looked.

| Where the other relationship stands | Records it covered | Records it did not cover | What the partner does |
|---|---|---|---|
| Talks only, nothing signed | None yet | All, subject to whatever is agreed | Ask whether the CEO wants a second conversation now or after the talks end |
| Signed and delivered, non-exclusive | Out | May be offered if the contract allows | Introduce, with the excluded set stated by the company |
| Signed, exclusive over one record type | Out | Other record types, after counsel reads the scope | Wait for counsel, then decide with the CEO |
| Signed, exclusive over all data created during the term | Out | Probably out for the term | Park the row with a dated trigger counsel provides |
| Ended | Out: an earlier AI training license still counts | May be offered if nothing survives the ending | Counsel reads what survives |

## Clues, relationship paths and a referrer who may already be attached

Public clues tell you that something happened. A candidate's press release about a "data partnership", a provider's case study about an unnamed company in the same industry, or a job post for a data partnerships manager: none of them says which records were covered, whether the grant was exclusive or whether the relationship is still live.

Other providers also run their own introduction programs. micro1's company-referral page, checked on 27 October 2026, describes a referral bonus for enterprise data partnerships with its own schedule and conditions, so a candidate in talks with a provider like that may have arrived through someone else's introduction. That person's arrangement is with the other provider. SourceX decides credit under its own terms, and section 3 is about history with SourceX: "Companies that already have an application, relationship or earlier valid introduction with SourceX are reviewed as duplicates and are not credited to a later partner." Another program's referrer appears nowhere in that test. The company's own contact with SourceX does, which is why question 7 below exists; the [duplicate-claim checklist](/guides/how-to-prevent-duplicate-claims-before-they-reach-sourcex) covers that side.

The relationship path matters as much as the clue. The CEO decides whether to talk. The person who negotiated the other deal, often a COO, a data lead or general counsel, is the one who knows its scope. Ask the CEO, and let the CEO bring that person in.

## Existing-relationship screening questions

Nine questions, asked of the CEO in one conversation. Record each answer as given, with the date: yes, no, unknown, or the CEO's own words. Never ask to see the contract, and never forward it.

| # | Ask the CEO | Why it matters | An answer that stops the introduction | An answer that narrows it |
|---|---|---|---|---|
| 1 | Are you talking to, or under contract with, a company that licenses data for AI? | Sets the stage: talks, signed, delivered or ended | "We agreed not to talk to anyone else while we negotiate" | "Talks only, nothing signed" |
| 2 | Which records did that deal cover: systems, years, record types? | Defines the excluded set | "All of our operational records" | "Project correspondence from 2015 to 2022" |
| 3 | Was the license for AI training, for evaluation, or for something else? | SourceX asks for confirmation that data was never licensed for AI training | "Training, on everything we hold" | "Analytics only", which counsel still checks |
| 4 | Is the grant exclusive, and does it reach records you have not delivered yet? | Future data and whole categories are where conflicts hide | "Exclusive for everything we create during the term" | "Exclusive only for the delivered set" |
| 5 | Does that provider have first refusal, notice rights or a say over other licenses? | A second license may need its consent or a notice | "They must approve any other data deal" | "A notice after signing, nothing more" |
| 6 | Does confidentiality let you say the deal exists, and to whom? | Decides what the company can tell SourceX | "We can't disclose anything", so counsel decides first | "We can name the provider, not the terms" |
| 7 | Has anyone at the company had contact with SourceX before? | Section 3 duplicates | Not a stop for the company; a yes goes to duplicate review | "Never", recorded with the date |
| 8 | Who read the other contract, and will they read it again for this? | Counsel reads, not you | "Nobody can look at it for months", so wait | A named counsel and a rough date |
| 9 | Do you want a second conversation now, or after something finishes? | Consent and timing | "Not now", so record it and stop | "Yes, about the design review records" |

## Observed, stated or inferred

Keep the three apart in your notes. Only the middle kind, said by the CEO or someone the CEO named, can move a row forward.

| What you have | Kind | What it supports |
|---|---|---|
| A provider's case study mentions "a mid-sized engineering firm" | Observed, unattributed | Nothing about your candidate |
| The candidate's 2025 press release announces a data partnership | Observed, attributed | That a relationship existed; not its scope, exclusivity or stage |
| The CEO says "we did a pilot with one of those AI data firms" | Stated, vague | A relationship; scope unknown until questions 2 to 4 are answered |
| The CEO says "non-exclusive, project correspondence 2015 to 2022, delivered" | Stated, specific | A defined excluded set; counsel still reads the paper |
| A colleague says "they'll be locked up" | Inference | Nothing; ask |

## Three candidates, three routes (Illustrative)

Illustrative. Generic companies, invented facts, no outcome implied.

**A. A narrowed introduction.** A 210-person engineering consultancy licensed its project correspondence from 2015 to 2022 to another provider for AI training. The CEO says the grant was non-exclusive and delivered. Its design review records, kept since 2012, and its QA checklists, kept since 2014, never left the building, and the CEO wants to talk about those. Correspondence from 2023 onward depends on whether the other license reaches later data, so it stays with counsel. Route: introduce. The company applies itself and describes the excluded set in its own words, and SourceX's rights review reads both agreements.

**B. A parked row.** A 160-person freight broker signed an exclusive deal covering all operational data created during the term. There is nothing to offer until the term ends, and counsel, not the partner, says when that is. Route: no introduction, a dated trigger, and no suggestion that the CEO test or break the contract.

**C. A no-contact case.** A 300-person medical billing company is negotiating with a provider, and the CEO says not to bring alternatives until that deal is signed or dead. Route: record the no with its scope, "until the current negotiation ends", and leave the next move to the CEO. Do not use what you know of the other deal as a pitch.

## Bringing it up without competing

The partner's job is to find out whether a conversation is possible, not to win one. Do not compare payouts, do not criticize the other provider, and do not predict what SourceX would offer: pricing stays indicative until SourceX and the company sign a deal confirmation. If the CEO asks how the two compare, point to SourceX's published process and let the company and its counsel compare signed paper with signed paper.

When the CEO does want to talk, a short, company-approved note travels with the introduction:

> The company has an existing AI data license with another provider covering [record set]. The CEO wants to discuss [other record set]. The company will describe the existing agreement itself; I have not seen it.

For related situations, [a company that already sells data](/questions/company-already-sells-data-can-it-license-to-ai) deals with subscriber and reseller contracts, [referring a business that explored licensing before](/guides/how-to-refer-a-business-that-has-already-explored-data-licensing) handles earlier attempts that went nowhere, [exclusive versus non-exclusive licenses](/compare/exclusive-vs-non-exclusive-data-license) explains the two grants, and the [candidate ownership conflict case](/guides/candidate-ownership-conflicts-exception-examples) shows a dispute over who holds the records at all.

## 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.

When the CEO has named records the other deal never touched and wants to discuss them, [sign up as a partner](/register), set the company against [the screening profile](/who-qualifies) and read section 3 of [the terms](/terms) before you submit.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/how-it-works
- https://www.copyright.gov/circs/circ12.pdf
- https://www.micro1.ai/company-referral
