This page is for fund platform teams and partners who introduce companies whose leaders work in a language other than English.
Your words, the company's words
Most translation questions in a referral are really ownership questions. Sort the text first; whose it is decides what you may do with it.
| Text | Whose it is | Can the partner translate it? | What to do instead |
|---|---|---|---|
| Your introduction message | Yours | Yes, with the meaning checks below | Send the English original underneath |
| SourceX's published pages and terms | SourceX's | No; a translated version would be your wording, not SourceX's | Link the page; explain a point in your own words, labeled as yours |
| A summary the company writes about its records | The company's | No | The company chooses whether to write one, in which language and for whom |
| The company's records | The company's | Never | Records stay with the company; you never collect, read or handle them |
| Agreements SourceX sends the company | Between SourceX and the company | No | The company's counsel reads them; questions go to SourceX |
The sample Channel Partner Agreement backs the last three rows from SourceX's side: section 4.2 gives a partner no authority to pass on a supplier's records, inventory, raw data or personal information, and section 7.1 says the partner "is not an agent of SourceX and may not commit SourceX to prices, licenses, payouts or other obligations." A translated message that sounds like SourceX speaking crosses that second line without meaning to.
When does the CEO need your message in another language?
Use a four-part test. Translate when the first three answers are yes and the fourth can be arranged.
- The reader decides, or was named by the person who does. The CEO, or an adviser the CEO asked to read your note. A translation for someone who cannot decide only adds a step between you and the CEO.
- They would read English with real difficulty. Base this on the CEO's own preference or what the relationship holder knows, never on the country: an address says nothing reliable about one person's reading habits.
- The CEO has shown interest in hearing more. A translated first approach to someone who has not asked is still an unsolicited approach, now with extra effort attached that can read as pressure.
- A second fluent reader can check it. If nobody can, send a short plain-English note and offer a conversation with a colleague who speaks the CEO's language.
Do not translate when the CEO already works in English, when the only text that needs translating is SourceX's terms (link them instead), or when the person asking for a translation cannot decide for the company.
What translation leaves untouched in SourceX's sentence
Language comes up twice in a cross-border referral: the language your message is in, and the language the company's data is in. Only the second appears in SourceX's published 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.
For the first half of that sentence, SourceX's FAQ says: "Yes, for companies in the U.S., Canada and the EU: multilingual and non-English data can be valuable, so tell us the languages involved." For the second half, the English condition applies to the data, and how a company counts its own share is set out in English-language data referral eligibility.
Translating your message changes none of this. Nor should a partner suggest that a company translate its records to meet the condition: none of the SourceX pages cited here says a translation would change how the sentence applies, and only SourceX could answer that question if a company chose to ask it. Keep the language of your note and the language of the company's records on separate lines of your file.
The translation review and meaning checklist
Eight meanings carry the whole introduction. If any one of them drifts in translation, the CEO is evaluating a different proposal from the one you meant.
| Meaning | Carry it as | Drift to catch |
|---|---|---|
| 1. SourceX decides fit | "This may be a fit; SourceX decides after its own review" | "You qualify", "you are approved", "eligible" as a statement of fact |
| 2. The CEO decides | "You, as CEO, decide whether to talk to SourceX" | "Your team can approve this", "finance can sign off" |
| 3. Who could be paid | "SourceX may pay me a referral reward; your company's payout is the same either way" | "A commission from your payout", "a fee you pay me" |
| 4. No records wanted | "I don't need any files, samples or exports" | "Send a sample so I can check" |
| 5. A license, not a sale | "Companies license data; they keep their originals" | "Sell your data", "buy your database" |
| 6. No agency or endorsement | "I am an independent referral partner" | "On behalf of SourceX", "SourceX's representative" |
| 7. Nothing promised | "No offer or payment is promised" | "You will be paid", "an assured offer" |
| 8. SourceX's pages stay the reference | Links to SourceX's own pages | A translated summary presented as the terms |
Row 3 rests on section 4 of the terms, which says the reward "is paid separately by SourceX and is never deducted from the supplier’s agreed compensation." Row 5 follows SourceX's FAQ, which describes deals as licenses rather than sales of a company's originals. Whether and how to disclose a reward to a client is discussed in do I have to disclose a referral fee.
How to run the check. A fluent colleague who knows the program translates your note. A second fluent person, who has not seen your English, translates it back. You compare the back-translation with your original, meaning by meaning, fix every drift and note what you changed. WHO's standards for translating one of its questionnaires follow the same pattern: translators fluent in both languages, forward and back translations made independently by different people and then compared, and a panel to settle differences (our paraphrase of a search excerpt). A referral note needs no panel; the two-reader rule is the part worth borrowing.
Send the translation with your English original beneath it, so the CEO can check any line against what you actually wrote.
A Brazilian CEO and an Italian CEO (Illustrative)
Illustrative: invented companies, people and figures, with no outcome implied.
A logistics company in Brazil. A fund's São Paulo venture partner knows the CEO of a 400-person freight company and learns that he prefers to read in Portuguese and wants to hear more. The partner's note is translated and back-translated; the back-translation of row 1 came back as "your company is eligible", so the line is rewritten. Brazil sits in Latin America, so the English condition applies to the company's data. The CEO's operations team estimates that most dispatch notes are written in Portuguese. The partner records that as the company's own estimate, says nothing about translating the notes, and tells the CEO that any question about it belongs with SourceX. File entry: "No fit for now on the company's own count; the CEO knows where to ask."
An engineering firm in Italy. A London fund's partner introduces the CEO of a 250-person engineering firm who reads English slowly and asks for Italian. Italy is in the EU, the first half of the sentence, and the FAQ asks such companies to tell SourceX the languages involved. The note is translated and checked; the firm's records stay in Italian, untouched by anyone outside it. After the CEO's written yes, the partner, who has signed the Channel Partner Agreement, makes the introduction. Whatever the firm later prepares for SourceX, and in which language, is the firm's own choice.
In both cases the message changed language and the records did not move.
Who answers the questions translation raises
| Question | Who answers it |
|---|---|
| What does a clause in SourceX's terms or agreement mean? | SourceX, and the company's own counsel |
| Does SourceX provide its materials in other languages? | SourceX |
| What share of the company's data is in English, counted how? | The company, using its own method |
| Would translated records change anything in SourceX's review? | SourceX, if the company asks |
| How is a partner's reward taxed? | The partner's own tax adviser |
This page gives no legal, tax or certification advice. For records whose language is unclear, the evidence note in stating data language without guessing from headquarters shows what a company can record, and the introduction brief for an English-operating international company covers groups that run in English while their records may not be. Groups with entities in several countries raise the questions in what to ask about overseas subsidiaries.
Closing the file: a next step or a no-fit
Every translated approach ends in one dated line: the language the note was sent in, who checked it, any drift found and fixed, the CEO's answer, and the next step or the reason for no fit. Keep the English original and the back-translation together for as long as your own record policy keeps the introduction.
Method note. The test and checklist apply SourceX's screening page, FAQ, program terms (Version 2026-10-22.2, since replaced by version 2026-11-04) and the unsigned sample of its Channel Partner Agreement, all read on 2026-10-27, with WHO's questionnaire translation standards as the model for the two-reader check. They measure nothing; no figures on translated introductions have been published.
Where translated outreach goes wrong
- Confident fluency. A colleague who speaks a language socially may miss business or legal register. The second reader exists to catch it.
- Back-translation is not proof. A clean back-translation shows that meanings survived; it cannot show that the tone suits the CEO.
- Forwarded translations. A CEO may forward your translated note internally as if it described SourceX's terms. The English original underneath and the links to SourceX's pages limit the damage.
- Stale wording. When SourceX publishes new terms, re-check rows 3, 7 and 8 before reusing a translated note.
- Language as a proxy. A CEO who prefers another language may run a company whose records are in English, and the reverse. Never infer one from the other.
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 a checked translation has done its job and the CEO wants the conversation, register as a partner, confirm the company against who qualifies and read the program terms in SourceX's own words before introducing it. More cross-border guidance is collected in the guides hub.
Introducing a company in another language is referral work; evaluating SourceX as an investment is a different matter, and the SourceX investor overview is the place to request materials for it.
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.