This page is for the person between a fund's general counsel and its platform or deal team who is asked to approve a referral form. It treats "minimum" as a design rule: every field must serve a named decision, come from the person entitled to give it and reach only the people that decision needs.
A referral serves three decisions, and only one is SourceX's
| Decision | Who makes it | What they need | What they do not need |
|---|---|---|---|
| Is it worth asking the CEO? | The fund's relationship owner | Public facts and the owner's own judgment | Anything from board packs or information rights |
| Does the company want a conversation? | The CEO | How SourceX licensing works, what the partner may earn and that it leaves the company's payout untouched | A profile of the company written by the fund |
| Can SourceX identify, contact and date the introduction? | SourceX | The six outbound fields below | Records, volumes, system lists or financials |
Most intake forms over-serve the third decision and under-serve the second. What a CEO needs in order to decide is information about SourceX, and it is already published: the program terms, how referrals work and the line in section 4 of the terms that the reward "is paid separately by SourceX and is never deducted from the supplier's agreed compensation."
The company describes itself, directly to SourceX
SourceX's company application calls itself "Three screens, about 7 minutes," and promises no files, no passwords or API tokens and nothing licensed or transferred at that stage. Its first screen asks for the company name, website, an industry group, the country, what the company does, the applicant's name, role, work email and phone, and the legal name, entity type and notice address for the agreement. Later steps cover a data overview, systems and privacy.
All of that is the company's to say, and it says it to SourceX itself. A fund that gathers the same facts in order to forward them adds a copy, not value. SourceX's main process page describes the same step as "A few questions, no files, and an indicative licensing estimate," and its referral process page tells partners they do not need to export, upload or describe confidential records. A CEO who wants a feel for fit before applying can use the company fit checker, which asks for no contact details.
The minimum-fields intake specification
Nine fields. The first six form the outbound set: they reach SourceX only after the CEO has agreed to be introduced and has seen them. The last three never leave the fund.
| Field | Decision it serves | Supplied by | Leaves the fund | Never in this field |
|---|---|---|---|---|
| 1. Company name | Identifies the company, including for duplicate review | The CEO or the public registry | Yes | Deal code names or fund labels |
| 2. Website domain | Ties the record to one company | Public | Yes | Data room links or internal system addresses |
| 3. Partner of record | Shows who signed the Channel Partner Agreement and is submitting | The fund | Yes | Names of other people at the fund |
| 4. Opportunity, in one line | Says what the conversation is about | The CEO's own words | Yes | Record lists, volumes, values or system names |
| 5. CEO name and work contact | Lets SourceX reach the person who decides | The CEO | Yes | Personal numbers or assistants' notes |
| 6. Introduction method and timestamp | Dates the introduction for credit | The fund | Yes | Earlier drafts or internal discussion |
| 7. CEO's agreement | Shows the CEO agreed, to what and when | The CEO, by email | No | The CEO's reasons or private context |
| 8. Relationship owner and approver | Shows who asked and who in the fund approved sending | The fund | No | Commentary on the company |
| 9. Screen and conflict check | Records pass, unknown or escalated, with a date | The fund | No | The facts behind an escalation, which stay with counsel |
Fields 1, 2, 3, 4 and 6 mirror the sample agreement's list of what an introduction record must identify; field 5 is how SourceX reaches the decision-maker. The sample names the partner as "an individual, or entity type and jurisdiction," so field 3 holds whichever signed, the fund itself or a person. Partners sign that agreement before submitting introductions (terms, section 1).
Fit belongs in a conversation, not a field. Ask the CEO whether full-time headcount reached 50 at its peak, whether the company's own records go back several years and whether it holds the rights to them. If an answer fails, there is no introduction and nothing to keep beyond field 9's "fail" and its date. If all pass, the company states the facts itself when it applies.
Material that never enters any field:
- board packs, management reports and anything received through information rights;
- investment memos, valuations, cap tables and fund performance data;
- names of customers, suppliers or employees;
- headcount evidence such as payroll extracts or org charts;
- screenshots, schemas, samples, exports and data room access;
- reward estimates or forecasts of what the company might receive.
The first item is not a matter of taste. In NVCA's model management rights letter, a common starting form for venture investors, the investor agrees that "any confidential information provided to or learned by it in connection with its rights under this letter shall be subject to the confidentiality provisions" of the investors' rights agreement. What a particular fund's documents say is for fund counsel to read. The safer design is a form with no field such information could land in.
Method note. The specification starts from three published sources checked on 2026-10-28: section 3.3 of the unsigned sample Channel Partner Agreement (version 2026-10-19) linked from terms section 9, SourceX's company application and its program terms (version 2026-10-22.2, since replaced by version 2026-11-04). Each candidate field was kept only if a named decision fails without it. Nothing here measures outcomes: SourceX has not published whether leaner or fuller referrals fare differently, and a partner's signed agreement, not the sample, governs.
Who may receive each field
The sample agreement counts "introduced contact identities, introduction records" among confidential information, so the record itself deserves a recipient list drawn up before the first referral.
| Recipient | Receives | Never receives |
|---|---|---|
| The CEO | Fields 1 to 6 before anything is sent; field 7 is their own email | Notes about other companies |
| SourceX | Fields 1 to 6, after the CEO agrees | Fields 7 to 9, or anything on the excluded list |
| The relationship owner and approver | All nine fields | Board material pasted into the record |
| Fund counsel | Field 9 escalations and their facts, kept in counsel's files | More than the question needs |
| Other partners, LPs and portfolio companies | Nothing | Any field |
| The public | Nothing | Any field, absent written authorization |
The sample also draws SourceX's side of the line: it "gives Partner no authority to share a supplier's inventory, records, raw data or personal information, or to access extraction systems." Section 7 of the terms adds that partners never see other partners' records, applicant documents or confidential buyer information. Information moves outward from the fund once, and nothing about the company's records comes back.
A 22-field draft cut to nine (Illustrative)
Illustrative. A generic fund and an invented form.
A fund's platform team drafts a portfolio referral form with 22 fields. The counsel liaison asks one question of each: which decision fails without it? Thirteen rows go. Seven show the reasoning:
| Draft field | Decision it claimed to serve | Why it went |
|---|---|---|
| Revenue band | Prioritizing | None of SourceX's published screening checks uses revenue |
| Headcount from the last board pack | Size check | Information-rights material; the company states peak headcount itself |
| Systems in use | Fit | The application asks the company directly |
| Years of records | History check | Asked in conversation; the company states it when it applies |
| Data room link | Context for SourceX | A partner holds no authority to share company records |
| Expected payout | Internal planning | No one can support it; a payout is fixed only in a signed Dataset Deal Confirmation |
| Other investors in the company | Coordination | Serves no decision about this introduction |
The six outbound and three internal fields survive. The form fits on one screen, and if a CEO later asks what the fund holds about the introduction, the answer takes a minute.
Escalation, withdrawal and publication each need their own yes
A CEO's agreement to be introduced covers an introduction. It does not stretch to three things that often follow:
- Escalation into records. Scope is the company's decision with SourceX. The trust page says "The supplier decides which systems, records and date ranges are in scope." When a question needs private context, send it to the company's own conversation, as the public-to-private escalation workflow sets out, and keep privileged documents out entirely, as the privileged-material guide explains.
- Withdrawal. If the CEO withdraws before submission, nothing is sent. Afterward, tell SourceX only that the CEO asked to stop, and note the date in field 9.
- Publication. The sample agreement bars either party from publicly naming the other as a partner or disclosing non-public deal details without written authorization, and SourceX's process page says "Neither side publicizes the deal." A newsletter mention or case study needs the company's separate written yes.
When a company's privacy lead joins the conversation, see the referral conversation with a privacy officer; when a founder wants to stay unnamed at first, see when a founder wants an anonymous first conversation.
Limits of a nine-field intake
- The sample is not the signed text. Section 8 of the terms says the signed Channel Partner Agreement governs confidentiality; where it differs from the sample, it controls.
- Fund documents may be stricter. A fund's own agreements may restrict what it says about a portfolio company to anyone outside it. Fund counsel reads them; a specification cannot.
- Groups need precision. A parent and its subsidiaries share one reward cap, and credit questions among related companies are decided by SourceX in duplicate review. Name the operating entity exactly in field 1.
- Lean can read as cold. A CEO may want the fund to say more on their behalf. They can say it themselves in the application; the fund still forwards nothing.
- No outcome data. Whether leaner intake changes results has not been measured, and the brief-detail evaluation is a design with no results yet.
A measurable check. Count the fields on your current referral form and ask of each which decision fails without it. If more than nine survive, write beside each extra field the decision it serves and who supplies it; any field supplied by "the fund, from board materials" goes first. More guides are in the guides hub.
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.
Once counsel has signed off on the nine fields and a CEO's agreement sits in field 7, the fund can open its partner account, hold the company up to SourceX's screening criteria and confirm the terms say what this page relies on before the first record leaves.
Designing a fund's referral intake is a separate task from evaluating SourceX as a business; readers doing the latter 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.