Funding status never establishes eligibility, and in an early-stage network that cuts both ways. Most of the companies you know best may fail the size test today, while the few that pass may sit outside the portfolio altogether.
Why a short eligible list changes what a pilot can learn
A comparison needs two groups large enough to differ for a reason other than chance, and nine companies cannot supply that however you split them. NCCIH's guidance on pilot studies, paraphrased from its own page, says pilot work exists to test whether an approach is feasible and acceptable before a larger study, not to test whether it works, and it lists estimating preliminary efficacy or an effect size among the common misuses of small pilots.
A referral pilot in a thin network inherits that limit. It can show how the work goes, what each ask costs and where it breaks, but not how many introductions the network "converts", and SourceX publishes no conversion rates against which to check one.
| Term | Meaning on this page |
|---|---|
| Frame | Every company for which someone in your network can name the person who would ask its CEO |
| Eligible pool | Companies in the frame that pass every published fit fact you can establish before asking anyone |
| Census pilot | A pilot in which every company in the pool is handled once, under one protocol, and reported as its own case |
| Feasibility question | A question about the process that a zero-transaction result can still answer |
Step zero: the desk count that decides whether to pilot at all
The small-network feasibility test starts at a desk, with no outreach. For each company in the frame, mark each fit fact pass, unknown or fail from public sources and from what the relationship owner already knows. Files, samples, logins and anything copied from board material stay out of the count.
| Fit fact | What you can establish before asking | Default mark |
|---|---|---|
| Full-time headcount of 50 or more at its peak, contractors left out | Public team pages and the relationship owner's knowledge; a team page that mixes contractors with staff is a reason to mark unknown | Unknown until confirmed |
| Years of the company's own records | Founding year from a registry or the company's site; when its own systems started is rarely visible | Unknown until confirmed |
| Rights to license those records | Almost never knowable from outside; settled only in SourceX's review | Unknown |
| A CEO who would want the conversation | The relationship owner's judgment, recorded as such | The owner's view |
| Location and language of the records | Where the company operates and the language it works in, read against the published sentence below | Pass or fail |
On geography, SourceX's who-qualifies page gives one sentence: Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Add no country rule of your own.
Rights stay unknown for every company, so the pool means "passes everything you can know so far". Unknown rows on the other facts are questions for their relationship owners, and they join the pool only once answered. Then read the pool size against three bands you write down before counting.
| Pool after the desk count | What to run | The reasoning |
|---|---|---|
| 0 to 2 | No pilot; a dated revisit list naming the trigger that would change each company | Two cases describe two CEOs, not a network, and each ask still spends a relationship |
| 3 to 15 | A census pilot: every company, one protocol, a case-by-case report | Enough cases to see whether the process works; far too few to split |
| 16 or more | A comparison may become thinkable, on outcomes frequent enough to count, as in comparing two outreach angles | Splitting only makes sense when each half still holds enough companies to see anything at all |
The cut points are design settings, not statistics; move them if you like, but before the count.
One protocol for every company, and no variant to test
In a census pilot every CEO hears the same truthful core, delivered by the person who holds the relationship: what SourceX does, that the company's CEO decides, whether anyone in your network could be paid if a license follows and who would pay it, that the company applies itself, and that a single no ends the subject.
The variant a small network is most tempted by is never a variant. A warmer version that says the fund recommends SourceX, or that the company "qualifies", is a breach of the protocol, because only SourceX's review decides fit and the fund endorses nothing. If you want to study wording, wait until the pool supports a comparison.
You may record who made each ask (a board member, an LP, a portfolio founder who supplies the company) without testing it. With nine rows, a pattern by asker is a hunch, not a finding.
The small-network feasibility test, question by question
Six questions make up the test. Each threshold below is an example setting; write your own into the pilot plan, with its date, before the first ask.
| Feasibility question | Count | Denominator | Feasible if (example setting) | A miss means |
|---|---|---|---|---|
| 1. Did the desk count hold? | Companies whose fit facts, as their CEO states them, still pass | CEOs who stated their facts | At least two in three | Desk screening needs a better source before any wider launch |
| 2. Will relationship owners ask? | Owners who agreed to ask | Companies in the pool | At least half | The pool exists on paper only |
| 3. How did CEOs respond? | Agreed to hear, declined, no reply by day 30, each listed | Asks made | No bar; reported in full | Nothing by itself; it describes the network |
| 4. Could founders say no freely? | CEOs answering yes to the freedom question | CEOs who answered it | Every one | One no or unsure triggers the stop review |
| 5. Did the protocol hold? | Breaches: a record offered or requested, a CEO not told first, fit or endorsement implied | Asks made | Zero | Stop and fix before another ask |
| 6. What did it cost? | Platform and relationship-owner hours per company | Companies asked | Inside the range set beforehand | A budget lesson, recorded beside the rest |
Question 4 is the one a venture network cannot skip. A founder asked by an investor may feel a no carries a cost. After each conversation, someone outside the deal team asks one optional question (Illustrative wording): "Did you feel free to say no to this without it affecting your relationship with the fund?" Answers are yes, no or unsure, and none is challenged.
Progress is reported and never judged: verified applications, the stage words your dashboard shows, and companies closed as duplicates because SourceX already knew them. Credit needs the company's own verified application inside the 90-day window, which no pilot can produce for anyone.
Stop rules and the decision date
- Breach stop: any protocol breach pauses every ask until the cause is found and fixed.
- Pressure stop: a no or unsure on the freedom question pauses asks by that asker and triggers a review of how the ask was made.
- Owner withdrawal: a relationship owner who changes their mind ends that row, with no route around them.
- Program change: SourceX's programs set their own criteria and can change; if the published fit facts move mid-pilot, pause and recount.
- Exhaustion: when every company in the pool has been asked once, outreach ends. Nobody is asked twice to fill a gap.
Fix the review date at day 120 after the last ask, so every introduction has passed its 90-day window. The review picks one of three outcomes.
| What the test showed | Decision | What it never justifies |
|---|---|---|
| Questions 1, 2, 4 and 5 met, whatever the application count | Keep the protocol as standing practice and re-run the desk count when a trigger fires | Announcing that the network's companies qualify |
| Question 1 or 2 missed, protocol held | Redesign the desk count or the frame, then recount | Asking the same CEOs again |
| Question 4 or 5 missed | Stop, fix the cause, and decide afresh whether to continue | Treating any application that followed as a success |
Nine companies, one protocol (Illustrative)
Illustrative. A seed fund's network, invented counts, no real companies or outcomes.
| Stage | Count | What the platform lead recorded |
|---|---|---|
| Frame | 64 companies | Each with a named relationship owner |
| Fail a known fact | 47 | Mostly below the size test at peak; dated, with the trigger that would change each |
| Unknown | 8 | Sent to their owners as questions, not asks |
| Eligible pool | 9 | Census band |
| Owners who agreed to ask | 6 of 9 | Question 2 met |
| CEOs asked | 6 | 3 agreed to hear, 2 declined, 1 no reply by day 30 |
| CEO-stated facts still passing | 4 of 5 | One team page had counted 70 people; the CEO said 38 were full-time |
| Freedom question | 4 yes, 1 unsure, of 5 answers | The unsure followed an ask made in a board meeting week |
| Breaches | 0 | Question 5 met |
| Verified applications | 1 | Dashboard stage words copied with the date read; no transaction |
The review kept the protocol with two fixes: the desk count now separates contractors, and no board member asks during a board week. The eight unknowns went back to their owners, and the single application was reported as one case, not a one-in-six rate. For companies the next count should look at, start with finding mature businesses near an early-stage portfolio and the five-ring relationship map.
What a thin-network pilot cannot tell you
- Rates and forecasts. With a pool this small, any percentage is an anecdote with a decimal point. SourceX publishes no conversion rates, and demand for a company's records is assessed only in its review.
- Message quality. One protocol means no comparison. A later, larger pool is where wording can be tested.
- Privacy in the report. In a nine-company pilot, even a count can point to one founder. Keep case notes to dates, stages and the founder's own words, and share them only inside the platform team.
- Selection. Relationship owners who agree to ask may be the warmest ones, so question 2 flatters the network if read as typical.
- Moving criteria and rights. Each program applies its own criteria, and a company that misses one may fit another later, so a pass or fail is valid on its date only; rights stay unknown throughout.
Method note. The test uses only SourceX's published fit facts and terms, both checked 2026-10-28, and NCCIH's framing of feasibility work. It counts cases, not rates, and leaves out demand, record quality and any payout. Related designs: the ten-company selection matrix, a pilot budget with reward income at zero, the five-member association pilot and, for the review once the pilot closes, what to do when a pilot has no completed transactions.
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.
If your desk count lands in the census band, register as a partner, recheck each pool company against who qualifies and read the program terms before the first relationship owner asks; whoever submits must have signed the Channel Partner Agreement first, and more designs sit in the guides hub.
Testing whether your network can make good introductions is referral work; deciding whether SourceX is worth investing in is a separate question, for which the SourceX investor overview takes requests for investor materials.
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.