This is for the community or platform lead who runs a fund's founder events, from portfolio summits to sector breakfasts, and owns the week afterwards. It assumes the fund is, or may become, a SourceX referral partner, which makes the follow-up the point where a polite event can quietly become a funnel.
An attendance list is not a list of requests
Three lists get confused after an event. Registration says who signed up; attendance says who came; the request list says who asked for something specific. Only the third justifies a message. Treating the first two as interest is how a founder who came for the coffee ends up in a sequence, and how a CTO's offhand "sounds interesting" becomes "the company is keen" in a fund's notes.
A request has four parts: a named person, their role at the company, a specific thing they asked for and the words they used. With any part missing you hold an impression, not a request, and impressions get no follow-up.
What the event may collect, and what it never asks
| Moment | Collect | Never collect |
|---|---|---|
| Registration | Name, work email, company, role | Headcount, systems, record volumes, "how much data do you hold?" |
| In the room | Requests, written on a card by the host team in the founder's words | Business cards scanned into a referral list; notes about a company's records |
| Afterwards | One read-back per request | Attendee lists for SourceX or anyone else |
Role matters because only the company's CEO can authorize a licensing discussion. And the community never suggests that attending says anything about a company's fit, that SourceX endorses the community or its members, that anyone gets preferential access to a company's data, or that the fund can decide anything on a company's behalf.
The requested-next-step follow-up template
Two parts: a ledger row the host team fills in within a day, and the read-back message built from it.
The ledger row
| Field | What goes in it |
|---|---|
| Requested by | Name and role, as the person gave them |
| CEO? | Yes, no or not known; after an acquisition closes, the acquirer's CEO decides for the company |
| Request, in their words | No more than 25 words, in quotation marks |
| Kind | Material, a question, a conversation with SourceX, or an introduction |
| What we said at the event | Anything the host promised, as close to word for word as possible |
| Done | Date, and a pointer to the sent message |
| Waits for | Nothing, or the CEO's written request |
| Do not | Anything the person asked you not to do |
The read-back message
At [event] on [date] you asked: "[request, in their words]".
What we did: [one line, for example: here is SourceX's page on which companies fit].
What we did not do: we have not mentioned your company to SourceX or added you to any list.
What waits for [CEO's name]: an introduction happens only if [CEO's name] asks us for one in writing.
Our interest: our fund is a SourceX referral partner and could be paid a reward by SourceX if a company we introduce licenses data. SourceX pays it separately, and it never comes off the company's agreed compensation.
If we have any of this wrong, reply and we will correct our note.
When the requester is the CEO and asked to be introduced, the "did not do" and "waits for" lines give way to the two checks described below the next table.
The last line does the real work. Aviation radio uses the same habit for the same reason: the FAA's Aeronautical Information Manual asks pilots to read back the parts of a clearance that carry altitudes, vectors and runway assignments so both sides can verify them, and notes that reading numbers back catches the ones that were misheard or wrong (our paraphrase). Event notes are written in noise and in a hurry. A read-back lets the founder fix them before anything depends on them.
Matching each request to its next step
| What the founder said (Illustrative) | Kind | What the read-back does | Needs the CEO? |
|---|---|---|---|
| "Send me whatever explains who fits." | Material | Links who qualifies and how it works | No |
| "Can you find out if our maintenance logs would count?" | Question | Explains that the company can put that to SourceX itself, and that the fund does not relay company facts | No |
| "I'd like to talk to someone at SourceX." (a COO) | Conversation | Sends the public pages and notes that the company can apply directly; an introduction from the fund needs the CEO | Yes, for an introduction |
| "Please introduce us." (the CEO) | Introduction | Confirms in writing and asks whether the company has ever dealt with SourceX; then the fund's partner of record submits | It is the CEO |
| "Send me the slides." | Material | Sends the slides with the disclosure slide left in | No |
| "What would we get paid?" | Question | Says nobody at the event could know: SourceX looks at records with the company, and an indicative range is not a payout | No |
| "Please don't follow up." | Stop | Records it and sends nothing, not even a confirmation unless one was asked for | No |
The introduction row carries two checks that protect the company. A company with any earlier application, account, lead or email correspondence with SourceX is a duplicate and is not credited to a later partner, so the question about earlier contact comes before submission, not after. And whoever submits must already have signed the SourceX Channel Partner Agreement. From there the program's rule applies: within the 90-day window, the earliest valid introduction of a company SourceX did not already know earns the credit, once that company submits a verified application. The partner agreement also wants an introduction recorded in writing, which is one more reason a spoken "introduce us" over drinks becomes a written request before anything is submitted.
When the person who asked is not the CEO
Most event requests come from someone other than the CEO: a COO who liked the session, a head of operations who knows where the records live. Their request is real and gets its read-back. What it cannot do is authorize a licensing discussion, which the CEO decides.
So the ledger marks "waits for the CEO", and the read-back asks the person how they would like the CEO approached: they raise it internally themselves, or the fund's relationship owner asks the CEO once, with their knowledge. The fund never goes to the CEO behind the requester's back and never treats a deputy's enthusiasm as the company's answer; SourceX's own screening guidance counts introductions made without the decision maker's knowledge among the usual poor fits. If the company is being sold, the target's CEO decides until closing and the acquirer's CEO after it.
One summit's request ledger (Illustrative)
Illustrative. A generic 40-founder portfolio summit; invented people and requests.
| Requester | CEO? | Request | Kind | Status after five working days |
|---|---|---|---|---|
| R1, COO | No | "Who at SourceX would we talk to?" | Conversation | Read-back sent; she will raise it with her CEO herself |
| R2, CEO | Yes | "Introduce us once I've checked with my board." | Introduction | Read-back quotes the condition; waiting for her written request |
| R3, CEO | Yes | "Send the slides." | Material | Sent |
| R4, CFO | No | "What would a deal pay?" | Question | Answered: not knowable before SourceX's review |
| R5, CEO | Yes | "Please introduce us." | Introduction | No earlier contact known; submitted on day 2 |
| R6, founder, now chair | No | "Don't add me to anything." | Stop | Recorded; nothing sent |
Forty people attended and six made requests; the other 34 get no message. R2's request is conditional, so the ledger waits and nobody contacts her board. R6 founded the company but no longer runs it, so the ledger marks him as not the CEO. For the different case of one relevance note to every demo day guest who asked to hear more, see a demo day follow-up that does not assume dataset fit; for a request to wait, see following up after a company has asked for more time.
Counting requests, read-backs and corrections
| Measure | Denominator | Why it matters |
|---|---|---|
| Requests per attendee | Attendees | How often the event raised a concrete question |
| Read-backs sent within five working days | Requests | Whether the host kept its side |
| Corrections received | Read-backs sent | Whether notes were accurate; zero over many events may mean nobody reads them |
| Unrequested messages | Attendees who asked for nothing | Should stay at zero |
| CEO introduction requests | Attending CEOs | Whether decision makers, not only staff, found it worth a step |
| Understanding | Founders who answer one optional question in the read-back: "Who decides whether your company talks to SourceX?" | Whether the event made the CEO's role clear |
Method note. These measures follow from the template's purpose and SourceX's published rules, checked 27 October 2026. The summit ledger is invented, SourceX publishes no figures on event follow-up, and none are implied here. Collect at least two events before comparing rates, and never report by company name. What founders do after they leave the read-back thread is not measured.
Where a request-led follow-up can fail
- Notes are wrong. A read-back catches some errors, not all, and silence is not confirmation.
- Requests made to be polite. "Send me something" at a reception may mean nothing; the read-back's low-key tone lets it lapse.
- Relationship pressure. A founder whose investor hosts the event may feel a request is expected. Say at the event that nothing is, and keep the follow-up consistent with that; avoiding founder fatigue from repeated platform offers covers the cumulative cost.
- People move. A requester who leaves the company takes the request with them, and the ledger row closes.
- The fund sees only itself. It cannot tell whether the company already talked to SourceX or another partner introduced it; only one introduction can be credited, and SourceX decides overlapping cases in duplicate review.
- The premise. The idea that established companies hold records AI developers want is a thesis, not a settled fact, and whether any one company's records are relevant is checked in SourceX's review against a current program.
Questions the host team cannot answer belong in a list of their own, as in a backlog for founder questions your platform team cannot answer. If the event was a webinar, keeping a referral webinar from becoming a payout pitch covers the session itself. More guides are in the guides library.
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 event, register the fund as a partner so a CEO's written request can be acted on the same week, link who qualifies in the material read-back and keep the current program terms behind the disclosure line.
Following up on founders' requests is referral work; evaluating SourceX itself as a possible investment is a separate decision, and anyone weighing it can request investor 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.