SourceX's who-qualifies page puts the location rule in one sentence: "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." The English-language eligibility guide explains how a company works out its share; this page covers the brief that carries an international introduction, and the assumption that spoils it.
The language-evidence referral brief, line by line
Eight lines in three voices, each holding one fact an international introduction tends to blur: where you are, who decides, where the company operates, what its records are written in and whose they are. You write lines 1 to 3; the company supplies lines 4 to 7, copied in its words with the date; line 8 holds what only SourceX can settle. It goes with the introduction you submit from your partner dashboard, after the CEO has read it; for the note to the CEO, use the warm introduction brief.
| Line | Whose words | What it holds |
|---|---|---|
| 1. Introducer | Yours | Name, firm, country, and the date you signed the SourceX Channel Partner Agreement |
| 2. Relationship | Yours | Who at the fund knows the CEO, and the date the CEO asked for a conversation |
| 3. Operating context | Yours, labeled "context, not records" | Languages of leadership, board reporting, the website and the head office, with where you saw each |
| 4. Entities | The company's | Operating entities, where their people work, the group parent |
| 5. Records in view | The company's | Systems, record types and years, described in words, never attached |
| 6. Record language | The company's, approved by the CEO | The languages of the line 5 records and how the company knows, or "not yet stated" |
| 7. Rights and history | The company's | Records the company made itself, any client ownership, any earlier AI-training license |
| 8. For SourceX | Yours, as questions | Geography per entity, program fit, final language measure, rights, overlapping introductions |
Notes on four lines:
- Line 1. Your own location is a separate question. Who-qualifies says: "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."
- Line 2. The CEO authorizes a licensing discussion and signs for the company. In a sale, the target's CEO decides until closing and the acquirer's CEO after it.
- Line 4. Each entity is read against the geography sentence; for a group straddling both halves of it, SourceX decides in review.
- Line 7. Material that belongs to clients is usually not a fit, and on SourceX's company process page a supplier confirms that its data "hasn't been licensed for AI training before".
Three rules apply.
- Line 3 never feeds line 6. Unanswered, it stays "not yet stated" and the question goes back to the CEO.
- Line 3 holds only what anyone could observe or what the CEO said for the brief. Something learned through a board seat may prompt one question to that company's CEO; it never enters a document others will read.
- The brief speaks for nobody. It never implies the company qualifies, that SourceX endorses the fund, that anyone gets preferential access to records or that the fund decides for the company. Nobody at the fund gathers records for SourceX.
The brief is also a dated record. Section 2 of the terms reads: "Attribution is decided from dated records, including written introduction evidence, existing applications and preexisting relationships; an earlier link click alone does not decide credit." A brief earns nothing alone: the first valid introduction inside the 90-day window is credited once the company submits a verified application, and a company SourceX already knew is a duplicate. If a deal partner, a regional office and a co-investor all know one CEO, only one introduction can be credited; SourceX decides overlaps in duplicate review. One reward cap covers the whole group; whether a parent's earlier contact with SourceX, or a sister company's introduction by someone else, affects credit is left to that review.
What goes wrong when a partner assumes the records are in English?
The brief overstates, the CEO hears a promise nobody made, and the error surfaces in SourceX's review rather than the first call. Investors are prone to it because nearly everything a fund sees was prepared for the fund.
Board packs, investor updates and the financing data room are written for investors; a fund working in English gets them in English whatever the branches use. Licensable records are made elsewhere, by agents, dispatchers and technicians writing for colleagues and customers. That is our reasoning, not a measured finding.
A language policy does not close the gap. In Harvard Business Review in 2012, Tsedal Neeley described multinationals that mandated English as their corporate language and reported that "English-only policies can create job insecurity and dissatisfaction and generate strife between native and nonnative English speakers in cross-national teams." A mandate governs cross-border communication, not what a branch typed into its ticketing system. Country context agrees: the UAE government's fact sheet names Arabic as the official language, so an English-run Dubai head office can sit beside customer records kept in Arabic.
What the assumption does:
- A guess becomes a representation. "Data in English" on a dated brief is your statement to SourceX, made without the company's authority.
- The CEO hears an eligibility claim. "You should clear the 90% rule" is a call only SourceX's review can make.
- Scope gets bent. A share under 90% tempts a company to drop the system that pulled it down, though scope must match what would be licensed.
Six questions the CEO's team answers about record language
Ask through whoever holds the CEO relationship, once the CEO wants a conversation. The company answers from its own knowledge or, if it chooses, its own count; you record answers and dates.
| Question | The assumption it tests | A yes changes line 6 to |
|---|---|---|
| Which teams write their working notes in another language? | Leadership's language is everyone's | Those teams' records, with their language or "not yet stated" |
| Do customer-facing records follow the customer's language? | Customers write to an English company in English | Customer correspondence listed apart from internal notes |
| Which records predate English as your working language, or came with an acquired business? | Today's habits reach back through the archive | The years or units that differ |
| Are any records kept in a local language for local staff, suppliers or authorities? | One working language serves every audience | Those record types as a separate entry |
| Has anyone counted the language of the records you might offer, and on what scope? | Someone has already measured it | The company's figure with unit and scope, or "not counted" |
| Who could answer SourceX's language questions, and may the brief name them? | The CEO will field the detail | The contact the CEO chose |
Six noes make line 6 the company's dated, CEO-approved statement, never yours. Related: stating data language without guessing from headquarters and checking language coverage before suggesting global fit.
A Dubai-run group, first draft and sent brief (Illustrative)
Illustrative: a generic company, invented facts, no outcome implied.
A fund's Singapore office holds a minority stake in a facilities-management group: 260 full-time employees, a Dubai head office, a dispatch team in Kochi, India, and a Riyadh branch. Its CEO, board and investor updates work in English. The CEO wants a conversation; a London platform manager drafts the brief.
| Line | First draft | Sent version |
|---|---|---|
| 1 | "London platform team" | Platform manager, London; Channel Partner Agreement signed 2026-09-14 |
| 2 | "CEO keen" | The Singapore deal partner holds the relationship; CEO asked on 2026-10-20 |
| 3 | "English-speaking company" | Observed: board, investor updates and website in English (context, not records) |
| 4 | "Dubai HQ, so covered" | Stated: entities in the UAE, India and Saudi Arabia under one parent |
| 5 | "Full data room available" | Stated: work orders and technician notes since 2015, customer email since 2018, call recordings |
| 6 | "Data in English, should clear 70%" | Stated: work-order fields in English; Kochi technician notes mix English and Malayalam, not counted; Riyadh customer email mostly Arabic, not counted; call recordings not yet stated |
| 7 | Left blank | Stated: made by the company; client-contract limits unknown; never licensed for AI training |
| 8 | Left blank | How the 90% condition applies across three entities; program fit; final measure; client-contract rights |
Each draft line is a belief; each sent line is the company's answer, unknowns showing. The technician notes, probably the richest records, are the least certain on language, and the brief says so instead of rounding up.
Handing off what the brief cannot answer
Route questions that sound like the partner's and are not.
- Whether the geography sentence covers an entity, or a group spanning both sides of it: SourceX. Quote the sentence and add nothing.
- Rights under local law, client contracts and privacy: the company's own counsel, then SourceX's rights review (see the guide to licensing risk).
- Translation of records: the company's call; the brief notes what it says was translated.
- Your own tax, reporting or professional obligations on a reward: your own adviser, in your country.
- The company's money: SourceX and the company, directly. Terms section 4: "The referral reward is paid separately by SourceX and is never deducted from the supplier's agreed compensation." The company receives the same amount with or without a partner.
Closing the brief: send, hold, ask SourceX or stop
Every brief ends with one dated outcome. Related guides sit in the guides library.
- Send. Lines 1 and 2 complete, lines 4 to 7 in the company's words (unknowns included), and the CEO has read it.
- Hold. Line 6 is blank because nobody has asked the company. Ask, then decide.
- Ask SourceX first. An entity sits outside the published sentence, or the group spans both sides of it.
- Stop. The CEO declined, a fit fact fails (client-owned records, records already licensed for AI training, or a peak below 50 full-time employees), or the company already has contact with SourceX. Record why, and what would change it.
Limits of a language-evidence brief
- A statement is not a measurement. Line 6 records what the company says; SourceX measures the dataset offered, and the published threshold names a share without naming a unit.
- Our thesis about the fund's English view is untested. No figures on it have been published. Compare line 3 with the company's line 6 across your next ten international briefs and count mismatches.
- Programs move. Who-qualifies says SourceX's current data needs differ, including by language, and a company missing one program may fit another later.
- Questions cost goodwill. Stop when the CEO says the detail can wait for SourceX. Neeley's research is about mandates, not archives: a reason to ask, never evidence about one company.
Method note. The brief and questions were built from SourceX's who-qualifies page, program terms (version 2026-10-22.2, since replaced by version 2026-11-04) and company process page, checked 2026-10-27. They record who said what, and when; they measure no language, demand, quality or rights, and use no SourceX conversion or payout figures, since none are published.
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 company's lines are in its own words and its CEO has read them, register for a partner link, check each entity against who qualifies and read the program terms before submitting.
Drafting a referral brief and judging SourceX as an investment are separate decisions; anyone weighing the second can request investor materials 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.