# Demo day data referral follow-up email | SourceX

Canonical: https://refer.sourcex.si/guides/a-demo-day-follow-up-that-does-not-assume-dataset-fit
Last updated: 2026-11-05

Send one email that lets readers judge relevance, never one that presumes their company holds a licensable dataset. Companies pitching at a demo day have usually just finished an accelerator batch, so SourceX's size and history tests rule most of them out for now; guests who run or work at established companies, and investors who know such CEOs, are more often the readers it concerns. Put the published tests first, disclose the fund's possible reward, offer four reply words including no, and send nothing further unless someone replies.

This is for a VC community lead who added a short data licensing session or mention to a demo day and now has to follow up. The demo day's own recap is not the place for it; this is a separate, optional note.

## Who reads a demo day follow-up

Demo days gather a particular room. Y Combinator, for example, describes its Demo Day as the event where founders from its latest batch present their companies to an invited audience of investors and press, and it describes the batch itself as running about three months (our paraphrase of both pages). Other programs differ, so read your own program's description. Our reading, not a measured finding: a company presenting at the end of a three-month batch has rarely had time to reach a full-time headcount of 50 or build years of its own records.

That matters because SourceX's screen ignores funding entirely and asks about size, history, rights and authority. Its published profile looks for a peak full-time headcount of roughly 50 or more (contractors excluded), several years of records the company created in its own work, the right to license them, and a CEO who authorizes the discussion. 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. Whether a company's records suit a current program stays unknown until SourceX reviews them.

| Reader | How the screen usually lands | What the email offers | What it never says |
|---|---|---|---|
| Founder who pitched | Usually not yet, on size and history | The tests in plain words and a reason to look again later | "Your data could be valuable" |
| Founder from an earlier batch | Sometimes, depending on growth since | The tests and the self-check | "You qualify" |
| Guest executive at an established company | Possible; that company's CEO decides | A way to pass the note to their CEO | "We will contact your CEO" |
| Investor or limited partner in the audience | Not a candidate; may know CEOs of mature companies | A pointer to the partner route | "Every portfolio company is a fit" |

The established-company readers are the reason the email exists at all; where they tend to sit in a venture network is mapped in [finding mature businesses in an early-stage fund's network](/guides/how-to-find-mature-businesses-in-an-early-stage-fund-s-network), and why history beats stage is argued in [operating history versus funding stage](/guides/when-operating-history-matters-more-than-funding-stage).

## The post-event relevance email, line by line

Illustrative template. Adapt the wording; keep each line's job.

> **Subject:** After demo day: a test, not a pitch
>
> You ticked "send me follow-ups" when you registered, so here is one note about the data licensing session. It is the only message we will send on this topic.
>
> SourceX pays established companies to license business records they produced themselves, such as support histories, project files and process documents, for training and evaluating AI. SourceX decides after its own review whether a company is a candidate, and that company's CEO decides whether to apply.
>
> Most companies that pitched today are too new for this, and that is expected. The screen comes first: a peak of at least 50 full-time staff, years of the company's own records, the right to license them and a CEO who wants the conversation.
>
> Our fund could be paid. If a company we introduce licenses data, SourceX may pay us a reward, separately from what it pays the company and never out of it.
>
> Reply with one word. READ: we send SourceX's published pages. CHECK: we send the non-binding fit checker. CEO: you run a company and would like an introduction, or you will ask your CEO. NO: we will not raise this with you again.
>
> If you do nothing, nothing happens. To leave this list entirely, reply STOP.

| Line | Its job | What it replaces |
|---|---|---|
| Why you are getting this | Ties the email to a box the reader ticked, and promises one message | A cold sequence to every attendee |
| What SourceX does, and who decides | Separates SourceX's review from the CEO's choice | "We have a great opportunity for your company" |
| The screen comes first | Lets most founders rule themselves out in one sentence | "Your startup's data could be worth a lot" |
| Our fund could be paid | Puts the conflict in front of the ask | A disclosure buried in a footer, or none |
| Four reply words | Makes every answer, including no, one word long | "Book a call this week" |
| Nothing happens | Removes the reminder the reader expects | A three-step follow-up cadence |

What the email leaves out matters as much: no dollar figures, no examples of other companies, no deadline, no attachment, no tracking pixel and no SourceX logo beside the fund's. The partner agreement bars partners from telling a company that an estimate or a show of interest assures a purchase or a reward, and an email that hints at value does exactly that by implication. For a different moment, an introduction email to a portfolio CEO after a first 100-day review, see the [annotated 100-day plan email](/resources/first-100-day-plan-introduction-email).

## Who receives it, and the list that stays with the fund

- **Only guests who opted in.** A registration checkbox ("send me follow-ups from side sessions") decides the list. The full attendee list is never used.
- **Never a candidate list.** The email never names or groups the companies that pitched as SourceX prospects, and no list of recipients goes to SourceX.
- **One send, one named sender.** Replies go to a platform team member with no board seat or deal role at the readers' companies.
- **NO and STOP hold everywhere.** A reader who replies NO is flagged on every channel the fund runs; the [network inventory that excludes people who declined](/guides/a-network-inventory-that-excludes-people-who-declined) shows how to keep the flag from being lost.
- **No public partner language.** The partner agreement does not let either side publicly present the other as a partner without written authorization, so the email describes the fund's referral role without calling SourceX "our partner".

US email rules may also apply. The FTC's CAN-SPAM compliance guide, in our paraphrase, says commercial email must tell recipients how to opt out, that opt-outs must be honored within 10 business days and that an opt-out may not demand more than a reply or a visit to a single web page. Whether the Act covers a given message is a question for the fund's counsel; this email offers a one-word opt-out either way and honors it the same day.

## Four reply words and what each one starts

| Reply | What the fund does next | What it never does |
|---|---|---|
| READ | Sends links to SourceX's [how it works](/how-it-works), [who qualifies](/who-qualifies) and [program terms](/terms) pages | Adds the reader to a newsletter |
| CHECK | Sends the [company fit checker](/tools/company-fit-checker) link | Asks for the result |
| CEO, from a CEO | Asks whether the company has already dealt with SourceX or been offered an introduction; after the CEO's written yes, the partner of record submits one written introduction | Submits before that answer, or before the Channel Partner Agreement is signed |
| CEO, from someone else | Suggests forwarding the note to the CEO | Contacts the CEO around the reader |
| NO | Sends one line of thanks and records the flag | Asks why |
| No reply | Nothing | Sends a reminder |

Credit follows the program's rule, not the order of replies: the first valid introduction of a new company within the 90-day window is credited once the company submits a verified application, and a company already known to SourceX is reviewed as a duplicate. When several people in the room know the same company, only one introduction can be credited, and SourceX decides overlapping cases. If a guest's company was acquired, the acquirer's CEO is the one who decides.

## Measuring relevance, not response rate

| Measure | How it is counted | Why it matters |
|---|---|---|
| Reply mix | READ, CHECK, CEO and NO replies, each against emails sent | Shows whether the note reached people it concerned |
| CEO replies that came from CEOs | CEO replies, split by whether the replier runs the company | Separates real requests from forwarded interest |
| Self-screened founders | Replies asking whether the company is too small, answered with the screen | A sign the tests landed where they should |
| Misreads | Replies that assume acceptance, a valuation or SourceX vouching for the fund | Each one is a wording fix for next time |
| Opt-outs and complaints | NO, STOP and any complaint, from anyone | A rise means the note felt like pressure |

Opens and clicks are not measured, because the email carries no tracking.

**One send, read through (Illustrative).** An invented demo day where 120 guests ticked the follow-up box. Twenty-one replied: 8 READ, 5 CHECK, 2 CEO, 4 NO, and 2 founders who asked whether their company was too small and were sent the screen. One READ reply said the note made SourceX sound like the fund's endorsed partner, so the fund rewrote that sentence. Of the two CEO replies, one came from the CEO of a 300-person regional logistics firm who had attended as a guest; after confirming no earlier contact with SourceX, the fund submitted one introduction. The other came from a guest executive, who forwarded the note to her CEO; nothing further happens unless the CEO writes. No one who stayed silent heard from the fund again.

## What could make this follow-up wrong

- **Some pitching companies are older or larger.** Spinouts and later-stage programs exist. The email lets them rule themselves in; it never rules them out by assumption.
- **Any note from a funder carries weight.** A founder may read even one email as a request. One send, a free no and no reminder keep the cost low; they do not make it zero.
- **A friendly tone can read as endorsement.** One misread in the illustrative send came from a single warm sentence. Test the wording on a colleague outside the platform team.
- **SourceX's criteria move.** SourceX applies each program's own requirements and says a company outside one program may fit another later. Date the email and reread the published screen before reusing it.
- **The fund has an interest.** Disclosure names the conflict; it does not remove it, which is why replies go to someone with no deal role.
- **No benchmark exists.** No published data shows how demo day guests respond to notes like this. The measurement table is the method; the figures are not yet published.

**Methods note.** The reader table, template and measures were built for this page from SourceX's program terms (Version 2026-10-22.2, since replaced by version 2026-11-04), its screening and process pages, the unsigned sample Channel Partner Agreement, Y Combinator's Demo Day and About pages and the FTC's CAN-SPAM guide, all read on 2026-10-27. The claim that most pitching companies fail the size and history tests is our inference from the batch length, not a count. The send is invented. A networking follow-up for one person, rather than a room, is covered in the [message templates after a networking event](/resources/linkedin-message-after-networking-event-template); the wider portfolio program is on the [venture platform teams page](/for/venture-platform-teams), and more guides are in the [guides library](/guides).

## 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 note goes out, [register the fund as a partner](/register) so a CEO reply can be acted on the same day, link the screen on [who qualifies](/who-qualifies) rather than restating your own version, and keep the [program terms](/terms) version the email quotes.

Following up a demo day is referral work; whether SourceX is a company worth investing in is a separate judgment, and readers making it can ask for materials through the [SourceX investor overview](https://sourcex.si/investors).

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.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://refer.sourcex.si/how-it-works
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://www.ycombinator.com/demoday
- https://www.ycombinator.com/about
- https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business
- https://sourcex.si/investors
