# Senior network relationship handover brief | SourceX

Canonical: https://refer.sourcex.si/guides/the-relationship-brief-for-a-new-senior-network-steward
Last updated: 2026-11-05

A senior network changes hands as purposes and permissions, never as a contact list. For each LP, executive or advisor, the outgoing steward writes down why the relationship exists, what the person agreed to be asked and by whom, what they declined and until when, and what they have been told about who could be paid. The new steward inherits the record but not the yes: every permission waits until the contact renews it, and every company those contacts know stays with its own CEO.

## Three things a departing steward leaves behind

A senior network steward is whoever at a fund keeps the relationships with LPs, senior executives and advisors in good order: a head of platform, an investor relations lead, a relationship partner. When that person moves on, three different things are left behind, and only one of them can be handed over whole.

- **The record.** What each relationship is for, what was asked, what was answered and when. It transfers in full.
- **The permissions.** What each person agreed to be asked, by whom, through which channel and how often. They were given to the outgoing steward, so they wait for renewal.
- **The trust.** The reason a senior contact takes the call at all. It cannot be written down, and the brief does not pretend to carry it.

SourceX's glossary describes a [data steward](https://sourcex.si/glossary/data-steward) as the person responsible for the quality, documentation and appropriate use of a dataset. A network steward does the same job for relationships, and appropriate use is the part a handover puts at risk. Funds already treat people changes as something LPs should hear about: ILPA's Principles 3.0 say "LPs should be notified in a timely manner of any personnel changes, not solely key person, with the potential to impact fund performance" (quoted from a search excerpt of the 2019 document). A steward change rarely reaches that bar, but the instinct carries over. Each senior contact hears about the change from the fund before the new steward asks them for anything.

## The relationship purpose and permission handover

One brief per senior contact, ten fields, each a line and a date. The third column is the design: it gives every field one of four fates at handover.

| Field | What the outgoing steward writes | At handover it | Example entry (Illustrative) |
|---|---|---|---|
| 1. Purpose | Why the relationship exists, in one line | Carries over as a fact | LP since 2019; a family office that also owns operating companies |
| 2. Relationship holder | Who at the fund the contact actually trusts, which may not be the steward | Carries over as a fact | The founding partner, who sat on a board with her for six years |
| 3. Permission | What the contact agreed to be asked, by whom, how and how often | Waits for renewal | "Ask me once a quarter, by email, about companies I know," given to the outgoing steward in March |
| 4. Declines | Each no, with any date the contact set | Carries over and binds at once | "Not before January," said in June |
| 5. Disclosures heard | What the contact was told about who could be paid and the company's unchanged payout | Repeated by the new steward | Told in March that the fund could be paid by SourceX |
| 6. Open asks | Companies the contact said they would raise with a CEO, with dates and nothing more | Returned to the contact, who decides whether to go on | Said in August he would ask a 400-person insurer's CEO; no word since |
| 7. Submitted introductions | Who submitted, when and under whose agreement | Stays exactly as recorded | The fund submitted one company in May |
| 8. Sensitivities | Open capital conversations, LPAC seats, employer approvals | Checked again before any contact | Re-up decision due next quarter |
| 9. Never written | Board material, company records, private reasons for a no | Never enters the brief | Left blank on purpose |
| 10. Next contact | The date of the new steward's first meeting | Owned by the new steward | 14 November, purpose only |

Field 6 is the one that tempts a newcomer. An open ask belongs to the contact who offered it. The new steward may ask, once, whether the contact still wants to raise it; the new steward never contacts that CEO on the contact's behalf.

**Method note.** The ten fields and four fates are this page's design, built from SourceX's program terms (Version 2026-10-22.2, since replaced by version 2026-11-04), its who-qualifies page, the sample Channel Partner Agreement and a SourceX glossary entry, all read on 2026-10-27, plus one ILPA passage read through a search excerpt. The brief measures no company and forecasts no reward.

## A no carries over; a yes is asked for again

The asymmetry is deliberate. A decline protects the person who gave it, so it binds the new steward from the first day: a contact who said "not before January" in June hears nothing about introductions until January, however keen the newcomer is. A permission is different. It was given to one person for one purpose, and the contact may feel quite differently about being asked by someone they have never met. So permissions are renewed, in the contact's own words, and dated again.

The partner agreement needs the same check. The sample Channel Partner Agreement can be signed by an individual or by an entity. If the outgoing steward signed in their own name, the new steward cannot submit under that signature; whoever submits next signs first, because section 1 of the terms says partners "must also sign the SourceX Channel Partner Agreement before submitting introductions." Introductions already submitted stay where the dated record puts them. Whether a later submission for a company already in someone's record can earn credit is not something the brief decides; SourceX settles any overlap in duplicate review. Referrals already moving through SourceX follow the [manager transfer checklist](/guides/when-a-referral-moves-between-partner-managers), and a temporary absence follows [the platform manager's leave handoff](/guides/the-platform-manager-s-handoff-when-taking-leave).

## Who still reaches each CEO after the change

The handover moves the steward, not the paths. An LP who knows a distributor's CEO still knows her, and the new steward does not acquire that relationship by reading a brief. The senior contact stays the person who asks, and the company's CEO stays the only person who decides whether the company talks to SourceX. Once a company has been acquired, its acquirer's CEO decides for it; before the deal closes, the target's CEO still does.

Two things never travel with a brief. The first is anything a contact learned in a boardroom or an engagement: what a board seat shows its holder may prompt one question to that company's own CEO, and it goes nowhere else, least of all to a different company. The second is any company's records. Section 4.2 of the sample agreement is plain that a partner cannot pass on what a supplier holds, whether that is its inventory, its records and raw data, or anything personal, so a brief that kept such material would keep something nobody in the chain should have. If the person who agreed to an introduction inside a company leaves, that is a different handover, covered in [when the executive sponsor leaves during review](/guides/when-the-executive-sponsor-leaves-during-review).

## The new steward's first sixty days

1. **Days 1 to 5: read, send nothing.** Read every brief and put each dated decline in the calendar.
2. **Days 5 to 30: one first meeting per contact.** The fund announces the change first, ideally through the person named in field 2. The meeting is about the relationship's purpose; no company is named and nothing is asked.
3. **At the end of each meeting: ask about permission, once.** "May I ask you now and then about companies you know that might suit SourceX?" Record the answer and the date. A contact who does not answer has not agreed.
4. **Days 30 to 60: hand open asks back.** Ask each contact with an open ask whether they still want to raise it. If they do, they raise it themselves.
5. **Day 60: close what was not renewed.** A brief without a renewed permission is marked "not renewed" with the date, and nothing more is sent until the contact brings the subject up.

## Capital, endorsement and pay when the steward is new

A new steward often arrives with an investor relations agenda as well, and first meetings are where the three topics blur. Keep any capital conversation (a re-up, a consent, an LPAC matter) out of the first meeting and out of the permission question. For how a single introduction request is worded without an investment ask, see [asking an LP for an introduction](/guides/how-to-ask-an-lp-for-an-introduction-without-making-an-investment-ask).

Never suggest that SourceX endorses the fund or its network, or that a contact's company would be treated more favorably; under section 4.5 of the sample agreement, neither side may even name the other publicly as a partner without written authorization. And repeat the disclosure in your own voice, because who could be paid may have changed with the steward. What has not changed is the company's payout: SourceX pays rewards from its own share, and section 4 of the terms says a reward is paid separately rather than taken out of what the company is owed. The default reward is the greater of $50,000 plus 5% and 15% of what SourceX actually pays the company, with no cap for that company, and a company's corporate group shares a single cap.

## Three relationships, one brief (Illustrative)

Illustrative. A generic fund whose head of platform leaves in October; invented people and dates.

- **An LP principal with a standing permission.** Her brief shows quarterly email asks agreed with the outgoing steward in March. The new steward meets her in November. She renews, but narrows the terms: email only, and only about companies she brings up first. The brief records her words and the new date.
- **A venture partner with a dated no.** In June he said "not before January; I'm on two boards in transition." The new steward sends him nothing about introductions until January, and the January note only asks whether he is open to the topic again.
- **An advisor with an open ask.** In August he offered to raise SourceX with the CEO of a 400-person insurance services firm. The new steward asks him once whether he still wants to. He replies that the CEO has since applied to SourceX on her own. The row is closed with that sentence and the date, and nobody tries to attach a claim to the application.

One permission renewed on narrower terms, one decline honored, one open ask closed. The network looks smaller on paper and is in better shape. Departures of partners themselves, rather than fund staff, are handled in [offboarding a partner](/guides/how-to-offboard-a-partner-while-preserving-active-company-relationships).

## Gaps a handover brief leaves open

- **Abrupt departures.** If the outgoing steward leaves without writing briefs, rebuild them from dated emails and call notes, and mark every permission "unknown" until it is renewed.
- **Trust that does not transfer.** Some contacts will not renew, and no brief can change that.
- **Records about people.** A brief holds facts about individuals. Keep it to the ten fields and handle it under the fund's own privacy obligations, which its counsel can explain; this page offers no legal advice.
- **An unclear signature.** If nobody can say who signed the partner agreement, pause submissions until that is settled.
- **Fit and demand.** A renewed permission makes no company a fit. SourceX applies each program's own criteria in review, and a company can be declined.
- **What to measure.** For the next handover, count briefs written, permissions renewed by day 60, declines carried over, open asks handed back and asks resumed. Write predictions before you start. Figures from funds using this brief are not yet published.

## 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 new steward asks any contact for anything, make sure whoever will submit has [registered as a partner](/register) and signed, share [who qualifies](/who-qualifies) as the only fit material, and read the [program terms](/terms) on credit and duplicates. Related playbooks are collected in the [guides library](/guides).

Handing over a senior network is referral work; a contact who would rather look at SourceX as an investment is a separate conversation, 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://refer.sourcex.si/who-qualifies
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://ilpa.org/wp-content/uploads/2019/06/ILPA-Principles-3.0_2019.pdf
- https://sourcex.si/glossary/data-steward
- https://sourcex.si/investors
