# Evaluation-only data referral intake | SourceX

Canonical: https://refer.sourcex.si/guides/what-if-a-company-wants-its-data-used-only-for-evaluation
Last updated: 2026-11-04

Introduce the company with that condition written down, not argued away. SourceX says a license can allow testing models only, not training them, and that such a license usually pays less but keeps tighter control. Whether a current program can use this company's records on those terms is SourceX's call after review, and the permitted use is fixed in the Dataset Deal Confirmation the CEO signs with SourceX. Your job is to record the preference accurately, disclose your own incentive and promise nothing.

For a VC operating partner the sentence tends to arrive mid-conversation: "We'd consider it, but only for evaluation. Nobody trains on our data." It sounds like a deal term. At referral stage it is more useful as information about what the founder fears and which records they have in mind.

## Four worries that arrive as "evaluation only"

| What the founder says | The worry underneath | What has been published | Who settles it |
|---|---|---|---|
| "Our people's judgment is the product. I don't want it inside a model." | Know-how absorbed by a model others use | Researchers extracted hundreds of verbatim training sequences from GPT-2, some present in only one training document (Carlini and co-authors, USENIX Security 2021) | SourceX in the license terms, the CEO in signing |
| "Once it's trained in, we can't take it back." | Irreversibility | SourceX says that once the fee is paid its license to the de-identified dataset is permanent, and models already trained on it aren't retrained or deleted | The CEO, before signing |
| "Let's start small and see." | Wanting a first step | SourceX's evaluation note says moving to training later takes a new or amended license | The CEO and SourceX, later |
| "Our customers wouldn't like training." | Contract or reputation limits | SourceX's screening page counts client-owned material among the usual poor fits | SourceX's rights review and the company's counsel |

Naming the worry matters because each one routes differently. A know-how worry may be met by leaving one record family out. An irreversibility worry is about the permanence of any training license, so it deserves a straight answer rather than reassurance. A first-step worry is about sequence. A customer worry may be a rights problem that no choice of permitted use repairs.

## What SourceX means by evaluation-only

SourceX's note on the question is short. Under such a license, it says, the Acquisition Partner "may use the data to measure model quality but not to train on it", and "Narrower uses generally mean lower value, but less risk." Its page on private evaluation sets explains the demand behind the idea: items published on the web end up in training data, so a high benchmark score can reflect memorization, while records that have only lived inside a company's systems have not been exposed that way. The license, it adds, can restrict items to evaluation and prohibit training on them.

Two further facts frame the conversation. SourceX's standard description is that licenses are exclusive for AI training, with "The term and any alternatives" set in the Dataset Deal Confirmation, so evaluation-only is an alternative SourceX describes rather than the default. And the company confirms its data has not been licensed for AI training before, so any family already licensed that way is out regardless of the founder's preference. Clause-level detail sits in the [evaluation-only license comparison](/compare/evaluation-only-data-license) and the [rights checklists](/compare/ai-evaluation-data-licensing-rights); a two-line explanation of the difference for an owner is in [explaining training and evaluation briefly](/guides/how-to-explain-the-difference-between-training-and-evaluation-briefly).

## The permitted-use preference intake

One page, written with the founder, approved by the CEO before it travels and sent without attachments. It turns a sentence into something SourceX can answer.

| Field | What to write | Example (Illustrative) |
|---|---|---|
| 1. The preference, in the CEO's words | Quote it; do not paraphrase | "Testing only for adjuster notes." |
| 2. How firm it is | Condition (no deal otherwise), preference (would weigh a trade-off) or question (wants to understand) | Condition |
| 3. The worry behind it | Know-how, irreversibility, first step, customers or other | Know-how |
| 4. The record families it covers | Each family marked evaluation only, open or undecided | Adjuster notes evaluation only; claim outcomes undecided; process manuals open |
| 5. Earlier licensing | Has any family been licensed to anyone for AI training? | No, per the CFO |
| 6. The fallback | What the company does if no program can work on these terms: decline, revisit or discuss a different split | Revisit next year |
| 7. Approval | Who approved the intake, and the date | The CEO, 14 October |
| 8. What you said | Your exact words, so nothing reads as a promise | "SourceX decides whether a program can work with this." |

Three rules keep it honest. The CEO approves the text. It names record families, never records. And it proposes no price, term or exclusivity, because those are set only in a Dataset Deal Confirmation with SourceX. If the founder wants to narrow which families are discussed at all, the [scope boundary statement](/guides/when-the-company-wants-to-limit-which-records-are-discussed) does that job; the intake is about permitted use within the families that are open.

**Method note.** The fields come from SourceX's published description of evaluation-only licensing, its how-it-works terms and the program terms, all checked 2026-10-27, plus our own grouping of founder worries into four kinds. The intake has not been tested on a cohort of founders. SourceX has not published how often evaluation-only requests are accepted or how they are priced, so those figures are not available here.

## What is settled, what waits for review and what nobody has examined

| Status | Statement | Basis |
|---|---|---|
| Settled | A license can be limited to testing models rather than training them | SourceX's evaluation note |
| Settled | Narrower uses generally mean lower value | The same note |
| Settled | The dataset, payout and permitted use are fixed in the Dataset Deal Confirmation the CEO signs with SourceX | SourceX's evaluation note and how-it-works page |
| Settled | Records already licensed to anyone for AI training are out | SourceX's how-it-works page |
| Waits for review | Whether a current program wants this company's records for evaluation | SourceX's review, which weighs Acquisition Partner demand |
| Waits for review | Whether the records belong to the company and can be licensed at all | SourceX's rights review |
| Not yet examined | Volume, years and outcome fields in each family | The company, described at metadata level |
| Not yet examined | Whether the condition still holds once the CEO sees an indicative range | The CEO |

## Your reward is the reason to stay neutral

Say this early and out loud. On a company's first qualifying transaction a partner earns the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, and a transaction only qualifies at the USD 100,000 Minimum Transaction or above unless SourceX agrees in writing; SourceX's own note says narrower uses generally mean lower value. So your incentive points toward the broader license, the opposite of what this founder wants.

| Scenario (Illustrative) | Actual Supplier Payout | Partner reward |
|---|---|---|
| A narrower license on one record family | USD 40,000 | None: below the USD 100,000 Minimum Transaction, unless SourceX agrees in writing |
| A broader license on several families | USD 100,000 | USD 55,000 (USD 50,000 plus 5%) |

Illustrative: invented figures chosen to show how the formula moves, not a price ratio SourceX publishes, and SourceX does not publish how offers are priced. The reward is paid separately by SourceX, and nothing for the partner comes off the compensation in the company's signed agreement. Describe both options in SourceX's words and let the CEO choose.

## A founder who wanted testing use only (Illustrative)

Illustrative. The claims administrator below is invented, and so is everything it says; no real company or result is described.

A 210-person insurance claims administrator in the portfolio keeps 13 years of claim files, with adjuster notes, decisions and appeal outcomes, in one claims system. Its founder-CEO tells the operating partner: "Our adjusters' judgment is what clients pay for. If anyone trains on those notes, I'm out. Evaluation, maybe."

The bounded answer: "SourceX says a license can be limited to testing models, and that this usually pays less. I can't tell you whether a program wants your records on those terms; SourceX decides that after a short assessment that needs no files. If you like, I'll write down what you just said, you check it, and it goes with the introduction. You should also know I'd earn a referral reward if a deal closed, and a broader license would usually mean a bigger one, so don't take my view on which to choose."

The intake records a condition on adjuster notes, claim outcomes as undecided and process manuals as open, no earlier AI licensing and a fallback of revisiting next year. The escalation path is the CEO's: the company starts the assessment from the partner's link, SourceX answers the CEO directly, and the partner sees only the referral's status. What would have gone wrong is easy to picture: a partner telling SourceX "they'll come round on training", or telling the founder "evaluation-only is always on the table".

## One step for the founder, and a clean way to say no

The step is SourceX's short company assessment: a few questions, no files, started from your link with the intake described in words. If the founder would rather not, that is a complete answer. Record the date and the reason, and raise it again only if the founder does. Do not offer the "start small" route as a foot in the door; if the founder wants a first step, they will say so.

## Where this approach can be wrong

- **Demand may be thinner.** SourceX checks relevance to its current data needs in review, and a firm evaluation-only condition can end a strong company's chances today, though a company that misses one program may fit another later.
- **Value is lower by design.** SourceX says narrower uses generally mean lower value. A founder expecting the economics of a training license will be disappointed.
- **Evaluation sets age.** SourceX's evaluation page notes that a held-out set loses value with use. Our reading, not SourceX's statement: one snapshot of records is unlikely to stay equally useful for evaluation forever.
- **Conditions get softened.** A partner who turns "only" into "preferably" misleads both the founder and SourceX; the verbatim field exists to stop that.
- **The research cuts both ways.** The USENIX result concerns a public model trained on web text. It does not show that a licensed, de-identified business dataset would be exposed the same way, so use it neither to frighten nor to reassure.
- **Rights come first.** No permitted-use choice cures records that belong to the company's clients.

## 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 approved the intake and wants SourceX to answer it, [set up your partner account](/register), measure the company against the screening profile on [who qualifies](/who-qualifies) and work through the reward and payment sections of the [program terms](/terms); then send the link and the intake together. The [venture platform teams page](/for/venture-platform-teams) and the [guides library](/guides) cover the rest of the portfolio side.

Recording a founder's permitted-use condition is referral work; whether SourceX itself deserves a place in a fund's portfolio is a different inquiry, and the materials for it are requested through the [SourceX investor overview](https://sourcex.si/investors).

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.

## Sources

- https://sourcex.si/insights/can-i-limit-licensing-to-evaluation-only
- https://sourcex.si/datasets/use-cases/evaluation-sets
- https://sourcex.si/how-it-works
- https://www.usenix.org/conference/usenixsecurity21/presentation/carlini-extracting
- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/investors
