This page is for the counsel liaison at a venture fund who sets the rules for calls in which a portfolio or network CEO discusses a SourceX introduction. It does not cover recording consent: whether a call may be recorded or transcribed at all, and what notice that takes, is a question for your own counsel, and the CEO may ask theirs. Group sessions with several CEOs have their own closed-door protocol, and whether a company's own transcripts could ever be licensed is discussed on sourcex.si.
Four ways a note-taker widens the room
An introduction conversation is small by design. Meeting software is built for the opposite case, a team whose absent members want to catch up, and its sharing features follow that purpose. Each row paraphrases the vendor's own help page, read through search excerpts on 2026-10-28; plans, admin policies and versions differ, so test each row on your own account.
| Mechanism | What the vendor's help page describes (paraphrase) | Who it can add | Setting to check |
|---|---|---|---|
| Automatic summary delivery | Zoom: if the host turns on the AI Companion summary and chooses to share it, participants get it by email after the call, and it can post to the meeting's group chat | Every signed-in participant and the chat | Summary off, or host only |
| Manual forwarding | Zoom: the host can email a summary from the web portal to any address they type in | Anyone the host picks | Who may send summaries |
| Default transcript access | Microsoft Teams: recording and transcript access starts at Everyone; narrowing it needs a Copilot or Teams Premium license, and third-party apps keep their access | Every invitee and connected apps | Whether your license can narrow it |
| Followers and recaps | Outlook: people who follow a meeting without attending can reach its recording and transcript through the recap | People who never joined | Who follows the meeting |
| A bot from another platform | Zoom documents a setting that lets Zoom AI join other platforms' meetings to write summaries | Whoever owns a bot you did not invite | Every participant tile |
Two more paths run outside the meeting tool. A CRM or note app connected to someone's calendar can file a summary against a contact record, which is how call notes turn into a shadow data room. And the CEO may run a note-taker of their own; that record is the company's, kept under the company's policy, and a partner asks for no copy of it.
The room the CEO agreed to
Agreement to talk about an introduction has a shape: a purpose, a set of listeners and an end. Write it down before the invitation goes out, so the capture settings follow the permission rather than the software's habits.
| Meeting | Purpose | Who may hear it | The only record the next step needs | Capture default |
|---|---|---|---|---|
| First conversation with the CEO | Learn whether the CEO wants to hear from SourceX | The relationship owner and the CEO | Yes, no or later, with the date | None |
| A three-way call the CEO asks for | Let the CEO put questions to SourceX directly | The CEO, people the CEO invites, SourceX | That the call took place and who requested it | The CEO decides |
| Internal fund discussion | Decide who asks and whether fund rules allow it | People named on the fund's referral approval | The decision and its owner | No company detail captured |
The internal row has its own guide: a partner meeting where guests and automatic notes are the main risk is handled in how to discuss an active referral in a partner meeting, so this page concentrates on calls the CEO joins.
SourceX needs very little from these calls. Its process page says no records are shared at the apply-and-qualify step, and tells companies that they approve the scope and terms, and sign, before any data is delivered. Section 3.3 of the sample partner agreement lists what an introduction record identifies: the company, its domain, the partner, the opportunity, how the introduction was made and when. None of that requires a transcript. SourceX's screening page also puts introductions the decision maker never heard about among the cases that rarely work, so the CEO has to know about the conversation, and a CEO who knows about it is entitled to know who hears it.
The meeting capture permission checklist
Twelve checks, in the order they arise. A failed check has a fallback in the last column, and the fallback is never "record anyway and tidy up later."
| # | Check | Who answers | Passes when | If it fails |
|---|---|---|---|---|
| 1 | Whose account hosts the call, and which AI features are on? | Host | Each feature set deliberately | Move to an account the fund controls |
| 2 | Which note-takers will join, including any from an invitee's calendar? | Host, asking invitees | Each is named in the invitation, or none | Ask the invitee to switch theirs off |
| 3 | Where would a summary go by default? | Host | Off, or kept with the host | Switch it off before the call |
| 4 | Who could open a transcript or recording? | Host | Capture off, or limited to named people | If the license cannot narrow access, do not transcribe |
| 5 | Which connected apps can read meeting content? | The fund's IT owner | No CRM or note-app sync | Disconnect it, or use another account |
| 6 | Has the CEO been told what will be captured? | Relationship owner | One line in the invitation says what is on and off | Send it before the call |
| 7 | Is every capture tool on the call claimed by a named person? | Host, at the start | Each participant tile is accounted for | Remove the unclaimed bot or reschedule |
| 8 | Has the conversation moved into company detail? | Either side | Records, customers and figures stay unsaid or off capture | Pause capture for that part |
| 9 | Who writes the shared note? | Relationship owner | A person, from the template below | Never forward the AI summary as the note |
| 10 | What happens to any machine copy? | Its owner | Kept under fund retention policy, sent nowhere | Ask the records owner or counsel |
| 11 | What reaches the CRM or referral record? | Relationship owner | Only the fields an introduction needs | Correct the entry under fund policy |
| 12 | What if the CEO later says no or asks for privacy? | Relationship owner | The note reads "withdrawn" with a date | Tell every recipient of the note, in one line |
Method note. The checks combine the vendor behavior above with SourceX's published process, section 3.3 of the sample agreement (version 2026-10-19) and the program terms (version 2026-10-22.2, since replaced by version 2026-11-04), all read on 2026-10-28. They were not tested on every meeting product and answer no legal question: recording consent, confidentiality duties from an NDA or a board seat, and what your fund must retain stay with counsel.
A shared note that carries the decision, not the company
A person writes the shared note after the call, in five lines: date and participants by name and role; the question asked; the CEO's answer in the CEO's own words (wants an introduction, will apply directly, or not now); the next step with owner and date; and which capture tool, if any, ran and who holds its output. Everything else stays out:
- descriptions of the company's records or systems, and any volumes, years or figures;
- names of customers, suppliers or employees, and anything said "between us";
- the fund's own view of the company, its valuation or board matters;
- guesses about what SourceX might pay, since SourceX's process page says a payout is fixed only in a signed Dataset Deal Confirmation and earlier estimates are indicative;
- other companies that came up.
Illustrative. A 30-minute call between a fund's platform lead and the founder-CEO of an invented 230-person field-services company. The host's summary was off; the CEO's own note-taker ran, and the CEO forwarded its summary "for your files." The platform lead did not file it, and wrote the shared note instead.
| Line in the forwarded AI summary (Illustrative) | In the shared note? | Why |
|---|---|---|
| "Company holds nine years of dispatch notes in one system" | No | Company detail; the company states it to SourceX itself |
| "Largest customer is a regional utility" | No | A third party's name |
| "Partner guessed the archive could be worth a lot" | No | An estimate nobody can support |
| "CEO will decide after an internal conversation and may apply directly" | Yes | The decision, in the CEO's words |
| "Partner to send links to SourceX's terms and screening criteria by Friday" | Yes | The next step and its owner |
The forwarded email is itself something the CEO sent unasked; handling it under your own policy is covered in what to do when someone sends confidential files unasked.
Deeper questions, a change of mind and a request to tell the story
Three later moments each need their own answer, and no transcript should decide one by existing.
The CEO wants to go into the records. That belongs to the company and SourceX once the company applies, with the company choosing the scope. Section 4.4 of the sample agreement bars partners from collecting or retaining supplier dataset copies through the program without separate written authorization. If a privacy lead joins, the privacy officer conversation sets out what a partner can answer.
The CEO changes their mind. Mark the note "withdrawn" with the date and stop. If an introduction was already submitted, tell SourceX only that the CEO asked to stop.
Someone wants to publish. A summary is never source material for a post, case study or LP letter. Section 4.5 of the sample agreement says "Neither Party may publicly identify the other as a partner or disclose non-public deal details without written authorization, except as legally required," and the company's own written yes is needed on top. Where a company has approved a case study, using it without promising the same result covers what comes next.
Where these controls fall short
- Defaults move. Vendors rename features and change defaults; recheck when the tool updates.
- Licenses decide some controls. Without the license that narrows transcript access, treat transcription as on or off, never as limited.
- You cannot switch off the other side. A company's own note-taker follows the company's policy; you can ask and keep your own capture off.
- People still remember and type. The template limits what is written down, not what is heard.
- Legal questions stay open. Recording consent, confidentiality duties and retention obligations are for counsel.
- Nothing here is measured. How often summaries reach unintended readers in referral work has not been published; a fund can log, for one quarter, every call where a check failed and which one.
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 call about an introduction, run the twelve checks with whoever hosts it; then register as a partner if the fund has not signed the Channel Partner Agreement, compare the CEO's own answers with who qualifies, and keep the program terms open while you write the shared note. Neighboring questions are collected in the guides hub.
Setting capture rules for referral calls has nothing to do with judging SourceX as an investment; anyone weighing that question can request materials through 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.