Most requests a corporate venture platform receives come from inside the building: a business unit head with a favorite supplier, a procurement director, a pilot startup, corporate development mid-deal. Each may carry a worthwhile company and a reason the corporate's interest and the company's freedom to refuse pull apart. The matrix is for those internal requests. For stopping a conversation that has already started with a founder, see when a referral partner should end the conversation.
Reach is not ownership: three seats around one company
Every corporate request involves up to three seats, and they hold very different things. Confusing them is the usual reason a request should have been declined and was not.
| Seat | What it may hold over the company | What it may do in a SourceX introduction | What it may never do |
|---|---|---|---|
| The corporate (venture unit, business units, procurement, corporate development) | Purchase orders, a minority stake, a board seat, a commercial partnership | Register, sign the Channel Partner Agreement and make one introduction the CEO asked for | Agree for the company, pass along its records, or present SourceX as its partner without SourceX's written authorization |
| A vendor in between (a pilot startup, a software or IT provider hosting the company's records) | Administrator access, hosted copies, a services contract | Tell its client's CEO the program exists, or be introduced itself on records it created | Treat a client's hosted records as its own, or send a client onward without that CEO knowing |
| The operating company | Its own records and its CEO | Decide, apply, and sign its Master Supplier Licensing Agreement and Dataset Deal Confirmation with SourceX | Have its decision made for it by the corporate or a vendor |
Two program rules sit underneath the table. SourceX's screening page lists material that belongs to a company's clients, and introductions made without the decision maker's knowledge, as usually not a fit. And section 4.2 of the unsigned partner agreement sample reads: "This Agreement gives Partner no authority to share a supplier's inventory, records, raw data or personal information, or to access extraction systems." Section 7.1 adds that a partner cannot commit SourceX to prices, licenses or payouts.
Large corporate referral programs already work on the same principle. Microsoft's Partner Center guidance on Solution Assessment deals tells partners: "Be sure that you have obtained the customer's consent to provide their contact information to Microsoft for the deal." A company's contact details, let alone its records, are not the referrer's to pass along.
Ownership can move under you. While a sale is pending, the target's own CEO decides for it; once closing happens, the acquirer's CEO decides, and the target and its new group count as one referred company: the USD 50,000 floor applies once, on the group's first qualifying transaction, and later qualifying transactions first agreed within the 12-month Repeat Window pay 15%.
The fit-consent-conflict stop matrix
Read the matrix row by row. A failed cell ends the request in its current form, whatever the other eight say.
| Seat | Fit: decline if | Consent: decline if | Conflict: decline if |
|---|---|---|---|
| The corporate | The request is about the corporate's own information sitting in the company's systems, such as its orders or specifications, or about a whole category of suppliers rather than one named company | The person asking cannot bind the corporate, the corporate's internal sign-off on partner registration is missing, or nobody has signed the Channel Partner Agreement | A tender, renewal, audit or dispute with the company is open, the requester controls the company's purchase orders, or the corporate wants something back such as early access to data |
| A vendor in between | The records in question are the vendor's clients', hosted under a services contract, or the vendor itself is the subject and its full-time headcount never reached 50 at its peak | The vendor proposes to introduce a client whose CEO has not asked, or treats its administrator access as permission | The vendor depends on the corporate's pilot budget and the client has not been told the vendor could be rewarded |
| The operating company | Peak full-time headcount never reached 50 (contractors excluded), no documented operating history, records already licensed for AI training, records that belong to its own clients, or location and language outside the criteria | No dated written yes from the CEO; the yes came from a plant manager, a procurement counterpart or a board member; or a sale is pending and the wrong CEO was asked | The company relies on the corporate for much of its revenue and cannot refuse freely, the corporate is negotiating to buy it, or the two are in a dispute |
On location, the published rule is exact: 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.
One check is not yours to run. If the operating company already has an application, account, lead or any email history with SourceX, it is a duplicate under section 3 of the terms and no partner is credited. SourceX checks its own records; your part is to tell the CEO the company is free to apply directly in that case.
Method note. The cells come from the program terms (Version 2026-10-22.2, since replaced by version 2026-11-04), SourceX's screening page and the unsigned Channel Partner Agreement sample (version 2026-10-19), all read on 2026-10-27, plus the owner's settled rules on who authorizes and on treating a group as one referred company. The matrix leaves out demand for the records, their quality and any payout, because only SourceX's review assesses those. It cannot see informal pressure that nobody mentions.
Decline, defer or reroute: what a failed cell means
A red cell does not always mean never. Before replying to the requester, label the failure with one of three verdicts and write down its trigger.
- Decline. A fact time will not fix: client-owned records, data already licensed for AI training, a CEO who said no. Close the request and tell the requester which cell failed.
- Defer, with a date. A condition that ends: a renewal closes, a sale completes, peak headcount passes 50. Record the date or event that reopens the cell and do not raise it with the company before then.
- Reroute. The request is valid in another shape. The company applies directly; the vendor is introduced on records it created; information that belongs to the corporate goes to the corporate's own CEO.
A polite no to a colleague follows the same rules as any declined introduction; the live guide on how to decline an introduction request has wording.
Internal sign-offs and the one only the company gives
Clearing the matrix takes approvals from two sides, and only one of them is the company's.
| Approval | Who gives it | Evidence kept | Cell it clears |
|---|---|---|---|
| Partner registration and the Channel Partner Agreement signature | An officer who can bind the corporate | The signed agreement and the internal approval | Corporate, consent |
| Policy on accepting referral rewards | The corporate's compliance or legal function, under its own policy | A dated note | Corporate, consent |
| No open sourcing event or dispute | Procurement, asked by the venture team | Date checked and the next renewal date | Corporate, conflict |
| One named relationship owner | The venture platform lead | The owner's name against the company | Corporate, conflict |
| The client CEO's yes, where a vendor is in the chain | The client's CEO, in writing to the corporate | The CEO's own message, not the vendor's summary | Vendor, consent |
| The operating company's yes | Its CEO, or the acquirer's CEO after closing | A dated written request for the introduction | Company, consent |
Nobody on the corporate's side collects the company's records, system lists or headcount for SourceX. Fit questions stay at the level of what the CEO says about the company. The procurement-versus-permission checklist covers purchasing leverage line by line, and an IT vendor that hosts data for many clients has its own route.
Four internal requests run through the matrix (Illustrative)
Illustrative. Generic companies and invented facts; no outcome is implied for any real company.
| Request | Cell that fails | Verdict | What happens next |
|---|---|---|---|
| A. Procurement asks the venture team to introduce a 300-person packaging supplier during its contract renewal | Corporate, conflict; company, consent (its CEO has not been asked) | Defer | Reopen after the award is signed; the venture team, not procurement, asks the CEO once |
| B. A pilot startup offers to introduce a freight operator whose dispatch records it hosts | Vendor, fit and consent | Decline the vendor route | The freight operator's CEO hears about the program only from someone it already deals with directly, and decides alone |
| C. A business unit head asks to introduce a 140-person engineering firm the corporate holds 20% of, after its CEO asked in writing | None | Proceed | One introduction from the named relationship owner; the firm applies itself |
| D. Corporate development asks to introduce a 400-person services company it is negotiating to buy | Company, conflict | Defer | Before closing, any decision is the target CEO's, made without deal pressure; after closing it is the acquirer's CEO's call, and SourceX should be asked in writing how a request from inside the buying group is treated |
Only request C clears all nine cells. Request A is the most common shape: a reasonable company, approached through the one channel that makes its CEO's answer hard to trust. The preferential access escalation brief handles the corporate that wants something back for the introduction.
A ten-request trial that measures trust, not volume
Before writing any policy, run the matrix on the next ten requests, opt-in introductions only, recording the failed cells, the verdict, any trigger date and who asked. Then count requests declined, deferrals whose trigger arrived, CEOs who asked for an introduction, introductions submitted, and companies that said the request felt tied to the corporate's buying power; ask that last question in one line of every CEO approached. SourceX has not published acceptance or conversion figures, so these counts are your own baseline, not a benchmark.
Set the stop rule before the first request: if any CEO says the ask felt tied to purchasing, the unit that raised it pauses all requests until the venture team reviews why the conflict cell missed it.
Blind spots in the nine cells
- Unspoken leverage. A supplier may never mention how much of its revenue the corporate represents; the conflict cells catch only what someone says aloud.
- Stricter house rules. A corporate's own policy may bar referral rewards outright and decline a request the matrix would pass.
- Ownership mid-request. A sale can close between the request and the ask, moving the decision to the acquirer's CEO and folding the company into a group that counts as one referred company for the once-per-company floor.
- Overlapping claims. When a business unit and the venture team both know the company, only one introduction can be credited, and SourceX decides contested cases in duplicate review.
- Criteria move. Each SourceX program applies its own thresholds, so a company that fails today can fit a different program later. Date every fit verdict.
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 request clears every cell and the operating company's CEO has asked in writing, register the corporate as a partner, hold the CEO's own description of the company up to who qualifies, and have the single named owner go through the program terms before writing the introduction. The corporate development overview covers the wider program from the deal team's side, and more guides sit in the guides library.
Turning down corporate requests is part of running a referral program well; deciding whether SourceX itself deserves capital is a different exercise, and readers doing it 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.