The hazards are a guest at the front with a commercial stake, a room of mostly young companies, and a host tempted to read the guest list as a prospect list. This runbook keeps the session useful to the companies in the room and gives the referral program no shortcut through it.
What to settle with SourceX, or a partner, before the date is announced
Get five answers in writing. If one is no, or never arrives, change the format rather than improvise.
| Question | Why it comes first | Who answers | If no or unclear |
|---|---|---|---|
| Will SourceX take part, and who approves the content? | The SourceX pages read for this guide (terms, screening, process and contact pages) offer no speaker or event program | SourceX, in writing, via its main website as the referral contact page directs | Present from published pages instead |
| May the invitation name SourceX or show its logo? | Section 4.5 of the Channel Partner Agreement sample grants no trademark license and bars either side from publicly naming the other as a partner without written authorization | SourceX, in writing | Name the topic, not a relationship, and use no logo |
| Who speaks, and who could be paid? | A speaker or host registered as a referral partner could earn a reward if a company in the room is later introduced and licenses its records | The speaker and the host, each about themselves | Hold the invitation until the disclosure is written |
| What if a company contacts SourceX directly afterwards? | Section 3 of the terms counts "any earlier lead, account or email correspondence between SourceX and the company, however it began" as a relationship, and such a company is not credited to a later partner | The terms; SourceX decides overlapping cases in duplicate review | Accept it before inviting anyone; for the company, going direct is an ordinary route |
| Which topics are out of bounds? | Improvised answers on price, buyers and security go wrong | The claims checklist below | List them as out of scope on slide one |
Hosts skip the fourth row most often. With a SourceX speaker, some companies will talk to SourceX before anyone introduces them; a community that minds that should not invite SourceX.
Who stands at the front changes what the room can hear
The audience asks one thing: does licensing company records for AI training apply to us, or to companies we know? Who answers sets what can be said and what must be disclosed.
| At the front | Speaks with authority on | Discloses in the invitation and on slide one |
|---|---|---|
| SourceX staff, once SourceX agrees in writing | Its own process, screening and terms | That SourceX is describing its own program, and whether the host is a registered partner |
| A registered referral partner | Only what SourceX publishes; under section 7.1 of the agreement a partner is not SourceX's agent and cannot commit it to prices, licenses or payouts | That the speaker could be paid for introductions and does not speak for SourceX |
| The host alone, reading published pages | The pages, each dated when read | Whether the host is a registered partner |
For a mixed founder community the third row is often the best default: it needs nobody's approval and nobody at the front has a reason to sell. Bring a guest only when questions go past what is published; only SourceX can speak for SourceX. The live guide on choosing between research events and direct introductions compares event formats over a quarter.
The speaker briefing and claims checklist
Two weeks out, send the speaker a one-page brief: the mix of startups and established companies invited, with no guest list attached; the exact disclosure sentence; the out-of-scope topics (prices, buyer identities, any one company's fit, security or privacy promises, investing in SourceX); and the single answer to a one-company question, that its CEO takes it up privately by one of two routes. Then walk through the checklist together.
Accredited medical education offers a tested order. ACCME's page on its Standard 3 says learners must be told about relevant financial relationships before the education begins, naming the people, companies and nature of each, with those companies' logos and trade names kept out (our paraphrase). The order transfers: disclose first, in words, with no logo.
| Topic | The speaker may say | Basis | Never say |
|---|---|---|---|
| What SourceX does | It licenses business data directly from companies for AI training and evaluation, as their counterparty through payment | Process page | Any AI developer's name as a buyer |
| Who it screens for | 50 or more full-time employees at peak (contractors excluded), years of the company's own records, rights to license them and a CEO who authorizes the discussion; funding plays no part | Screening page | That anyone here fits because of a round, a backer or this invitation |
| Where | 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. | Screening page | A list of places of your own |
| What usually does not fit | Client-owned material, personal consumer data, scraped data, and data already licensed for AI training, since the company confirms it never has been | Screening and process pages | That review can work around an earlier AI-training license |
| Who decides | The CEO; after an acquisition the acquirer's CEO, and during a pending sale the target's CEO until closing | Screening page; owner's settled rule | That an investor, a board seat or this community can say yes |
| Applying | A few questions, no files and an indicative estimate; no records are shared at that stage | Process page | Bring a sample export so we can look |
| Price | Indicative until a Dataset Deal Confirmation is signed; SourceX does not publish how offers are priced | Process page | A figure for anyone's records, or talk of easy money |
| Exclusivity | Exclusive for AI training, with the term and any alternatives set in each deal's Confirmation | Process page | Any term length, or a date the restriction lapses |
| Ownership and handling | The company keeps ownership of its original data; the selected data is extracted, transferred and de-identified through approved processing routes; neither side publicizes a deal | Process page | Fully anonymous, nobody will ever see it, any other security promise, or any company hinted at as a supplier |
| The reward | the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, one cap for a parent and its subsidiaries; paid separately by SourceX and never deducted from the supplier's agreed compensation | Terms, section 4; owner's settled rule | Any comparison of the company's payout with and without a partner |
| Credit | The first valid introduction within the 90-day window is credited once the company submits a verified application, one partner per company; a link click alone does not decide credit | Terms, sections 2 and 3 | Sign up through my link so you're registered to me |
| Access and endorsement | Attending creates no relationship, nobody gets preferential access to a company's data, and nobody collects company data for SourceX | Partner agreement, sections 4.2 and 4.5 | SourceX partners with this community, or members get priority |
Method note. Built on 2026-10-27 from the program terms (Version 2026-10-22.2, since replaced by version 2026-11-04), the screening and process pages, the unsigned partner agreement sample (version 2026-10-19) and the owner's settled rules on who authorizes and on group caps. It tests whether a sentence has a published basis, never whether a company fits, which only SourceX's review decides. Re-read the sources the week of the session.
How do you invite mature businesses to a founder community session?
Through the person who already knows each company's CEO, with an invitation that states the session's limits up front and an RSVP that asks nothing about the company. Never buy or borrow a list to reach them.
Founder communities grow around young companies; companies that may match the size and history profile usually sit around them: founders' former employers, family businesses, LP-owned companies, portfolio customers, acquirers of alumni companies. The live guides on the operating history in a founder alumni network and on founder-owned companies around a VC fund show how to find them.
Who sends. Each company hears from its relationship owner, such as the founder who used to work there or the LP principal on its board. The community lead writes the text; the owner first asks the CEO once whether they want an invitation to a talk, not a screening, and says so if the owner is a registered partner who could be paid. No mailing list, no reminder, and a no ends it, as the live guide on founder fatigue from repeated platform offers argues for any unrequested ask.
Groups and sales. Two companies in one corporate group count as one company for the reward cap. After an acquisition the acquirer's CEO decides; during a pending sale, the target's own CEO until closing. Whether one group company's past dealings with SourceX matter for a sister company is left open by the terms; SourceX settles it case by case in duplicate review.
The invitation (Illustrative wording).
Subject: A 45-minute session on licensing company records for AI training
[Relationship owner] thought this might interest you. On [date], [community] hosts a talk on how established companies license their own records for AI training and evaluation.
Speaker: [name, role]. [Either "SourceX staff will describe SourceX's own program." or "[Name] is a registered SourceX referral partner, could be paid by SourceX if a company is later introduced and licenses its records, and does not speak for SourceX."] [If it applies: "[Community] is also a registered referral partner."]
What it is not: a screening. Attending says nothing about whether your company fits, nobody asks about your headcount, systems or records, and the guest list goes to no one, the speaker and SourceX included.
Afterwards: one recap email with published links. If your company wants more, your CEO decides how: apply to SourceX directly, or ask someone in writing to introduce you.
The RSVP card.
| Ask | Never ask |
|---|---|
| Name and email, for the calendar invitation | Headcount, revenue or growth |
| Role: CEO, other executive or founder | Systems, years of records or data volumes |
| One optional question, without company figures or customer names | An "interested in licensing" box or a lead score |
| Whether the guest wants the recap | Consent to pass details to SourceX or the speaker |
The FTC's guide to protecting personal information is blunt about sensitive personal data a business has no legitimate need for: "don't keep it. In fact, don't even collect it." A talk has no use for a company's headcount or systems either. A community and its chapters never gather company records, systems or headcounts for SourceX; every introduction is one company whose CEO agreed to it.
Seats stay optional, questions go private, lists stay home
Each step of the event journey has an exit, and only the last leads toward SourceX.
- Invitation. Declining costs nothing and triggers nothing.
- Arrival. Disclosure first; name badges, no sign-in sheet.
- Talk. Checklist lines only; no show of hands by headcount, no on-the-spot "see if you qualify" slide.
- Questions. General ones are answered; one-company questions get the private-route answer. Any recording is announced in the invitation and stops before questions.
- Afterwards. One recap to every invitee, attendee or not, and no follow-up sequence.
- Private escalation. Started only by the CEO, who applies directly or asks someone in writing for an introduction. That person must already have signed the SourceX Channel Partner Agreement and introduces that one company.
The guest list, RSVP answers, questions and notes go neither to SourceX nor to the speaker; the partner agreement sample gives a partner no right to pass on a supplier's records or personal information (section 4.2). A company that decides against licensing has given a complete answer; SourceX's own article on declining an AI company that wants your data treats no as a normal outcome.
Measuring the session on four levels, none of them a pipeline
Kirkpatrick Partners describes its training evaluation model in four levels: reaction, learning, behavior and results (our paraphrase). They suit a guest session if the fourth stays off the host's scorecard.
| Level | What the host counts | Denominator | Reading |
|---|---|---|---|
| Reaction | Guests marking the session useful on a one-question card | Cards returned | Low scores from established companies: the talk was pitched at startups |
| Learning | Exit cards answering two items as the published rules do: who decides (the CEO) and whether attending means a company fits (no) | Cards returned | Wrong answers point at the brief |
| Behavior | CEOs who asked the host or a named member in writing for an introduction within 30 days, plus private questions | Established companies that attended; counted, never targeted | Direct applications stay invisible, so it undercounts |
| Results | Nothing: acceptance, licensing and any reward are SourceX's decisions, months later if ever | Not applicable | Counting it turns the session into a funnel |
Also count established companies invited and attending per relationship owner, and any guest who felt sold to. SourceX has published no results from community sessions, so the first session sets the baseline.
What can still go wrong with a guest at the front
- The stake at the lectern. Disclosure tells the room a speaker could be paid; it does not stop that interest shaping the emphasis, and a SourceX logo on the event page implies an endorsement SourceX has not given in writing.
- The room. Most founders present lead companies years away from the size and history profile. Say so in the invitation, or they will hear an offer that does not apply to them.
- Direct contact. With SourceX present, some companies become direct relationships that no introduction can be credited for.
- Price and demand. The most-asked question has no published answer, relevance to current data needs is judged in review, and a company that fits no program today may fit one later.
- Rights. The records a company knows best often belong to its clients, which the screening page lists as usually not a fit.
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 who heard the session asks for an introduction, register as a partner and sign the agreement first, check what the CEO told you against who qualifies, and keep the program terms open while you write it; the venture platform overview, the company fit checker and the guides library cover what follows.
Hosting a guest session is community work; deciding whether SourceX itself is worth investing in is a separate matter, and materials for it 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.