Funding status does not decide the lane, and neither does how well the platform team knows someone. A celebrated AI startup in the portfolio is usually a buyer contact; an unglamorous 25-year-old services firm owned by an LP may be the supplier. What decides it is the company's role in the deal and who can authorize it.
Why the two lanes never merge
The money runs one way. The default reward is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout: the compensation SourceX actually pays the company you referred. The terms exclude SourceX's fees and the Acquisition Partner's full transaction price from that base. So an introduction to a buyer creates nothing to calculate a reward on; the published terms describe no reward for it.
The decision-makers differ. On the supplier side the operating company's CEO decides whether to discuss licensing and signs for it. On the buyer side a data or research lead at an AI developer decides what to request. A thread that mixes them asks the wrong person for the wrong decision.
The details are confidential in opposite directions. Under the program terms, partners never receive access to confidential buyer information. A platform lead therefore cannot tell a supplier which developer might license its records, and must not tell a buyer which companies are in review.
The buyer has its own door. SourceX's data request page is addressed to frontier model developers, AI data labs and training or evaluation partners. It asks for scope, volume, format, timing and licensing needs, and says datasets are sourced on request rather than held in stock. A buyer contact needs the link, not an introduction. The explainer on AI data buyers describes who sits on that side.
Which side is each company on, and who owns the relationship?
One venture network often holds both sides. Andreessen Horowitz, for example, describes investing across AI, enterprise, fintech, infrastructure and other practices; an AI practice brings model builders, the others bring operating companies with long records. Map each company before anyone writes an email.
| Contact | Usual side | Who decides for the company | Who in the fund usually holds the relationship | Lane |
|---|---|---|---|---|
| AI model developer or AI-native startup training models | Buyer | Its data or research lead | The deal partner | Buyer |
| Operating company with years of its own records | Supplier | The CEO | Whoever holds the CEO relationship: a partner, an LP, a portfolio founder | Supplier |
| Operating company that also runs an internal AI team | Both | The CEO for its records; the AI lead for its data needs | Often two different people | Split |
| Customer of a portfolio AI startup | Supplier candidate | The customer's CEO | The portfolio founder | Supplier, if the founder agrees |
| Data broker, scraper or labeling vendor | Neither, usually | Not relevant | The deal partner | No lane |
The buyer-versus-supplier route map
Run two tests on every contact, then follow the lane rules.
- Buyer test. Would this company acquire or use data to train or evaluate models?
- Supplier test. Does it hold records it created about its own operations, with 50+ full-time employees at peak?
One flag sends the row to that lane. Two flags split it into two rows with two owners. No flag ends the row.
| Lane | Who acts | What the platform lead does | What never happens | Reward under the published terms |
|---|---|---|---|---|
| Buyer | The AI developer, through its own data request | Shares the public request page and steps out | No supplier names, review status or claims about available supply | None described |
| Supplier | The relationship holder, then the company's CEO | Registers, confirms the CEO wants the conversation, submits once | No records, samples or logins; no claim that a buyer is waiting | Default the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, once payment conditions are met |
| Split | Two different people at the same company | Opens one row per lane with separate owners and notes | Knowledge from one lane used to steer the other | Only the supplier row, if it qualifies |
| No lane | Nobody | Writes down why | Forcing a fit to keep a relationship warm | None |
Four habits keep the lanes apart in practice: a lane tag on every CRM row, separate email threads, separate notes fields, and no forwarding between them. A portfolio company that is a buyer should never learn from the fund which companies the fund has introduced. When a portfolio AI company and another holding could deal with each other, read portfolio conflicts when a sister company builds AI first.
Method note. The route map applies SourceX's program terms (version 2026-10-22.2, since replaced by version 2026-11-04), its published fit criteria and its data request page, all read on 2026-10-26, to the contact types a venture network holds. It sorts contacts by role and authority. It does not measure buyer demand, supplier record quality or any payout, and it is not legal advice on conflicts inside a fund.
Three contacts routed (Illustrative)
Generic companies and invented facts; no outcome is implied.
A. An owner-led supplier. A 260-person commercial HVAC services firm, still run by its founder as CEO, keeps 18 years of service tickets and inspection reports in one field-service system. A partner knows the founder from a shared board. Buyer test no, supplier test yes. The partner asks the founder whether he wants the conversation; if he does, the partner registers and submits. Nobody tells the founder what any developer might pay.
B. A network intermediary with a dual role. A 60-person portfolio startup builds AI tools for insurance adjusters and wants more training data. Its largest pilot customer, a 700-person independent adjusting firm, holds two decades of claim notes, and the startup's founder is the one who knows its CEO. Two rows open. The startup's need goes to its own data request. The adjusting firm is a supplier row that moves only if the founder chooses to raise it and the CEO wants the conversation. The fund never presents the introduction as a way to get that data to the startup: whether any dataset reaches any Acquisition Partner depends on SourceX's process and on terms the adjusting firm itself signs, as whether a data owner can choose the AI buyer explains.
C. A no-fit counterexample. A data-labeling vendor has 35 full-time staff and several hundred contractors, and its datasets are built from files its clients send. It fails the size test, since contractors are excluded, and its material belongs to clients. It is no supplier. If it wants data, it can make its own request; the platform lead introduces nobody.
Reachable suppliers versus companies that fit
Only the supplier lane meets the fit tests, and a reachable CEO is not the same as a company that fits. The tests are 50+ full-time employees at peak with contractors excluded, documented operating history, rights to license and location: 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.
Discovery stays at metadata level: record types, a rough count, the span of years, the systems and who administers them. Three things stay unknown until SourceX reviews the company: whether its records suit a current program, whether customer contracts restrict reuse and what a license would cover. For the reward cap, a corporate group counts once: the parent and every subsidiary share a single cap. Readers used to finder's fees should note the difference set out in finder's fees for supplier introductions: here SourceX licenses directly from the company, and the partner never connects it to a buyer.
Rank supplier conversations without projecting proceeds
Ranking applies to supplier rows only. SourceX has not published conversion rates or typical payouts, so order rows on evidence rather than imagined proceeds:
- Relationship holder agreed. The person whose ask the CEO will hear has said yes.
- Fit facts known. A row with every fit fact confirmed goes ahead of one still missing a fact.
- No buyer dependency. A row that only makes sense if a particular buyer shows up drops to the bottom.
- A dated event. A scheduled system replacement, archive deletion or ownership change, with a date.
Each company earns credit for only one partner, the first to make a valid introduction within the 90-day attribution window, and that credit attaches when the company submits a verified application. Settle in writing who registers when a portfolio founder or LP holds the relationship. Whoever submits signs the SourceX Channel Partner Agreement first; a copy signed back when the document was called the "Channel Partner Non-Circumvention and Non-Disclosure Agreement" stays in force on its signed terms, and the signed agreement governs confidentiality. The overview for venture platform teams covers the supplier side from the fund's seat.
Where routing goes wrong
- Dual roles drift into one thread. The same partner ends up carrying a buyer's data wish and a supplier's introduction. Assign different owners on day one.
- Promised demand. Telling a supplier that a developer wants its records is a claim nobody in the fund can check. SourceX checks relevance to its current data needs in review, and a strong company can still be declined.
- Portfolio pressure. An AI company in the portfolio may lean on the fund for supplier introductions. The conflicts page above is the starting point; the fund's own counsel settles the rest.
- Leakage. Notes copied between threads breach the separation the program depends on. Keep the lane tag and the separate fields.
- Rights. Many attractive records belong to customers. SourceX's screening guidance treats client-owned and scraped material as usually not a fit.
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 contact lands in the supplier lane with a willing relationship holder, register as a partner, test the company on who qualifies and go through the program terms before anyone contacts its CEO.
A reader assessing SourceX as a possible investment, a decision separate from routing contacts, can request 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.