# Disputed investor introduction: escalation path | SourceX

Canonical: https://refer.sourcex.si/guides/the-escalation-path-for-a-disputed-investor-introduction
Last updated: 2026-11-05

SourceX decides which partner is credited, from dated records, and an argument between investors does not change that. When two funds claim one introduction, a VC ecosystem lead's job is to keep the dispute small: stop all outreach, separate what SourceX decides from what the funds owe each other, send SourceX one evidence-first packet, and treat the partner agreement's 30-day notice and arbitration clause as the last rungs. Nobody asks the company's CEO to referee.

Overlapping networks make this ordinary: a lead fund's platform team, a co-investor's partner and an angel adviser can all know one CEO, and each can believe the introduction was theirs. Below is the route a disagreement should travel, the packet that travels with it and the points where it should stop.

## The credit question and the investor question are different disputes

Most quarrels between funds bundle two questions. The first is which introduction SourceX credits. Section 2 of the program terms answers it: the first valid introduction of a company new to SourceX, made inside the 90-day attribution window, earns credit once that company submits a verified application; only one partner is credited; and the decision rests on dated records. Section 3 removes any company that already had an application, a relationship or an earlier valid introduction with SourceX, and it counts any earlier lead, account or email exchange as a relationship. The second question is what the funds promised each other, and the terms say nothing about agreements between partners, so it stays with the funds.

| Question | Who answers it | Where it is written | Where it goes if it stays open |
|---|---|---|---|
| Which introduction is credited? | SourceX, from dated records | Terms, sections 2 and 3; Schedule A, paragraph 2 | SourceX review at hello@sourcex.si (terms, section 7) |
| Did SourceX apply its terms correctly? | SourceX first, then the agreement's dispute clause | Terms, sections 7 and 12; partner agreement 7.4 | Written notice, 30 days of discussion, then arbitration |
| Which fund was meant to make the ask? | The funds | Your inter-fund note, if one exists | Between the funds, outside the program |
| May a fund's staff accept a reward? | Each fund | That fund's own policy | Inside the fund |
| Does the company want the conversation? | The company's CEO | The CEO's dated written answer | Nowhere: nobody overrides it |

Sorting a dispute into these rows usually shrinks it: two funds that agreed in writing who would introduce often have only an internal slip to correct.

## Who touched the company, in what order, with whose permission

Before anyone argues, the dispute owner on each side draws the chain on one page. One line per person, with six facts:

1. **Person and firm.** Including associates who forwarded anything.
2. **Link to the CEO.** Board seat, co-investor partner, advisory board, former colleague.
3. **First mention to anyone at the company,** with its date and to whom.
4. **Written introduction,** if any: portal submission, tracked application or sent email, with its timestamp.
5. **Partner agreement date.** The terms require the SourceX Channel Partner Agreement to be signed before an introduction is submitted.
6. **The CEO's knowledge.** A dated written yes, or nothing.

The CEO is the one accountable company contact on the chain, because under the program the CEO authorizes a licensing discussion. Record a CFO or COO who also heard from an investor, but SourceX's screening guidance says introductions made without the decision maker's knowledge are usually not a fit, so a link that reached the CFO while the CEO knew nothing is weak however early it landed. The partner agreement adds that an introduction has to be recorded in writing, and an oral one protects nothing until it is confirmed in writing (1.2). Whether investor rights require consent before a company licenses data is a separate question, covered on the main site in [do VC investor rights require consent](https://sourcex.si/insights/do-vc-investor-rights-require-consent-before-licensing-company-data).

## The evidence-first escalation packet

Evidence first means the packet exists before anyone writes an argument, and both funds use the same eight sections. Each row says what goes in, who assembles it, the first rung that needs it and what must stay out.

| # | Section | What goes in | Assembled by | First needed at | Keep out |
|---|---|---|---|---|---|
| 1 | Company identity | Legal name, website domain and the entity the CEO runs | Dispute owner, from public records | Rung 2 | Facts taken from board packs |
| 2 | Chain sheet | One line per person, with the six facts above | Dispute owner | Rung 2 | Opinions about the other fund |
| 3 | CEO permission | The CEO's dated written yes, naming who introduces | The introducer | Rung 3 | Call notes the CEO never confirmed in writing |
| 4 | Agreement date | When the submitting partner signed the Channel Partner Agreement | Each submitter | Rung 4 | Reward estimates |
| 5 | Introduction record | Portal reference and timestamp; the sent email, unedited, headers intact | Each submitter | Rung 3 | Edited forwards, screenshots of other people's inboxes |
| 6 | Inter-fund note | Any written agreement on who would introduce this company | Both dispute owners | Rung 3 | Side terms unrelated to this company |
| 7 | Known gaps | What you cannot see: SourceX's own history with the company, the other partner's file | Dispute owner | Rung 4 | Guesses written as facts |
| 8 | The ask | One sentence naming the decision you want reviewed | Dispute owner | Rung 4 | Requests for the other partner's records |

Keep originals untouched: the partner agreement says a dispute must not erase original evidence (3.3), and SourceX keeps its own dated introduction evidence (Schedule A, paragraph 8). Company records never enter the packet, not even material a board seat once showed you. A log kept on the [company introduction record template](/resources/a-company-introduction-record-template) makes sections 3 to 5 a copy-and-paste job.

**Method.** Each section maps to what SourceX's documents say decides or explains credit: dated records (terms, section 2), earlier relationships (section 3), written records and their fields (partner agreement 1.2 and 3.3) and the dispute route (terms, sections 7 and 12; partner agreement 7.4; Schedule A, paragraph 8), read on 2026-10-27. It does not measure how often investor disputes happen or how long a review takes; SourceX has published neither figure.

## Five rungs from a paused inbox to arbitration

Climb one rung at a time, and only when the rung below has failed.

| Rung | What happens | Who acts | Climb only if | What leaves your hands |
|---|---|---|---|---|
| 1. Pause | No new message to anyone at the company about SourceX; nobody re-submits or forwards a link | Every investor on the chain | Always the first move | Nothing |
| 2. Inside each fund | Confirm who holds the partner account, what was sent and what your policy allows | Each fund's dispute owner | Your own fund's facts are settled | Nothing |
| 3. Between funds | Swap chain sheets and introduction records; one fund stands down in writing, or both agree to send packets | The two dispute owners | You still disagree after comparing dated records | Your packet |
| 4. SourceX review | Each claimant emails hello@sourcex.si with the referral details and its packet; SourceX reviews and tells each claimant its decision | SourceX | A claimant disagrees with the decision | The decision |
| 5. Formal process | Written notice and 30 days of good-faith discussion, then confidential binding arbitration before one arbitrator | The partner and SourceX, each with counsel | The 30 days end unresolved | The outcome |

**At rung 3,** a written stand-down ends the argument between the funds but awards no credit: SourceX still decides from dated records, and a link click alone decides nothing (section 2). A joint note puts both positions in one message, which is how the partner agreement wants a pending competing claim handled: recorded and resolved in good faith (1.3).

**At rung 4,** expect to see your own file and nothing else. SourceX explains with reference codes, status information and redacted calculations, never with other partners' records or confidential Acquisition Partner identities and contracts (Schedule A, paragraph 8). Why no exception is granted outside the signed terms is covered in [explaining attribution without promising exceptions](/guides/how-to-explain-attribution-without-promising-manual-exceptions).

**At rung 5,** the dispute is between one partner and SourceX over SourceX's decision. Section 12 of the terms and 7.4 of the partner agreement both send it, unresolved, to confidential binding arbitration under the JAMS Comprehensive Arbitration Rules and Procedures, seated in Wilmington, Delaware, unless a signed referral agreement sets its own process. JAMS publishes those rules itself; under them one neutral arbitrator conducts the case unless the parties agree otherwise (paraphrase). A quarrel between two funds over their own side note never reaches this rung. Nothing here is legal advice: at this point each party reads its signed agreement with its own counsel.

## One dispute owner per fund, one company contact

Name one dispute owner per fund, usually the platform or ecosystem lead rather than the partner whose relationship is in question. The relationship owner keeps talking to the CEO about everything else; the dispute owner holds the packet, talks to the other fund and writes to SourceX.

The company has one accountable contact, the CEO, and the dispute never lands on her desk. Do not ask her which fund came first: it turns an investor quarrel into a board-level irritant, and section 2 lets SourceX contact a referred company directly without affecting valid attribution, so SourceX can ask for the company's account itself. Her dated written yes should already exist. If she raises the matter, one sentence is enough: two of her investors are settling an administrative question with SourceX, and nothing is needed from her.

## What each fund hears and earns while the question is open

**Status.** Each claimant hears about its own claim only: generic stages or reference codes for its own referral (partner agreement 4.6), never other partners' records (terms, section 7). Agree that neither fund relays SourceX's updates to the company or to the other fund.

**Money.** One partner is credited per company, and the terms describe no split. The reward on a company's first qualifying transaction is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, paid separately by SourceX and never deducted from the company's compensation; the USD 50,000 floor applies once per referred company, and further qualifying transactions first agreed within 12 months pay 15%. Illustrative only, not a promise of earnings: if the company's Actual Supplier Payout eventually reached USD 400,000, the credited partner's reward would be USD 70,000 and the other claimant's would be nothing. Any arrangement between the funds sits outside the program and inside each fund's rules; settle it in writing before the company hears another word, and keep reward figures away from the company, since a reward lets anyone work backward to the payout.

## Three disputes and the rung where each one ends (Illustrative)

Illustrative: a 280-person, founder-led inspection and testing firm with sixteen years of its own inspection reports and test logs. Fund A leads (its platform lead owns the dispute), Fund B co-invests, an angel sits on the advisory board, and the CEO is the one company contact.

| Dispute | What the dated records show | Ends at | Why it stops there |
|---|---|---|---|
| The backup submission | A dated email between the funds says Fund A introduces; Fund A sent the CEO-confirmed introduction and portal submission on day 2; a Fund B associate who missed the email forwarded Fund B's link to the CFO on day 6 | Rung 3 | Fund B finds its own email, stands down in writing and joins a joint note to SourceX, which still decides from the dated records |
| The dinner conversation | Fund B's partner says he raised SourceX with the CEO over dinner in the spring; nothing was written, and the CEO's written yes names Fund A | Rung 4 | An oral mention protects nothing until confirmed in writing; Fund B sends its packet anyway and SourceX reviews both |
| The earlier email | SourceX's review finds that the company's COO emailed SourceX about licensing a year earlier | Rung 4, with nobody credited | Earlier email correspondence is a relationship under section 3, so the company was not new to SourceX |

None of the three reaches rung 5, because none disputes how SourceX applied its own terms. The third is the hardest to accept, since only SourceX held that record; the [existing relationship check](/guides/how-to-check-whether-an-existing-sourcex-relationship-affects-credit) lists questions that can surface it before anyone introduces.

## What escalation cannot repair

- **A company SourceX already knew.** Section 3 makes it a duplicate, credited to no one, however strong each packet is.
- **A missing written record.** An unwritten or unconfirmed introduction gives a review nothing to weigh.
- **An introduction the CEO never agreed to.** SourceX's screening guidance treats that as usually not a fit, so winning the argument may leave nothing to credit.
- **Time.** SourceX has not published how long a dispute review takes, and the company's own conversation with SourceX does not wait for the funds.
- **The relationship.** A CEO who learns two investors fought over her company may trust neither. No data on how founders react has been published; note it in your own records.
- **The payout itself.** Credit promises no money: requirements vary with SourceX's current data needs, and a reward is payable only once the conditions in section 5 of the terms are met.

For two partners from different professions, the [seven evidence checks for a shared company](/guides/when-two-partners-refer-the-same-company) go deeper; [first valid referrer versus last touch](/compare/referral-attribution-first-vs-last) explains the rule itself, and the [overview for venture platform teams](/for/venture-platform-teams) covers the fund side.

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

If your network shares CEOs with other funds, write the inter-fund note and collect the CEO's written yes before the first introduction goes out; then [register as a partner](/register), screen the company against [who qualifies](/who-qualifies) and keep sections 2, 3, 7 and 12 of the [program terms](/terms) where your dispute owner can find them. More attribution cases sit in the [guides hub](/guides).

Settling a referral dispute is program business; deciding whether SourceX is a company worth investing in is a separate question, and readers weighing it can request materials through 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/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://refer.sourcex.si/who-qualifies
- https://www.jamsadr.com/rules-comprehensive-arbitration
- https://sourcex.si/investors
