How to separate research participants from referral leads: a two-track event registration design with its own consent, owner, list and withdrawal for each track, and a no-join rule so a founder who answers your research never becomes a lead by default

Short answer

Run research and referral interest as two tracks that share nothing but the event seat. Each track gets its own tick box, its own wording, its own owner, its own list and its own withdrawal. Neither is a condition of attending, and neither is inferred from the other. Research answers never become a contact list, and a request to hear about SourceX reaches the research only as a count. If you are tempted to compare the two person by person, report them side by side instead.

Visual briefFull-size diagram
A registration card with the seat confirmed and two unticked boxes, research and follow-up, feeds two separate horizontal lanes: the research lane runs to a research store and ends at totals only, the follow-up lane runs to a follow-up list and a private reply and ends at CEO decides; a dashed orange wall between the lanes reads no row-level join.
Illustrative design. Each track has its own consent, owner, list and withdrawal; only event totals cross between them.

This runbook is for a VC community lead whose founder events do two jobs: the community studies what founders want to know about their company records, and the fund, or some of its people, take part in SourceX's referral program. The founder roundtable runbook covers running a research-first session and the event quality funnel covers reading outcomes. This page is the plumbing under both.

How one registration form turns a research answer into a lead

The leak is rarely a decision. It is a form field, a shared spreadsheet or a helpful colleague.

Where it happensWhat it looks likeWhat the founder believed
One consent box"I agree to be contacted about relevant opportunities" next to the questionnaireThat the questionnaire was the point
A helpful researcherAn interview note saying "sixteen years of claims files, strong fit" forwarded to whoever holds the partner accountThat interview answers stay in the study
The attendee listEvery registrant added to a post-event SourceX emailThat attending was all they agreed to
A flag in the datasetA "referral interest" column beside named answersThat their answers were analyzed without a name attached
One withdrawalLeaving the study also deletes a follow-up they still wanted, or leaving the follow-up leaves their answers in useThat each yes could be taken back on its own
Fit questions in disguise"How many years of records does your company keep?" asked as researchThat the question was about the topic, not their company

Market research has a standard written for exactly this. The ICC/ESOMAR International Code says researchers "must diligently maintain a clear distinction between research and non-research activities", requires that people be told about promotional or commercial follow-up before any data is collected, and adds: "Separate consent must be obtained for non-research purposes." Whether a community event is research in the Code's sense, and whether the Code binds you, are questions for your counsel; founders will judge you by its standard either way.

The program points the same way. Nobody collects company data for SourceX, a partner never needs to export or describe a company's records, and the company applies itself if its CEO decides to. A questionnaire that quietly screens companies for fit does a job nobody asked the community to do.

The two-track event registration design

Confirm the seat first. Then show two optional boxes, both unticked, each with its own short paragraph.

ElementTrack R: research participationTrack F: follow-up about SourceX
The questionMay we use your answers to a short questionnaire, without your name or company, in our study of founders' questions about company records?Would you like a private follow-up about SourceX's company program after the event?
DefaultUnticked; the seat does not depend on itUnticked; the seat does not depend on it
What it collectsTopic interest and understanding items; no company name, headcount, systems or record descriptionsName, email and the question the person wants answered; nothing about the company's records
OwnerA named research lead who holds no partner account and earns no rewardThe community lead or the person who owns the founder relationship
Where it livesA research store keyed by a random codeA follow-up list kept apart from the research store
Who may read itThe research lead, and an analyst bound by the same ruleThe follow-up owner only
What it can produceEvent totals and themes, released after a disclosure reviewOne private reply; then, if the CEO wants it, an introduction or the company applying itself
WithdrawalEnds Track R onlyEnds Track F only
RetentionDeleted on a published date after totals are reportedUntil the follow-up closes
DisclosureWho runs the study and what the totals will be used forThat the fund or person may be paid by SourceX, and that the company's payment is the same either way

The no-join rule. The two stores are never merged at the level of a person. The only numbers that cross between them are event totals: attendees, research consents, follow-up requests. If someone wants to know whether founders who understood the program asked for more follow-up, the honest answer is that this design cannot say, and that is deliberate. A person-level comparison would need a third, explicit consent and an analyst with no referral interest. The default is not to run it.

Consent records. For each box keep the wording version, timestamp and channel, so a later reader can see exactly what each person agreed to.

Method note. Built for this page from SourceX's terms (Version 2026-10-22.2, since replaced by version 2026-11-04), its screening and how-it-works pages, section 4.5 of the sample partner agreement and the 2025 ICC/ESOMAR Code, all read on 2026-10-28. Field choices, owners and the no-join rule are this page's own; the design is untested, and nothing here measures how founders respond to it.

Wording for the two boxes (Illustrative)

Illustrative. Adapt it with your counsel; the brackets mark choices only you can make.

Your seat is confirmed. Two optional extras follow. Each is separate, and saying no to either changes nothing about your seat.

Research (optional). [Community name] is studying which questions founders have about their company records. If you tick this box, we will send a ten-minute questionnaire. Your answers are stored under a code, without your name or company, and we report only totals. They are never used to contact you about any company or program. You can withdraw until [date].

Private follow-up (optional). If you would like someone to answer a question about [SourceX's company program, named only once SourceX has authorized it in writing] after the event, tick here and tell us your question. If a company we introduce completes a licensed transaction, SourceX may pay us a referral reward. SourceX pays it separately, so the company's own payment is unchanged. Whether your company ever talks to SourceX is your CEO's decision.

The bracket matters: section 4.5 of SourceX's sample partner agreement bars either party from publicly identifying the other as a partner without written authorization, and a registration page is public. The payment sentence rests on section 4 of the terms: "The referral reward is paid separately by SourceX and is never deducted from the supplier's agreed compensation."

When the tracks touch during and after the event

An interview reveals fit signals. A founder tells the researcher the company has kept every service ticket since 2009. The researcher stores the theme under the code, with no company detail, and tells the follow-up owner nothing. At the end of every interview, the researcher reads the same sentence: a separate follow-up route exists if you want it.

A founder asks a company-specific question in the open Q&A. Answer the general rule in the room and stop before the company's facts are spoken; the workflow for questions that need private context covers the handoff. The private route is Track F, and only if the founder chooses it.

Fit comes up in the follow-up. Answer from SourceX's published pages, never from a guess. A company's full-time headcount must have reached 50 or more at its peak, and it needs years of its own records, the rights to license them and a CEO who wants 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 fits a current program is decided only in SourceX's review.

The founder runs a portfolio company. Whatever the fund knows from a board seat enters neither track. It may prompt one question to that company's CEO, and it never travels further.

Write this down and post it before the first invitation goes out.

Sampling frame. Everyone registered for a named event, counted per event; every rate divides by attendees who checked in, not registrants.

Consent process. Two versioned boxes as above, Track R consent captured before the questionnaire opens, and nobody re-asked after a no.

Variables, Track R. Topic interest, plus four understanding items:

  1. Who decides whether a company discusses licensing its records? (Scored correct: the CEO.)
  2. Would a partner's reward reduce what the company is paid? (Correct: no.)
  3. Will your questionnaire answers be used to contact you about SourceX? (Correct: no.)
  4. What does a company need before SourceX will consider it? (Open text, coded against the published criteria.)

Variables, Track F. Counts only: follow-up requests, requests answered, CEO-approved introductions, and the stages a partner dashboard later shows for those introductions.

Measures. Research participation rate: Track R consents divided by attendees. Requested follow-up rate: Track F requests divided by attendees. Understanding: share correct on each item, divided by the Track R participants who answered that item. The two tracks are reported in adjacent columns, never in one cross-table.

Missing, declined and unsuccessful cases. Report registrants who did not attend, attendees who ticked neither box, items participants skipped, and follow-ups that ended without an introduction because nobody replied, the company did not fit, the CEO declined, or SourceX declined the application.

Descriptive, not causal. Two events have different audiences, so a change in rates between them says nothing about the form. For a causal answer, randomize two consent wordings across one event's registrants and name one primary measure in advance, such as item 3.

Results. No event has been run under this design for this page, and no figures are published.

Optional at every step

StepFounder may skipFounder is toldPrivate route
InvitationEverything but reading itThe host may be paid by SourceXNone needed
RegistrationBoth boxesThe two paragraphs aboveTrack F box
The eventQuestions, questionnaire, Q&ANo attendee list leaves the hostTrack F, any time
AfterwardAny replyOne recap with public links onlyThe Track F owner

The recap links SourceX's public pages, so a founder can read who qualifies without asking anyone. For what to ask before a session, see the pre-webinar survey design.

Where the two-track design can fail

  • Small rooms. At a twelve-person dinner, totals can identify people. Set a minimum cell size before the event and publish nothing below it; the anonymization and consent review gives the full test.
  • One person, two hats. Where the researcher and the follow-up owner are the same person, analyze Track R only after every follow-up has closed, and say so in the method.
  • Founders may not believe it. Anyone who has seen research used as a sales funnel will expect it again. Item 3 measures that suspicion; a low score means the wording failed.
  • A request is not a fit. A full Track F list says nothing about whether any company qualifies. Credit under the terms comes only from a valid introduction, decided from dated records once the company files a verified application, and a click on a partner link alone does not decide it.
  • Rules differ by place. The ESOMAR Code is a benchmark; what consent must contain where your founders live is for your counsel.

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.

When a Track F founder's CEO wants the conversation, register as a partner and sign the Channel Partner Agreement before introducing anyone, check who qualifies, and quote the program terms in your reply.

Running events for founders is referral work; deciding whether SourceX is worth investing in is a separate question, and readers weighing it can ask for 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

Can one tick box cover both the research and a SourceX follow-up?

Not in this design. A combined box makes research participation the price of hearing about SourceX, or the reverse, and the person cannot say yes to one and no to the other. Two boxes, both unticked, with the seat confirmed before either appears.

Our researcher heard that a founder's company looks like a strong fit. May they tell the community lead?

No. What a participant says in research stays in research. The researcher may tell every participant, in the same words, that a separate follow-up route exists; whether to use it is the founder's choice, and whether the company talks to SourceX is the CEO's.

Is a follow-up request a referral in SourceX's sense?

No. It is a person asking a question. Credit under the terms comes only from a valid introduction the CEO agreed to, made by a partner who has signed the Channel Partner Agreement, and is decided from dated records once the company files a verified application.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. refer.sourcex.si/how-it-works
  4. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  5. standards.esomar.org/assets/documents/icc-esomar-code-2025.pdf
  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