This page is for the investor-side reader, often someone liaising between a fund's partners and its general counsel, who wants SourceX's view of a situation before any company has agreed to be named. It does not cover a founder who wants to talk to SourceX anonymously; that is the founder's own choice, made with SourceX directly.
When an unnamed question is the right tool
A hypothetical earns its place in three situations: you want to know whether raising SourceX with a CEO is worth that CEO's time; you need a program rule the published pages do not settle; or the company has asked you to keep its interest private while it thinks. It is the wrong tool in four others.
- The answer is already published. Who-qualifies settles more than people expect: a staffing firm counts only its own full-time staff, a parent and its subsidiaries are one company for the reward cap, and once a company enters a formal insolvency process its CEO alone may not be enough to say yes.
- You want a fit decision. The who-qualifies page describes itself as screening guidance, not a promise that any company is eligible, and SourceX checks relevance to its current programs when it reviews a real application.
- The facts came from a board or advisory seat. Board-sourced knowledge may prompt one question to that company's own CEO. It never travels anywhere else, and taking the name off does not change where it came from.
- You want to know whether SourceX already knows the company. Section 3 of the terms has SourceX check its own records before inviting a company that was introduced; with no name there is nothing to check, and section 7 says partners never receive access to other partners' records.
| Your question | Answerable without a name? | Where the answer lives |
|---|---|---|
| How are placed workers at a staffing firm counted? | Yes, already published | Who-qualifies |
| Who decides for a company in a formal insolvency process? | Yes, already published | Who-qualifies |
| Do a parent and its subsidiaries share one reward cap? | Yes, already published | Who-qualifies |
| Would records of this kind interest current programs? | Only in general terms | A message to SourceX; review decides |
| Is this company already known to SourceX? | No | Only after a named introduction |
| What would this company be paid? | No | An indicative range from the company's own inventory, later |
| Does this company fit? | No | SourceX's review of the company's own application |
The payment row follows SourceX's how-it-works page, which says SourceX proposes an indicative range from the company's inventory and that pricing stays indicative until a Dataset Deal Confirmation is signed. No one can price a company described in four lines.
The hypothetical inquiry template
Each field has a form that helps SourceX answer and a form that identifies the company. Use the left one.
| Field | Write it as | Never write |
|---|---|---|
| Who is asking | "A partner at a venture fund", "an independent advisor" | How you know the company ("I sit on their board") |
| What you read first | The published page and the terms version, 2026-10-22.2 | Nothing; skipping this invites an answer you already had |
| The question | One question about a program rule or how a situation is handled | "What do you think of them?" |
| Size | "Above 50 full-time at peak", "near the threshold", "unknown" | An exact headcount |
| History | "Roughly ten years of its own records" | A founding year or exact dates |
| Records | A category SourceX itself uses, such as support tickets or project histories | Named system instances, volumes read off a file, sample contents |
| Ownership | "Founder-led", "PE-owned platform with add-ons", "in a formal process" | Investor, acquirer or deal names and dates |
| Location | The region, at the level of the who-qualifies list | A city, or a state that leaves a handful of candidates |
| Sector | A broad category | A niche label that leaves five possible companies |
| What you are not doing | "I am not introducing anyone or sharing company information" | A hint that an introduction will follow |
A finished question, Illustrative:
I'm a partner at a venture fund and have read your who-qualifies page and the program terms, version 2026-10-22.2, since replaced by version 2026-11-04. A hypothetical, not a named company: a founder-led field-service business above 50 full-time employees at peak, with roughly ten years of its own work orders and technician notes. In general terms, is that record type relevant to current programs, or is it too early to say without an application? I am not introducing anyone and not sharing any company's information.
The identifiability test: coarsen until nobody could guess
A description can name a company without its name. NIST's report on de-identifying personal information, NISTIR 8053, gives re-identification attacks and quasi-identifiers sections of their own, apart from the removal of direct identifiers (paraphrase of the search excerpt). The report is about people, not companies, and the step from one to the other is ours: details that are harmless one at a time can point to a single company together. "The only cold-chain logistics firm in a mid-size port city, sold this spring" is a name in all but spelling.
Run three tests before sending:
- The competitor test. Could a competitor, customer or trade journalist list fewer than ten candidates from your description? If so, move every detail one rung up the ladder below.
- The source test. Did any detail come from somewhere other than public information or the CEO's own words for this purpose: a board pack, an information-rights report, a data room, an investment memo, a file someone sent you? Remove it, however coarse.
- The CEO test. Would the company's CEO be comfortable reading the question over your shoulder? If not, do not send it.
| Exact detail | One rung up | Program level |
|---|---|---|
| 212 full-time employees | 200 to 250 | Above 50 at peak |
| A named port city | A state or province | A region on the who-qualifies list |
| A named field-service product since 2016 | A field-service system, about nine years | Work orders, several years |
| "Sold to a strategic buyer in March" | Recently acquired | Ownership changed |
| "In an assignment for the benefit of creditors" | In a formal process | In a formal process (keep it: it changes who decides) |
What comes back, and what an unnamed question cannot do
An answer to a hypothetical is information about the program. It is not a fit decision, a reservation or a promise.
- No credit. Section 2 of the terms decides credit from dated records, including written introduction evidence, for the first valid introduction of a new company. The sample Channel Partner Agreement defines an Introduced Contact in section 1.2 as an identified prospective supplier, recorded in writing. An unnamed company is neither identified nor introduced.
- No protection. Section 5.2 of the sample agreement protects only contacts and opportunities recorded during the agreement's term. If another partner introduces the same company with its CEO's yes, your earlier hypothetical gives you no standing; overlapping claims go to SourceX's duplicate review, decided on dated records.
- No fit decision. Programs change, and who-qualifies says a screen is valid only on the date it was made.
- No commitment. A general reply cannot commit SourceX to anything; offers come only through the company's own application and SourceX's process.
Use a published channel. The referral site's contact page sends introductions through the partner dashboard or link and says that for anything else you should contact SourceX via sourcex.si. Whatever channel you choose, a form, an email or a chat assistant, treat it as writing to SourceX, and apply the template there too. SourceX's own trust center asks people reporting a security concern not to include "passwords, personal information or confidential customer records"; the same restraint suits any question.
Information-flow map: what goes in, what stays home
| Information | Goes into the question? | Who holds it afterward |
|---|---|---|
| Published criteria and terms wording | Yes, cited by page and version | Everyone; it is public |
| Public facts, or category-level facts the CEO gave you for this purpose | Yes, coarsened to program level | You and SourceX |
| The company's name, domain and people | No | You, until the CEO agrees to be named |
| Facts from board packs, information rights, data rooms or investment memos | Never, even coarsened | Where they came from |
| Anything from files someone sent you | Never | Your counsel's decision |
| SourceX's reply | Not applicable | You; never republished as a ruling |
Escalation, withdrawal and publication are three separate steps
Escalation turns the hypothetical into something real, and only the CEO can do that. Share the general answer with the CEO if it helps, and ask whether they want a conversation. If they do, the partner registers and signs the SourceX Channel Partner Agreement before submitting the introduction, and the company applies itself, deciding what it tells SourceX.
Withdrawal ends the thread. If the CEO says no, send no follow-up to SourceX with more detail "for next time"; record the no and its date.
Publication stays off the table. A reply to a hypothetical is not something to quote in a newsletter or on a partner page as "SourceX confirmed companies like ours fit". It was a general answer about an invented case. For research that describes companies in aggregate, publishing network research without exposing companies sets the rules, and when the person you would approach is a privacy officer, the conversation with a privacy officer covers that meeting.
Where an unnamed question can mislead
- False comfort. "That sounds relevant" is easily read as approval. Repeat to yourself and to the CEO that review decides.
- Leakage by combination. Each detail passes alone, and together they identify. Run the competitor test on the whole question, not each line.
- Laundered board knowledge. A coarsened board fact is still a board fact. The source test exists for this.
- Stale answers. A reply from last quarter describes last quarter's programs.
- Nothing reserved. A hypothetical holds no place in line. If another partner introduces the company first with its CEO's agreement, credit follows that dated record.
Methods note. The template and the three tests were built from SourceX's who-qualifies, terms (Version 2026-10-22.2, since replaced by version 2026-11-04), contact, how-it-works and trust pages, the unsigned sample Channel Partner Agreement and the NIST report cited below, all checked on 2026-10-28. They have not been tested on real inquiries, and no figures on how SourceX answers hypothetical questions have been published. Nothing here is legal advice about your confidentiality obligations; your own counsel, or the company's, decides those.
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 general answer is in hand and the CEO wants to be named, register for a partner link, suggest the CEO try the company fit checker against who qualifies, and read the program terms before the introduction goes in. Other boundary questions sit in the guides hub.
A question about how the program treats a hypothetical company is referral work; a question about SourceX as an investment is separate, and readers weighing that can ask for investor materials 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.