# International company referral screening grid | SourceX

Canonical: https://refer.sourcex.si/guides/why-geography-is-only-one-part-of-referral-qualification
Last updated: 2026-11-05

A company's country tells you whether it can be considered, not whether it qualifies. Four more gates sit behind location, and none of them depends on a map: 50 or more full-time employees at peak, a documented operating history, rights to license the records it would offer, and a CEO who knows about and wants the conversation. Outside the U.S., Canada and the EU a language test applies as well. Screen all of them on one grid before anyone at the fund promotes the company to a founder, an LP or SourceX.

In an international network, a country name gets treated as a verdict: "they're in Germany, so they qualify", "they're in Brazil, so forget it". Both shortcuts fail, and the first fails in public, after someone has told a founder it looks good.

## What the published location rule settles, and what it leaves open

The current criteria come from two dated SourceX pages: the who-qualifies page (updated 20 Oct 2026) and the program terms (Version 2026-10-22.2, since replaced by version 2026-11-04). The location rule, verbatim: 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 terms add the size floor: introduced companies need 50 or more full-time employees at peak. SourceX also says its current data needs differ by company size, operating history, geography, language and data category, and that it applies the criteria of the specific program rather than one universal minimum.

Four phrases in that rule get misread more than any others.

| Phrase | What the published sources say | What it means on a screen |
|---|---|---|
| "the EU" | The EU's own site lists 27 member states | Switzerland, Norway and Iceland are in Europe but not in the EU, and not on the list; the UK is listed separately, with the English test |
| "Latin America" | SourceX's referral home page: Mexico, Central America, South America, the Dominican Republic, Haiti and Puerto Rico, not Cuba | A Chilean or Mexican company can be considered when at least 70% of its data is in English |
| "at least 70% of the data is in English" | Applies outside the U.S., Canada and the EU | A Spanish or French company faces no language test for location, though a particular program may still care about language |
| "based in" | The referral site asks partners to introduce companies based in the listed places | The place where the operating company sits; unclear for cross-border groups, covered below |

Your own location is a separate test: partners can join from most countries, though not from countries or regions under U.S. sanctions or on U.S. restricted-party lists. The [guide for partners outside the United States](/guides/global-partners-referring-us-businesses) covers that side.

## Pin down the operating entity and whoever controls it today

Location attaches to a company, so decide which company first. In a cross-border group the brand on the pitch deck, the entity that employs the people and the entity whose systems hold the records can sit in three countries. Three metadata questions settle it:

1. **Which legal entity employs the full-time staff who create the records?** Ask for the peak count, contractors excluded.
2. **Which entity's systems hold those records, and where is it based?**
3. **Who controls that entity today?** The founder, a fund, a parent company or a court-appointed officer. The CEO of that entity authorizes a licensing discussion and signs for it; a fund's shareholding does not, and in a receivership or bankruptcy the CEO alone may not be enough.

When all three answers point to one entity in a listed place, the location gate is done. When the headquarters is in a listed country but the staff and records sit in a subsidiary elsewhere, the published sentence does not decide the case, so neither should you: mark it "route". One group rule is settled, though it concerns rewards, not location: the USD 50,000 floor on a referred company's first qualifying transaction is counted once for a parent and its subsidiaries together. The [guide to companies that operate across several countries](/guides/how-to-refer-a-company-that-operates-across-several-countries) covers multinational structures.

## The geography-language-rights screening grid

Five gates, read left to right. A company must clear every gate a partner can check from the outside. Anything a partner cannot check goes to SourceX as a stated question, never as an assumption.

| Gate | The question | Evidence you can gather without seeing records | Clear | Stop | Route to SourceX |
|---|---|---|---|---|---|
| 1. Location | Is the operating company based in a listed place? | Registered address and where the staff work | U.S., Canada, an EU member state, or another listed place once gate 2 clears | A place that is not on the list | Headquarters and operations in different places |
| 2. Language | Outside the U.S., Canada and the EU, is at least 70% of the data in English? | The company's own estimate, system by system | Estimate of 90% or more for the records in scope | The company's own estimate is well below 90% | Estimate close to 90%, or nobody has counted |
| 3. Rights | Did the company create the records, and can it license them without breaching client confidentiality, employee privacy or third-party contracts? | Who created each record family, and whether clients own it | Records the company made about its own work | Records that belong to clients | Mixed ownership, or personal data about people in other jurisdictions |
| 4. Size and history | 50+ full-time employees at peak and several years in operation? | Peak headcount and founding year | Both met | Peak below 50 | Peak near 50, with contractor questions |
| 5. CEO | Does the CEO know, and want the conversation? | The relationship owner's confirmation | The CEO agreed | The CEO declined | Nobody has asked yet |

Gate 3 is where geography misleads most. A company's address does not settle which privacy laws reach its records. Under Article 3(2) of the EU's General Data Protection Regulation, the regulation can apply to a controller with no establishment in the Union when it processes personal data of people in the Union in connection with offering them goods or services, or monitoring their behavior there. An Indian support center serving European consumers carries rights questions its location never answers. A partner records the question; SourceX's rights review and the company's counsel answer it.

## Five companies through the grid (Illustrative)

Illustrative: invented companies, screened only on what a relationship owner could learn in one conversation. None of these rows describes a SourceX decision.

| Company (Illustrative) | Location | Language | Rights | Size and history | CEO | Grid result |
|---|---|---|---|---|---|---|
| A. 240-person software testing firm in Poland | EU member state: clear | No test for location | Its own test plans and defect histories: clear | 11 years, peak of 260: clear | Agreed | Introduce, with the CEO's consent |
| B. 310-person customer support center in India | Listed: clear once language clears | Company estimates 95% English | Most tickets belong to its clients' customers: route | 8 years: clear | Agreed | Route: introduce only with the rights question stated, scoped to its own SOPs and QA rubrics |
| C. 180-person freight forwarder in Brazil | Latin America: listed | The COO estimates about 60% English | Its own shipment exception records: clear | 14 years: clear | Interested | Stop: fails the 70% English test on today's published criteria |
| D. 400-person engineering consultancy in Switzerland | Not an EU member and not listed: stop | Not reached | Not reached | Not reached | Not asked | Stop: outside the published list |
| E. 260-person group, U.S.-incorporated, staff and records in a Vietnamese subsidiary | Holding company listed; operating entity not | Not counted | Its own project records | 9 years | Agreed | Route: ask SourceX how the location rule applies before any promotion |

**Company C is the rejected example, and the reason the grid exists.** On location alone it looks like a fit, because Latin America is on the list. It fails the published language test on its own COO's estimate. So the platform team does not promote it, does not tell the founder "maybe", and records what would change the answer: records in scope reaching 70% English, or a change in the published criteria. Fourteen years of history do not cure it. SourceX has not reviewed company C; the stop is the screener's call, and SourceX's own page leaves room for a company that misses one program to fit a later one.

Company B is the opposite trap: location and language clear easily, and the case still turns on rights. Even company A earns "introduce", not "qualifies", because SourceX checks relevance to its current data needs in review.

## Mandate, language and history: what to ask next

Every follow-up stays at metadata level. The relationship owner asks; nobody sends a file.

- **Language.** "Across the systems you would consider, roughly what share of the records is in English? Count it yourselves, system by system." The [English-language eligibility worksheet](/guides/english-language-data-referral-eligibility) shows the counting method. Never ask for a sample to prove the share.
- **History.** "How many years of records are still kept, and in which systems?" Founding year overstates history when a migration dropped the old archive.
- **Mandate.** "Which kinds of records are these: tickets, project files, QA logs, call notes?" A partner names the record families; SourceX judges relevance in review.
- **Control.** "Has ownership changed recently?" An acquisition can move both the authorizing CEO and the entity holding the records.

For a quick first pass on a single company, the [company fit checker](/tools/company-fit-checker) gives a preliminary, non-binding read. For a whole portfolio, the [portfolio company screening workbook](/resources/a-portfolio-company-screening-workbook) holds one row per company and pairs with this grid.

## Where a case goes when the grid cannot decide

The words used at this point decide whether the relationship survives a "no".

| Grid result | What the relationship owner tells the company | What nobody says |
|---|---|---|
| Introduce | "This looks like a fit on the published criteria, and SourceX reviews it with you directly" | "You qualify" or "you will be accepted" |
| Route | "One question needs SourceX's answer before we take this further" | "It's a formality" |
| Stop | "On today's published criteria this does not fit, and criteria can change" | "SourceX turned you down", since SourceX has not reviewed it |

Route questions go to SourceX at metadata level: the entities, the location question and the record families. Only a partner who has signed the SourceX Channel Partner Agreement submits introductions. The [qualification checklist](/resources/company-qualification-checklist) lists the remaining fit questions.

## Where this grid can mislead

- **Criteria move.** SourceX calls its profile screening guidance that varies with its current data needs. Date every printed grid.
- **Self-estimates.** The language gate runs on the company's own count, and a rushed one can land on either side of 90%.
- **Law the grid does not model.** Rules such as GDPR Article 3(2) follow the people in the records, not the company's address, and SourceX's own rights test names client confidentiality, employee privacy and third-party contracts. The grid flags these questions and resolves none.
- **Demand.** Five clear gates do not mean the records match a current program; a clean row can still be declined in review.
- **Group structures.** A grid filled in at holding-company level can pass a company whose operating entity would not.

**How the grid was built.** Gates and thresholds come from SourceX's who-qualifies page (updated 20 Oct 2026), the referral home page's definition of Latin America, the program terms (Version 2026-10-22.2, since replaced by version 2026-11-04) and the EU's list of member states, all read on 26 Oct 2026. The grid measures only what a partner can learn without seeing records. It does not measure demand, record quality or acceptance rates, none of which SourceX has published. For the wider portfolio program, start with the [overview for venture platform teams](/for/venture-platform-teams).

## 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 company clears every gate a partner can check, [register for a partner link](/register), set its row beside [who qualifies](/who-qualifies) and take the [program terms](/terms) in full before the relationship owner asks the CEO.

Readers weighing SourceX as a possible investment, rather than as a place to refer a company, can request investor materials through the [SourceX investor overview](https://sourcex.si/investors); that diligence runs on its own track, apart from this grid.

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://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://refer.sourcex.si/
- https://european-union.europa.eu/principles-countries-history/eu-countries_en
- https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng
- https://sourcex.si/investors
