This page is for the person who sits between a venture fund's general counsel and its investment, platform and finance teams. It covers the moment a referral idea leaves the desk where it started. Agreeing which office speaks to a CEO when several know them is covered in coordinating a referral across regional fund offices, and keeping memo content out of referral tools in keeping investment memos out of referral workflows. Who may read referral notes once they are stored is a separate design problem, handled in limiting access to referral notes inside a fund. Here the question is what travels from one department to the next. The company's own departments are a separate matter: which of them take part in any licensing discussion is the company's decision, as the question on excluding departments explains.
Why one introduction passes through several desks
A fund can be the partner itself. The sample Channel Partner Agreement linked from section 9 of the terms names the Partner as "[an individual, or entity type and jurisdiction]," so either the firm or one of its people may sign, and section 1 of the terms requires that signature before any introduction is submitted. When the firm signs, the account usually lives with a platform or operations team, while the relationship with the CEO lives with a board member, a deal lead or an operating partner. Finance tracks any reward, counsel clears conflicts, and investor relations sooner or later asks whether there is a story. One introduction can touch five desks.
Each desk has a different task, and the task is the right test for what it receives. The sample agreement already applies that test to SourceX's own confidential information: section 4.2 allows disclosure to employees, professional advisers and service providers "who need the information for the permitted purpose and are bound by confidentiality duties at least as protective as this Agreement." That clause governs information exchanged between SourceX and the partner, not what the fund knows about a company; the fund's duties to a company come from its own agreements with it, which only fund counsel can read. As a design rule for internal handoffs, though, the same test works: a department receives what its task needs and nothing more.
SourceX's screening page makes the starting point plain. What a fund learned through board packs or information rights is a reason to ask the CEO, never material to pass along, and opening a licensing discussion belongs to the CEO alone.
Who may receive what, department by department
| Department | Its task in this referral | Receives | Never receives |
|---|---|---|---|
| Relationship owner (board member, deal lead or operating partner) | Ask the CEO, and hold the CEO's reply | The CEO's own words | Nothing new; this desk is the source |
| Partner-of-record team, often platform | Send the partner link or submit the introduction | The handoff slip | Board packs, diligence files, the owner's private notes |
| Counsel or compliance | Clear conflicts and decide escalations | The slip and the specific question asked | The company's records |
| Finance and operations | Track reward status and supply the fund's tax and payment details | SourceX's status updates by reference code | The company's deal terms, which fall outside what a partner receives |
| Investor relations and marketing | None, unless a publication request is approved | A separate written permission, if one exists | The slip, until then |
| Other deal teams and the investment committee | None | Nothing | Anything |
The finance row rests on section 4.6 of the sample agreement: a partner receives what it reasonably needs to track its own referral and reward, "using generic stages or reference codes," and SourceX need not reveal Acquisition Partner names, contracts, prices or margin. Section 3.4 adds that a partner receives only what it reasonably needs to understand its own referral and reward, so a finance team that wants more is asking for something the fund will not get.
The scoped handoff protocol
Six steps, each with a gate. A step that fails stops the handoff; it does not get filled in from somewhere else.
- Name the source of the knowledge. Before anything moves, the relationship owner records where the idea came from: public information, a conversation with the CEO, or material received in confidence. If the only source is confidential, such as a board pack, diligence material or information-rights reporting, the single permitted move is one question to that company's own CEO, and nothing goes to another desk until the CEO answers.
- Get the CEO's words. The CEO says in writing that they want to hear from SourceX, or that they will apply themselves. The slip quotes that line with its date.
- Fill the slip. Only the fields in the table below.
- Address it to named people. Not a team alias, a shared channel or the deal folder.
- Act on the slip alone. The receiving team works from the slip and sends questions back to the relationship owner, who asks the CEO if needed. Nobody opens the deal file to fill a gap.
- Close it. Submitted, declined, withdrawn or held for counsel, with the date. How long the slip is kept follows the fund's records policy.
| Slip field | Filled by | Allowed source | To partner-of-record team | To finance |
|---|---|---|---|---|
| Company legal name and website | Relationship owner | A public record or the CEO | Yes | Yes, with SourceX's reference code once issued |
| CEO's name and work contact | Relationship owner | The CEO | Yes | No |
| The CEO's request, quoted and dated | Relationship owner | The CEO's own message | Yes | No |
| Relationship owner | Relationship owner | Self | Yes | Yes |
| Partner of record | Partner-of-record team | The signed Channel Partner Agreement | Yes | Yes |
| Source of knowledge | Relationship owner | Public or CEO conversation; a confidential source stops the slip | Yes | No |
| Named recipients | Relationship owner | Self | Yes | Yes |
| Status and date | Partner-of-record team | SourceX's updates | Yes | Yes |
Nothing else rides along. In particular, these stay behind on the desk where they arrived:
- diligence files and data room access from any deal process, including one the fund walked away from;
- investment committee memos, models and the fund's valuation marks;
- board decks, minutes and information-rights reports;
- names of the company's customers, suppliers and staff;
- the relationship owner's private notes about the CEO;
- any estimate of what the company or the fund might receive.
Method note. The protocol was built on 2026-10-28 from sections 1, 2, 4 and 5 of the program terms (version 2026-10-22.2, since replaced by version 2026-11-04), sections 3.4, 4.2, 4.5 and 4.6 and the party description of the unsigned sample Channel Partner Agreement (version 2026-10-19), SourceX's screening page and its process page. A field survived only if a named department's task fails without it. The protocol interprets no one's confidentiality duties and has not been measured at any fund.
Four handoffs at one fund (Illustrative)
Illustrative. A generic mid-sized venture firm that has signed the Channel Partner Agreement as an entity, with its platform team holding the account.
| Handoff | Source of knowledge | What the protocol does |
|---|---|---|
| A board member forwards a founder-CEO's email asking how SourceX works | The CEO's own message | Slip completed; the platform team sends the partner link; the company applies itself, and SourceX's process page says no records are shared at that first step |
| A deal team that passed on a company after diligence asks the platform team to refer it | A confidential process | Held for counsel; nothing moves, and whether anyone at the fund may raise it with the CEO at all is counsel's call |
| Finance asks for the company's expected payout to forecast the reward | Not a slip field | Declined. The terms call portal and calculator estimates projections, not promises; once SourceX has actually paid the company a cumulative P, the reward is the greater of $50,000 plus 5% and 15% of P with no cap, and finance can only work in those symbols until then |
| Investor relations wants to mention the introduction in the next LP letter | Not a slip field | Declined pending the company's written permission and SourceX's written authorization under section 4.5 of the sample agreement |
The second row is the one that tempts a fund most, because the deal team often knows the company better than anyone. Knowing it better is exactly the problem: everything it knows arrived for a different purpose.
Sending the slip back: deeper questions, a CEO who stops and a request to go public
A desk wants more. Any request to add a field, attach a document or widen the recipient list goes to counsel with the slip, and counsel's answer is written on it. If the CEO wants to go further into records, that conversation runs between the company and SourceX once the company applies; SourceX's process page puts the company's own sign-off on scope and terms ahead of any delivery of data.
The CEO stops. The status changes to withdrawn with the date, and each named recipient gets one line saying so. If an introduction was already submitted, SourceX is told only that the CEO asked to stop.
Someone wants to publicize it. The sample agreement's section 4.5 bars either side from publicly identifying the other as a partner, or disclosing non-public deal details, without written authorization. The company's own written yes is needed as well, and neither travels on the slip.
Two desks both claim the relationship. Only one introduction can be credited, and where two partners know one company SourceX settles the overlap in duplicate review from dated records; a slip's date is internal paperwork, not evidence of credit. A company and its corporate group share one reward cap. Questions fund counsel tends to raise about all of this are gathered in the questions fund counsel will ask about referral economics, and checking SourceX's terms against the fund's own documents is covered in reviewing referral terms against fund documents.
Where the protocol breaks down
- Small funds. When one person is relationship owner, account holder and finance, the slip becomes a self-check and a dated log. It still stops the board pack from riding along.
- Informal channels. A forwarded email chain carries the whole thread, including the parts that should stay behind. Strip it to the slip before sending.
- Stricter fund documents. NDAs, side letters and information-rights clauses can restrict more than this protocol does. Fund counsel reads them.
- The slip proves nothing to SourceX. Credit is decided from SourceX's dated records under section 2 of the terms, and companies SourceX already knew are duplicates under section 3.
- No outcome data. Whether scoped handoffs change what happens to introductions has not been measured. A fund can count, for two quarters, slips held for counsel and slips sent back for a missing CEO request.
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 counsel has approved the slip fields and named who receives each one, register the fund or the individual as a partner, keep who qualifies beside the CEO conversation, and read the program terms before the first slip leaves its desk. Related guides sit in the guides hub.
Moving an introduction between fund departments is referral administration; whether SourceX is worth investing in is a separate review, and investor materials for it are available on request via the SourceX investor overview.
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.