The question is a good sign. A founder who asks where the records will end up is already thinking like a licensor, and deserves a precise answer rather than reassurance. The two wrong answers are a guess ("probably one of the big labs") and a brush-off ("it's anonymized, so it doesn't matter"). The first invents a fact; the second answers a different question.
Four questions packed into "who gets it?"
"Who will use it?" usually bundles four concerns. Hear which ones the founder means before you answer.
| What the founder asks | What they are weighing | What they want before agreeing |
|---|---|---|
| "Which company gets it?" | Reputation, competitors, their own view of particular AI developers | A name before a call |
| "What will they do with it?" | Training or evaluation, and what a model might reproduce | A plain description of the use |
| "Where does it go after that?" | Onward sharing, and how long any license lasts | Limits in writing |
| "What comes back to us?" | Publicity, customer reaction, being named | Confidentiality |
One thing defuses the urgency in all four. A first conversation or an application commits the company to nothing: no data moves until the company has approved the scope and the terms and signed, and nothing is shared without its approval. The founder can ask every question on this page directly before deciding.
The unknown-versus-confirmed use disclosure sheet
Each row sorts one part of the founder's question by how firmly it is known today. "Published" means a SourceX page states it for every company. "Fixed in the company's agreement" means the company's own signed documents settle it. "Not told to partners" means the terms keep it from you. "No published answer" means nobody should guess, including you.
| # | The founder's question | Status today | What you can say |
|---|---|---|---|
| 1 | Who is our counterparty? | Published | SourceX itself, which licenses data directly from companies, pays them and describes itself as their counterparty from agreement through delivery and payment |
| 2 | What kind of organization ends up using it? | Published | AI developers, to whom SourceX licenses the dataset onward in its own name |
| 3 | Which AI developer? | Not told to partners | "I'm not told; partners receive no confidential buyer information. SourceX's investor page lists anonymity for its Acquisition Partners." |
| 4 | Will our company learn the name? | No published answer | "That is a question for SourceX before you sign. I won't guess." |
| 5 | For what purpose? | Published | AI training and evaluation; licenses are exclusive for AI training |
| 6 | Exactly which records? | Fixed in the company's agreement | The Dataset Deal Confirmation fixes the exact dataset, payout, rights, processing route and deadlines before SourceX presents the opportunity externally |
| 7 | Do personal details go with it? | Published, then fixed | Data is de-identified through approved processing routes, and the route for this company is set in its Confirmation |
| 8 | Can SourceX pass it on? | Published | SourceX owns the de-identified dataset, subject to the company's underlying intellectual property rights, and the company's exclusivity does not limit SourceX's right to distribute or sublicense it |
| 9 | How long does it last? | Published | Once the fee is paid, the license to the de-identified dataset is permanent, and models already trained on it are not retrained or deleted |
| 10 | Will anyone announce it? | Published | Neither side publicizes the deal |
| 11 | Can we rule out a competitor or a kind of buyer? | No published answer | Raise it with SourceX before signing, and have the company's counsel read the scope |
Read the sheet as a timeline as much as a table. Rows 1, 2, 5 and 8 to 10 are known before anyone takes a call. Rows 6 and 7 become concrete only when the company signs its Confirmation, which, according to SourceX's process page, comes before SourceX presents the opportunity externally. Row 3 never reaches you. Rows 4 and 11 are the founder's questions to put to SourceX directly, and the honest partner answer to both is that you do not know.
Rows 8 and 9 matter most to a careful founder, so say them plainly rather than bury them. The company keeps ownership of its original records; what travels is a de-identified dataset that SourceX may sublicense, under a license that becomes permanent once the fee is paid. A founder who would refuse those terms should hear them from you before the first call, not discover them in the agreement. The guide on answering "Is SourceX a broker?" explains why SourceX signs the onward license in its own name.
Training and evaluation are different uses
Founders usually picture training, where records shape how a model behaves. Evaluation uses records as tests. Anthropic's engineering guide to evaluating AI agents describes a task as one test with defined inputs and success criteria, and separates the outcome, the real end state, from what the agent claims; its example is a booking agent, where what counts is whether a reservation actually exists in the database. A support ticket with its resolution, or a work order with its closing code, has that shape: a starting point and a known ending. SourceX lists "shows how work ended" among its fit signals. For a two-line version a founder can repeat, use the guide to explaining training versus evaluation briefly.
What to say to three founders (Illustrative)
Illustrative: three generic companies around a fund, invented details, no outcomes implied.
Founder interest. The COO of a 140-person claims administrator, not its CEO, asks at a portfolio event which lab "would get our adjuster notes." The operating partner answers rows 2, 3 and 5 and stops: "SourceX licenses to AI developers in its own name, for training and evaluation. I'm not told who they are. Whether to look at it at all is your CEO's call; I can send you the published pages to share." No introduction follows until the CEO asks for one.
Authorized sponsorship. The CEO of a 420-person freight brokerage wants rows 4 and 11 answered before the company applies. The operating partner sends the sheet, and with the CEO's written permission passes both questions to SourceX through the partner account, quoted exactly. SourceX's reply goes back to the CEO unedited. The CEO applies and will read the Confirmation, rows 6 and 7, before signing anything.
A voluntary decline. The founder-CEO of a 75-person legal services firm says: "If I can't know who uses it, we're out." The operating partner does not argue: "That's a reasonable line, and I can't change the answer." The log reads "declined; reason: buyer anonymity", and nobody raises it at the next board meeting.
Your curiosity, the founder's and the company's decision
In this program the authority to open a licensing discussion, and to sign for the company, sits with the CEO. A COO or CTO who asks about buyers may be the most engaged person in the building, but their question is personal interest until the CEO takes it up. Keep three interests apart on your side as well. Yours is a reward from SourceX, the greater of $50,000 plus 5% and 15% of what SourceX actually pays the company, with no cap for that company, paid separately and never out of the company's payout; it gives you a reason to soften the anonymity point, which is exactly why you should not. The fund's interest is a portfolio win. The company's interest is the only one that decides.
Some founders ask "who uses it?" because they would rather meet AI developers themselves, as customers or partners. That is a different conversation with a different owner, and it should never ride along with a supplier introduction; the guide to separating buyer contacts from supplier introductions shows how to route it.
Pass the question on in the founder's words
- Write the question down verbatim, with the date and who asked it.
- Ask the CEO whether you may pass it on with the introduction, and what else may travel: usually their contact details and descriptive facts about the records, never board materials.
- Send it through your partner account or the introduction itself, quoting the founder exactly.
- Forward SourceX's written answer unedited, with the question above it. Do not restate it as your own promise.
- Name no AI developer, even as an example of who it "might" be.
SourceX decides attribution from dated records and credits the earliest valid introduction inside the 90-day attribution window, at the point the company submits a verified application. The note you made in step 1 is part of that record.
Fit comes before the buyer question
The use question only matters for a company that could license at all. The published checks are a peak headcount of at least 50 full-time employees, not counting contractors; documented operating history in records the company created; licensing rights over those records; and a CEO who has asked for the conversation. Records that belong to the company's clients are usually not a fit, and when a company's own customers ask what happens to their information, the replies for a customer asking about AI and their data are the right tool. Only SourceX's review can say whether the records match current demand, what customer contracts allow and what any license would pay.
Where this sheet can mislead
- Published pages change. Every status above was read from SourceX's pages on 2026-10-26. The terms also say signed supplier and buyer agreements govern their own transactions, so the company's own documents outrank this sheet.
- Anonymity can end the conversation. For some founders not knowing the end user is decisive. That outcome is legitimate, not a failure of the pitch.
- The sheet describes SourceX's model, not any AI developer's conduct. What a licensee does within its permitted use is not something a partner can see or vouch for.
- It is not legal advice. Questions about scope, sublicensing or a competitor exclusion belong with the company's counsel.
Methods note. The sheet sorts eleven founder questions by status using only SourceX's published terms (version 2026-10-22.2, since replaced by version 2026-11-04), its how-it-works and investor pages, and the refer site's how-it-works and who-qualifies pages, all checked 2026-10-26. It does not measure how often founders ask each question or how answers affect their decisions; SourceX has published no founder interview data. To build that evidence, log each buyer question you hear, its row on the sheet and what the founder decided.
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 a founder asks who will use the records, answer from the sheet and pass the rest to SourceX in their words; a tracked introduction starts with partner registration, a look at whether the company meets the qualification criteria and a full reading of the referral terms. The overview for venture platform teams covers the fund's side of the program.
A reader asking about SourceX as a business to invest in, rather than as a licensing counterparty, has a separate question; investor materials are available on request through the SourceX investor overview.
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.