Owners who ask usually mean something else: will our records end up inside a model, is one use safer, and are you steering us? The card below answers all three.
Start from the records this company already keeps
"Your data" makes an owner picture customer lists and inboxes; "your 14 years of maintenance work orders" is something they can see and decide on. First get four facts at metadata level: the record type, the system, the years covered and how each outcome is written down. They are also your company-specific reason for raising the subject.
The outcome field matters most. SourceX's comparison of evaluation-only and training licenses notes that records showing real tasks with known outcomes, such as resolved tickets, are useful for both purposes, and that a license can name which one is permitted.
The two lines rest on definitions from outside SourceX. The EU AI Act defines training data as data used to train an AI system by fitting its learnable parameters, and testing data as data used for an independent evaluation of its expected performance. Google's machine learning course adds the rule that gives a test its value: evaluate on examples the model did not see in training. Anthropic's guide to agent evals describes the test itself: run the system on a task and let grading logic check the result. SourceX's referral site says it supplies licensed datasets for both uses.
The business-owner explanation card
Six slots, about 130 words. Lines 2 and 3 are the explanation; the rest make it about this company, keep it conditional and leave an easy choice.
| Slot | Most words | What to say (fill the brackets) | Rewrite it if |
|---|---|---|---|
| 1. Why this company | 20 | "You have [years] of [record type] in [system], each closed with [outcome field]." | You are guessing, or the records belong to the company's clients |
| 2. Training | 25 | "Training: an AI model learns from examples like your [record type], the way a new [role] learns from past [jobs]." | It treats "goes into the model" as settled |
| 3. Evaluation | 25 | "Evaluation: some [record type] are kept out of training as a test; the model works each case and is graded against what your team actually did." | It says the model never sees the records; working through them is the test |
| 4. Who decides | 20 | "Which use applies is written into the license your CEO would sign, after SourceX's review." | It promises a use, a price or acceptance |
| 5. Your role | 25 | "I'd only make the introduction. If your company licensed records, SourceX would pay me a referral reward; it never comes out of your payment." | The reward is missing, vague or buried after the request |
| 6. The choice | 15 | "Want the link? If not, no reply needed." | It asks for two actions or carries an invented deadline |
Use one record noun in both lines: if line 2 says "work orders" and line 3 says "data", evaluation sounds like a bigger request. Keep the two sentences parallel, so "learns from" against "is graded on" carries the contrast. And translate technical words before they leave your mouth:
| If you are about to say | Say instead |
|---|---|
| Fine-tuning, pretraining | The model learns from examples |
| Evals, benchmark, holdout | A test the model has not seen |
| Ground truth, labels | What your team actually did |
| Contamination, leakage | Test cases slipping into training |
Slot 5 is there because the FTC's endorsement FAQ treats a business relationship or payment as a material connection to disclose clearly, not vaguely. A private note to one owner is not necessarily advertising, but the plain sentence costs nothing.
Analogies for five kinds of company, and where each one breaks
An analogy from the owner's own business beats a definition. Each one breaks somewhere, and the break is where the next question lands.
| Company (Illustrative) | Records | Training is like | Evaluation is like | Where it breaks |
|---|---|---|---|---|
| Property manager | Maintenance work orders | A new coordinator reading past jobs | Routing closed jobs they never saw, checked against what was done | A person forgets; what a model keeps after a license ends is a contract term |
| Corporate training provider | Course modules and quiz banks | The lessons | The final exam | A test question that leaked into the lessons scores well and proves nothing |
| Engineering consultancy | QA comments on drawings | An apprentice studying marked-up drawings | A blind review of drawings with logged errors | A comment reversed later gives the test two answers |
| Software company | Resolved support tickets | A new agent reading closed tickets | Answering past tickets, scored against the recorded fix | A polite reply can still be wrong; grading checks the outcome |
| Distributor's finance team | Invoice exception notes | Shadowing an experienced clerk | An audit sample checked against the recorded resolution | An audit hunts for problems; a test set must also represent ordinary cases |
The breaks come from the sources: Google's rule that a test case duplicated in training is not a fair test and that test sets must be representative, Anthropic's distinction between what an agent says and the outcome it produced, and the reversal question in the evaluation holdouts guide.
One reply to a COO, before and after (Illustrative)
Illustrative facts: a 230-person property management company, run by its founder as CEO, with 14 years of maintenance work orders in one system, each closed with a resolution code. The company's outside IT consultant knows the COO, who asks: "When you say AI training, what would they actually do with our work orders?"
Before: "Great question! Your data would be used for model training or evals. Evals are basically benchmarks, and eval data is really valuable right now and lower risk, because it never actually goes into the model. It's a great revenue opportunity, so it's worth moving quickly."
After: "Your 14 years of work orders, each closed with a resolution code, are the kind of record SourceX reviews for AI training and evaluation. Training means a model learns from them; evaluation means some are kept apart and the model is graded against what your team did. The license your CEO would sign after SourceX's review says which. I'd only make the introduction; if your company licensed records, SourceX would pay me a referral reward that never comes out of your payment. Want the link? If not, no reply needed."
| Before says | The problem | After does |
|---|---|---|
| "training or evals", "benchmarks" | Jargon explained with more jargon | Names both uses in terms of work orders |
| "really valuable right now" | A value claim nobody has made for these records | Leaves price to SourceX's review |
| "never actually goes into the model" | Wrong: in evaluation the model works through the records | Leaves retention to the license |
| "great revenue opportunity", "moving quickly" | An outcome and urgency with nothing behind them | One link, no deadline |
| No mention of the reward | The partner's interest goes unstated | One plain sentence before the request |
The four questions owners ask after the two lines
| Owner asks | What you can say | What only the license or SourceX settles |
|---|---|---|
| "So our records end up inside the model?" | "Training: it learns from them. Evaluation: it works through them as test cases. Either way it uses them." | What is kept, deleted or returned, and when |
| "Can we allow testing only?" | "You can raise it. SourceX treats evaluation-only as a narrower use to discuss, not a default." | Whether it is available for these records |
| "Which one pays more?" | "Nobody has priced your records, and I won't guess." | Price, agreed between the company and SourceX |
| "Who sees how the model scored?" | "That's a license term your counsel can check." | Access to results and how long tests may be rerun |
For the last question, the evaluation and training clause checklists show which clause answers each scope question. The third has a consequence for you: the program terms calculate the reward on the Actual Supplier Payout and do not distinguish training from evaluation, so you have no reason to steer.
Which records support either use, and who can say yes
Whichever use a buyer has in mind, an introduced company must reach 50 or more full-time employees at peak, not counting contractors, and bring documented operating history, rights to license the records and an authorized contact. Here that is the CEO, who authorizes a licensing discussion and signs; a COO can sponsor the idea internally. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.
Personal consumer data and material that belongs to a company's clients are usually not a fit; drawings a consultancy made for a client may be the client's, which SourceX's rights review settles. Your questions stay at metadata level: what, how many, which years, which system, who administers it. No files, samples or logins. Demand fit, which use a license would name and what customer contracts permit stay unknown until SourceX reviews the company.
What the company signs, and what you earn under either use
The company signs its license directly with SourceX, the data is delivered and SourceX pays the company; your part ends at the introduction, as the guide to an introduction versus data delivery explains. You sign the SourceX Channel Partner Agreement before submitting any introduction.
The default reward on a company's first qualifying transaction is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; Actual Supplier Payout is what SourceX actually pays the referred company. Further qualifying transactions with that company first agreed within 12 months of the first Closing pay 15%, and a transaction qualifies only from USD 100,000 unless SourceX agrees in writing. It is never calculated on SourceX's fees or revenue and never deducted from the company's payout. It falls due within 60 calendar days of whichever event is later, completed handoff or final written acceptance of the complete, validated dataset given by the Acquisition Partner, and the payment conditions in the terms apply. A later reduction of the supplier payout reduces the reward. Illustrative only: a USD 100,000 Actual Supplier Payout gives a USD 55,000 reward; USD 400,000 gives USD 70,000.
Offer the link once and leave the timing to the owner
End with slot 6 and stop: your partner link, or the company fit checker for a non-binding look, with no deadline unless the company has a dated event of its own, such as a system being retired. Owners who want more can read the one-minute explanation or SourceX's page on training data versus evaluation data.
No test of these wordings with owners has been published. If your team adopts the card, log which slot draws follow-up questions, count them against every owner who heard it, and rewrite that slot first. More in the guides library.
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 an owner hears the two lines, understands that the license decides the use and asks how to start, sign up for a partner link, compare the company with who qualifies and keep the program terms open for the reward sentence.