The event follow-up that records what the founder requested: a read-back template that quotes each request, says what was done and what was not, and leaves every introduction to the company's CEO

Short answer

Follow up on what each founder asked for, not on the fact that they came. Note every request at the event in the founder's own words, then send one read-back that quotes it, says what you did, says what you did not do and names the one step still waiting for the company's CEO. Someone who is not the CEO can ask for information but cannot ask for the company to be introduced. Anyone who asked for nothing hears nothing.

Visual briefFull-size diagram
An Illustrative receipt titled one request, read back, itemizing what a founder asked for after a summit: under requested, a fit criteria link marked sent; under not requested, any list and a word to SourceX, both marked none; under waits for the CEO, an introduction marked on request; and a total line reading introductions made 0. A note beside it says wrong? reply and we correct it.
Illustrative read-back. The layout follows the template on this page; the event and founder are invented.

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

MomentCollectNever collect
RegistrationName, work email, company, roleHeadcount, systems, record volumes, "how much data do you hold?"
In the roomRequests, written on a card by the host team in the founder's wordsBusiness cards scanned into a referral list; notes about a company's records
AfterwardsOne read-back per requestAttendee 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

FieldWhat goes in it
Requested byName 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 wordsNo more than 25 words, in quotation marks
KindMaterial, a question, a conversation with SourceX, or an introduction
What we said at the eventAnything the host promised, as close to word for word as possible
DoneDate, and a pointer to the sent message
Waits forNothing, or the CEO's written request
Do notAnything 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)KindWhat the read-back doesNeeds the CEO?
"Send me whatever explains who fits."MaterialLinks who qualifies and how it worksNo
"Can you find out if our maintenance logs would count?"QuestionExplains that the company can put that to SourceX itself, and that the fund does not relay company factsNo
"I'd like to talk to someone at SourceX." (a COO)ConversationSends the public pages and notes that the company can apply directly; an introduction from the fund needs the CEOYes, for an introduction
"Please introduce us." (the CEO)IntroductionConfirms in writing and asks whether the company has ever dealt with SourceX; then the fund's partner of record submitsIt is the CEO
"Send me the slides."MaterialSends the slides with the disclosure slide left inNo
"What would we get paid?"QuestionSays nobody at the event could know: SourceX looks at records with the company, and an indicative range is not a payoutNo
"Please don't follow up."StopRecords it and sends nothing, not even a confirmation unless one was asked forNo

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.

RequesterCEO?RequestKindStatus after five working days
R1, COONo"Who at SourceX would we talk to?"ConversationRead-back sent; she will raise it with her CEO herself
R2, CEOYes"Introduce us once I've checked with my board."IntroductionRead-back quotes the condition; waiting for her written request
R3, CEOYes"Send the slides."MaterialSent
R4, CFONo"What would a deal pay?"QuestionAnswered: not knowable before SourceX's review
R5, CEOYes"Please introduce us."IntroductionNo earlier contact known; submitted on day 2
R6, founder, now chairNo"Don't add me to anything."StopRecorded; 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

MeasureDenominatorWhy it matters
Requests per attendeeAttendeesHow often the event raised a concrete question
Read-backs sent within five working daysRequestsWhether the host kept its side
Corrections receivedRead-backs sentWhether notes were accurate; zero over many events may mean nobody reads them
Unrequested messagesAttendees who asked for nothingShould stay at zero
CEO introduction requestsAttending CEOsWhether decision makers, not only staff, found it worth a step
UnderstandingFounders 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.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Should every attendee at least get a thank-you note?

A thank-you that carries no SourceX content is ordinary event courtesy and sits outside this template. The moment a note mentions data licensing, the referral program or a next step, it needs a request behind it.

How quickly should the read-back go out?

Within five working days, while the founder still remembers the conversation and can correct your note. A read-back sent weeks later reads like a sales sequence that happens to quote them.

Can the fund's notes from the event be shared with SourceX to save the founder time?

No. The company tells SourceX about itself when it applies or when its CEO asks for an introduction. Event notes record what a founder asked the fund for; they are not a company profile and never travel to SourceX.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/how-it-works
  3. refer.sourcex.si/who-qualifies
  4. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  5. faa.gov/air_traffic/publications/aim_html/chap4_sect…
  6. sourcex.si/investors

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment