# Company expansion data referral complexity | SourceX

Canonical: https://refer.sourcex.si/guides/what-a-geographic-expansion-reveals-about-referral-complexity
Last updated: 2026-11-04

A geographic expansion usually means a company now keeps records in more than one legal entity, under more than one privacy regime and in more than one language. That does not make it a weaker referral, but it changes four questions: which entity created the records, whose CEO authorizes the conversation, whether those records meet the language rule for their location, and whether personal data would cross a border. Read the expansion announcement's own wording for those clues before anyone is introduced.

The location rule is short and exact: 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. SourceX's home page adds two details that matter for expansions: it prioritizes companies in the U.S., and Latin America covers Mexico, Central America, South America, the Dominican Republic, Haiti and Puerto Rico, not Cuba. Programs also differ in geography and language, so a company that misses one program may fit another later.

## An expansion announcement is a structure signal, not a size signal

The growth signal here is a dated public statement that the company now operates somewhere new: a press release, a subsidiary registration, a new office page, an acquisition announcement or a support page in another language. Its source is the company's own wording, and that wording is evidence. Headcount growth answers "how many"; an expansion answers "where, in which entity and in which language". Each answer adds a row to the referral rather than points to a score.

The core screen does not change: 50 or more full-time employees at peak, contractors excluded, years of original records, rights to license them and a CEO who wants the conversation. How a multi-entity group is counted and scoped is settled in SourceX's review, so describe each entity separately. For a foreign group's American arm, see [introducing the US subsidiary of a foreign client](/guides/how-introduce-us-subsidiary-foreign-client).

## The expansion authority-language review

Run two passes over the same announcement. The first reads its authority words, the second its language words, and a short border check follows.

**Pass 1: authority words.** The verb a company chooses tells you which entity holds the new records and who decides about them.

| Wording in the announcement | What it usually means for the records | Who authorizes | Question for the relationship owner |
|---|---|---|---|
| "Opened an office in" or "hired a team in" | Same legal entity or a branch; new staff usually work in the existing systems | The company's CEO | Do the new team's records sit in the same systems as headquarters? |
| "Established a subsidiary" or a local legal suffix such as GmbH, Ltd or S.A. de C.V. | A new legal entity with its own employees and possibly its own systems | The CEO of the company being introduced | Which entity employs the people who create the records? |
| "Acquired" | Older records arrive, created under the seller's ownership | The acquirer's CEO, not the seller's former CEO | Did the purchase transfer the records, and has integration finished? |
| "Entered through a distributor", "reseller" or "franchise partner" | The partner creates the market's records in its own systems | The partner is a separate company; those records are not this company's to license | Whose systems hold customer and service records in that market? |
| "Now serving customers in" with no local entity | Records stay at home but now describe people abroad | The company's CEO | Do home systems now hold personal data about people in the new market? |
| "Moved its headquarters to" | The location rule may now read differently | The company's CEO | Where is the company registered and run from today? |

A parent and its subsidiaries count as one company for the reward, so the USD 50,000 floor applies once, to the group's first qualifying transaction, however many entities license, and later qualifying transactions agreed within 12 months pay 15% with no cap; the [subsidiary guide](/guides/subsidiary-referral-reward-cap) works through it.

**Pass 2: language words.** Phrases such as "launched Spanish-language support", "bilingual team" or "local-language service desk" mean new records are being written in another language. Apply the location rule entity by entity:

| Where the entity holding the records is | What the published geography asks | What to record |
|---|---|---|
| U.S., Canada or the EU | Location qualifies with no language threshold | The working languages anyway, since language can affect which datasets fit |
| UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE or Saudi Arabia | At least 70% of the data in English | The company's own estimate of the English share, system by system |
| Anywhere else | Not on the published list | Describe it separately and keep it out of the fit case |

The system-by-system arithmetic for that estimate is in the [English-language eligibility guide](/guides/english-language-data-referral-eligibility).

**The border check.** If the records include personal data about people in the EU and would be processed outside the European Economic Area, the European Commission's rules allow the transfer only on an adequacy decision or, where there is none, appropriate safeguards such as standard contractual clauses. A partner does not resolve that; it notes the question for SourceX's rights review, which already asks whether records can be licensed without breaching employee privacy, client confidentiality or third-party contracts.

**Method note.** The review was built on 2026-10-26 from the published geography and screening profile, the home page's Latin America definition, the program rule that a group counts as one company for the once-per-company floor and the European Commission's transfer rules. It does not assess demand for any entity's records, the content of purchase agreements or privacy law outside the EU; those belong to SourceX's review.

## Two expansions, one set of questions (Illustrative)

Illustrative. Two generic groups with invented details; no outcome is implied.

The first grew by hiring. A U.S. building-automation services company with 420 full-time employees at peak and 18 years of work orders in one field-service system announced in 2024 "a subsidiary in Monterrey, Mexico", where 70 technicians and dispatchers work in Spanish in a separate dispatch tool. The second grew by buying. An engineering services firm in Pune, India, with 900 full-time employees and 21 years of English-language design reviews announced in 2023 that it had "acquired" a German design consultancy of 150 people whose 30 years of project files are mostly in German.

| Question | Hire-led: U.S. company and Mexican subsidiary | Acquisition-led: Indian firm and German consultancy |
|---|---|---|
| Which entity created the records | The U.S. company holds 18 years; the subsidiary holds two | Both: 21 years in India and 30 years in Germany, the latter under its previous owner |
| Location and language | The U.S. company qualifies on location; Mexico sits in Latin America, so the 70% English rule applies there, and mostly Spanish dispatch notes would not meet it on their own | India requires 70% English, so the firm estimates its share by system; Germany is in the EU and qualifies on location, though German files may limit which datasets fit |
| Border check | Any personal data in the Mexican records raises a local privacy question for the rights review | German files containing personal data and processed outside the EEA need an adequacy decision or appropriate safeguards |
| Who authorizes | The U.S. company's CEO | The group CEO in Pune; the German managing director owns the records and prepares the case |
| Reward basis | One company: the USD 50,000 floor once, on the group's first qualifying transaction; 15% on repeats within 12 months; no cap | One company: the USD 50,000 floor once, on the group's first qualifying transaction; 15% on repeats within 12 months; no cap |

The hire-led expansion adds little licensable history and a language complication that is easy to scope out: the U.S. company's 18 years are the case. The acquisition-led expansion imports a deeper archive than the buyer's own, but in German, under EU transfer rules and created under a former owner, so it needs the purchase documents and a rights review before it counts. Two partners who each know one half of that group should not each introduce their half; whether an earlier contact with one entity affects credit for the other is not settled in the terms, and SourceX decides it in duplicate review.

## Does the expansion reveal operating history, or only footprint?

Usually footprint. A new office or subsidiary has months of records, often in a new tool, and those records describe a start-up phase rather than settled work. An acquisition is different: it can bring decades of history at once, and SourceX's home page notes that acquired companies can qualify. Whether the buyer can license those records depends on how the purchase was structured; [asset and stock sales](/compare/asset-sale-vs-stock-sale-data-ownership) move records and rights differently.

Two dates matter more than the announcement: the expansion date, which divides records written in one entity and language from records written in several, and any announced system consolidation, when an acquired or new entity moves onto group systems. A consolidation with a cutover date is real urgency to keep exports; a launch party is not. The [operational complexity guide](/guides/how-to-assess-operational-complexity-without-requesting-confidential-files) lists other outside signs of how many systems a company runs, without asking for files.

## Order expansion-stage conversations by settled ownership, then leadership bandwidth

Rank entities, not groups, with four rules applied in order:

1. **Settled ownership and a long single-language history** come first.
2. **Acquired entities** follow once the purchase has closed and the records' ownership is documented.
3. **New entities** come last and get a revisit date for when they have history.
4. **Leadership bandwidth** can delay any of them: a launch quarter or an integration absorbs the people who would take the call, so ask through the board member who knows the calendar, or wait.

| Order | Entity (Illustrative) | Ownership | History | Language | Bandwidth now |
|---|---|---|---|---|---|
| 1 | U.S. building-automation company | Settled | 18 years | English | Normal |
| 2 | Indian engineering firm | Settled | 21 years | English share to estimate | Integration under way |
| 3 | German design consultancy | Acquired 2023, closed | 30 years | Mostly German | Integration under way |
| 4 | Mexican subsidiary | Settled | 2 years | Mostly Spanish | Launch phase |

## Five ways an expansion reading can mislead

- **Announcements overstate.** "Opened an office" can mean a sales desk in a shared workspace. The entity record and the people listed there tell you more than the press release.
- **Your reading is not a language measurement.** The company estimates its English share by system, and SourceX reviews it on the records proposed.
- **Privacy law beyond the EU is outside this review.** The border check names one regime because its transfer rules are published and clear; others exist and the rights review reads them.
- **Program criteria move.** Geography and language requirements differ by program, and SourceX prioritizes U.S. companies, so a non-U.S. entity in a qualifying group may be weighed differently.
- **Group credit is not a formula.** Beyond counting as one company for the once-per-company floor, how related entities affect attribution is decided case by case in duplicate review.

**A measurable next step.** Take the last 12 expansion announcements in your network and run both passes. Count how many add a legal entity, how many change the language mix of the records and how many name a dated system event. After a quarter, compare which of those companies agreed to a conversation. SourceX has not published figures on how expansions affect review outcomes, so your tally would be original evidence.

## 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.

Once the review shows which entity holds the history and its CEO wants the conversation, [register for a partner link](/register), confirm the fit facts on [who qualifies](/who-qualifies) and read the [program terms](/terms), including the duplicate rules, before you submit.

Reading a portfolio company's expansion is referral work; deciding whether SourceX is a company you might invest in is separate, and that conversation starts with a request for materials on the [SourceX investor overview](https://sourcex.si/investors).

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/who-qualifies
- https://refer.sourcex.si/
- https://refer.sourcex.si/terms
- https://commission.europa.eu/law/law-topic/data-protection/international-dimension-data-protection/rules-international-data-transfers_en
- https://sourcex.si/investors
