# Innovation team data partnerships: meeting brief | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-approach-an-innovation-team-about-company-introductions
Last updated: 2026-11-05

Bring a one-page brief, not a pitch. Tell the innovation team what SourceX does, which companies tend to fit, that each company's CEO decides alone, and that whoever introduces may be paid a reward. Ask for no lists, no pilot data and no contacts. Ask only whether relationship owners may raise the idea with three to five companies they already know well, end the meeting with a decision, and leave startups in active pilots out of the first round.

Innovation teams are protective for good reason. Their relationships with startups and suppliers run on trust and on deals still in progress, and a stranger asking for "introductions" sounds like someone who wants the pipeline. A brief that rules that out in its first line gets a different meeting.

## What an innovation team holds, and in which role

An innovation team touches companies through scouting, pilots, accelerator cohorts, open challenges and co-development. In several of those the corporate is not an investor at all but a customer. The BMW Group Startup Garage, for example, describes itself as a venture client unit: in our paraphrase of its own pages, BMW buys a first unit of a startup's product rather than taking equity, the startup receives supplier status and a purchase order, and it keeps ownership of its intellectual property. Under that model, a request from the corporate reaches the startup from its customer.

| Relationship | Role the company plays toward the corporate | Whose records are in play | What to watch |
|---|---|---|---|
| Scouting pipeline | Prospect | The company's own; the team has seen none of them | Names in a scouting tool belong to the corporate's process, never to an introduction list |
| Venture-client pilot | Vendor | The startup's own records, plus anything the pilot agreement assigns | A live purchase order makes any request feel commercial |
| Accelerator or challenge cohort | Participant | The company's own | Often young; the size and history tests come first |
| Co-development partner | Vendor or joint partner | Its own project history, and shared work under the joint agreement | Joint terms may cover the shared work |
| Startup the corporate acquired | Part of the corporate group | The group's | The acquirer's CEO now decides; this is an internal route |

Three roles have to stay separate in the conversation. The **corporate** (the innovation team, the venture unit and the business unit that sponsors a pilot) can open a door. The **vendor relationship** (any company currently selling to the corporate) is a reason for care. The **operating company** is the only party whose records are in question, and its CEO is the only person who can decide to discuss licensing them. SourceX's screening page lists introductions made without the decision maker's knowledge as usually not a fit, so reach without that CEO's consent is worth nothing.

## The innovation-team meeting brief

One page, nine lines, sent ahead of the meeting. Each line answers a worry the team will otherwise raise.

| Line | What it says | Why it is there |
|---|---|---|
| 1. Purpose | We would like to agree whether relationship owners may mention a data licensing program to a few companies they know well. We are not asking for names today. | Removes the fear of a pipeline grab |
| 2. What SourceX does | SourceX licenses records from an established company's own operations for AI training and evaluation, and pays the company under agreements it signs itself | A plain description, taken from SourceX's own pages |
| 3. Who tends to fit | Full-time headcount that reached 50 or more at its peak, contractors left out; several years of its own records; rights to license them | Screens out most early-stage pilots before anyone is asked |
| 4. Who decides | Each company's CEO, never the innovation team or the venture unit | Separates reach from authority |
| 5. Who could be paid | Whoever registers as partner may receive a reward from SourceX if a company completes a qualifying, paid deal; it is not taken from the company's compensation | Disclosure before anyone has to ask |
| 6. What we never ask for | Scouting lists, pilot data, contacts, logins, samples | The partner agreement gives a partner no authority to share a company's records |
| 7. What the corporate will not say | That it endorses SourceX, or that any company is accepted | Public naming needs SourceX's written authorization; acceptance is SourceX's call |
| 8. The proposal | Three to five companies, chosen by their relationship owners, asked once, over 60 days | Small enough to stop without harm |
| 9. The decision | Yes, no or not yet, with a date | The meeting ends with an answer |

Line 6 rests on the sample Channel Partner Agreement, whose section 4.2 says "This Agreement gives Partner no authority to share a supplier's inventory, records, raw data or personal information, or to access extraction systems." Line 7 rests on section 4.5: "Neither Party may publicly identify the other as a partner or disclose non-public deal details without written authorization, except as legally required." Quoting both in the meeting does more for trust than any assurance of your own.

## A 30-minute agenda

1. **Minutes 0 to 5, purpose.** Read line 1 aloud. Confirm nobody expects a list.
2. **Minutes 5 to 12, who holds what.** Walk the relationship table. Ask the team which relationships it would never touch, and write them down as exclusions.
3. **Minutes 12 to 20, fit and who decides.** Lines 3 to 5. Expect the question "so most of our startups are out?" and answer it honestly: many pilot-stage companies are, for now.
4. **Minutes 20 to 25, what we never ask.** Lines 6 and 7. Invite the team to add its own red lines.
5. **Minutes 25 to 30, decision.** Line 8, then line 9. If the answer is "not yet", agree what would change it and a date to revisit.

## What the team will ask

**"Will this touch our pilots?"** It should not. Companies in a live pilot stay out of the first round, and nothing about a pilot, its data or its terms is mentioned to anyone.

**"Why not just send you our scouting list?"** Because a list is not an introduction, and companies on it have agreed to nothing. A company becomes a referral only when its own CEO decides to apply, which is also why [creating a referral link](/questions/does-creating-a-referral-link-make-an-introduction-eligible-for-a-reward) achieves nothing by itself.

**"Do we get credit or money?"** Possibly, if the corporate's policy allows it. The sample agreement can be signed by an individual or an entity, so the corporate decides which, if either, registers. If its policy forbids rewards, a company's CEO can still apply directly without any partner.

**"What if a startup we work with asks us about it?"** Point it to SourceX's public pages and let its CEO decide. Nobody on the team needs to introduce it, and doing so mid-pilot is the case to avoid.

## Separate approvals once the team says yes

A yes from the innovation team is permission on the corporate side, not consent from any company. Before a relationship owner writes to anyone, three corporate answers should be on file: the owner agrees to ask, compliance says who may register and accept a reward, and the team confirms the company is not in a live pilot or negotiation. On the company side, one answer matters: the CEO's own yes, given knowing that someone could be paid.

Two checks sit between them. Ask the CEO whether the company has ever applied to, corresponded with or held an account with SourceX; if so, it is a duplicate under the terms and no partner is credited. And if the venture unit and the innovation team both know the CEO, agree who speaks. The program credits one introduction per company, and colliding claims go to SourceX's duplicate review, decided from dated records. Whichever person or entity submits must first sign the SourceX Channel Partner Agreement.

## Three names the team might raise (Illustrative)

Illustrative: invented companies, each showing how the brief sorts a name rather than what SourceX would decide.

**A. A startup in an active venture-client pilot, 45 people, founded three years ago.** It sells to the corporate today and is below the published size baseline. Outcome: not in this round. Revisit if full-time headcount passes 50 and no pilot is live.

**B. An engineering services firm, 280 people, 15 years, a co-development partner.** Its own project history across many clients is its strongest material; the shared work with the corporate sits under the joint agreement and is left aside. The engineering director who owns the relationship waits until the current milestone is signed off, then asks the CEO. Outcome: one ask, after the milestone.

**C. A startup the corporate acquired last year, now 120 people.** It is part of the group, so the acquirer's CEO decides, and the program treats the parent and its subsidiaries as one referred company, so the USD 50,000 floor applies once across the group. The terms do not address an employee introducing their own group, so compliance and SourceX hear about it before anyone else. Outcome: internal route only.

## Running the trial and reading trust

Over 60 days, record for each of the three to five companies: whether the relationship owner agreed to ask, how many days that took, whether the CEO opted in, what the CEO said about how the request felt, and whether anything reached the innovation team afterward, such as a startup asking whether the pilot depended on it. That last signal stops the trial at once.

Report back to the team with the counts, including the declines. SourceX has not published conversion or acceptance figures, so the trial measures your own process; no figures are published here. For a portfolio-wide version of the same choice, see [opt-in versus mandatory portfolio programs](/compare/opt-in-vs-mandatory-portfolio-company-programs).

## Where this approach can fail

- **Leverage nobody admits.** A company selling to the corporate may agree in order to protect the account. Excluding live pilots helps; it does not remove the problem for long-standing vendors.
- **Young companies.** Innovation teams know many companies that miss the size and history tests today. A small first round may find no candidate at all, which is a result worth reporting.
- **Joint work.** Co-development records can fall under joint terms; rights are settled in SourceX's review, not in the meeting.
- **Program fit.** SourceX screens against current programs, and a company that misses one may suit another later.
- **Policy.** The corporate may bar rewards for staff or for the entity, which ends its role without affecting any company's own application.

**Method note.** The brief and agenda apply SourceX's program terms (version 2026-10-22.2, since replaced by version 2026-11-04), the screening page and the sample Channel Partner Agreement (version 2026-10-19), read on 2026-10-27, plus one corporate's published description of a venture-client unit. They organize a meeting; they do not assess any company's records, demand or payout, which only SourceX's review judges. The companies above are invented. The portfolio-side version of these steps is in the [portfolio team guide](/guides/a-portfolio-team-guide-to-data-licensing-introductions) and the [overview for venture platform teams](/for/venture-platform-teams).

**The reward, worked once.** Illustrative: if SourceX's Actual Supplier Payout to company B on its first qualifying transaction totaled USD 200,000, the registered partner's reward would be USD 60,000 (USD 50,000 plus 5%, which exceeds 15% of that payout), paid by SourceX itself and never deducted from the firm's agreed compensation.

## 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 innovation team agrees to a trial and the first CEO says yes, [register whichever partner your compliance team approved](/register), run that company past the published [who qualifies](/who-qualifies) criteria and attach the [program terms](/terms) to the brief you sent the team.

Meeting an innovation team about introductions is separate from evaluating SourceX as an investment; anyone weighing the latter can request 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/terms
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://www.bmwstartupgarage.com/en/faq.html
- https://sourcex.si/investors
