# Explore a data referral without uploading files | SourceX

Canonical: https://refer.sourcex.si/guides/can-i-explore-a-referral-without-uploading-company-files
Last updated: 2026-11-04

Yes. Neither the introduction nor SourceX's first step needs a single file. The partner never handles records, and SourceX's fit check takes three screens with no files, passwords or API tokens, licensing or transferring nothing. The company describes its systems, its years of history and what could be exported, and that description is enough for an indicative licensing estimate. Records stay with the company through both signatures; data is first extracted only after the CEO signs a Dataset Deal Confirmation and SourceX gives the go-ahead.

That is the answer a VC operating partner can give a founder who will not send files to anyone. The walkthrough below goes step by step, says who acts and what changes hands at each one, and marks the single step where a record first leaves the company.

## Why the founder asks about files first

A founder who opens with "we're not uploading anything" usually has one of five concerns. Each one has an answer the partner can point to.

| What the founder says | The concern underneath | What the first step actually asks for |
|---|---|---|
| "I'm not sending customer data to someone I just met" | Exposure | No files at all; the form's optional drafting helper even warns against pasting customer records |
| "My IT lead has no time to build exports" | Effort | A list of systems, years of history and what could be exported, not the exports themselves |
| "Once they hold a copy, we've lost control" | Control | No copy exists at this stage; when delivery comes, large datasets stay in the company's storage or ship on encrypted drives |
| "How can anyone put a figure on this unseen?" | Credibility of the estimate | The estimate is indicative and built from the description; quality is reviewed after delivery |
| "Will you want to look at our files?" | The partner's role | No. The partner agreement bars partners from collecting dataset copies without separate written authorization |

## The metadata-only first-step walkthrough

Eight steps, in the order they happen. Read the last column: until step 8, every record is where it has always been.

| Step | Who acts | What changes hands | Where the records are |
|---|---|---|---|
| 1. The conversation | The partner and the CEO | Spoken answers: peak full-time headcount, country, which systems, how many years, who runs each one | With the company |
| 2. An optional summary | The partner | A descriptions-only inventory from SourceX's builder: system, kind of material, years covered, format, who controls it, and whether it holds personal or third-party data | With the company; the summary stays in the partner's browser until copied |
| 3. Fit check, screen 1 | The company | Company name, website, sector group, country and a one-line description; the applicant's name, role, work email and phone; legal name, entity type and notice address | With the company; nothing is signed by applying |
| 4. The rest of the application | The company | Answers in steps named company details, data overview, systems and privacy: which systems, how far back and what could be exported | With the company; nothing licensed or transferred |
| 5. SourceX's first review | SourceX, with the company | Fit checked, the inventory completed together, a rights check, a processing route and an indicative estimate | With the company; no records are shared at this stage |
| 6. The Master | The CEO signs | SourceX presents the completed inventory under confidentiality | With the company |
| 7. The Confirmation | The CEO signs | The exact dataset, payout and processing route are fixed | With the company |
| 8. The go-ahead | SourceX | Data is extracted, transferred and de-identified through the approved route | The first time any record moves; large datasets stay in the company's own storage or ship on encrypted drives |

Steps 1 to 5 run entirely on descriptions. Steps 6 and 7 add two signatures, both the CEO's, and still move no records. Only step 8 moves data, and it happens because of a Confirmation the CEO signed, not because of anything the partner did.

**Method note.** The walkthrough applies SourceX's application page, its nine-step process, its guide to who sees data, its referral process page, its inventory builder and the unsigned Channel Partner Agreement, all checked 2026-10-27. Screen contents after screen 1 are described only by the step names and process text SourceX publishes; this page does not reproduce fields it could not see. Nothing here measures how long a company takes or what it is offered.

## Four places an upload request slips in anyway

The process asks for no files, yet requests still appear. Each of these has a fixed response.

1. **The eager founder or COO.** Someone offers "a quick export so you can see what we have." Decline it before it arrives; [six no-upload replies](/guides/how-to-handle-a-founder-who-wants-to-send-data-immediately) give the wording, including what to do if a file has already landed.
2. **The drafting helper on the form.** The application offers to draft answers from a website or a sentence, and warns not to paste customer records or anything private. A rushed applicant can still ignore that warning; a pasted ticket is content, not a description.
3. **The partner's own curiosity.** "Send me a sample so I can describe it properly" is the partner asking for something the partner agreement forbids: no authority over the company's records, no access to extraction systems, no dataset copies without separate written authorization.
4. **A summary that carries content.** Top customer names, example notes or a screenshot inside a "metadata" list turn a description into data. The FTC's security guide opens with a lesson headed "Don't collect personal information you don't need", and the same discipline applies here: system names, years, counts and owners, nothing more.

For portfolio-wide screening, a [twelve-field screening form without attachments](/guides/a-portfolio-screening-form-that-avoids-sensitive-uploads) applies the same rule across many companies. The wider risk of copying documents into AI tools is set out in [data-room access versus document uploads](/resources/mcp/mcp-data-room-vs-document-upload).

## What a description can settle, and what it cannot

| Status | Question | Settled by |
|---|---|---|
| Settled from description | Does the company pass the size, country and language tests? | Headcount history, location and the language of the records |
| Settled from description | Which systems hold which kinds of records, for how many years? | The inventory, completed with SourceX |
| Conditional | Can the records be licensed under the company's customer, vendor and employee commitments? | SourceX's rights check, and the company's counsel |
| Conditional | What the company would be paid | Indicative until the Confirmation fixes it |
| Not knowable yet | Whether the delivered data meets quality expectations | Acceptance review after delivery, up to 30 days |
| Not knowable yet | Whether any Acquisition Partner wants it now | SourceX's commercial process |

Two facts end the exercise early, whatever the description says. Records that belong to the company's clients are usually not a fit, and the company has to confirm its data has not been licensed for AI training before; data already licensed that way is not eligible.

## A COO with an export ready to send (Illustrative)

Illustrative. The company, the people and the conversation are invented.

**The offer.** At a portfolio check-in, the COO of a 260-person property management company says: "I can pull last year's maintenance tickets tonight, so you can see what we've got."

**The bounded answer.** The operating partner says thank you and no, before anything is sent. She explains that SourceX's first step runs on descriptions, shows the walkthrough, and offers to fill in the inventory builder with the COO in ten minutes, using system names and years only.

**The authorization point.** The COO knows the records best, but the CEO decides whether the company discusses licensing at all. The partner asks the COO to raise it with the CEO and does nothing further until she hears back.

**The escalation path.** If the CEO goes ahead, questions about delivery, such as where the records would sit or how they would travel, go from the CEO to SourceX once the company applies. The partner does not describe a route for this company, because the Confirmation sets it.

**The voluntary next step, or the decline.** The CEO either starts the fit check, which asks for no files, or says no. On a no, the partner deletes the draft summary, notes the date and the decline, and never asks for the tickets again. Who learns the company's name along the way is mapped in [who sees my company name before I agree](/guides/who-sees-my-company-name-before-i-agree).

## Limits of a metadata-only start

- **Descriptions can be wrong.** Years of history and rough counts come from memory and system settings. The rights check and the acceptance review are where they are tested, and a strong description can still fail there.
- **This defers data movement; it does not remove it.** A company that reaches step 8 will move records. What the walkthrough shows is that this comes after two signatures by the CEO, not before them.
- **A description can still be sensitive.** Naming a confidential customer, a pending dispute or an unannounced system change inside a summary discloses something. Keep summaries to what the inventory builder's columns ask.
- **Fit is not settled by fit facts alone.** SourceX checks relevance to its current data needs in review, so a company that passes every description-level test can still hear no.

## 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 CEO is comfortable that nothing leaves the company before two signatures, [register for a partner link](/register), test the company against [who qualifies](/who-qualifies) and read the [program terms](/terms); the company's own first step is the file-free fit check.

Evaluating SourceX as an investment is unrelated to how a referral starts; anyone weighing it 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://sourcex.si/apply
- https://sourcex.si/how-it-works
- https://sourcex.si/insights/who-sees-your-data-during-a-licensing-process
- https://refer.sourcex.si/how-it-works
- https://refer.sourcex.si/tools/data-inventory-builder
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://www.ftc.gov/business-guidance/resources/start-security-guide-business
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/investors
