This page is for VC portfolio engagement leads and platform teams who send portfolio companies offsite templates, facilitator lists or planning advice, and who want data ownership on the agenda without turning the offsite into a referral channel.
What an offsite brings to the surface, and who owns it
Offsites set priorities, budgets and owners for the year. AI plans, system consolidation and customer renewals now push data questions into that agenda: which team owns which records, what customer contracts and employee notices promise, which vendors hold copies, when old systems retire and what happens to their history. Those are the company's governance questions. The answers, the debate and the notes are the company's too, whether or not anyone ever mentions licensing.
Ownership and the right to license are not the same thing, and leaders who discuss one often assume the other. SourceX's FAQ separates them plainly: "Owning your records doesn't automatically give you the right to license personal information or data that belongs to customers, vendors or other third parties." A room that agrees "we own all of this" has started a question, not settled it.
Nor does an offsite say anything about fit. SourceX's published screen looks at full-time headcount at the company's peak, years of records the company created itself, its rights to license them, a CEO who authorizes the discussion and relevance to a current program, which SourceX checks in review. Knowing that a company held an offsite, or what its agenda covered, tells you none of that.
Offer the module, then stay out of the room
| You may | You never |
|---|---|
| Send the module as a document the CEO can use, rewrite or ignore | Attend the offsite for SourceX, or run the module on SourceX's behalf |
| Say plainly, if you send it as a SourceX partner, that SourceX could pay you if the company ever worked with it | Ask for pre-reads, notes, system lists, whiteboard photos or a debrief |
| Ask the CEO, in a normal check-in, how the offsite went | Contact other attendees about what was discussed |
| Answer a question the CEO puts to you | Treat the agenda, or the fact the module was used, as a lead |
Sometimes a partner is in the room for another reason: a board member invited to one session, or a consultant hired to facilitate the strategy work. Then you are there in that role only. Leave the data module to the company's own leaders, keep no notes for SourceX, and treat what you hear the way board information is treated: it may prompt one question to this company's CEO, it travels to no one else, and it never reaches a different company.
The optional offsite discussion module
Five parts, about 40 minutes, led by the company's own people. It never mentions SourceX, a price or a buyer, and it is useful whether or not the company ever licenses anything.
| Part | Question for the room | Who answers | What the company keeps |
|---|---|---|---|
| 1. Ownership map, 10 minutes | Which record sets do we rely on, which team created each, and who maintains it today? | Department heads | One line per record set, with an internal owner |
| 2. Promises we made, 10 minutes | What do customer contracts, employee notices and our privacy policy say about reusing those records? | Counsel, after the offsite if needed | A list of questions for counsel |
| 3. Copies outside, 5 minutes | Which outside services hold copies of our records, and what do their terms let them do? | The IT lead | A short list of vendor terms to read |
| 4. Dates that matter, 5 minutes | Which systems are due to be retired, and what happens to their history? | The IT lead or COO | A dated retirement list |
| 5. Decision rights, 10 minutes | Who decides any outside use of our records, and do we want to look at it now, later or not at all? | The CEO | One line in the decision log |
Four rules travel with it, printed at the top:
- No records, samples, screenshots or exports in the room; names of systems and record types are enough.
- No valuation and no talk of what anything might pay.
- Every output goes into the company's own decision log.
- No copy goes to any partner, investor or vendor unless the CEO decides otherwise.
Part 5 is why the module is optional in the full sense. "Not at all" is recorded as calmly as "look at it now", and a team that chooses "later" sets its own date. The module also works if the company never answers part 5: parts 1 to 4 are ordinary housekeeping that most leadership teams find useful in their own right.
The week after the offsite, compared with the week before
| What you look at | The week before | The week after |
|---|---|---|
| Who owns each record set | Known piecemeal | Named in the company's own list |
| Contract and privacy questions | Unasked | With counsel, inside the company |
| Outside use of records | Never discussed | The leadership's answer: now, later or no |
| What you know | Nothing | Still nothing, unless the CEO tells you |
| Who decides | The CEO | The CEO |
| Leadership attention | On preparing the offsite | On the action list the offsite produced |
A badly timed follow-up (Illustrative). The Monday after a 230-person distributor's offsite, a fund's platform associate emails the COO: "Heard the data session went well. Could you send the notes and the system list so we can get the SourceX introduction moving?" Every part of it is wrong. The COO does not decide; the CEO does. The notes belong to the company. A system list is exactly the kind of company material a partner never collects. And the week after an offsite belongs to its action items. The repair is an apology to the COO, a note to the CEO that nothing more will be asked, and a line on the fund's own file so no colleague repeats it.
A second kind of bad timing comes before the offsite: suggesting the module for an offsite convened to plan layoffs, a restructuring or a crisis response. Leave it out. The questions will keep, and the module is worth more in a calm year.
Module owner, CEO and the action list
Whoever led the module, often the COO, the CFO or a head of operations, may well own the follow-ups inside the company: questions for counsel, vendor terms to read, retirement dates to confirm. That is company work, and it needs nothing from you. The CEO alone decides whether the company talks to anyone outside about its records, and signs for it.
Capacity is the other check. An offsite produces more actions than a quarter can absorb, and the data questions compete with everything else on the list. If the leadership chose "later", the date is theirs; your calendar does not move it.
If the CEO brings outside use to you
The CEO may mention it in passing ("we decided to look at whether our old records could be licensed") or ask you directly whether you know anyone who does this. Then, in your own words:
Thanks for telling me. SourceX licenses business records directly from companies for AI training and decides in its own review whether a company fits, so I can't say whether yours does. If you went ahead after an introduction from me, SourceX could pay me a referral reward, separately from what it pays the company. I don't need anything from the offsite; if you'd like an introduction, the company applies and answers SourceX's questions itself. Or I can leave it there.
Before submitting anything, sign the SourceX Channel Partner Agreement. Write one dated line: the CEO's words, the step the CEO chose and who owns it. Under section 2 of the terms, SourceX credits at most one partner per company, from dated records and only once the company's application is verified, and section 4 says the reward "is paid separately by SourceX and is never deducted from the supplier's agreed compensation", so the company's payout is the same with or without you.
Other planning moments call for the same restraint. A process audit is a date, never a source; a move to professional management or a first CFO hire changes who carries work, not who decides; and the relevance-and-consent calendar sorts all of these before anyone asks.
How a borrowed module can backfire
- It can read as a pitch. A module sent by someone who could be paid may look like a sales tool. Keeping it neutral and disclosing your interest reduces that impression; it does not remove it.
- Offsites are confidential. Asking how the data discussion went can feel like asking for what was said. Ask about the offsite, not the module.
- Confidence is not a rights review. A room that agrees the records are "ours" has not read its customer contracts or privacy notices; SourceX's screening page lists client confidentiality, employee privacy and third-party contracts among the things the right to license must not breach.
- Fit is decided elsewhere. Relevance to a current program is checked in SourceX's review, and programs change.
- No outcome data. Nobody has published how often offsite discussions lead to licensing conversations, and this page implies no rate.
Method note. The module, the boundary table and the comparison were drafted on 2026-10-27 from SourceX's terms in version 2026-10-22.2, since replaced by version 2026-11-04, its screening profile and its FAQ. They describe a division of roles between a company and a partner; they record no company's offsite and measure nothing.
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.
If a CEO comes back from an offsite wanting to talk to SourceX, register as a partner, check the company against the published screening profile and read the program terms before making the introduction; related timing guides are collected in the guides hub.
Helping a portfolio company plan its year is portfolio work, and so is any referral that follows; weighing SourceX as an investment is a different decision altogether, for which materials can be requested 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.