# Corporate partner turnover during a referral | SourceX

Canonical: https://refer.sourcex.si/guides/when-corporate-partner-staff-change-during-an-active-referral
Last updated: 2026-11-05

Ask where the person went before you change anything. A staff move never rewrites the introduction record: its date, the partner named on it and the CEO's decision stay where they were. What moves is a seat: who answers the company's CEO, who receives SourceX's notices, who holds the partner login. A colleague who takes a commercial job with the company steps back from the referral; one who joins the company changes sides; one who joins another firm cannot submit the company again.

The protocol assumes the corporate entity signed the SourceX Channel Partner Agreement. Choosing the owner first is covered in [who owns the introduction in a corporate venture unit](/guides/who-owns-the-introduction-in-a-corporate-venture-unit), and staff changes inside the referred company in [when the executive sponsor leaves during review](/guides/when-the-executive-sponsor-leaves-during-review).

## What a staff change can move, and what it cannot touch

The agreement, the company's records and the CEO's authority never belonged to one employee, so none of them leave with one.

| Holder | What it holds while a referral is active | Does a corporate staff change move it? |
|---|---|---|
| The corporate entity, as registered partner | The signed agreement, the introduction records it submitted and any reward that becomes payable | No. Section 7.6 allows assignment only with written consent, or with notice in a merger, acquisition or sale of substantially all relevant assets where the successor assumes the obligations |
| The colleague who made the ask | A personal tie to the CEO, working notes and a portal login | Partly: the tie is theirs, the notes and login are the corporate's |
| A business unit with a commercial contract | A supply, sales or service relationship with the company | No, and that relationship never carried any licensing role |
| The operating company | Its records, its application and its talks with SourceX | No. Its CEO decides, and SourceX deals with the company directly |
| SourceX | Review, attribution decisions and notices to the partner | No. It learns of a change only when the corporate writes to it |

Two published rules keep the referral steady: SourceX may talk to a referred company directly without affecting valid attribution (terms, section 2), and the company's 90 days to file a verified application run from the recorded introduction, so a new contact neither restarts nor extends them.

Nor were the records ever the corporate's. SourceX's screening page asks that the company own its material or be able to license it, and under the program its CEO authorizes the discussion; an investment, a supply contract or a long friendship with the CEO changes neither.

## The continuity protocol: six destinations, one row each

Sort the change by destination, because the destination decides the risk. Fill one row for every company whose CEO has said yes and whose introduction is recorded, until any reward is paid.

| Where the person went | What they may still do | What stops on the day | Who takes the seat | What the CEO hears | What SourceX hears |
|---|---|---|---|---|---|
| 1. Same team, new desk | Stay the CEO's contact if the CEO prefers it | Nothing, unless a conflict appears later | Usually the same person | Nothing, unless the contact changes | Nothing |
| 2. Procurement for the company, or any buying or selling seat | Talk to the company about their new job only | Every part of the referral | A colleague with no open deal with the company | One note naming the new contact | Nothing, unless a notice address changes |
| 3. Joins the company | Speak for the company if its CEO names them | Access to the corporate's referral file, notes and status updates | A new corporate contact | Confirmation of who now speaks for the corporate | The company tells SourceX about its own people |
| 4. Another fund or firm | Keep a personal friendship with the CEO | Any second submission, and the corporate's notes | A successor at the corporate | One note naming the successor | Nothing, unless a second introduction arrives |
| 5. Leaves work | Nothing in the referral | Portal login, shared trackers and working notes | A successor | One note naming the successor | Nothing, unless a notice address changes |
| 6. Signer or notice inbox | Nothing in the referral | The old address as a channel for notices | A named replacement | Nothing | Written notice of the new address or signer, acknowledged |

**Row 2 is the move most often missed.** An internal transfer rarely triggers an exit checklist, yet security practice treats it as a reason to look again: in our paraphrase of NIST's control PS-5 on personnel transfer, an organization checks whether a reassigned person still needs their old access, changes it to fit the new role and keeps access to records from the earlier job. Here, the colleague now negotiating prices with the company loses every line into its referral, and the register keeps what they wrote before the move.

**Row 3 changes sides, not records.** The colleague now works for the party that decides, but the corporate's introduction stays as submitted (section 3.3 of the sample agreement says a dispute must not erase original evidence), and what they saw at the corporate stays there: section 1.6 counts introduction records as confidential information, and section 4.2 makes each party answerable for its own people.

**Row 4 meets the duplicate rule.** A company with an earlier valid introduction, application or relationship with SourceX is reviewed as a duplicate and not credited to a later partner, so a resubmission from the new employer adds a conflicting record and nothing more. The agreement is no non-compete (section 2.4 rules out any blanket non-compete or employment restriction), so the new job and the friendship are the leaver's business. If records collide anyway, SourceX decides in duplicate review; the [two partners, one company guide](/guides/when-two-partners-refer-the-same-company) shows what each side should keep.

**Row 6 needs paper, not a dashboard edit.** Section 7.5 sends notices to the addresses in the agreement "as updated by written notice," and adds: "An automated send event alone is not acknowledgment of receipt." Section 7.7 adds that a dashboard edit does not amend the agreement. So write to SourceX with the new details, file the acknowledgment and refresh the payment and tax details in the same letter: no reward is paid without them, and under section 5 of the terms a condition still open at the deadline is paid promptly once met, with no fresh 60-day period.

**Method note.** The protocol applies SourceX's terms (Version 2026-10-22.2, since replaced by version 2026-11-04), the unsigned sample Channel Partner Agreement (version 2026-10-19) and one NIST control, all read on 2026-10-27. The six destinations are this page's own sorting device, not SourceX categories; the protocol is untested on a completed referral, and no outcome data exists for it.

## Handover sign-offs, and the yes the company never repeats

Inside the corporate, each step has one owner and leaves one piece of evidence.

| Step | Who in the corporate | Evidence kept |
|---|---|---|
| Record the destination and any conflict | Platform manager, with compliance for rows 2 and 3 | A dated line in the referral register |
| Name the successor | Platform manager; the successor has no open deal with the company | The successor's written acceptance |
| Close the leaver's access to the register, login and shared notes, and file their notes | IT or security, with the leaver's manager, on the transfer or exit date | The access log and the filed notes |
| Send SourceX any new notice address or signatory | The authorized signatory | SourceX's acknowledgment |
| Tell the CEO who the new contact is | The successor, in one message | A copy in the register |

On the company side, nothing is re-approved. The CEO's yes belonged to the company; it was never a favor to one colleague, and asking for it again because the corporate reshuffled its staff reads as pressure. Tell the CEO instead, in one short note. An Illustrative version:

> From [date], [name] on our venture team is your contact for the introduction we made to SourceX on [date]. My colleague has moved to a role in our purchasing team and is no longer involved in it; your commercial dealings with us and your conversation with SourceX stay separate. SourceX deals with your company directly, and you remain free to stop at any time. If you would rather have a different contact, or none, tell me.

Only events at the company change who decides: a new CEO decides whether to continue, and once an acquisition closes the acquirer's CEO decides, with the whole group treated as one referred company: the USD 50,000 floor applies once, to its first qualifying transaction, and further qualifying transactions within the Repeat Window pay 15%. The [acquired subsidiary screen](/guides/when-a-corporate-portfolio-company-is-an-acquired-subsidiary) covers a buyer that is your own parent.

## Three handovers worked through (Illustrative)

Illustrative. Invented companies and colleagues; nothing here predicts what SourceX would decide.

**A. The account manager who moved to procurement.** Thirty-five days after the introduction of a 260-person freight forwarder is recorded, the colleague who made it joins the purchasing team that buys freight services from that company. Row 2: she keeps no access, a venture associate with no commercial ties becomes the contact, and the CEO gets the note above. The window still closes 90 days after the original introduction.

**B. The associate hired by the company.** During SourceX's review, a 180-person engineering firm hires the corporate's venture associate as COO. Row 3: whether she sponsors the firm's side is its CEO's call. The platform manager becomes the corporate's contact, and her copy of the register and the status updates stay with the corporate.

**C. The signatory and the dead inbox.** The executive who signed the agreement retires and IT closes the shared partner inbox. Months later a referred company's data is accepted and handed off. Row 6: written notice of the new address and signatory, acknowledged, and fresh payment details were already on file, so nothing waited on paperwork. If the company's Actual Supplier Payout on its first qualifying transaction were USD 250,000, the reward would be USD 62,500 (USD 50,000 plus 5%, which exceeds 15% of the payout), payable to the corporate entity, never to the retired executive.

## Test the protocol on the next three handovers

Run the table on the next three staff changes that touch an active referral and log the days from notice to a named successor, any CEO who heard of the change from someone other than the successor, any CEO asked to confirm again (the target is none), notices sent against acknowledgments received, and any attempt at a second submission. Thirty days on, ask each CEO: did the change of contact make you less comfortable continuing? SourceX has published no turnover or completion figures for corporate partners, so these counts are the corporate's own, and one unsettled CEO is reason to rewrite the note.

## Where the destination map breaks down

- **A colleague registered personally.** The agreement then names that person, not the corporate. The published documents do not say whether their introductions still in review stay, follow them or lapse when they leave; ask SourceX in writing before anyone is told an outcome.
- **Exits with no notice.** Keep the register current weekly so a successor can start cold.
- **The CEO said yes because of the person.** If that trust leaves with the colleague, the CEO may decide to stop. That is a decline, and the row closes.
- **The venture unit is reorganized.** Section 7.6 allows assignment with notice when a successor assumes the obligations, without defeating existing attribution or payment rights; the new owner still needs this register.
- **Late conflicts.** Ask HR to flag transfers of anyone named in the register, since a move into a business unit can surface weeks later.
- **Credit is not the corporate's to settle.** Overlapping claims go to SourceX's duplicate review.

When a whole partner relationship ends, use the [partner offboarding checklist](/guides/how-to-offboard-a-partner-while-preserving-active-company-relationships); more corporate material sits on the [corporate development referral page](/for/corporate-development-data-licensing-referral) and in the [guides library](/guides).

## 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 the next reorganization reaches your team, [register](/register) the corporate entity as the partner if a colleague is still signed up personally, check every active company against [who qualifies](/who-qualifies) once more, and file the version of the [program terms](/terms) your handovers relied on alongside the register.

Keeping a referral steady through staff changes is partner work; whether SourceX is a sound investment is a separate decision, and investor materials can be requested 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://refer.sourcex.si/how-it-works
- https://csrc.nist.gov/CSRC/media/Projects/risk-management/800-53%20Downloads/800-53r5/SP_800-53_v5_1-derived-OSCAL.pdf
- https://sourcex.si/investors