How to route data interest from a business unit to SourceX: a twelve-field sponsor handoff that sorts each request by whose records it concerns, so the unit leader sponsors, the right CEO decides and the venture team only routes

Short answer

Route by whose records they are, never by who raised the idea. A business unit asking to license the corporate's own records is not making a referral: the corporate's CEO decides whether the group applies. A business unit that knows an outside company holds a relationship, and that company's CEO decides. A vendor hosting records is a custodian, so each client it hosts for decides about its own. The unit leader sponsors, the venture platform manager routes, and nobody in the corporate authorizes for anyone else.

Visual briefFull-size diagram
A rail switching diagram: one track carrying a business-unit request reaches a switch labeled whose records, which sends it down one of three tracks, the corporate's own records to the corporate's CEO and a direct application, an outside company to its CEO and one introducer, and vendor-hosted records to each client's CEO; a dead-end siding marked hold waits for an open tender or renewal to close.
Routes follow the handoff on this page; the switch is set by whose records they are, never by who asked.

Getting this wrong is easy because the requests arrive in the same voice, from the same senior people, often in the same week.

Three requests that sound alike and route differently

  • "Our field service division has twelve years of work orders. Can we license them?"
  • "Our largest distributor asked whether we know anyone who licenses business data."
  • "The vendor that runs our claims platform says it holds years of records from all its clients."

Each names a different owner, and the roles have to be kept apart before anyone acts:

RoleWho it isWhat it holdsWhat it can decide
The corporateThe parent and its business unitsIts own operating records, through the legal entity that created themWhether the corporate group itself applies, through its CEO
The vendorA provider that hosts or processes records for clientsCustody of its clients' records, plus its own operating recordsOnly about its own records, through its own CEO
The operating companyAn outside business the unit knows: a customer, distributor or supplierIts own recordsWhether it talks to SourceX, through its CEO

A business unit is a division, not usually a licensing party. The records belong to whichever entity in the group created them, which the live guide on which entity owns the data works through.

Running a system is not owning the right to license it. NIST's glossary defines a system owner as "An organizational official responsible for the procurement, development, integration, modification, operation, maintenance, and disposal of a system." A business unit head often fits that description exactly for the platforms the unit runs. Nothing in it reaches licensing the records to an outside party, and the glossary itself notes that its entries are not meant as official or preferred definitions. Under SourceX's program the CEO authorizes a licensing discussion, a distinction the guide on founder permission and corporate authority draws for portfolio companies.

The business-unit sponsor handoff

Twelve fields, filled in one conversation between the unit's sponsor and the venture platform manager, from what the sponsor knows and what the company itself says. No records, samples, customer lists or screenshots are attached, ever.

No.FieldWho answersWhat it decides
1Whose records: ours, an outside company's own, or held by a vendor for clientsUnit sponsorThe route: A, B or C
2The legal entity that created and holds themUnit sponsor, checked by legalWhich company would apply; a whole corporate group counts as one referred company for the once-per-company floor
3That entity's CEO, and since whenPlatform manager, from public records or the companyWho decides: the acquirer's CEO once it was bought, the target's CEO until a pending sale closes
4Whether that CEO has been told and wants the conversationThe companyProceed, or stop here
5How the interest arose: unprompted, or during a negotiation, tender, renewal or disputeUnit sponsorHold until the commercial event is over
6What the unit knows only through the commercial relationshipUnit sponsorStays out of every message
7Any earlier contact with SourceX: application, account, lead or emailThe companyA duplicate earns no partner credit, though the company can still apply
8Full-time headcount at peak, in the company's own wordsThe companyAgainst a baseline of roughly 50 or more, contractors left out
9One named introducer, or nonePlatform managerA single person makes any introduction
10Corporate clearances: compliance, conflicts, legalPlatform managerInternal permission to ask, never the company's permission
11Whether anyone in the corporate could be paid, and how it is disclosedPlatform managerWhat the company hears first
12Route chosen, and the datePlatform managerA, B, C, hold or stop

The five outcomes:

  • Route A, the corporate's own records. There is no introduction to make. The corporate's CEO decides whether the group applies, the unit leader prepares the internal case, and counsel reads the corporate's own customer and vendor contracts. The published terms say nothing about an insider registering as partner for its own employer's application, and that idea collides with the corporate's conflict rules; a direct application, with nobody credited, avoids the question.
  • Route B, an outside operating company. That company's CEO decides. One person the CEO trusts makes the introduction, and the unit stands back from the ask while any commercial negotiation is open. The trade-off between asking through a sponsor and writing to the CEO yourself is laid out in the sponsor-or-CEO comparison.
  • Route C, records a vendor hosts. The vendor is a custodian. Each client owns its records and decides about them through its own CEO; the corporate's own records inside that vendor go to route A. The vendor's own operating records, such as its support history, are a separate route B question for the vendor's CEO.
  • Hold. An open tender, renewal or dispute between the unit and the company.
  • Stop. The CEO declines, the records belong to someone else, a fit fact fails, or the records were licensed for AI training before.

Method note. The handoff applies SourceX's program terms, screening page and process page, all read 2026-10-27, and two owner decisions that settle questions the terms leave open: the CEO is the one who authorizes, and a corporate group counts as one referred company, so the USD 50,000 floor applies once to it. It does not assess demand, record quality or any payout, which only SourceX's review can judge, and it records the company's own words for every fit fact rather than what the unit believes.

Approvals on each side, kept apart

Inside the corporate. The unit sponsor puts the request in writing. The venture platform manager routes it. Compliance clears conflicts and any reward. Legal confirms that nothing learned through the commercial relationship travels, and for route A reads the corporate's own contracts. The corporate's CEO decides route A.

At the outside company. Its CEO decides whether to talk at all. Its own counsel reads its own contracts. SourceX reviews fit and rights after the company applies, a step that involves no files and shares no records at the qualification stage.

No approval on the first list stands in for any on the second. The partner agreement can be signed by an individual or by an entity, so who registers for the corporate is the corporate's policy decision; whoever it is, signing confers no right to pass along any company's records. Team members weighing whether to accept a reward at all should read the corporate development referral page and the corporate opportunity guide.

For route B, the reward terms should be stated to the company before it decides. If the company licenses its records, SourceX pays the credited partner, on the company's first qualifying transaction, the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, with the company and every entity in its group counted as one referred company for the USD 50,000 floor, from SourceX's own funds and with nothing removed from the compensation in the company's signed agreement. The payment clock is 60 calendar days, and it starts only once two things have both happened: the Acquisition Partner has given final written acceptance of the whole validated dataset, and its handoff is complete. A condition still open at that point delays payment until it is met, with no fresh 60 days. Only one partner can be credited per company: the first valid introduction within the 90-day window, once the company submits a verified application. Where two partners claim one company, even two colleagues who registered separately, SourceX settles it in duplicate review. Illustrative: a USD 40,000 actual payout falls below the USD 100,000 Minimum Transaction and earns nothing unless SourceX agrees in writing; a USD 800,000 payout would mean a USD 120,000 reward, and a repeat transaction first agreed within 12 months would pay 15%.

Four requests through the handoff (Illustrative)

Illustrative. Four made-up requests from one imaginary corporate; none reflects a real company or result.

RequestWhose recordsRouteWho decidesWhat stays out
Field service division, twelve years of work ordersThe corporate's ownAThe corporate's CEONo introduction exists; customers' site details inside the orders go to counsel and SourceX's rights review
A 340-person distributor asks about licensingThe distributor's ownB, once its CEO confirms interestThe distributor's CEOVolumes and pricing the unit knows from the account
The claims platform vendor offers "all clients' data"Each client'sCEach client's CEO; route A for the corporate's own claimsThe vendor's client list
A supplier in an open tender asks the category leadThe supplier's ownHold until the awardThe supplier's CEOAny link to the tender

A first pilot: five routed requests and the trust signals

Route the next five requests through the handoff and record five things for each: days from the request to a routing decision, whether it arrived during an open commercial event, the route chosen, whether the CEO said yes or no, and any complaint from a customer, distributor, supplier or vendor. Count misroutes too: a request first logged as route B that turns out to concern the corporate's own records. SourceX has not published figures from corporate routing pilots, so these numbers will be the corporate's own. Report declines and complaints beside introductions, never instead of them.

Risks and limits of the routing approach

  • Rights. The corporate's own records can carry customers' material, and SourceX's screening page puts client-owned material on its list of usual misfits. Route A is a rights question before it is a sales one.
  • Demand. SourceX checks relevance to its current data needs during review, so a perfectly routed company can still be declined, and may fit a different program later.
  • Earlier licensing. Records already licensed for AI training cannot be licensed again through SourceX, which is why the stop list includes them.
  • Commercial pressure. A distributor may not feel free to refuse a request that arrives through its largest supplier's business unit. The live answer on referring a supplier your company buys from covers the mirror case.
  • Incentive drift. A possible reward can pull a venture team toward the unit's biggest accounts rather than the companies with the strongest records.
  • One floor per group. A corporate group counts as a single referred company, so the USD 50,000 floor applies once to its first qualifying transaction and later ones first agreed within 12 months pay 15%, as for an outside company with its subsidiaries; the question on several companies in one group explains the effect.
  • The thesis itself. This page assumes most unit requests concern outside companies. If most turn out to be route A, the venture team is the wrong owner and the corporate's own data governance should take them.

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 route B handoff shows a confirmed CEO, a clean commercial calendar and one named introducer, register for a partner link, compare the company's own answers with who qualifies and read the program terms with compliance before anyone writes to the CEO.

Routing a business unit's request is referral work; whether SourceX itself belongs in a corporate venture portfolio is a separate diligence question, and materials for it are available on request 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.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Can the venture team introduce its own parent company and be credited?

The published terms do not address an insider registering as partner for its own employer, and the idea runs straight into the corporate's conflict rules. The clean route for the corporate's own records is a direct application decided by the corporate's CEO, with no partner credited.

A business unit leader runs the system and wants to go ahead. Is that enough?

No. Running a system makes the leader its operational owner, not the person who can license its records. In this program the CEO of the entity that holds the records authorizes a licensing discussion, so the unit leader's role is to sponsor the request internally.

What if the outside company the business unit knows has already been in touch with SourceX?

Then no introduction is needed and no partner is credited. Earlier applications, accounts, leads or email exchanges make it a duplicate under the terms, and the company simply continues with SourceX directly if its CEO wants to.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. csrc.nist.gov/glossary/term/system_owner_or_program_manager
  4. sourcex.si/how-it-works
  5. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  6. sourcex.si/investors

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment