# Strategic investor data access requests | SourceX

Canonical: https://refer.sourcex.si/guides/when-a-strategic-investor-wants-preferential-data-access
Last updated: 2026-11-04

Take the request out of the introduction. SourceX's partner agreement gives an introducer no data license, no right to train models, no authority over a company's records and no copies of its data without separate written authorization, and the program terms add that partners never see applicant documents. Whatever a strategic investor wants, whether a copy of operating data, a first look or better terms, is a separate request to the company, decided by its CEO under the company's own agreements. Log it, split it into its separate asks, route each one and pause the introduction until it is settled.

The request may come from inside your own corporate: a business unit or an internal AI team that hears a portfolio company is talking to SourceX and wants the same records, or wants them first. The venture team is then the only party that sees both sides, which is why it should hold the brief.

## What the investor already holds, and what an introduction adds

A strategic investor's rights to company information come from the investment documents it negotiated with the company. They are specific and conditional. One public example: the investors' rights agreement Silverback Therapeutics filed with the SEC as an exhibit to its 2020 registration statement gives information and inspection rights to "Major Investors" in Section 3.1, and only "as long as at least twenty percent (20%) of the shares of Preferred Stock originally issued remain outstanding." The same agreement also carries competitor language, under which an investor is not treated as a competitor merely for holding less than 20% of one (a paraphrase of the filing's excerpt). Other companies' documents say other things. The venture team does not interpret them; the company's counsel reads its own.

An introduction to SourceX adds nothing on the data side. The unsigned sample of the SourceX Channel Partner Agreement says "No data license, trademark license or right to train models is granted." It gives a partner no authority to share a supplier's records or reach its extraction systems, and bars collecting or keeping supplier dataset copies through the referral program without separate written authorization. A partner tracks its own referral through generic stages or reference codes, and SourceX may deal with the company directly without the partner on every call. A strategic investor that registers as a partner therefore gets the same thing any partner gets: a possible reward, and no window into the company.

SourceX's screening page makes a related point about board knowledge: what a fund learns from board materials is a reason to ask the CEO, never material to pass along. [What a board observer can learn](/guides/what-a-board-observer-can-learn-without-sharing-board-material) works through that line.

## Seven asks hiding in one request

"Preferential access" usually bundles several asks. Separate them before anyone answers, because each has a different owner. Illustrative wording below; the routes follow SourceX's published documents.

| Ask | Route | Why |
|---|---|---|
| A1. A copy of the company's operating records for the corporate's own AI work | The company's CEO, as a separate commercial question | Only the company can license its records, and records it licenses to the investor for AI training could not later be licensed through SourceX, because suppliers confirm their data has not been licensed for AI training before |
| A2. A first look before the company talks to anyone else, SourceX included | The company's CEO, with its counsel reading existing agreements | A promise like this is the company's to give or refuse; a later SourceX license would be exclusive for AI training for the data selected |
| A3. A seat in the company's calls with SourceX | The company's CEO | The company decides whom to bring; the partner agreement does not require a partner on calls |
| A4. Whether the venture team may raise any of this with the company at all | Corporate legal and compliance | It can touch confidential board information and the corporate's own conflict rules |
| A5. Credit for the introduction when the business unit also knows the company | SourceX, under its terms | One partner per company; overlapping claims go to SourceX's duplicate review, and a company that already knew SourceX credits nobody |
| A6. Better terms through SourceX for companies the corporate backs | Not available through a referral | A partner may not commit SourceX to prices, licenses or payouts, and each payout is set in the company's own Dataset Deal Confirmation |
| A7. Sight of the company's application, dataset or payout through SourceX | Not available through a referral | Partners never receive applicant documents, and neither the company nor SourceX publicizes a deal ([why licensing deals stay confidential](/questions/why-are-ai-licensing-deals-confidential)) |

Three of the seven go to the CEO, one to legal, one to SourceX's terms, and two end where the referral ends. That split is the reason the request cannot ride along with an introduction: the introduction answers none of them.

## The access-request escalation brief

Fill one brief per request, the day it arrives. It travels with the request until every ask is closed.

| Field | What to write | Who supplies it |
|---|---|---|
| 1. Received | Date, channel and the exact words used | Platform manager |
| 2. Requester | Name and role: business unit, venture partner, board designee | Platform manager |
| 3. Asks | One numbered line per ask, confirmed in writing by the requester | Requester |
| 4. Basis claimed | A clause in investment documents, a commercial contract, or none | Requester, never interpreted by the venture team |
| 5. Company and decider | The legal entity and its current CEO; the acquirer's CEO if it has been sold | Platform manager, from public or company-confirmed facts |
| 6. Introduction status | Not started, paused on a date, or submitted on a date | Platform manager |
| 7. Route per ask | CEO, corporate legal, SourceX's terms, or not available through a referral | Platform manager, using the table above |
| 8. Reply to requester | The script below, with the routes | Platform manager, cleared by legal |
| 9. Owner and date per ask | Who decides each routed ask, and by when | Each owner |
| 10. Outcome | Granted, declined or withdrawn, and whether the introduction resumed | Platform manager |

The escalation runs in a fixed order. Legal sees the brief first, because if it says the team may not raise the matter, nothing goes to the company at all. Asks for the CEO then go in one separate note that says plainly it has nothing to do with any SourceX introduction. Program questions go to SourceX in writing. The introduction stays paused until field 10 is filled, and if the company was acquired in the meantime, the acquirer's CEO is the one who decides; before closing, it is still the company's own CEO.

**Method note.** The routes rest on SourceX's program terms, its process page and the sample partner agreement, checked 2026-10-27, with one public investors' rights agreement as an example of how information rights are drafted. The brief records who decides; it does not assess whether any ask is reasonable, lawful or valuable, which belongs to the owners it routes to.

## What to tell the requester, and a short trial

A script for the business unit:

> An introduction to SourceX gives us nothing of the company's: no data, no documents and no say in its terms. If you want access to their records, that is a separate request to their CEO. I have logged it, legal will tell us whether we can raise it, and the introduction waits until then.

Then test whether introductions and access requests stay apart in practice. Run three to five introductions with CEOs the team already knows, log every access request that surfaces, and after each CEO answers, ask one question: "Did anything suggest the investor would see or receive your data?" Any yes means rewriting the outreach before the next ask. Count the requests logged, the days each brief stayed open and the CEOs' answers. SourceX has not published results for strategic-investor introductions, so these are the measures to keep, not findings. The [overview for venture platform teams](/for/venture-platform-teams) covers the rest of the program from the platform side.

**Illustrative.** The venture arm of a 25,000-person logistics group holds a minority stake in a 300-person freight-audit company with records back to 2009. The group's AI team asks for "the same data SourceX would get, before SourceX." The brief splits that into A1, A2 and A7. Legal clears a note to the CEO on A1 and A2 only; A7 is answered no on the spot. The CEO declines both, and the paused introduction resumes a week later because the CEO still wants to talk to SourceX.

## Where the escalation brief can fail

- **Hallway requests.** An ask made in passing never reaches field 1. Treat any mention of the company's data by a business unit as a request.
- **Board seats.** A director sees board materials, and the line between that information and the company's records blurs. Keep the brief's asks tied to the company's records and its licensing choices, never to what the director learned in the boardroom.
- **Pressure on the company.** A CEO may feel unable to refuse a strategic investor. Say in writing that refusing changes nothing in the investment relationship, and mean it.
- **Competition questions.** Where the investor competes with the company, counsel may see issues the brief cannot.
- **Contracts the team cannot read.** The brief routes questions about investment documents; it never answers them.
- **Credit overlap.** If the business unit and the venture team both claim the company, SourceX decides in duplicate review; settle internally who registers before anyone writes. [Preventing duplicate claims](/guides/how-to-prevent-duplicate-claims-before-they-reach-sourcex) covers that step.

## 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 every ask in the brief is closed and the CEO still wants the conversation, [register as a partner](/register), compare the company with [who qualifies](/who-qualifies) and work from the [program terms](/terms), not from the investor's expectations, when you write the introduction.

Handling a strategic investor's request belongs to the referral side; judging SourceX as an investment is a separate question, and investor materials for it can be requested 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/how-it-works
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://www.sec.gov/Archives/edgar/data/1671858/000119312520290236/d67046dex42.htm
- https://sourcex.si/investors
