# Regional fund referral coordination workflow | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-coordinate-a-referral-across-regional-fund-offices
Last updated: 2026-11-05

When two or more of a fund's regional offices know the same company, agree on one speaker before anyone contacts it: normally the person with a direct, current relationship with the CEO of the company that holds the records. Write the choice down with a date in one shared log, let the other offices send their context through the speaker, and keep location facts on separate lines. Offices coordinate who speaks to the company, not who gets credit. Only one introduction can be credited, and SourceX settles overlapping cases in duplicate review from dated records.

This page is for platform leads and operating partners at funds with offices in several countries.

## Three offices, one company, one week

A multinational company touches many regions at once. One office meets its CEO on a panel, another backs a supplier that sells to its subsidiary, a third has a partner on its advisory board. Without coordination, the company can hear about SourceX from the same fund three times in a week, each time slightly differently, and SourceX can receive three claims for one company.

The terms leave no room for a shared result. Section 2 says "Only one partner is credited per company," decides attribution from dated records and adds that "an earlier link click alone does not decide credit." Section 3 goes further: a company SourceX already knew, whether through an application, an account, a lead or nothing more than an exchange of emails, is a duplicate and is credited to no later partner. Internal coordination cannot change either rule; it can only stop the fund from creating the overlap in the first place.

## What offices settle, and what they leave alone

| Question | Who settles it | How it is recorded |
|---|---|---|
| Which person speaks to the company | The offices, together, before contact | A dated line in the fund's shared log |
| When, in which language and through which channel | The speaker, guided by the CEO's preferences | The speaker's own note |
| Whether the company talks to SourceX at all | The CEO of the company that holds the records | The CEO's written answer |
| Whether the company fits a current program | SourceX's review | SourceX's decision |
| Which introduction, if any, is credited | SourceX, from dated records | SourceX's decision; any dispute goes to SourceX with evidence |

The first two rows are the fund's business. The last three are not, and no internal rule should pretend to decide them.

## The single-owner global workflow

Six steps, one owner per company. The owner of the log entry is usually someone on the platform team; the speaker is whoever the tie-break order picks.

1. **Claim.** Any office that spots a company adds it to the shared log before contacting anyone: company, date, the office, and the kind of tie it holds (direct, through a sponsor, through a seat with duties attached, or public facts only). A claim is a request to be considered, not a right to speak.
2. **Hold.** The log entry stays open for two working days in the latest time zone among the fund's offices, so every office can add its own tie. This is our suggestion for a sensible pause, not a SourceX rule; pick a window your offices can keep.
3. **Choose.** The log owner applies the tie-break order below and names one speaker, with the reason, in the log. Every other office reads the decision before doing anything else.
4. **Speak.** The speaker asks the CEO once, says that the fund could receive a referral reward and that the company's payout is the same either way, and links SourceX's own criteria rather than promising fit. The payout point rests on section 4 of the terms, under which the reward "is paid separately by SourceX and is never deducted from the supplier’s agreed compensation." Other offices send any useful context to the speaker, never to the company.
5. **Submit.** If the CEO says yes in writing, the speaker submits, or a colleague submits with the speaker's written consent; either way the submitter must already hold an approved account and have signed the Channel Partner Agreement. The agreement's sample text says each introduction record identifies the company, domain, partner, opportunity, introduction method and timestamps, so make sure your own copy holds the same.
6. **Release.** The log entry closes with one dated outcome: introduced, declined by the CEO, waiting on a named question, outside the published sentence, or revisit on a named trigger. A declined company is not reopened by a different office next quarter without a new reason.

The agreement's sample also says a competing attribution claim "must be recorded and resolved in good faith." Inside a fund, the log is where that starts; between partners, SourceX is where it ends.

## Choosing the speaker: a tie-break order

This order is the fund's internal choice. It ranks ties by how directly and freely they reach the person who decides.

| Rank | Tie | Who speaks |
|---|---|---|
| 1 | A direct, current relationship with the CEO of the company that holds the records | That person |
| 2 | A relationship with someone the CEO trusts, who agrees to carry the question | The person who holds that relationship, through the sponsor |
| 3 | A tie that comes with duties, such as a board or advisory seat or a confidentiality agreement | Only if no rank 1 or 2 tie exists, and then only with one question to that company's own CEO |
| 4 | Public facts only | Nobody; park the entry until a real tie appears |

**Equal ties.** If two offices hold rank 1 ties, ask whichever relationship the CEO would expect to hear from; if nobody can tell, pick the office that shares the CEO's working language and time zone, and record why.

**Never a reason.** Who logged first, seniority, the size of an office, or who expects to be paid. None of these reaches the CEO any better.

Whatever an office learned through a board or advisory seat may prompt one question to that company's own CEO. It never travels to the speaker, to another office or to another company.

## Location facts every office logs on its own line

Facts from different countries are easy to blur together; SourceX keeps them apart, so every log entry holds four separate lines:

- **Where the speaker and the submitter are.** SourceX's screening page 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." An office unsure where it stands asks SourceX before speaking.
- **Where the company is.** The published sentence, 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.
- **What language the records are in,** where that condition applies. The company counts, using the approach described in [English-language data referral eligibility](/guides/english-language-data-referral-eligibility); no office counts for it.
- **Who decides.** The CEO of the company that holds the records, named with the date you confirmed it.

The office's own country appears on the first line only. It says nothing about the company.

## Four offices and a Dutch group (Illustrative)

Illustrative: an invented fund, people and company, with no outcome implied. A fund with offices in New York, London, Singapore and São Paulo looks at a 900-person software support group headquartered in the Netherlands, with a subsidiary in India.

- **New York, day 1.** An associate saw the group present at a conference and logs it. Tie: public facts only.
- **London, day 1.** A partner has spoken with the group CEO every quarter since they shared a panel. Tie: direct and current, rank 1.
- **Singapore, day 2.** A principal knows the CEO of the Indian subsidiary, which is a separate company with its own decider. Tie: direct, but to a different company.
- **São Paulo, day 2.** A venture partner sits on the group's advisory board. Tie: rank 3, with duties attached.

On day 3 the log owner names London as speaker for the Dutch parent, whose support records prompted the claim. São Paulo stays silent and shares nothing from the advisory board. Singapore and London agree that Singapore waits until the group CEO has answered, so the group does not hear from the fund twice in one week; if Singapore later asks the Indian subsidiary's CEO, that is a separate introduction of a separate company.

What stays open: whether the group had any earlier contact with SourceX (the CEO confirms), which records each entity holds, and, for the Indian subsidiary, its English share by the company's own count. Two facts are settled whatever happens: the group shares one reward cap of no cap across all its entities, and how an introduction of the subsidiary relates to one of the parent is for SourceX to decide in duplicate review, not for London and Singapore to agree between themselves. For the subsidiary questions in more depth, see [what to ask about overseas subsidiaries before an introduction](/guides/what-to-ask-about-overseas-subsidiaries-before-an-introduction).

## Questions that belong to someone outside the offices

| Question | Who answers it |
|---|---|
| Can SourceX work with an office in a particular country? | SourceX |
| Does the company fit, and which introduction is credited? | SourceX, from dated records |
| Who in the fund signs the Channel Partner Agreement, and how is anything shared internally? | The fund, with its own advisers |
| How is a reward taxed for the person or entity paid? | That person's or entity's own tax adviser |
| Can records cross a border? | The company's counsel, with SourceX's review |

Nothing on this page is legal or tax advice. How one regional partner and a platform team divide the work on a single introduction is mapped in [a regional venture partner's role in global referrals](/guides/a-regional-venture-partner-s-role-in-global-referrals), and screening a whole portfolio market by market in [a global portfolio is not a single data referral market](/guides/a-global-portfolio-is-not-a-single-data-referral-market). The 90-day clock itself is explained in [what an attribution window is](/questions/what-is-an-attribution-window).

**Method note.** The workflow rests on SourceX's program terms (Version 2026-10-22.2, since replaced by version 2026-11-04), its screening page and the unsigned sample of its Channel Partner Agreement, all read on 2026-10-27. The hold window and the tie-break order are our suggestions for a fund's internal practice, not SourceX rules. The workflow measures nothing, and no figures on multi-office funds have been published.

## When coordination breaks down

- **An office speaks anyway.** Record it, tell the log owner, and do not send a second message to "correct" the first. SourceX will read the dated records.
- **The company already knows SourceX.** Then no office is credited, whoever spoke. Say so plainly to colleagues who invested time.
- **The speaker leaves the fund.** The log keeps the CEO's answer and the date. A colleague asks the CEO again before submitting anything, rather than relying on an old yes.
- **Time zones stretch the hold.** Two working days across four offices can become four calendar days. Keep the window anyway; a rushed call is the usual source of a second message.
- **Pressure from the reward.** An office that could be paid has a reason to push for the speaker's role. Choosing by tie, in writing, keeps that reason visible.

## 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 log names one speaker and the CEO has answered yes in writing, the person who will submit should [register](/register) and sign the agreement, test the company once more against [who qualifies](/who-qualifies) and keep the [program terms](/terms) open while the introduction is written. Other cross-border workflows are listed in the [guides hub](/guides).

Coordinating offices on an introduction is referral work; deciding whether SourceX is worth investing in is a separate question, and the [SourceX investor overview](https://sourcex.si/investors) is where materials for that can be requested.

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://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://sourcex.si/investors
