The pull toward contracts is stronger in a corporate network because the corporate already holds some: procurement's supply agreement, the venture unit's investment documents, perhaps a diligence copy of the company's customer terms. Holding a document is not permission to use it here, and SourceX's process needs none of them.
Three contract drawers in one strategic relationship
A corporate usually knows a network company through several doors, and each door's paper belongs to whoever signed it.
| Role | Contracts it holds | What they can tell the introduction | Where they stay |
|---|---|---|---|
| Corporate (venture unit, board seat) | Investment agreement, information rights, board materials | That the company exists and who its CEO is | With the venture team and its counsel |
| Vendor relationship (business unit or procurement) | Supply or services agreement, order forms, the corporate's own data terms | Whether a tender, renewal or dispute makes the timing wrong | With procurement and the business unit |
| Operating company | Its customer agreements, data processing terms, AI addenda, supplier and employee contracts | Whether its records can be licensed, which only its counsel and SourceX's review can settle | Inside the company, always |
The third row is the only one that bears on rights, and it is the one the corporate has no business opening. SourceX's screening page counts a company as holding the rights when it owns the material outright, or can license it without breaking a confidentiality promise to clients, an employee's privacy or a contract with someone else. It also lists material that belongs to the company's clients among the cases that are usually not a fit. Those are questions about the company's paper, answered by the company, which is why a strategic partner can introduce without owning the data and never needs to read it.
A common complication: the corporate may itself be one of the company's customers, so some records in the company's systems concern the corporate, under its own contract with that company. If the company later asks whether the corporate's account can be included, that is a customer question for the corporate's legal team, raised through the commercial relationship. It is not part of the introduction, and the venture team should not answer it in passing.
The contract-free qualification summary
Nine lines, each from a statement someone is entitled to make. Nothing is sent until the company's CEO has read it.
| Line | What it records | Who supplies it | Never in this line |
|---|---|---|---|
| 1. Company and CEO | Legal name, the CEO's name, the date checked | Public records, confirmed by the CEO | Org charts taken from board packs |
| 2. Full-time headcount at peak | A number and the year it peaked, contractors left out | The CEO or the finance lead | Payroll exports |
| 3. Record families | Kinds of records, such as service tickets or project files | The company | Samples or screenshots |
| 4. Years and systems | The first year of records and the system names | The company | Logins or exports |
| 5. Whose records | The company's own operations, set apart from content customers supplied | The company | Customer names |
| 6. Reuse review status | Whether the company's counsel has looked at customer reuse limits: yes, not yet or unknown | The company | Clause text, excerpts or summaries of any contract |
| 7. The corporate's own tie | Investor, supplier, customer or none, and any open commercial event | The platform manager, after asking procurement | The supply agreement or its terms |
| 8. Earlier contact with SourceX | Yes, no or unsure | The CEO | Guesses from anyone else |
| 9. The CEO's words | A dated sentence saying they want the conversation | The CEO | A colleague's yes |
Line 6 is the one people overfill. A status is enough: "counsel reviewed customer terms for reuse in March" says what SourceX needs to know at this stage. A paraphrase of a clause is still the contract, just less accurate. SourceX's guide on no-AI-training clauses explains why: such limits mostly arrive through negotiated paper such as order forms, data processing agreements and AI addenda, while public terms may say nothing about AI. In its process the supplier identifies restricted accounts, their records are excluded before preparation starts, and the supplier's counsel interprets the clauses while SourceX records the result.
A test for every line: could the company read the line aloud to its largest customer without breaking a promise? If not, the line holds too much.
Line 8 saves a wasted ask. Section 3 of the terms says "A relationship includes any earlier lead, account or email correspondence between SourceX and the company, however it began." A company SourceX already knew is reviewed as a duplicate and credited to no later partner.
Method note. The nine lines come from SourceX's screening page, its program terms and its published description of how customer AI restrictions are handled, all read on 2026-10-27. The summary does not measure demand for the records, their quality or any payout, and it has not been tested against completed introductions; no such figures are published. It records who said what, on which date, and nothing more.
Why nothing more needs to travel
SourceX's how-it-works page says no records are shared at the first assessment, and the company itself later confirms its rights to license and that the data has never been licensed for AI training. The sample Channel Partner Agreement draws the same line for partners. Section 4.2 gives the partner "no authority to share a supplier's inventory, records, raw data or personal information, or to access extraction systems." The terms also let SourceX speak with a referred company directly without disturbing valid attribution, so nobody needs to relay documents.
Other programs guard far less than contracts. Microsoft's co-sell guidance, in our paraphrase, tells partners to get the customer's approval before passing on its contact details, because Microsoft may contact that person directly. If a name and an email call for consent, a customer agreement has no place in a referral.
Sign-offs that keep the papers where they are
The full approval sequence for a corporate venture introduction is set out in the two-path approval map. For the contract question alone, four sign-offs matter.
| Sign-off | Who gives it | What it covers |
|---|---|---|
| No open tender, renewal or dispute | Procurement or the business unit | Timing only; it grants no permission to ask |
| Line 7 holds nothing confidential | The venture team's counsel | That the tie is named without its terms |
| The summary is accurate and may be sent | The company's CEO | Every line, before anyone outside the company sees it |
| Line 6 is answered | The company's counsel, when the company chooses | A status, never a copy |
Procurement's sign-off is a reason for care, not a route; the procurement-versus-permission checklist explains why buyers stay out of the ask.
Four requests to turn down, and what the summary carries instead
| Request you may hear | Why it fails | What the summary says instead |
|---|---|---|
| "Send their standard customer terms so we can check" | Public terms rarely hold the limits that matter, and checking is counsel's job | Line 6: the review status |
| "Procurement has their master agreement; we can confirm what it says about data" | That agreement is the corporate's commercial paper, not a source for an introduction | Line 7: the kind of tie, and any open event |
| "Forward their data processing agreement so SourceX can pre-screen" | SourceX reviews rights with the company, not through the corporate | Line 9: the CEO wants the conversation |
| "Attach a redacted customer list to show the client base" | A redacted list is still the company's confidential information | Line 5: the split between own records and customer content |
Two network companies on one summary (Illustrative)
Illustrative. Both companies are invented, and each cell shows how the summary reads, not what SourceX would decide.
| Line | A: 340-person logistics software company in the venture portfolio | B: 150-person industrial services firm that supplies a business unit |
|---|---|---|
| 1. Company and CEO | Confirmed by the founder-CEO, dated | Confirmed by its CEO, dated |
| 2. Peak full-time headcount | 340 in 2025 | 150 in 2023 |
| 3. Record families | Support tickets, implementation project files | Work orders, inspection reports |
| 4. Years and systems | Since 2016, help desk and project tool | Since 2009, field-service system |
| 5. Whose records | Own support and project work; customer shipment data excluded | Own field work |
| 6. Reuse review status | Counsel reviewed customer terms last quarter | Not yet |
| 7. Corporate's tie | Investor and a customer of one business unit | Supplier; renewal open until spring |
| 8. Earlier contact with SourceX | None, per the CEO | Not asked yet |
| 9. CEO's words | "Happy to talk to SourceX," dated | Not asked during the renewal |
| Next move | One introduction, with the CEO copied | Wait until the renewal is signed |
Company A shows the customer complication: the summary names the business unit's purchase and nothing about the contract behind it. Company B shows the vendor role: an open renewal means wait, never ask sooner.
A first round of opt-in introductions, and the trust signals to log
Choose three network companies with no open commercial event, ask each CEO through whoever holds the relationship, and fill the summary only with CEOs who say yes. Log:
- how many of the nine lines the CEO answered without hesitation, and which line caused pause;
- every request, from anyone, to see or send a contract, and who made it;
- any CEO who asked whether the corporate would learn what the company licensed;
- the days from the first ask to the CEO's approved summary.
Write the stop rule before the first ask: if a contract ever lands in a venture inbox, send it back unread to the sender, tell the CEO and pause the round until the cause is fixed. SourceX has not published conversion or response rates for corporate networks, so these counts belong to your team alone.
Where a contract-free summary can still go wrong
- Rights are decided later. A "yes" on line 6 means counsel looked, not that the records clear; review may narrow or end the scope.
- The company can be mistaken. Some records a CEO calls the company's own may have come from customers. The summary records the claim; review tests it.
- Earlier AI licenses. Data already licensed for AI training is not eligible, and only the company knows its history.
- Commercial pressure. A CEO whose largest customer is the corporate may agree to please it. Any sign of that is a reason to stop.
- Demand moves. Fit with SourceX's current needs is assessed in review; a strong summary is not a forecast.
Deal teams can start at the corporate development page; customer contract data use restrictions shows what counsel reads, and the guides library holds the rest.
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 a CEO has read and approved all nine lines, register as a partner, test the summary against who qualifies and read the program terms before anything is recorded with SourceX.
Building a contract-free summary is referral work; judging SourceX as a company to invest in is a separate decision, and readers weighing it can ask for 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.