# Strategic partner as introducer, not data owner | SourceX

Canonical: https://refer.sourcex.si/guides/when-a-strategic-partner-is-the-introducer-but-not-the-data-owner
Last updated: 2026-11-05

A strategic partner can open the door to a company; it cannot walk through on the company's behalf. A minority stake, a supply contract, a co-sell arrangement or even hosting the company's systems gives a corporate reach and information, never the right to license the company's records or to agree to a licensing discussion. That decision belongs to the operating company's CEO, rights depend on the company's own contracts, and SourceX runs the review. The corporate's job is one permissioned introduction, cleared inside its own walls first.

Corporate venture teams are built for exactly this kind of reach. Intel Capital's site, for example, says its team made nearly 1,000 curated introductions between portfolio companies and Global 2000 customers in 2025 (the firm's own count). An ecosystem that can arrange that many meetings can certainly arrange one more. The discipline is in keeping that reach from being mistaken for authority.

## Six corporate ties, and what each one leaves out

Each tie between a corporate and an operating company carries something real. None carries licensing authority, and some carry duties that make the corporate more careful, not less.

| Corporate tie | What it gives the corporate | What it never gives | The duty it adds |
|---|---|---|---|
| Minority equity stake held by the venture arm | A relationship with the founder or CEO, and often reporting | Any say over the company's records or its licensing decisions | Confidentiality over what the reporting revealed |
| Board observer or board seat | A voice in the boardroom | The CEO's role in opening a discussion and signing | The duties that come with the seat |
| Commercial or distribution agreement | Account teams on both sides, joint plans | Rights in records the company created for itself | The agreement's confidentiality clause |
| Co-sell or partner-program membership | Shared pipeline and named contacts | Consent from the company to pass its details to third parties | Program rules on sharing customer contacts |
| Supplier relationship, with the corporate as the buyer | Leverage, spend data, supplier files | A neutral ask, since a large customer's request carries weight | Procurement confidentiality and conflict rules |
| Hosting or running the company's systems | Administrative access to its data | Ownership, or the right to move or describe that data | The service contract's limits on use |

The pattern is the one SourceX's screening page sets out for funds: owning shares does not run a company, and under the program it is the CEO who opens a licensing discussion and signs for the company. A corporate is no different because it is larger or more strategic. Even inside very large partner ecosystems, consent is recorded tie by tie. Microsoft's referral resource, for instance, carries separate consent flags for sharing a deal with Microsoft sellers, for sharing personal data and for contacting users (a paraphrase of its documentation). The procurement tie is the hardest of the six to keep neutral, and it has its own page: [separating procurement relationships from licensing permission](/guides/how-to-separate-procurement-relationships-from-licensing-permission).

## The introducer-owner authority diagram

Put the corporate group in one column: the venture team, the business unit that owns the commercial relationship, procurement, legal, and any product team that hosts the company's systems. Put the operating company in a second column: its CEO, the people who own each record family, and its counsel. SourceX gets a third column of its own.

Exactly one line may join the first two columns: an introduction, sent after the company's CEO has said yes in writing. Every other arrow you are tempted to draw, from hosting team to records or from business unit to decision, is the mistake the diagram exists to catch.

| Role | Sits in | Holds | May do in the referral | May never do |
|---|---|---|---|---|
| Venture or platform manager | Corporate | The investment relationship | Explain the program to the CEO, disclose any reward, submit the introduction | Promise fit, or describe the company's records |
| Business unit relationship owner | Corporate | The commercial account | Agree, before anyone asks, that the ask may be made, or decline it | Tie the ask to the commercial relationship |
| Product or hosting team | Corporate, acting as vendor | Admin access to the company's data | Nothing in the referral | Export, count or sample the company's records |
| Corporate legal and compliance | Corporate | Policies on confidentiality and outside payments | Clear the corporate's participation and who registers | Speak for the operating company |
| The company's CEO | Operating company | The decision and the signature | Say yes or no, apply, sign or walk away | Delegate the decision to the corporate |
| Record owners and counsel | Operating company | Knowledge of the records and their contracts | Prepare the company's own answers | Hand records to the corporate for the referral |
| SourceX | Its own column | Its review and its agreements with the company | Assess fit and rights, deal with the company directly | Receive the company's records through the corporate |

Two cells deserve a second look. The hosting team can see more of the company's data than anyone else in the corporate, and it has the least to do with the introduction. And SourceX may deal directly with a referred company without the partner on every call, as section 2.2 of the unsigned partner agreement sample allows, so the corporate's part ends once that one line is drawn. Section 4.2 of the same sample gives the partner no authority to share a supplier's records or reach its extraction systems, and section 7.2 says supplier agreements grant the partner no data rights. Partners never see, upload or handle a company's records, inventory or data room, whatever access their other roles provide.

**Method note.** The diagram was built on 2026-10-27 from SourceX's screening page and program terms (version 2026-10-22.2, since replaced by version 2026-11-04), the unsigned Channel Partner Agreement sample (version 2026-10-19), and the two partner-ecosystem sources cited above. It sorts roles by where they sit and what they hold. It does not measure how often corporates make such introductions or how they turn out; none of that is published. A corporate whose stake gives it control of the company is a different case, covered in the risks below.

## Sign-offs the corporate needs, and the one only the company can give

Two sets of approvals have to exist before the introduction goes anywhere, and neither can stand in for the other.

**Inside the corporate**, in this order:

1. **The relationship owner agrees.** The business unit or venture partner who holds the CEO relationship decides whether raising data licensing helps or strains it. A no ends the row.
2. **Legal clears participation.** Who signs the SourceX Channel Partner Agreement: the corporate entity or a named employee? The sample agreement allows either an individual or an entity, so the corporate's own policy on outside payments decides.
3. **Confidentiality is checked.** Anything learned through investment reporting, a commercial agreement or hosting stays out of the conversation with SourceX.
4. **Earlier contact is checked.** If the company already has an application, lead, account or email thread with SourceX, it is a duplicate under section 3 of the terms, and no introduction goes in.

**Inside the operating company:**

1. **The CEO says yes in writing**, knowing the corporate may receive a reward and that the decision is the company's alone.
2. **The company applies itself**, describing its own systems and years of records.
3. **Counsel reads the contracts** that touch the records, because records that really belong to the company's own clients rarely make a good fit, and rights are settled in SourceX's review.

Fit stays a short list the CEO can answer: a full-time headcount of 50 or more at its peak, contractors excluded; years of records the company created itself; rights to license them; and a CEO who wants the conversation.

## A logistics group's minority stake (Illustrative)

Illustrative. Generic companies and invented figures; no outcome is implied.

A 4,000-person logistics software group holds a 12% stake in a 340-person freight audit firm through its venture arm. The group's platform also hosts the firm's shipment workflows. The venture manager thinks the firm's fourteen years of audit decisions and carrier disputes might interest SourceX.

The diagram sorts it out. The business unit that sells to the firm agrees the ask can be made. Legal decides the group itself will register as partner. The hosting team is told, in writing, that it has no part. The venture manager asks the firm's CEO on a regular call, mentions the possible reward and says the answer has no bearing on the commercial relationship. The CEO says yes by email a week later. The group checks that the firm has no earlier contact with SourceX, signs the partner agreement and submits the introduction; the firm applies with its own description of its systems. Counsel flags that some shipment records describe the firm's own clients, which SourceX's rights review will weigh.

If a license later closed and SourceX paid the firm USD 480,000 under its Dataset Deal Confirmation, the firm's first qualifying transaction would pay the greater of USD 50,000 plus 5% and 15%: USD 74,000, with no cap. A further qualifying transaction with the firm first agreed within 12 months of that first Closing would pay 15% of its Actual Supplier Payout. SourceX would pay the reward to the group on its own account once every payment condition was met, within 60 calendar days of whichever came later, the Acquisition Partner's unconditional written sign-off on the validated dataset or the finished handoff of it, or promptly once a condition still open at that point was met. None of it would come out of the firm's agreed compensation. SourceX does not publish how it prices offers.

## Test with three to five CEOs the corporate already knows

Announcing the program across an ecosystem implies that the corporate stands behind each company's fit, which it cannot. Start smaller.

- **Cohort.** Three to five companies whose CEOs the corporate already speaks with directly, each with a relationship owner who has agreed, and none in an active commercial negotiation with the corporate.
- **The ask.** One conversation per CEO, with the reward disclosed and the decision left explicitly with the company.
- **Trust measures.** Ask each CEO, after the conversation, whether it felt connected to the commercial relationship. Count any complaint from a business unit or a company, and any request to stop.
- **Fit measures.** CEO yeses, introductions submitted, duplicates found at the earlier-contact check, and verified applications within 90 days of each introduction.
- **Stop rule.** One CEO who felt pressured pauses the pilot until the ask is rewritten.

These figures are not yet published for any corporate cohort, and this page gives none; the first readout becomes the corporate's own baseline. If a CEO says not now, [what to say to an owner who is not ready](/guides/owner-not-ready-to-sell-business-what-to-say) applies.

## Where the diagram can be wrong

- **Control changes the roles.** If the corporate acquires the company, the target's CEO decides until closing and the acquirer's CEO decides afterward. The corporate is then an owner, not an introducer; [strategic and financial buyers](/compare/strategic-buyer-vs-financial-buyer) are compared separately. A parent and its subsidiaries count as one referred company, so the USD 50,000 floor applies once, to the group's first qualifying transaction, and later qualifying transactions pay 15% with no cap; whether earlier contact by another part of a group, or another partner's introduction of a sister company, affects credit is not spelled out in the published terms, and SourceX settles it when it reviews duplicates.
- **Rights.** Many of the records a corporate notices exist because of its own dealings with the company, and records that belong to the company's clients are usually not a fit.
- **Programs move.** SourceX's screening page says criteria follow each program and can change; a company that does not fit today may fit later.
- **Competing interests.** A corporate that builds AI models itself may want the same records, and should say so to its own legal team before it introduces anyone.
- **No evidence yet.** No data has been published on how companies react to a strategic partner raising data licensing; the pilot above is how to find out.

## 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 relationship owner has agreed, legal has cleared who registers and the company's CEO has said yes in writing, [register as a partner](/register), test the company against [who qualifies](/who-qualifies) and read the [program terms](/terms) before that single line is drawn. Related questions for corporate teams are covered on the [corporate development page](/for/corporate-development-data-licensing-referral) and in [why a co-investment relationship is not company permission](/guides/why-a-co-investment-relationship-is-not-company-permission). Other corporate and venture playbooks sit in the [guides hub](/guides).

Introducing a company is one decision; looking at SourceX as an investment is another, and readers weighing the second can request investor materials through the [SourceX investor overview](https://sourcex.si/investors).

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.

## Sources

- https://refer.sourcex.si/who-qualifies
- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://www.intelcapital.com/
- https://learn.microsoft.com/en-us/partner-center/developer/referral-resources
- https://sourcex.si/investors
