# Industry consortium data referral role map | SourceX

Canonical: https://refer.sourcex.si/guides/a-data-introduction-from-an-industry-consortium
Last updated: 2026-11-05

A consortium can tell its members that SourceX exists. It cannot introduce members as a group, offer the data members contributed to it, or decide for anyone. Each member company is a separate introduction that starts only when its own CEO asks, and the company then applies, is reviewed and signs on its own. The corporate that convenes or funds the consortium gets no preferred view of any member's records, and nobody gathers member data for SourceX.

## Membership is a relationship, not a permission

A platform manager whose corporate sits in an industry consortium sees an obvious shortcut: dozens of established companies that already meet, already trust one another and already share some data. Membership does carry real relationships, meetings and whatever the consortium agreement says about contributed material. It carries no authority over a member's own records.

SourceX's process makes that concrete. Its company page says the company approves scope and terms and signs before any data is delivered, confirms the data has not been licensed for AI training before, and grants a license that is exclusive for AI training, with the term set in each Dataset Deal Confirmation. Every one of those is a promise only the company can make. A consortium cannot make it for a member, and an anchor corporate cannot make it for a supplier or a portfolio company. The member's CEO authorizes the discussion; once a member has been acquired, the acquirer's CEO decides, and until closing the member's own CEO keeps that call.

**The shared pool stays out.** Many consortia hold material their members contributed under the consortium's own terms. This page does not propose licensing that pool, as a whole or in pieces, through a referral. Whether a member's past contributions affect what it can do with its own records is a question for that member and its contributor terms; the [benchmark contribution question](/questions/data-shared-with-industry-benchmark-consortium) sets out what to read. Why a pooled license is a poor model in the first place is covered in [collective data licensing for associations](/questions/collective-data-licensing-association).

**Competitors share the table.** The FTC's guidance on trade associations says that forming an association does not shield members' joint activities from antitrust scrutiny (our paraphrase of its Spotlight on Trade Associations page). A SourceX conversation at a consortium meeting must not turn into competing members comparing what they hold, what they would accept or whom they would deal with. This page offers no legal advice; the consortium's counsel decides what may be discussed, and the [antitrust basics for associations](/guides/trade-association-antitrust-guidelines) list the usual meeting rules.

## The member permission and role map

Seven roles appear whenever a consortium touches a data introduction. Each row says what the role holds, what it may do, whose permission it needs and what it never does.

| Role | Holds | May do | Needs permission from | Never |
|---|---|---|---|---|
| Consortium secretariat | Member contacts, the meeting calendar, shared project files | Publish one neutral notice through consortium channels | The consortium's governing body, after its counsel reviews the wording | Pass member names, attendance or contributed data to SourceX, or present the consortium as introducing members as a block |
| Anchor corporate and its venture team | Its own commercial ties to members, perhaps board seats or stakes | Mention SourceX to a member CEO it knows; as partner of record, submit one company whose CEO asked | Its internal approvals, then that member's CEO | Suggest preferred access to any member's data, or that membership or investment depends on taking part |
| Each member company | Its own records, and whatever it contributed under consortium terms | Apply directly, ask anyone to introduce it, or ignore the notice | Its own CEO | Owe the consortium an account of what it decided |
| A member that competes with another | The same as any member | The same as any member | Its own CEO | Discuss with competitors what it holds, expects or would accept |
| The shared pool | Contributed material under the consortium agreement | Nothing in a referral | Not applicable: it is not offered | Be described, sampled or offered to SourceX through an introduction |
| SourceX | Its own records of earlier contact | Review each company on its own, sign with it and pay it | Each company's signed agreements | Receive a member list or one member's information about another |
| A member's acquirer | Control of the member once the sale closes | Its CEO decides for the member after closing | The closing itself | Decide anything before closing |

Two members can also belong to the same corporate group. The group then shares one reward cap, however many of its companies license. Whether an introduction of one group company changes credit for its sister is not written into the terms, and SourceX decides it in duplicate review; the [corporate group question](/questions/can-i-introduce-several-companies-from-the-same-corporate-group) covers introducing several of them.

**Method note.** The map applies the program terms (Version 2026-10-22.2, since replaced by version 2026-11-04, sections 1 to 3 and 7), the partner agreement sample (version 2026-10-19: the party block and sections 3.3, 4.2, 4.6 and 7.1), SourceX's company process and screening pages, and the FTC's trade association guidance, all checked 2026-10-27. It does not estimate how many members would fit or what anyone could earn; SourceX has published neither, and fit is decided only in its review.

## Approvals inside the corporate and at each member

Six approvals, in order. A missing one stops everything after it.

1. **The consortium's governing body** decides whether any notice goes out at all, after counsel reviews the words. If it says no, the corporate can still speak to member CEOs it knows, outside consortium channels.
2. **The corporate names a program owner** and an officer who can bind it signs the SourceX Channel Partner Agreement. Section 1 of the terms requires the signature before any introduction, and in section 7.1 of the agreement the signer represents that they have that authority.
3. **A member's CEO asks in writing.** One company per request; a list of interested members is not a request.
4. **The introduction record** names the company, its domain, the partner, the opportunity, the method and timestamps, as section 3.3 of the agreement lists, and nothing about the member's records, which section 4.2 gives a partner no authority to share.
5. **The company applies itself**, and SourceX checks its own records. Under section 3 of the terms, a company with any earlier application, account, lead or email exchange with SourceX is a duplicate, credited to no one.
6. **The company signs, or does not,** its own Master Supplier Licensing Agreement and Dataset Deal Confirmation with SourceX. The corporate sees none of it; the agreement gives a partner only what it needs to follow its own referral, in generic stages or reference codes.

When a strategic investor asks for something extra, such as first sight of a member's data, the [preferential access brief](/guides/when-a-strategic-investor-wants-preferential-data-access) splits the request and routes each part. If the corporate's account sellers will mention the program to members they serve, train them first with the [sales-team boundary card](/guides/how-to-explain-the-referral-role-to-corporate-sales-teams).

## A pilot with opt-in members, and how to read trust

Pilot it before any standing arrangement. The governing body approves one notice. The consortium holds one open session on how direct licensing works, chaired by someone with authority to stop the discussion if it drifts toward what members hold or would accept. There are no company breakouts and no sign-up sheet, and introductions happen only on a CEO's written request. After 90 days, read trust before volume: members who objected to the consortium raising the subject, members who felt the anchor corporate's presence as pressure, any competitively sensitive topic that surfaced (which stops the pilot and is recorded), then CEO requests and declines. SourceX has not published response figures for consortia, so the counts are the consortium's own and too few to be rates.

## Four consortium situations (Illustrative)

Illustrative. Invented consortia, members and people; nothing here implies an outcome.

| Situation | What the map says |
|---|---|
| A logistics consortium's data committee proposes a "consortium dataset" built from members' contributions | Not through a referral, and not as a pool; each member decides about its own records, alone |
| The anchor corporate's venture team knows the CEO of a member that also supplies the corporate | One mention, outside any sourcing round; if that CEO asks in writing, one introduction of that one company |
| Two competing members ask about SourceX during the same session | Each is answered separately afterwards; neither hears about the other, and nobody discusses what either holds or expects |
| A member's CEO asks the secretariat for an introduction | If the consortium has not signed the partner agreement, the secretariat points the CEO to apply directly; if it has, it sends one message quoting that CEO |

## Limits of the consortium role map

- **Contributor terms.** A consortium agreement may limit what members may do with material they submitted, and only the member, reading its own terms, can say how far that reaches. SourceX's screening page treats data a company does not control as usually not a fit.
- **Earlier AI licensing.** A member that has already licensed records for AI training cannot offer those records again; SourceX's process page has the company confirm they were never licensed for that purpose.
- **Antitrust specifics.** The FTC's general guidance does not settle any particular consortium's facts. Counsel does.
- **Demand.** Relevance to SourceX's current data needs is assessed in review, so a member with long, well-kept records can still be declined today.
- **The anchor corporate's weight.** Members that depend on the corporate commercially may hear any mention as a request. No published data measures this; the pilot's first counts do.
- **Duplicates.** Members already in contact with SourceX cannot be credited to anyone, however the consortium raises the subject.

## 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 governing body has approved one neutral notice and a member's CEO has asked in writing, [register the corporate](/register) if it has not already, check that member against [who qualifies](/who-qualifies), and keep the [program terms](/terms) version with the request.

Mapping consortium roles is referral work; assessing SourceX as a business to back is a separate exercise, and anyone doing it can ask for materials through the [SourceX investor page](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://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://sourcex.si/how-it-works
- https://refer.sourcex.si/who-qualifies
- https://www.ftc.gov/advice-guidance/competition-guidance/guide-antitrust-laws/dealings-competitors/spotlight-trade-associations
- https://sourcex.si/investors
