The audience is what makes this different from a CEO session. Operators know where the records are and are often proud of them, which is why a roundtable can drift into "let me show you". They also cannot authorize a licensing discussion: under the program the CEO does. A CEO-level office hour run by two funds is laid out in the joint office hour for two venture portfolios; this page is for the room one level down.
Who sits at the table, and whose permission each seat rests on
An operator attending a peer roundtable has agreed to attend, not to anything else. Their seat is not their company's consent to an introduction.
| Seat | Invited by | Can say yes to licensing | Follow-up contact afterward |
|---|---|---|---|
| Head of support at a company in Fund A's portfolio | Fund A's platform team | No; the company's CEO decides | Fund A's named contact, through the CEO |
| Operations director at a company both funds back | One joint letter from both funds | No; the company's CEO decides | The single fund agreed for that company before invitations |
| IT lead at a portfolio company's largest customer | The portfolio founder who knows that customer | No; that company's CEO decides | The founder's fund, only with the founder's agreement |
| Facilitator from one of the host funds | The host funds jointly | Not applicable | None; the facilitator follows up with nobody |
Two cautions before the seating plan is final. Introductions made without the decision maker's knowledge are usually not a fit, SourceX's screening page says, so an operator's enthusiasm is a reason to ask their CEO, never a substitute. And if a company changes hands before the session, its follow-up follows the new owner's CEO.
The no-upload roundtable format
Part one: a rule for every artifact. Each thing the roundtable produces gets a job and a limit. SourceX's own guidance for a first discovery meeting sets the standard: "Keep the meeting itself free of records." Screens of live customer data, sample exports and spreadsheets with names, it adds, are not needed for any item on its metadata checklist.
| Artifact | May carry | Never carries | Owner |
|---|---|---|---|
| Invitation | Topic, agenda, the no-upload rule in one sentence, and that attending commits no company | Requests to "bring examples" or "bring your numbers" | Host funds |
| Sign-up form | Name, role, company and which fund invited them | System lists, record counts, upload fields, a free-text box about their data | Host funds |
| Pre-read | Links to SourceX's public pages and the four describe-don't-show prompts | Templates to fill in and send back | Facilitator |
| Screens in the session | The facilitator's slides only | Anyone's live systems, sample files or dashboards | Facilitator |
| Chat and whiteboard | Questions and links to public pages | Pasted records, screenshots, dropped files; anything dropped is deleted on the spot | Facilitator |
| Recording | Nothing from the open discussion | A record of what attendees said or showed | Host funds |
| Notes | Themes and unattributed questions | Any company name next to a system, a volume or a problem | Facilitator |
| Describe-don't-show card | One attendee's description of one record family | Anything the hosts collect: the card leaves with its writer | The attendee |
| Follow-up | A thank-you from the company's own fund contact and the public links | Surveys about data, upload links, a second fund's message | The named fund contact |
Part two: seventy-five minutes in five segments.
- House rule, 10 minutes. Read the rule aloud: describe, don't show. Explain why: nobody in the room can accept records for SourceX, and SourceX's own application asks for no files, passwords or API tokens.
- What makes operating records useful, 20 minutes. From SourceX's public screening page: original documentation the company made itself, such as SOPs, project histories, QA records and support workflows, held over several years, with the rights to license it.
- Describe-don't-show cards, 25 minutes. Each attendee privately completes four prompts about one record family: which kind of system holds it, for how many years, roughly how much in order of magnitude, and who at the company would decide. Volunteers read one line aloud if they wish. The card goes home.
- Open questions, 15 minutes. Answered from public pages. On price, the honest answer is that SourceX does not publish how it prices offers.
- Close, 5 minutes. Each attendee learns the name of their company's fund contact and gets one line to take to their CEO: "There is a direct licensing route for company records; if you want to hear more, [contact] will introduce you."
Part three: when someone offers a file anyway. It will happen, usually kindly. Say, in your own words: "Please keep that on your side. Nothing today needs records, and nobody here can take them for SourceX. If your CEO wants to look into it, the company applies itself with a list of its systems." If a file has already landed in the chat, delete it, say so, and carry on.
One fund contact per company, named before the invitations
Each attending company has exactly one fund contact, recorded in the hosts' plan before any invitation leaves. For a company in one portfolio, it is that fund's person closest to the CEO. For a company both funds back, the funds agree on one in advance, and if they cannot, they ask the CEO, not the operator.
That contact is the only person who follows up on licensing, and the follow-up goes to the CEO. Attendance is not an introduction: under section 1.2 of SourceX's sample partner agreement an introduction has to be recorded in writing, and one made only in conversation needs written confirmation before it is protected. When a CEO asks to be introduced, the contact signs the Channel Partner Agreement if they have not already, sends one written introduction, answers SourceX's questions about it and handles nothing from the company's systems, in line with section 4.2.
Ask one more question before introducing: has anyone at the company already written to SourceX, perhaps an operator inspired by the session? Section 3 of the terms makes such a company a duplicate. Nobody is credited, and the company continues directly, which costs it nothing.
What the host funds settle about updates and rewards first
Write both points into the hosts' plan, because they are hardest to fix after a CEO is interested.
Updates. After an introduction, the contact receives what it reasonably needs to follow its own referral and reward (section 3.4 of the sample agreement). The other host fund hears only what the CEO chooses to share, and section 7 of the terms keeps partners away from one another's records.
Rewards. SourceX credits one partner per company, and hosting earns nothing: the terms describe no reward for running a session. Illustrative: if SourceX later paid a company from the roundtable USD 100,000 under its signed agreement, the credited contact's reward on that first qualifying transaction would be USD 55,000 under the default terms, paid by SourceX on its own account, and the co-host would receive nothing from SourceX. Before the session, each fund checks whether its own policy lets its people accept a reward at all; when the two funds' answers differ, follow the decision tree for mixed reward policies.
Fit facts an operator can check from memory
Operators are often the best people to answer the screening questions, as long as they answer from memory and take the answers to their CEO. Did full-time headcount reach 50 or more at its peak, contractors excluded? Do the records span several years of the company's own work? Did the company create them, or do they mostly belong to its clients? 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's requirements move with its current data needs, so a company that misses one program may fit another later. A portfolio-wide version of these questions, as a form with no upload fields, is in the portfolio screening form that avoids sensitive uploads.
Where a no-upload roundtable can still go wrong
Our thesis is that a format which gives records nowhere to go leads to fewer accidental disclosures, and fewer premature applications from operators acting without their CEO, than an open discussion of the same topic. It has not been measured, and nobody has published how portfolio operators behave in sessions like this.
- Operator pressure on the CEO. An excited head of support can push upward harder than any fund would. The closing line routes the question; it cannot cool the enthusiasm.
- Competitors in one room. Portfolios overlap in markets. Keep segment 2 general and let nothing in segment 3 be read aloud unless its writer chooses.
- Leaky notes. The facilitator's notes are the likeliest place for a company name to sit next to a volume. Review them before circulating.
- Demand moves. Criteria differ by program and change over time, so a well-run session can end with no company that fits today.
- Uneven follow-up. One fund writes the next day and the other never does. The named contact exists to stop that.
Methods note. The format rests on five documents read on 2026-10-27: SourceX's referral terms (version 2026-10-22.2, since replaced by version 2026-11-04), the unsigned partner agreement sample (version 2026-10-19), SourceX's screening page, its application page and its guidance on no-upload assessments. It measures nothing about demand, record quality or payouts. To test it, log per session the files offered and deleted, cards completed, CEOs who later asked for an introduction and companies that applied directly. No results have been published. Ideas for a client-facing version of the same event are in client roundtable event ideas.
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.
When a CEO whose operator attended asks to be introduced, the named fund contact should register as a partner, screen the company once more against who qualifies and read sections 1 to 3 of the program terms before writing. The portfolio side of the program is described for venture platform teams, and other coordination guides are in the guides library.
Hosting a roundtable is referral work. Weighing SourceX as a potential investment is a separate decision, and a fund that wants to make it can ask for 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.