# Departing partner referral ownership protocol | SourceX

Canonical: https://refer.sourcex.si/guides/when-a-partner-leaves-the-fund-with-an-active-introduction
Last updated: 2026-11-05

When a partner walks out with an introduction still open, nothing about the introduction moves on its own. Credit stays wherever SourceX's dated records put it, with the party named on the signed agreement, whether that is the fund entity or the partner personally. What the fund has to move is everything around the introduction: the CEO's contact, the board seat, the login and notice inbox, and the partner's working notes. Sort each open introduction by the agreement it sits under, hand each piece to a named person in writing, and ask SourceX about whatever the published terms leave open.

Two pages surround this one. [Who receives a reward when a fund makes the introduction](/guides/who-receives-a-reward-when-a-fund-makes-the-introduction) sets out the general case, including a table of changes after signing. The stage-by-stage checklist for any partner network is in [offboarding a partner while preserving active company relationships](/guides/how-to-offboard-a-partner-while-preserving-active-company-relationships). This page covers what is particular to a fund: a board seat that changes hands, a partner who joins a rival fund, a personal account built on a fund relationship, and the economics the departing partner leaves behind.

## Whose introduction is it on the day the partner resigns?

Read three facts from the record, not from memory.

1. **The party on the signed agreement.** SourceX's sample agreement names the Partner as "an individual, or entity type and jurisdiction", so the party is either a fund entity or a person. That party, and only that party, holds the agreement.
2. **The written introduction.** Section 2 of the terms decides attribution "from dated records, including written introduction evidence, existing applications and preexisting relationships", and an earlier link click does not decide it. Find the dated message and the 90-day window that runs from it.
3. **Where the relationship came from.** Did the partner know the CEO through the fund's investment or board seat, or from before joining?

Those facts sort every open introduction into one of four capacities.

| Capacity on the record | Partner of record | What the exit changes | Fund owner of the follow-up |
|---|---|---|---|
| A. A fund entity signed; the departing partner asked on its behalf | The fund entity; the person was never the party | The entity's contact person, login holders and notice address | COO |
| B. The partner signed personally, with the fund's written approval | The partner | Nothing in the partner's own agreement; the fund's approval file and any internal arrangement | Compliance lead, with fund counsel |
| C. The partner signed personally, but the company came through the fund's board seat or deal | The partner, as the record stands | Whether the fund's policy treated that ask as fund work; any question about credit is SourceX's to decide | Fund counsel |
| D. No account: an unpaid mention, and the company applied on its own | Nobody | Only who the CEO calls with questions | Platform lead |

**The money question.** The departure changes neither the company's payout, call it P, nor SourceX's published formula: the greater of $50,000 plus 5% and 15% of P, with no cap across every installment and renewal (terms, section 4). Whether the departing person shares in anything a fund entity might later receive in row A, or owes the fund anything from a personal reward in rows B and C, is written in the fund's own papers, such as its partnership agreement, employment or consulting terms and any separation agreement. Only counsel reading them can say. This page describes none of those documents.

## The departure attribution handoff protocol

Five handoffs, each with an owner, a dated output and one shortcut the fund refuses.

| Handoff | When | Owner | Dated output | Shortcut refused |
|---|---|---|---|---|
| 1. Read the record | Notice day | COO | One register row per company: capacity, date of the written introduction, day 90, generic stage, whether the company applied | Rebuilding dates from memory, or asking the company |
| 2. Freeze | Notice day to last day | COO, to the whole deal team | A short note listing what nobody does | A colleague resubmitting a company, or a new account opened to "hold" it |
| 3. Re-point the contacts | Before the last day | Departing partner and successor together | One message to each CEO in conversation; the board-seat change; written notice to SourceX for row A; logins removed | Telling a CEO the deal must close before the partner goes |
| 4. Ask in writing | Within the notice period | COO, or the partner for rows B and C | Questions to SourceX and their replies, each dated | Promising the partner, the fund or the CEO an outcome |
| 5. Settle the fund's side and close | Separation papers, then each review date | Fund counsel and COO | Counsel's conclusion; the partner's confidentiality confirmation; a check at day 90, and another when protection runs out if an agreement ends | Writing SourceX's decision into the separation papers in advance |

**Handoff 1** works from the fund's own register and the partner dashboard. Section 4.6 of the sample says a partner follows its own referral through "generic stages or reference codes", which is all the register needs: no Acquisition Partner names, prices or records.

**Handoff 2** exists because the duplicate rule makes a second submission useless and confusing. Section 3 says companies that already have "an application, relationship or earlier valid introduction with SourceX are reviewed as duplicates and are not credited to a later partner." A colleague's fresh introduction restarts nothing.

**Handoff 3** has four parts. The CEO hears once, ideally from the departing partner with the successor copied, and learns who now answers questions; section 2 lets SourceX "communicate directly with a referred company without affecting valid attribution", so the company's process does not depend on the fund. The board seat passes under the company's own documents, and the new designee inherits no referral ask. For row A, SourceX gets the entity's new contact in writing: section 7.5 of the sample sends notices to the addresses identified, "as updated by written notice", and counts email notice only "upon acknowledged receipt". Logins to the firm account close on the last day; a personal account in rows B and C belongs to the partner, so the fund removes only its own trackers.

**Handoff 4** carries the questions the published terms leave open. How SourceX treats an introduction still in review when the person who made it leaves is not written down anywhere public, and SourceX decides it. For row C, so is any question about which party the record should credit.

**Handoff 5** closes the loop. Counsel records the fund's treatment of rows A to C. The partner confirms in writing that SourceX confidential information held for the fund has been returned or deleted: section 4.4 of the sample provides for return or deletion on request or termination, and section 4.2 makes a party "responsible for its representatives' compliance". The register is checked again at day 90 and, if an agreement itself ends, when the six-month protection period in section 9 of the terms runs out.

**Method note.** The capacities and handoffs apply SourceX's terms (version 2026-10-22.2, since replaced by version 2026-11-04), its unsigned sample agreement (version 2026-10-19) and its who-qualifies page, all read on 2026-10-28. They sort introductions; they do not read any fund's documents or predict SourceX's decisions, and they have not been tested on real departures. SourceX publishes no figures on introductions in flight when a partner leaves.

## Board seats, a rival fund and the duties that follow a partner out

**The board seat.** SourceX's screening page says a board seat lets a fund speak in the boardroom but does not let it start a licensing discussion; that belongs to the CEO. What a partner learned through the seat may prompt one question to that company's own CEO and goes nowhere else. It does not travel to the partner's next fund, and it never reaches a different company.

**A move to another fund.** If the new fund, or the partner personally, later wants to introduce a company the old fund already introduced, section 3 treats it as a duplicate. Where the old fund and the new one both know a company that neither has introduced, only one introduction can be credited, and SourceX settles overlapping claims in duplicate review from dated records.

**Staying on as a venture partner or advisor.** The fund's policy should say whether the person still acts for the fund when speaking to a portfolio CEO; if it is silent, settle that first.

**Confidentiality.** Section 9 of the terms keeps confidentiality obligations for three years, longer for trade secrets. Any restriction the fund places on a departing partner, from non-solicitation to the return of notes, sits in the fund's documents and belongs with counsel.

**The CEO's freedom.** A CEO who trusted the departing partner may lose interest. That is the CEO's call, and the fund presses neither way.

## One partner, three open introductions (Illustrative)

Illustrative. A generic growth fund with invented companies and dates; no outcome is implied.

A partner gives 30 days' notice before joining another fund. The COO finds three open rows.

| Company | Capacity | Written introduction | Day 90 | Generic stage | CEO's contact after the exit | Open question to SourceX |
|---|---|---|---|---|---|---|
| 260-person claims processor | A | March 3 | June 1 | Application in review | Operating partner who already works with the CEO | Treatment of an introduction in review when its introducer leaves |
| 180-person dispatch company | C | April 20 | July 19 | No application yet | New board designee, for questions only | Which party the record credits, given how the relationship began |
| 400-person regional distributor | D | None | Not applicable | Applied on its own | Platform lead | None |

For the claims processor, the COO writes to SourceX naming herself as the entity's contact and asks the in-review question; counsel notes in the separation papers how the fund's documents treat anything the entity might later receive. For the dispatch company, the partner had written to the CEO with her personal link after a board meeting where she sat as the fund's designee. Nobody resubmits, counsel reviews whether the fund's policy treated the ask as fund work, the credit question goes to SourceX in writing, and day 90 goes in the diary. The distributor needs only a new name for the CEO.

## Writing the handoff into the fund's records

The departure file holds the register, the freeze note, each CEO message, SourceX's dated replies, counsel's conclusion, the confidentiality confirmation and the two review dates, and no company records.

Funds that want fewer row C cases next time decide routing before anyone asks, as [the account ownership worksheet](/guides/how-to-handle-personal-versus-firm-owned-referral-links) shows. How the wider network of LPs, executives and advisors is handed to a successor is a different job, covered in [the relationship brief for a new senior network steward](/guides/the-relationship-brief-for-a-new-senior-network-steward), and [checking whether an existing SourceX relationship affects credit](/guides/how-to-check-whether-an-existing-sourcex-relationship-affects-credit) explains the duplicate test.

## Where a departure protocol can fail

- **SourceX decides the open cases.** The protocol can route questions; it cannot settle how an introduction in review is treated.
- **No notice.** After an overnight exit, rebuild the register from dated emails and the dashboard and mark every unknown.
- **A dispute between the fund and the partner.** That is governed by the fund's documents. The dispute route in section 7 of the terms covers attribution, eligibility and reward decisions, not a fund's arrangements with its people.
- **Fit does not change with people.** A company still needs 50+ full-time employees at peak, contractors excluded, its own documented records and the rights to license them. 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 can still decline it.
- **Acquisitions.** If a portfolio company is sold mid-handoff, the acquirer's CEO decides for it after closing.

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

Before a successor makes any new introduction, make sure the right party has [registered](/register) and signed the Channel Partner Agreement, recheck each company against [who qualifies](/who-qualifies) and keep the [program terms](/terms) version beside the departure file; other fund decisions are in the [guides library](/guides).

Handing over a departing partner's introductions is referral work. Anyone at the fund weighing SourceX as an investment does that separately, through the [SourceX investor overview](https://sourcex.si/investors), where investor materials are available on request.

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://sourcex.si/investors
