The two get confused because they start in the same place: a venture team that knows a company and wants to be useful to it.
Three roles a pilot and an introduction hand out differently
Every corporate pilot has a corporate, a vendor and an operating company, and so does every introduction. What changes is the job each one does.
The corporate. In a pilot it is the customer and the test site. STARTUP AUTOBAHN's program page describes its Pilot Lane as a program for later-stage startups whose main goal is to run pilot projects with its corporate partners, which it calls venture clients, through a 100-day pilot phase. "Venture client" names the role exactly: the corporate tries the product and may buy it. In a SourceX introduction the corporate is not a party at all. At most a person or entity registered as a SourceX partner passes on an introduction, and the role ends there.
The vendor. In a pilot it is the startup whose product is tested, hoping for a contract. In an introduction nobody sells anything to the corporate. SourceX licenses records directly from the operating company and pays that company, usually a one-time fee for the dataset. The corporate is not SourceX's customer, and nothing SourceX does is a product the corporate evaluates.
The operating company. In a pilot it is often the corporate's own business unit, using the tool. In an introduction it is the company whose records are in question, often a portfolio company or a supplier with its own CEO. That CEO decides whether to talk, and the company signs its own Master Supplier Licensing Agreement and Dataset Deal Confirmation with SourceX.
A strategic stake, a supply contract or a hosting arrangement does not move ownership of those records to the corporate. SourceX's screening page says opening a licensing discussion and signing for the company fall to the CEO, and that a board seat lets an investor speak in the boardroom without letting it start that discussion. Founder permission and corporate authority covers the cases where those two blur.
The pilot-versus-introduction scope table
Read each row across. If any cell in the right column starts to look like the left one, the introduction has been turned into a pilot.
| Scope question | Corporate pilot | SourceX introduction |
|---|---|---|
| Corporate: its role | Customer and test site, a venture client of the vendor | Not a party; at most the introducer, through a registered partner |
| Corporate: money | Commits budget or a purchase path for the test | Pays nothing; a registered partner may later receive a reward from SourceX, where policy allows |
| Corporate: reviews it runs | Vendor onboarding, security review and data access for the test | Its own rules on staff making introductions and taking rewards, and on what it learned in confidence |
| Vendor: who it is | The startup whose product the corporate tests | No vendor to the corporate; SourceX licenses the company's records and pays the company |
| Vendor: what it receives | Use of the corporate's environment and feedback, as the pilot contract sets | From the corporate, an introduction only; the partner agreement grants no data or trademark license |
| Operating company: role | Often a business unit that uses the tool | The licensor; its CEO decides and signs, and the company applies itself |
| Operating company: records | The corporate's data, used inside the test | The company's own records, none shared at application and later only under its own signed agreements |
| Clock | A fixed test period, 100 days in the STARTUP AUTOBAHN model | 90 days from introduction to a verified application for credit, then SourceX's own process |
| Success test | Buy, extend or stop | The CEO's informed yes or no, which the corporate does not grade |
| Publicity | Whatever the pilot contract allows | Neither the company nor SourceX publicizes a deal, and neither SourceX nor a partner names the other publicly as a partner without written authorization |
| Who can stop it | The corporate's sponsor | The company's CEO, at any point before signing; SourceX, in its review |
Method note. The pilot column uses one published pilot model (STARTUP AUTOBAHN's program page) as its reference; other corporates run pilots differently, so check your own pilot agreement. The introduction column uses SourceX's program terms, its process page and the unsigned sample of the SourceX Channel Partner Agreement, all checked 2026-10-27. The table compares roles and duties, not commercial value: no row estimates what either arrangement is worth.
Five ways an introduction gets dressed up as a pilot
| What happens inside the corporate | What a company's CEO hears | The fix |
|---|---|---|
| An internal memo calls it "the SourceX pilot" | The corporate is testing SourceX and will report back | Call it an introduction program; the corporate tests nothing |
| It is routed through vendor onboarding | The corporate is buying data, or has approved SourceX as a supplier | Keep procurement out; SourceX supplies nothing to the corporate here |
| Business units are asked to nominate datasets | Records are being gathered for someone | Nobody nominates records; each company's CEO decides what, if anything, to discuss |
| Someone promises pilot pricing for portfolio companies | The corporate negotiated special terms | The published terms hold no such thing, and a partner may not commit SourceX to prices, licenses or payouts |
| Success is set as licenses closed | The corporate will press CEOs to sign | Count CEO answers and trust signals, never deals |
The fourth row matters most. A company's payout is fixed in its own Dataset Deal Confirmation with SourceX, SourceX does not publish how it prices offers, and any reward a partner receives is a separate SourceX obligation that takes nothing out of the compensation the company signs for. There is nothing a venture team can negotiate on a company's behalf, and offering to do so tells the CEO something untrue about who is at the table.
Who approves what, on each side
Approvals split the same way as the roles. On the corporate's side, the venture lead approves the introduction program; compliance decides whether an employee or the corporate entity may register and accept a reward, since the sample partner agreement allows either an individual or an entity as partner; legal checks that nothing passed on was learned in confidence; communications approves any external mention. On the company's side, the CEO alone decides whether to talk to SourceX. If the company has been acquired, that is the acquirer's CEO, and before closing it is still the company's own.
SourceX holds a third set of decisions: whether the company fits a current program, whether it has the rights to license, and who gets credit. A company that already applied to or corresponded with SourceX is a duplicate and credits nobody. When two introducers claim one company, SourceX resolves it in duplicate review; only one can be credited. The two-path approval map sets out the corporate's and the company's sign-offs in detail, and introducing several companies from one group covers the once-per-company floor.
A first round run as introductions, not as a pilot (Illustrative)
Illustrative. The venture arm of a 9,000-person industrial group knows two companies well: a 180-person field-service software firm in its portfolio, with records back to 2013, and a 400-person contract logistics firm that supplies one of its plants.
The first draft of the outreach reads: "We are piloting SourceX with select portfolio companies and partners." Every word but the last two signals a pilot: a test, a selection and the corporate in charge. The rewrite reads: "SourceX licenses business records from companies for AI training. I am registered in its referral program and could receive a reward from SourceX if your company licenses. Whether you look at it is entirely your decision, and nothing you share with SourceX comes to us." The logistics firm is left out of this round, because its account is up for renewal with the plant and the ask would sound like leverage.
Run three to five such asks, each to a CEO the team already knows and whose fit facts (50 or more full-time employees at peak, contractors excluded; years of its own records; rights to license) are already known. Record three things per company: the CEO's answer, the time spent, and the reply to one follow-up question, "Did you read this as something we were testing or recommending?" Any yes to that question means rewriting the message before the next ask. SourceX has not published results for corporate introduction rounds, so this is a method to run, not a finding. For choosing the first companies, see the ten-company first round.
Where the line between the two can blur
- The corporate buys data itself. If a business unit wants to license data for its own AI work, that is a purchase with its own procurement path, unrelated to any SourceX introduction. Keep the two in separate threads.
- Subsidiaries. An operating company the corporate owns is decided by the group's CEO, and the whole group counts as one referred company: the USD 50,000 floor applies once, to its first qualifying transaction, and further qualifying transactions within the Repeat Window pay 15%.
- Reward policy. If corporate policy bars rewards, the company's CEO can still apply to SourceX directly. Whether someone can introduce a company and turn the reward down is not settled in the published terms; raise it with SourceX before relying on it.
- Earlier contact. A company that already spoke to SourceX cannot be credited to anyone, however well the introduction is framed.
- Template drift. Teams reuse pilot templates out of habit, and the vocabulary returns. Reread every message against the scope table.
- Corporate development teams. Acquired and declined targets raise their own questions; the corporate development page starts there.
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 scope table shows a clean introduction, with no procurement, no test and no corporate say, register as a partner, set the company's known facts beside who qualifies and keep the program terms at hand while you draft the one message its CEO will get.
A venture team deciding whether to introduce companies is doing something different from an investor deciding whether to back SourceX; readers on that second question 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.