What to measure in a cross-fund referral pilot: a cohort plan that counts each company once, tracks collisions, founder touches and CEO answers to day 90, and leaves rewards to a read the pilot cannot make

Short answer

Measure what coordination changes, on a cohort of companies frozen on day 0 and counted once however many funds know them: how often two funds prepared the same ask, how long it took to agree on one introducer, how many investor messages each CEO received, how many CEOs said yes and how many guardrails broke. Read those at day 30 and day 90. Leave rewards out. They depend on acceptance, handoff and payment months after any pilot ends, and estimating them would put a guess at the top of the report.

Visual briefFull-size diagram
An Illustrative cohort waterfall for a four-fund pilot: 52 candidate rows narrow to 46 distinct companies, 27 with fit facts known, 18 with the owner agreed, 16 CEOs asked, 7 yes and 6 introductions submitted, with applications read later; a side panel notes 6 collisions resolved in a median of 3 days and 1 CEO who heard twice.
Illustrative counts for an invented four-fund pilot. They show the plan's stages and are not SourceX data.

The reader here is an ecosystem lead coordinating three to five funds, or several investing teams inside one firm, that share some portfolio companies and want to try SourceX introductions together before anyone commits to a standing arrangement.

Why a pilot across funds needs measures of its own

A single fund can count its own introductions and be roughly right. Pool four funds and the same count goes wrong in a specific way: a company two funds both know appears twice, and the overlap looks like extra output when the program will credit that company once. Section 2 of SourceX's terms credits one partner per company, the first valid introduction inside the 90-day window, and only once the company has submitted a verified application. So the unit of the pooled report is the company, never the fund and never the introduction.

The second trap is definitions. Each fund arrives with its own idea of what "qualified" or "converted" means, and the numbers only add if the words match. Microsoft's Partner Center shows how easily one label hides two formulas: its referrals insights page defines the co-sell win rate as won divided by accepted plus outbound, times 100, while the leads win rate divides won by accepted alone. A cross-fund pilot that does not fix its formulas on day 0 will produce a pooled rate nobody can interpret.

Day 0: the roster, the chain and the point of permission

Before any company is contacted, the pilot fixes three things in writing.

  1. The roster. Each fund lists the companies it would consider, privately, and reports only the number of rows to the pool. The coordinator never receives a full list.
  2. The chain. When two funds discover they share a company, through the overlap process the funds agreed, each records it as a collision and names the relationships involved: board seat, observer seat, information rights, personal tie.
  3. The point of permission. A company moves past "candidate" only through its agreed introducer asking its CEO, who under the program authorizes a licensing discussion. Once a company has been acquired, the acquirer's CEO decides for it; before closing, the target's CEO still does.

Report rows and companies separately at the candidate stage. They converge as collisions are resolved, and the gap between them is itself a finding.

The cross-fund cohort measurement plan

Twelve measures, each with its formula fixed on day 0. A measure with no stated denominator does not go in the report.

#MeasureFormulaRecorded byFirst readReported to the pool as
1Candidate rowsRows on all funds' day-0 listsEach fundDay 0A count
2Distinct companiesRows minus rows found to be the same companyCoordinator, from collision reportsDay 30A count
3CollisionsCompanies with two or more funds preparing an ask, over distinct companiesFunds involvedDay 30Count and denominator
4Days to one introducerDays from a collision found to a signed introducer noteFunds involvedDay 30Every value, plus the median
5Fit facts knownCompanies with all four fit facts confirmed, over distinct companiesIntroducerDay 30Count and denominator
6Owner agreedRelationship owner has agreed to ask, over companies with fit facts knownIntroducerDay 30Count and denominator
7CEO answersYes, no, not now and no reply, over CEOs askedIntroducerDay 90Four counts
8Investor touches per CEOMessages about SourceX the CEO recalls from any pilot fund, asked once at the endIntroducerDay 90How many CEOs heard once, twice or more
9Introductions submittedOne per company, by its introducerIntroducerDay 90A count
10Verified applicationsApplications verified within the window, over introductions submittedIntroducer, its own referrals90 days after the last introductionCount and denominator
11DuplicatesIntroductions treated as duplicates, over introductions submittedIntroducer, its own referralsSame as 10Count and denominator
12Guardrail breachesRecords, files, samples or logins offered or passed; confidential facts reused; asks after a stand-downEvery fundEvery readCount, each with a one-line note; the target is zero

Four things stay off the plan on purpose: rewards, payouts, deal values and anyone's guess at SourceX's demand. The first three cannot exist inside the pilot window, and the fourth is known only to SourceX's review.

The fit facts in measure 5 are the published ones a fund can check before anyone asks the CEO: a full-time headcount that reached 50 at its peak with contractors excluded, years of records the company made itself, rights to license them and a location that meets SourceX's geography rule. The CEO's own wish to talk is counted separately, in measure 7. Funding plays no part, so a fund's newest companies are not more likely to pass.

Method note. The measures follow SourceX's program terms (version 2026-10-22.2, since replaced by version 2026-11-04) and screening page, read on 2026-10-27, with Microsoft's published win-rate formulas as the example of why definitions must be fixed. The plan measures coordination and permission. It does not measure demand for any company's records, record quality or payouts; SourceX has not published conversion figures, and the plan assumes none.

One introducer per company, one coordinator for the pilot

Every company has exactly one introducer, agreed in writing before its CEO hears anything. That person signs the SourceX Channel Partner Agreement before submitting, asks the CEO, submits one introduction and answers SourceX's questions about it. They never see, upload or handle the company's records, inventory or data room. The CEO, or a colleague the CEO names, is the company's single contact for the whole pilot.

The pilot also needs one coordinator, usually the ecosystem lead who proposed it. The coordinator owns the formulas, collects the counts at each read and writes the report. The coordinator holds no company names beyond those the funds chose to share while resolving a collision, and sees no SourceX status for any referral but their own fund's.

Status and compensation, settled before the first outreach

Status. The program keeps every partner away from other partners' records, so pooled outcomes exist only as the sum of what each introducer reports about its own referrals. Agree that each fund reports counts and generic stages, never a CEO's words without that CEO's consent, and never another fund's company.

Compensation. A pilot does not pool rewards, because the program does not. SourceX credits one partner per company and pays that partner the greater of $50,000 plus 5% and 15% of what it actually pays the company, with no cap, separately from the company's own payment: nothing for the partner comes off the compensation in the company's signed agreement. Some funds bar staff from accepting outside compensation, so each fund records its policy on day 0, and a fund that cannot accept a reward should not be assigned as an introducer by default; whether a partner can decline a reward is not covered by the terms, so ask SourceX before relying on it. Timing settles the rest: no reward is payable until SourceX has paid the company and the conditions in section 5 are met, and the 60-day payment clock starts only after the Acquisition Partner has accepted the finished dataset in writing and the handoff is done, whichever comes later. That is long after day 90.

A four-fund pilot at its day-90 read (Illustrative)

Illustrative. The funds, companies and counts are invented and are not SourceX data.

Four funds join: two early-stage venture funds, a growth fund and a search fund investor group. On day 0 they report 52 candidate rows.

MeasureDay-90 reading
Distinct companies46, after 6 companies were found on two lists each
Collisions6 of 46; all 6 resolved to one introducer
Days to one introducer1, 2, 2, 4, 5 and 9; median 3
Fit facts known27 of 46
Owner agreed18 of 27
CEO answers16 asked: 7 yes, 4 no, 3 not now, 2 no reply
Investor touches per CEO15 heard once; 1 heard twice, at the company whose collision took 9 days
Introductions submitted6, with one more CEO still scheduling
Verified applications and duplicatesNot yet readable; first read 90 days after the last introduction
Guardrail breaches1: a founder emailed a sample export, which the fund deleted unopened and logged

Read it as counts. With 16 CEOs asked, one answer moves the yes share by more than six points, so the report gives numerators and denominators, as the guide to reporting a small pilot recommends. The useful findings are operational: the slowest collision is the one that produced the only double touch, so the funds agree to a five-day limit for naming an introducer.

Where this plan can mislead

Our thesis: a pilot judged on coordination and permission tells funds more about whether to continue than one judged on outcomes it cannot yet see. That is untested; no cohort data from cross-fund pilots has been published.

  • The window. Credit needs a verified application inside 90 days of an introduction, and reward events come after acceptance and handoff. A pilot scored on rewards will look like a failure whatever happened.
  • Hidden duplicates. Section 3 of the terms lets SourceX treat a company it already knew as a duplicate, and only SourceX can see those records, so measure 11 can surprise everyone.
  • Partial visibility. Pooled outcomes are only as complete as each introducer's reporting, because no fund sees another fund's referrals.
  • Demand. SourceX's requirements move with its current data needs, so a well-coordinated cohort can still produce few accepted companies for reasons that have nothing to do with the funds.
  • Selection. Funds may list only their warmest companies; compare day-0 lists by fund before reading any rate.
  • Drift. Formulas that change mid-pilot break every comparison; the denominator check is a quick test before each read.

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.

Once the four funds have signed the day-0 plan and named an introducer for each shared company, each introducer can register for a partner link, screen every candidate against who qualifies and read sections 2, 3 and 7 of the program terms before the first CEO is asked. For a smaller start inside one fund, see choosing a ten-company pilot and the venture platform overview.

A fund that wants to measure SourceX as a company, rather than measure introductions to it, is running investment diligence, which is a separate exercise; the SourceX investor overview takes requests for 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.

  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

Why not report introductions per fund, as each fund already does?

Because a company several funds know would appear in several funds' counts while the program credits it once. Per-fund counts are fine inside each fund; the pooled report counts companies, with each company assigned to the one fund agreed as its introducer.

How long should a cross-fund pilot run?

Long enough for two reads: a coordination read at day 30 and a permission read at day 90, plus one application read 90 days after the last introduction, since credit depends on a verified application inside that window. Reward events arrive later still and are outside any pilot of this size.

Can the coordinator ask SourceX for the pooled outcomes?

The program keeps each partner away from other partners' records, so outcomes reach the pool only through each introducer reporting its own referrals. Plan the reports that way from day 0 rather than expecting a combined view.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. learn.microsoft.com/en-us/partner-center/insights/referral-insig…
  4. 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