How to handle a lead passed through multiple investors: an introduction-chain transparency log that traces every hop, strips what should never have traveled and leaves one person to make the ask

Short answer

Stop the lead where it reached you and rebuild the chain hop by hop before anyone contacts the company. For each hop, note who told whom, when and in what words, then test every fact against one question: would the company have let this travel? Remove whatever came from board packs or other confidential material, hand the ask to the person closest to the CEO, and let one partner submit a written introduction once the CEO wants the conversation. Nobody forwards a referral link down the chain.

Visual briefFull-size diagram
A lead passes from a family office to Fund A, Fund B, a portfolio founder and the company CEO, with a log tag under each hop: verify with the CEO, strip the headcount, retract the forwarded link, and one ask from the founder; an arrow back from the CEO shows the CEO picking Fund B to submit the one written introduction.
Illustrative chain. People, dates and log entries follow the worked example on this page; no real firms.

Leads in venture networks rarely arrive first-hand. A family office principal mentions a company to a fund partner, who tells a platform lead at another fund, who asks a portfolio founder. By the time the lead reaches someone ready to act, three people have retold it and nobody in the chain has asked the company's CEO anything.

Why a lead decays at every hop

Each retelling drops a hedge or adds a guess. W3C's PROV data model describes provenance as information about the entities, activities and people involved in producing a piece of data, which can be used to judge how far it can be trusted (our paraphrase). A secondhand lead needs the same treatment as data of unknown origin: its worth depends on knowing who said what, when and on what basis.

What left the sourceWhat arrived three hops laterWhat changed
"About 120 full-time staff, I think""Big company, easily fits"A fit fact became an assumption
"Their CFO asked what AI firms pay for records""They want to license their data"Curiosity became an intent the CEO never stated
The CEO said "not this year""Timing is open"A no became a maybe
A figure from a recent board pack"Revenue is climbing fast"Confidential material now sits in three inboxes
One investor's referral linkThe same link, forwarded twiceAn attribution record nobody meant to create

None of these changes is dishonest. Each is a small compression, and together they produce a lead that could not survive the first question from the CEO.

Rebuild the chain and test the company's permission at each hop

Ask each person upstream for their own piece only: whom they told, when, the words they used and where they learned it. Do not ask anyone to retell other hops; reconstruct those from the people who made them.

Then mark, hop by hop, whether anyone at the company knew the lead was traveling. SourceX's screening page lists introductions made without the decision maker's knowledge among those that usually do not fit, and a chain is the easiest place for that to happen. The same page notes that what a fund learns through board packs or information rights comes with a confidentiality duty. If one hop is a limited partner, the route normally runs through the general partner rather than through fund reports, as whether a limited partner can contact portfolio companies explains.

The introduction-chain transparency log

One row per hop, eight fields. Fill it from what each person tells you about their own step, and keep it to yourself: it is a working record, not something to send the company.

FieldWhat to writeWhy it matters
HopA sequence number counted from where the lead beganShows how far you are from the source
From and toNames and roles of the two peopleTells you who can confirm the step
Date and channelWhen, and whether by call, email, message or meetingCredit is read from dated records, and a call leaves none
Words passedWhat was said, as close to verbatim as the sender recallsShows where a hedge fell away
BasisPublic, said by the company with permission, from confidential material, or unknownDecides what may travel further
Company awareYes, no or unknown, and who at the companyA lead the CEO never heard about usually fails
Link forwardedWhose referral link, if any, and to whomFlags a record you may need to explain
ActionKeep, strip or verify with the CEOThe only field that changes the next step

A filled log (Illustrative). The people, dates and company are invented. The company is a 230-person industrial parts distributor.

HopFrom and toDate and channelWords passedBasisCompany awareLink forwardedAction
1Family office principal to Fund A partner2 September, dinner"Their CFO asked what AI firms pay for records"The CFO, with no permission to repeat itCFO onlyNoneVerify with the CEO
2Fund A partner to Fund B platform lead9 September, call"Big distributor, about 300 staff, wants to license"Headcount from a lender deck Fund A reviewedNoNoneStrip the headcount; verify the rest
3Fund B platform lead to Fund B portfolio founder15 September, email"Do you know their CEO? Possible data fit"Public facts onlyNoFund B lead's link, sent to the founderRetract the link; keep the question
4Portfolio founder to the distributor's CEONot yet sentNothing so farNot applicableNot yetNoneHold until one person owns the ask

The log does its work at hops 1 to 3. The CFO's question at hop 1 was idle curiosity until verified. The "about 300 staff" at hop 2 came from a document Fund A received in confidence, so it is stripped, and the true number is asked of the company. The link at hop 3 is withdrawn, because nobody had yet agreed who would introduce. Section 3.3 of the partner agreement sample adds a reason to keep the log as written: in a dispute, original evidence must not be erased.

Who asks, decided from the end of the chain

The ask goes through the person nearest the CEO, and the introduction comes from one partner the CEO knows about. In the example, only the portfolio founder knows the distributor's CEO, through a monthly account call, so the founder asks whether the CEO would like to hear about SourceX and from whom. The CEO agrees and names Fund B's platform lead, who has signed the SourceX Channel Partner Agreement and submits one written introduction with the founder copied. The family office principal and the Fund A partner each get a short note saying they have stood back.

Three rules come out of it:

  1. Relationship decides who asks. Position in the chain, seniority and who heard first do not.
  2. Writing decides what counts. Section 1.2 of the agreement sample wants each introduction recorded in writing, and an oral one confirmed in writing before its protection attaches.
  3. No path means no ask. If nobody in the chain knows the CEO, park the lead. A cold email presented as a warm introduction spends every upstream relationship at once.

Deals that ended without a purchase raise a similar handoff, covered in what to do with search fund deals you passed on.

Section 2 of the program terms is the reference: "Attribution is decided from dated records, including written introduction evidence, existing applications and preexisting relationships; an earlier link click alone does not decide credit." So the dinner remark at hop 1 is not a written introduction, and the link forwarded at hop 3 decides nothing by itself. Credit goes to the first valid introduction of a new company inside the 90-day window, once the company submits a verified application, and only one partner is credited.

Section 3 can end the lead outright. If the CFO from hop 1 had already emailed SourceX, the company has a relationship with SourceX and no partner will be credited. When two people in a chain both submit, SourceX settles it in duplicate review from dated evidence; the terms state no rule about chains, so do not promise anyone an outcome. What to include if review asks is set out in the evidence to include in an attribution question, and written introductions versus referral links compares the two kinds of record.

Who hears what afterward, and who is paid

Updates. The partner who submitted receives news of its own referral in generic stages or reference codes (section 4.6 of the agreement sample), limited to what it needs to follow that referral (section 3.4). Upstream hops hear what the CEO is happy for them to hear, passed on by the submitter. Section 7 of the terms keeps every partner away from other partners' records.

Money. One partner is credited, and SourceX pays nobody else in the chain. Promise the upstream hops nothing; any thank-you between investors sits outside the program and inside each firm's own rules. Illustrative: if the distributor were later paid USD 200,000 by SourceX under its signed agreement, the submitter's reward on that first qualifying transaction would be USD 60,000 (the greater of USD 50,000 plus 5% and 15%), and the other three people in the chain would receive nothing from SourceX. That reward comes from SourceX's side of the ledger; section 4 bars subtracting it from what the company agreed to be paid.

Fit facts to re-ask at the source

Every fit fact in a secondhand lead is suspect, so the person who asks gets them again from the CEO, or from someone the CEO names, as descriptions only:

  • Did full-time headcount reach 50 at its peak, leaving contractors out?
  • How many years of its own records does the company hold, and in which systems?
  • Are the records the company's own rather than its clients'?
  • Has anyone at the company been in touch with SourceX before?
  • Where is it? 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.

Nobody in the chain sees records, inventories or data rooms, and whether the records suit a current program is for SourceX's review to judge.

When the log tells you to drop the lead

Our thesis is that logging a chain before outreach prevents duplicate approaches and stops confidential detail from traveling further. It is untested, and nothing has been published on how often multi-hop leads reach a verified application.

  • The company already talks to SourceX. Section 3 makes it a duplicate; the company can carry on directly, and an existing relationship is handled as described in introductions that overlap an existing opportunity.
  • The only evidence of fit is confidential. If nothing survives once stripped, there is no lead.
  • Nobody knows the CEO. Park it and record why.
  • The source said no. A "not this year" at hop 1 binds every hop after it.
  • Demand. SourceX's requirements move with its current data needs, so even a clean chain can end in "not a fit today".

Methods note. The log follows SourceX's referral terms published 22 October 2026, the unsigned partner agreement sample dated 19 October 2026 and SourceX's screening page, with W3C's PROV data model as the idea behind tracing each hop; all were read on 2026-10-27. It does not assess record quality, demand or payout. To test it, record per lead the number of hops, the facts stripped, the days until the CEO answered and whether duplicate review followed. To stop duplicates before they form, see preventing duplicate claims before they reach SourceX.

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 the log is complete and the CEO has named the person to hear from, that partner signs up through partner registration, runs the company through who qualifies one more time and goes over sections 2, 3 and 7 of the program terms before submitting. Once the CEO agrees, the separate consents behind that yes can be kept in a permission log for investor-led introductions. Related playbooks are in the guides library.

Tracing a secondhand lead is referral work; deciding whether SourceX is worth backing as a company is a separate exercise, and investor materials can be requested from 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

Does the investor who first heard about the company earn the credit?

Not for hearing first. SourceX credits the first valid introduction of a company that is new to it, judged from dated records, once that company submits a verified application inside the 90-day window. A remark at a dinner three hops up is not, by itself, a written introduction.

Should I forward a referral link that reached me from someone upstream?

No. A forwarded link carries another person's record, and the terms say an earlier click does not decide credit on its own. Agree who will introduce, and let that person submit a written introduction once the CEO wants the conversation.

What should I do with chain details that came from a board pack or lender deck?

Mark them strip in the log and keep them out of everything you send onward. If the fact matters to fit, ask the CEO for it directly, at the level of descriptions.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  4. w3.org/TR/prov-dm
  5. 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