How better business introductions could improve the data behind AI: a seven-link pathway, and the point where a partner's claim has to stop

Short answer

Mostly through context, not volume. A trusted introduction can reach the CEO who can authorize a license, name the system and the person who runs it, and say which records the company itself owns. That context may make a dataset review faster and its provenance clearer. It cannot, on its own, show that a model trained on the data performs better: that is a separate technical test on the delivered dataset. The seven-link pathway below keeps the two claims apart and names where each link can break.

Visual briefFull-size diagram
A swimlane diagram with three lanes, partner, SourceX review and AI developer, carrying seven numbered links from a trusted relationship to measured model usefulness; each link has a failure marker, and a dashed wall before link 7 marks the separate technical test.
A proposed causal pathway, not measured results. Link 7 is evaluated by whoever trains on the data.

The temptation is to draw a straight line from "I know this company well" to "AI gets better data". The line exists, but it has seven joints, and a partner can see only the first three.

The information a context-free lead loses

A purchased list or a cold contact gives a reviewer a row: sector, approximate headcount, a name with a job title. Almost everything a dataset review needs first is missing.

ContextContext-free leadTrusted introductionWhy a review needs it
Who can say yesA job title, often not the CEOThe CEO, who knows the request is comingIf the person who decides is unaware of it, the introduction usually counts as no fit
Where the records liveUnknownNamed systems and the person who administers themDecides how records could be reached and prepared
How far back they goUnknownA span of years per systemOperating history is part of fit
Whose material it isUnknownCompany-owned versus client-owned, at least as the CEO understands itClient-owned material is usually not a fit
Why the records existUnknownThe workflow that produced themThe first question a dataset's documentation has to answer
What is changingUnknownA dated migration or archive change, if anyReal timing, not invented urgency

The cost of lost context in AI data is documented outside this program. The Data Provenance Initiative audited 1,858 text datasets and reported license omission rates above 70% and license error rates above 50% on widely used dataset hosting sites. Those datasets lost their context somewhere between the people who made them and the people who used them. A licensing path that starts with the company's own CEO starts with that context intact.

How a trusted introduction surfaces the owner and the workflow

Two things travel with a good introduction that no database holds. The first is authorization: the CEO hears about licensing from someone they already trust, decides whether to discuss it and, under the program, authorizes the discussion and signs. The second is workflow knowledge: an accountant knows which system closes the books, an IT provider knows which helpdesk holds ten years of tickets, an operating partner knows the company migrated its CRM in 2021.

Both reach SourceX only at metadata level. Partners do not need to export, upload or describe confidential records, and an IT provider that administers a company's systems must not use that access to look at or sample records for an introduction. What it shares is what the CEO approves: the system names, record families, years and administrators. The metadata-only opportunity map gives the columns, and the managed service provider page covers that partner type.

Why clearer provenance may make review more efficient

This is the hypothesis, stated as one. Datasheets for Datasets, a proposal published in Communications of the ACM, argues that every dataset should come with documentation of its motivation, composition, collection process and recommended uses, to improve transparency and help practitioners choose the right dataset. An introduction cannot write a datasheet, but it can seed the first answers at metadata level, which may spare a review several rounds of basic questions.

Datasheet question areaWhat an introduction can supplyWhat only review can establish
Motivation: why the records existThe workflow that produces themWhether that workflow matches a current data need
Composition: what the records areRecord families, systems, rough countsActual content, quality and duplication
Collection process: how they were madeWho enters them, in which system, since whenGaps, format changes and consistency over time
Uses and restrictionsWhose material it is, as the CEO understands itRights under customer contracts, privacy and third-party terms
Distribution and maintenanceWho administers the systemScope, preparation and handoff under a signed agreement

Whether this actually shortens reviews is not yet measured. SourceX has not published review-efficiency figures by introduction type.

The separate test that decides usefulness

A dataset's usefulness for AI is measured by training or evaluating models on it, not by how it was sourced. DataComp shows what such a test looks like: it holds training code and compute fixed so that only the training set varies, then evaluates each resulting model on 38 downstream test sets. Whoever trains on licensed records runs its own version of that comparison, and the results belong to them.

So the honest claim for a partner stops before that test. "My introduction reached the CEO, named the records and surfaced a rights question early" can be true and checked. "My introduction improved a model" cannot be checked by the partner and should never be made. The data quality page explains why documented, real records attract interest; the trajectory evaluation gap analysis shows how missing context limits what can be graded later.

The introduction-to-data-quality causal pathway

This is the asset. Each link is a mechanism with an observable sign and a named failure. A chain is only as strong as its weakest link, and a break anywhere stops the claim at that point.

LinkMechanismObservable signWhere it breaksWho can observe it
1A trusted relationship brings the request to the CEOThe CEO knew in advance and agreedIntroduction goes around the CEOPartner
2The CEO names the right records and their administratorSystems, years and an administrator are namedThe CEO does not know where records live, or an outside vendor holds themPartner
3Named records come with an ownership pictureCompany-owned versus client-owned is statedThe richest records belong to clientsPartner, then SourceX
4Clear context at intake reduces basic review questionsFewer clarification roundsThe partner's account was wrong, and review spends time correcting itSourceX
5Review turns into an agreement and preparation planScope and preparation agreed, personal details handledRights review narrows scope to littleSourceX and the company
6The prepared dataset carries documented provenanceMotivation, collection and restrictions documentedDocumentation stays thinSourceX
7Documented records prove useful in a modelA downstream evaluation with training held fixedNo measurable gainWhoever trains on the data

The graphic shows the same seven links in three lanes, with a wall before link 7.

One relationship followed through, and one that stops (Illustrative)

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

A 340-person property management company, introduced by its managed IT provider. Link 1 holds: the provider's account lead has known the CEO for years and asks first. Link 2 holds: work orders in one system since 2012, tenant messages in a helpdesk, both administered by the provider. Link 3 is mixed: work orders are the company's own, while tenant messages contain personal details that would have to be removed. The CEO approves sharing that picture, and the provider submits the introduction. Links 4 to 6 are now SourceX's and the company's to test; the outcome is open. Link 7 will never be the provider's claim, whatever happens.

A 90-person call center outsourcer, introduced by its accountant. Links 1 and 2 hold: the CEO agrees, and recordings and QA scorecards go back eight years. Link 3 breaks: the recordings belong to the outsourcer's clients under its service contracts, and the who-qualifies page treats client material as usually not a fit. The chain stops. The introduction still did its job by reaching that answer in one conversation, with nothing exported and no records seen.

What partners and SourceX could measure without overstating AI impact

MeasureLinkDefinitionHeld byNot evidence of
CEO-consented introductions1Share of introductions where the CEO knew and agreed beforehandPartnerFit
Facts known at handoff2Of size, location, own records and authorized contact, how many were knownPartnerRecord quality
Early rights flags3Introductions where an ownership question was raised before submissionPartnerA rights decision
Clarification rounds4Basic questions a review had to ask before assessing the recordsSourceX; not publishedDataset usefulness
Scope after rights review5How much of the named records stayed in scopeSourceX; not publishedModel performance
Provenance completeness6Share of documentation fields answered for a prepared datasetSourceX; not publishedModel performance
Downstream usefulness7Evaluation results with training held fixedThe developer; not publishedAnything about the introduction alone

None of these figures has been published. A partner can start on the first three tomorrow; the middle three would need SourceX to publish them with cohorts and definitions; the last one is not SourceX's or the partner's to report.

What every introduction still has to meet

Context helps a review see fit; it does not create it. 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. Beyond location, the company must have reached 50+ full-time employees at its peak, contractors aside, must document its operating history and must hold the rights to license its own records, and the CEO authorizes the discussion and signs for the company. Material belonging to clients, personal consumer data and one-off files with no documentation or context are usually not a fit. Two things stay open until SourceX reviews the company: whether its records fit current demand, and what a license would cover. Partners sign the SourceX Channel Partner Agreement, formerly titled the Channel Partner Non-Circumvention and Non-Disclosure Agreement, before submitting introductions. Payment follows the conditions in the terms and is due within 60 calendar days after the later of two dates: the day the Acquisition Partner's final written acceptance of the complete, validated dataset is given, and the day handoff is completed.

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.

If you can hold links 1 to 3 for a company you know, sign up as a referral partner, compare that company with SourceX's who-qualifies criteria, review the program terms, and then pass on the context the CEO approves and nothing more.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Can a partner say an introduction improved an AI model?

No. A partner can show that the CEO was reached with consent, that the records and their owner were named, and that rights questions surfaced early. Whether a model improves depends on an evaluation by whoever trains on the data, which partners and SourceX do not publish.

Does a better introduction make a company more likely to qualify?

It can make the answer arrive sooner, not change it. Size, history, rights, authorization and current demand decide fit; context only helps the review see them clearly.

What context should a partner pass on, and what not?

Pass on what the CEO approves at metadata level: record families, systems, years covered, who administers them and whose material it is. Never pass on files, samples, exports or logins, even if you have access to the systems.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. refer.sourcex.si/how-it-works
  4. cacm.acm.org/research/datasheets-for-datasets
  5. arxiv.org/abs/2310.16787
  6. arxiv.org/abs/2304.14108

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment