# Partial dataset interest, explained to a founder | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-explain-partial-dataset-interest-at-referral-stage
Last updated: 2026-11-05

Say it before the first call: SourceX licenses selected data, not a company. The founder lists systems and years of history; what ends up licensed may be one system, one record family or one stretch of years, and only that part is paid for. Buying part of an offered dataset needs fixed-price lots in the Dataset Deal Confirmation or a signed amendment, the exclusivity covers only the selected data, and everything else stays with the company. A referral opens a review of the inventory, never a sale of all of it.

Founders hear "data licensing" and picture a buyer taking the whole archive. When the reality turns out to be a slice, the reaction is often disappointment, or suspicion that something was oversold. A partner who explains lots at the start prevents both.

## "Are they cherry-picking us?" and the other worries behind it

When a founder balks at the idea of partial interest, the objection usually carries one of five worries. Ask which one before answering.

- **Undervaluation.** "If they only take the best part, the rest is worth nothing." The founder fears the remainder is spoiled.
- **Effort for a sliver.** Exports, review and sign-off for a fraction of the records may not seem worth the team's time.
- **Exclusivity creep.** "Does licensing one system tie up everything else?"
- **Moving goalposts.** A worry that a buyer will take less later and pay less.
- **The partner's motive.** If a partner is paid on the deal, will they push the company to accept any slice?

Each has a bounded answer in SourceX's published documents, and none needs a promise from you.

## What SourceX publishes about licensing part of an inventory

| Rule | What it means for a founder | Source |
|---|---|---|
| The Dataset Deal Confirmation fixes the exact dataset, payout, rights, processing route and deadlines | The lot is written down before SourceX presents it externally; nothing outside it is licensed | SourceX process page, checked 2026-10-27 |
| Buying part needs fixed-price lots in the Confirmation or a signed amendment | A smaller purchase needs one of those two signed documents | SourceX process page; partner agreement sample, Schedule A 5.6 |
| Exclusivity covers only the selected data; future data and unselected records are excluded | Licensing one system does not tie up the others | SourceX process page |
| Licenses are exclusive for AI training; the term and any alternatives are set in the Confirmation | The term is agreed deal by deal and is not published | SourceX process page |
| Data that does not reach Closing earns no payment, and unclosed data is treated as declined and deleted | A lot that is never accepted costs the company its time, not its records | SourceX process page |
| Pricing stays indicative until the Confirmation is signed | No figure binds before the signature | SourceX process page |
| A lower Acquisition Partner quote does not automatically change the supplier's fee | A buyer's change of mind does not silently cut the company's price | Partner agreement sample, Schedule A |

The process page also says qualifying companies list at least 5 systems. An inventory of five or more systems, each with its own years and record families, is exactly the situation in which one part draws interest and another does not. SourceX's own answer on non-selection lists "interest at a different scope", where buyers want part of the data or different date ranges, as one possible outcome, and leaves it to the company to decide whether the narrower scope works.

## Whole-company-versus-lot examples

Illustrative. Four generic companies with invented inventories, lots and figures. Each reward is the default for a company's first qualifying transaction, the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, applied to the amount actually paid for the closed lot; a lot paid below the USD 100,000 Minimum Transaction earns nothing unless SourceX agrees in writing. None is a forecast, a quote or a completed deal.

| Company | What it listed | What the Confirmation covered | Why the line fell there | What stays with the company | Paid, and partner reward |
|---|---|---|---|---|---|
| A 600-person contact-center operator | Six systems: tickets, call notes, QA scores, workforce schedules, HR files, billing | Tickets and QA scores, 2017 to 2025, as one lot | The two systems that record work and its outcome; HR and billing were never offered | Call notes, schedules, HR files and billing | $800,000 paid; $120,000 reward (15%, the larger figure) |
| A 240-person B2B software company | Support tickets, engineering issues, CRM notes, product documentation | Two fixed-price lots: support tickets, and engineering issues; only the first was selected | The Confirmation allowed either lot to be taken alone | Engineering issues, CRM notes and documentation; the unselected lot is not covered by the exclusivity | $250,000 paid for one lot; $62,500 reward (USD 50,000 plus 5%, the larger figure) |
| A 130-person freight broker | Twelve years of dispatch notes and claims | The most recent six years of dispatch notes | The records were kept the same way only after a system change | The older six years and all claims files | $40,000 paid; no reward: below the USD 100,000 Minimum Transaction, unless SourceX agrees in writing |
| A 95-person engineering consultancy | Project files and design reviews | Nothing | No current program needed these records | Everything; no obligation and nothing owed | Nothing paid; no reward |

**What the four cases teach.**

1. **Even the widest case is a lot.** The contact-center operator licensed two of six systems. A license covers selected data, not a company, so even a generous outcome is a large, defined dataset.
2. **Fixed-price lots protect the company.** In the software case the lots were priced separately in the Confirmation, so selecting one did not reopen the price of the other. Without that structure, a partial purchase would need a signed amendment.
3. **Consistency often draws the line.** The freight broker's older years were not wrong, just recorded differently. A selected range is a statement about fit, not a judgment on the company.
4. **No lot is a normal result.** The consultancy keeps everything and owes nothing.

For the partner, the reward follows the closed lot only. Section 4 of the terms defines Actual Supplier Payout as compensation actually paid for "selected data that reaches Closing", and says indicative ranges, unclosed data and unpaid supplier amounts do not count. If a deal ever delivers in separately approved parts, section 5 says each part counts as its own qualifying handoff for the reward only by express written agreement; Schedule A 5.6 of the agreement sample adds that this agreement is between SourceX and the partner. That also answers the motive worry honestly: a partner earns only if a lot closes, which is a reason to say so up front, and section 4 adds that SourceX pays the reward separately and never deducts it from the company's agreed compensation. The [referral earnings calculator](/tools/referral-earnings-calculator) runs the same arithmetic on a figure you choose.

## Why model developers license slices

Partial interest is not a SourceX quirk. Research on how language models are trained treats selection as a core step. A 2024 survey of data selection methods by Albalak and coauthors, published in Transactions on Machine Learning Research, opens with the argument that naively training on all available data may be neither optimal nor feasible, because the quality of available data varies, and then catalogs the methods used to choose subsets. A buyer looking at a company's five systems is making the same kind of choice on a smaller scale.

That framing helps with the undervaluation worry. A lot is chosen because it fits a specific use, not because the rest of the inventory has been graded worthless. It also explains why the same inventory can draw interest at one time and not another, since current needs move.

## Known at referral, set in the Confirmation, unknown until review

**Known at referral stage:** SourceX licenses defined datasets; partial purchases need fixed-price lots or a signed amendment; exclusivity reaches only selected data; nothing is paid for data that does not close; the company keeps what is not licensed.

**Set in the company's Confirmation:** which records form each lot, the payout for each, the rights granted, the processing route and the deadlines, and the term of the exclusivity.

**Unknown until SourceX's review:** whether any part of the inventory fits a current program, how large the lot would be, and what it would be paid. Separately, some records may fall outside any lot for reasons that have nothing to do with demand, such as client ownership or personal data; those boundaries are covered in [why a referral does not mean every record is usable](/guides/why-a-referral-does-not-mean-every-record-is-usable). And if the founder wants to rule records out before anyone looks, the [scope boundary approach](/guides/when-the-company-wants-to-limit-which-records-are-discussed) starts from the company's side.

## Phrases that keep the founder's expectation honest

| Say | Instead of |
|---|---|
| "SourceX licenses defined datasets; often that is one or two of the systems you list." | "They'll license your data." |
| "If they take part, the Confirmation says which part and what it pays." | "They might take some of it." |
| "Whatever is not selected stays yours and is not tied up." | "The rest probably isn't worth much." |
| "Any figure before the Confirmation is indicative." | "It could be worth a few hundred thousand." |
| "If nothing fits a current program, you keep everything and owe nothing." | "I'm sure something will fit." |

For the first explanation of licensing itself, before lots come up, the [founder explainer](/guides/how-to-explain-company-data-licensing-to-a-founder) is the better starting point; for why an indicative range is not a price, see [why a licensing conversation is not a valuation promise](/guides/why-a-data-licensing-conversation-is-not-a-valuation-promise).

## One voluntary step, and how to decline

Offer one step: the CEO lists the company's systems, years of history and record families in SourceX's short assessment, which asks for no files, and notes any systems that are off the table. That inventory is what any lot would be cut from.

Make declining easy. A founder who would only proceed if the whole archive were licensed has a clear answer now, and the right response is to log "declined: wants the whole inventory licensed" with the date and stop. A founder who says "a slice is fine" should still hear that no slice is promised.

The company must pass the screen first: 50 or more full-time employees at its peak (contractors excluded), documented operating history, rights to license its records and a CEO who wants the conversation. 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.

## Where the lot explanation breaks down

- **A small lot may not be worth the work.** The company carries export and review effort whatever the lot's size, and SourceX does not publish how lots are priced. Some founders will rationally decline.
- **Exclusivity still binds the lot.** The selected data cannot be licensed to anyone else for AI training on the terms in the Confirmation. Counsel reads that clause before signing.
- **Demand moves.** A lot defined this year says nothing about what might fit next year, in either direction.
- **No published distribution.** SourceX has not published how often deals cover one system, several or none. A partner should not imply typical lot sizes.
- **Investors should not read lots as metrics.** Lot structure explains the program; it is not evidence of SourceX's volumes or revenue, which SourceX shares with investors directly.

**Method note.** The four examples were built on 2026-10-27 from SourceX's process page, the program terms and Schedule A of the Channel Partner Agreement sample (version 2026-10-19), and the rewards were recomputed on 2026-11-05 under the program terms of version 2026-11-04. Company sizes, systems, lots and amounts are invented; each reward was computed as a company's first qualifying transaction: the greater of USD 50,000 plus 5% of the paid amount and 15% of it, and nothing where the paid amount is below the USD 100,000 Minimum Transaction. Not measured: how often partial lots occur, lot prices, or how founders respond to partial interest. To measure the last, log each founder conversation where partial interest comes up, which of the five worries it carried and whether the CEO went ahead.

## 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 founder understands that a lot, not the company, is what gets licensed and still wants the review, [create your partner account](/register), screen the company against [who qualifies](/who-qualifies) and look up how the [terms](/terms) define Actual Supplier Payout before you mention any number.

Explaining lots to a founder is part of making a careful referral; assessing SourceX itself as an investment is a separate decision, and the [SourceX investor overview](https://sourcex.si/investors) is where investors can ask for materials.

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/how-it-works
- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://arxiv.org/abs/2402.16827
- https://refer.sourcex.si/questions/what-if-no-buyer-wants-my-data
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/investors
