"Paid" here means that a fund entity or a fund person expects a SourceX reward if a license follows. The reader is the fund COO or platform leader who may be asked, months later, by an LP, an auditor or the CEO, why a reward was proper. The unpaid route is lighter, and the end of the page says which items it keeps.
What the friendly email proves, and what it leaves out
Section 1.2 of the sample agreement says an introduction must be recorded in writing, through a portal submission, a tracked verified application, an email or a mutually acknowledged log, and that "Oral introductions must be confirmed in writing before protection under this Agreement attaches." So the email is not worthless. It can be the dated record.
What it cannot show is everything that had to be true before it was sent and everything that has to happen after it. Section 1 of the terms requires partners to sign the Channel Partner Agreement "before submitting introductions." Section 2 credits the first valid introduction of a new company only "when that company submits a verified application," decides attribution "from dated records", and adds that "an earlier link click alone does not decide credit." Section 3 treats as a duplicate any company with an earlier relationship, which "includes any earlier lead, account or email correspondence between SourceX and the company, however it began." SourceX's screening page puts "Introductions made without the decision maker's knowledge" on its usually-not-a-fit list.
A typical warm note shows the gap. Illustrative wording: "Thought of you straight away. These people pay real money for data like yours and you'd be perfect. Copying Sam." It implies the company fits, which only SourceX's review can say; it hints at money without saying who else might be paid; it was sent before anyone checked whether the sender's firm had signed; and it may lean on something the sender saw in a board pack. None of that is visible in the email itself, which is the problem.
The sender, the named partner and whoever keeps the money
The person who presses send is often not the partner. The sample names the Partner as "[an individual, or entity type and jurisdiction]", and section 3.3 says each introduction record must identify "the company, domain, Partner, opportunity, introduction method and timestamps." If the management company is the signed party and a deal partner writes the message, the record must name the management company, and the message should say whom the writer acts for.
Who finally keeps any reward is a separate question that SourceX's documents never answer; the fund's own documents and counsel do. Choosing the named party is mapped in who receives a reward when a fund makes the introduction, and whether the fund should take part at all in should a venture fund accept data referral rewards. This page assumes both are settled and asks what one introduction needs.
The approval and evidence checklist
Ten items for each company. The last column is the event each item must precede; an item dated after that event does not repair it.
| # | Item | Why the friendly email alone falls short | Basis | Who signs off | Dated before |
|---|---|---|---|---|---|
| 1 | The fund's policy covers paid introductions by this named party | An email cannot show that the fund approved anything | The fund's own policy, as counsel reads it | COO or chief compliance officer | Any contact with the CEO |
| 2 | The named party has signed the Channel Partner Agreement | Senders rarely check | Terms section 1 | The signatory | The introduction |
| 3 | Company-level clearance: board seat, information rights and conflicts checked for this company | The email shows what was said, not what the sender knew | Screening page; fund policy | Chief compliance officer | The ask to the CEO |
| 4 | Disclosure wording approved: who may be paid, on what basis, and that the company's payout is unchanged | Warm notes usually skip it | Terms section 4; counsel | Counsel or compliance | The ask to the CEO |
| 5 | The CEO's own yes to an introduction, in writing | A forwarded "sounds interesting" from a colleague is not the CEO's decision | Screening page | The partner keeps it | The introduction |
| 6 | The CEO's answer to one question: has the company ever applied to, held an account with or corresponded with SourceX? | The sender seldom knows | Terms section 3 | The partner records the answer; SourceX decides | The introduction |
| 7 | Content check: no board-pack facts, no figures from files, no claim of fit, endorsement or favored access, no talk of price | Enthusiasm drifts into all of these | Sample agreement 4.2 and 7.1; screening page | A second reader at the fund | Sending |
| 8 | The record carries every field section 3.3 lists | Casual notes leave out the domain, the opportunity and the method | Sample agreement 3.3 | The partner | Sending, or the portal submission |
| 9 | The company's own verified application | Only the company can create it | Schedule A, paragraph 2: within 90 days of the recorded introduction | The CEO applies; SourceX verifies | Day 90 |
| 10 | SourceX's decision filed: credited, duplicate or declined, with the terms version | The email records nothing after it was sent | Terms sections 2 and 7 | COO | Closing the file |
Item 6 deserves a word. A partner cannot see SourceX's records, and SourceX checks its own before inviting an introduced company. Asking the CEO does not settle credit; it stops the fund from spending a CEO's goodwill on an introduction section 3 would treat as a duplicate. Item 7 is the one most often skipped: SourceX's screening page warns that a line such as "our companies qualify" implies an acceptance nobody has given, and section 7.1 of the sample says the partner "may not commit SourceX to prices, licenses, payouts or other obligations."
Method note. Items 2, 5, 6, 8, 9 and 10 restate SourceX's terms (version 2026-10-22.2, since replaced by version 2026-11-04), its unsigned sample agreement (version 2026-10-19) and its screening page, read on 2026-10-28. Items 1, 3, 4 and 7 are this page's design for a fund's own controls; they describe no fund's documents and no legal requirement. How often funds that use such a list are credited has not been measured, and no such figures are published.
Duties, outside roles and potential conflicts the checklist screens
Disclosure. The FTC's plain-language guide to its Endorsement Guides is mostly about when and how to disclose a material connection: in our paraphrase, a connection calls for disclosure when a significant minority of the audience would not expect it and it would affect how they weigh the endorsement. Whether that guidance reaches a private introduction from a fund partner to a CEO is for the fund's counsel. Item 4 stays either way, and it rests on a published fact: section 4 of the terms says the reward "is paid separately by SourceX and is never deducted from the supplier's agreed compensation", so the company's amount is the same whether or not anyone is paid. Model wording for that note is in how to disclose a referral incentive to a portfolio founder.
Board seats. What a partner learns from board materials can prompt one question to that company's own CEO. It never goes into the email, never reaches SourceX and never reaches another company. Items 3 and 7 are where that rule gets checked.
Outside roles. An operating partner serving as interim officer at the company sits on the company's side of the table for that period; the CEO still decides, and a paid route for that person needs counsel's view under item 1 before anything is written. An LP who owns the company and prefers not to be paid has its own routes in when an LP wants to participate without compensation.
Investment talk. An introduction email is no place to mention investing in SourceX. Keep that conversation in its own channel, as separating a company referral from an investment introduction sets out.
One introduction, sent two ways (Illustrative)
Illustrative. A generic fund and company, invented dates; no outcome is implied beyond what the terms say.
The company is a 260-person freight audit firm in the fund's portfolio. A deal partner knows its CEO well.
| Step | The friendly version | The checked version |
|---|---|---|
| Before writing | Nothing; the management company has not signed | Items 1 to 4 approved and dated; the management company signed in March |
| The ask | A text to the CEO, then an email copying a SourceX address from the partner's personal inbox | A call, then the CEO's written yes; the CEO says the company has never contacted SourceX |
| The message | "You'd be perfect", plus a remark about the company's ticket volumes from the last board pack | A plain note on whom the partner acts for, who may be paid and that the company's payout does not change; no board facts |
| The record | No domain, no opportunity, no stated method | Every field section 3.3 lists, timestamped |
| What follows | The CEO's operations director had emailed SourceX a year earlier; the company applies four months later | The company applies in week three |
| Under the terms | Sent before any signature, which section 1 rules out; a duplicate under section 3; applied after the 90 days in Schedule A. The last two each defeat credit on the terms' own wording | Reviewed normally; SourceX decides credit from dated records |
The friendly version was not dishonest. It was simply unprovable, and three separate facts defeated it before anyone at the fund knew they existed.
Record the approved paid or unpaid introduction path
For the paid path, file the ten items per company with their dates, beside the terms version in force. A missing date is a missing item.
The unpaid path keeps three: item 3, so no board knowledge travels; item 5, so the CEO chose to hear about SourceX; and item 7, so nothing implies fit or endorsement. The CEO applies on the company's own initiative and no record fields are needed. One consequence belongs in the file: a company that applies directly is then known to SourceX, so any later paid introduction of it would be reviewed as a duplicate.
How payment follows once a company is credited is explained in how to get paid for referrals, and the 90-day window is set out on a calendar in what an attribution window is.
Limits of a ten-item introduction file
- It slows a warm relationship. Some CEOs want a two-line note. The checklist does not forbid one; it stops the fund from claiming a reward the note cannot support.
- Two items depend on others. Item 6 relies on the CEO's memory and item 9 on the company acting; the fund controls neither.
- It is not legal advice. Items 1 and 4 rest on counsel's reading of the fund's documents and any rules that apply to the people involved.
- A reward is never certain. Section 5 of the terms says "A lead, meeting or signed agreement alone does not earn a payable reward," and payment follows only a licensed, accepted and paid dataset.
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 warm note leaves anyone's outbox, have the named party register and sign, check the company against who qualifies, and keep the program terms version beside the ten items. More fund-side decisions sit in the guides library.
Introducing a portfolio company is referral work; anyone at the fund who wants to look at SourceX as a potential investment should do so through a separate request on 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.