This is for a global platform manager preparing a quarterly note for partners, an LP update or an internal review of regional offices. The temptation is a single line, "our network introduced 26 companies and 6 applied", followed by a league table of offices. Both mislead, for reasons that are arithmetic rather than opinion.
What a platform can report, and what belongs to SourceX
The platform owns its own activity and nothing beyond it. Everything in the left column comes from your dated records or from your partners' dashboards; nothing in the right column is yours to publish.
| You may report | You may not report |
|---|---|
| Companies your partners considered, and why some were screened out | SourceX's acceptance or approval rates |
| CEOs asked, and CEOs who agreed, with dates | Whether SourceX wants a sector or a country |
| Introductions submitted after the CEO agreed | Another partner's or another network's results |
| Stages your partners see on their own dashboards | Payout or reward amounts, in anything shared beyond the team |
| Cases SourceX treated as duplicates, as a count | SourceX's reasons for a decision, unless SourceX gave them to you to share |
SourceX's own research guide sets the tone: "No outcomes, averages, or earnings figures appear until such evidence exists." It also warns against generalizing from a single referral. A platform report inherits both rules. The dashboard's statuses (Estimated, Eligible, Approved, Paid) are listed on SourceX's how-it-works page and explained in the referral status glossary; "Paid" appears only after an actual payout has been recorded, so it is the only stage a report should treat as a completed outcome.
Why one global number misleads
Offices do not work the same population. They differ in when they started asking, in the kind of relationships they hold and in where their companies are. SourceX's geography rule is one sentence, quoted here as published:
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.
The language condition attached to the second list is explained in SourceX's English-language guide. An office whose companies mostly sit in that second list may screen more of them out before asking, and rightly so; a report that ignores this compares unlike work.
Pooling can do worse than blur. The Stanford Encyclopedia of Philosophy's entry on Simpson's paradox describes how an association can reverse when a population is split into groups, and how associations inside every group can reverse when the groups are pooled (paraphrase). Its own example is international: early Covid-19 data showed a higher overall fatality rate in Italy than in China, while China's rate was higher within every age group. A referral report pooled across offices of different ages can flip the same way, as the Illustrative report below shows.
The region-context results comparison
One row per office. Context columns come first, so nobody reads a count without its circumstances.
| Column | What goes in it | Rule |
|---|---|---|
| Office | The office whose partner asked the CEO | Each company counted once, under the office that asked |
| Company locations | How many companies fall under each part of the published sentence | Quote the sentence's wording; never score a country |
| Cohort window | First and last ask dates, and the report's cutoff date | Same cutoff for every row |
| Past 90 days | Asks made at least 90 days before the cutoff | Shown as a count beside total asks |
| Considered and screened out | Companies looked at but not asked, with the reason | A screen-out is diligence, not failure |
| Asked, agreed, submitted | Three counts in order | Submitted only after the CEO agreed |
| Verified applications | From partners' dashboards | No estimates |
| Open, closed, paid | Current stage of each verified application | "Paid" only from the dashboard status |
| Contested | Companies another office or partner also claims | Kept out of every row until SourceX's records settle it |
Four reporting rules apply to the whole table. Below 20 asks in a row, print counts and never a percentage. Never add a total row across offices with different cohort windows. Never rank offices on these numbers. And end every row with a dated next step or a dated no-fit outcome, so the report records decisions as well as counts.
Method note. The comparison uses the who-qualifies page, the program terms (version 2026-10-22.2, since replaced by version 2026-11-04) and the how-it-works page, read on 2026-10-27, together with the platform's own dated records. It measures the platform's activity and the stages its partners can see. It does not measure SourceX's decisions, demand, record quality or any money, and it cannot explain why a case is open. A related design that splits cohorts by the criteria in force on the day of each introduction is in a cohort report across criteria versions.
A three-office report with its unknowns kept (Illustrative)
Illustrative. Invented offices, invented counts and a cutoff of 15 October 2026; none of it describes SourceX's results.
| Office | Company locations | Cohort window | Past 90 days | Screened out | Asked | Agreed and submitted | Verified applications | Open | Closed | Paid |
|---|---|---|---|---|---|---|---|---|---|---|
| New York | 12 under "the U.S., Canada and the EU" | Jan to Jun 2026 | 12 of 12 | 3, below the size test | 12 | 5 | 3 | 2 | 1, a duplicate per SourceX | 0 |
| London | 4 under "the EU"; 3 in the UK, on the English-condition list | Mar to Aug 2026 | 5 of 7 | 2, records belonged to clients | 7 | 4 | 2 | 2 | 0 | 0 |
| Singapore | 7 on the English-condition list; 1 location the sentence does not name, routed to SourceX unasked | Jun to Sep 2026 | 2 of 7 | 2, the company's stated language mix | 7 | 3 | 1 | 1 | 0 | 0 |
The tempting summary: 6 verified applications from 26 asks, with Singapore last on 1 of 7.
What the context says: Singapore's asks are the youngest, and only 2 of its 7 have run their full 90 days. All six applications came from asks past 90 days, so count only those older asks and the order flips: New York has 3 applications from 12, London 2 from 5 and Singapore 1 from 2. Neither ordering means anything at these sizes, and that is the finding to report. The fair line for the quarter reads: "Three offices asked 26 CEOs; 12 agreed; 6 companies applied; 5 are with SourceX; none has reached Paid. Singapore's cohort started five months after New York's, and most of its companies fall under the English-language condition."
Still unknown at the cutoff: why the five open cases are open, whether the Singapore company routed unasked fits any program, and how many of the London and Singapore asks will reach an application once their 90 days run out.
Questions that leave the report
- A partner's local professional rules or tax on a reward. That partner's own adviser.
- Company-side legal questions about records crossing borders. The company's advisers.
- Fit, duplicates and credit. SourceX, from its dated records; the terms say only one partner is credited per company.
- Whether a country "works". Nobody in the platform: SourceX publishes one sentence, and a report that grades countries invents rules SourceX has not published. Cross-border screening before an ask is covered in checking language coverage before suggesting global fit.
Where an office-by-office report can still mislead
- Small numbers. With a dozen asks per office, one company moves any share a long way. Counts are the honest unit until rows reach 20 or more.
- Who draws the regions. Grouping by office, by company country or by relationship type gives different pictures. State the grouping and keep it from quarter to quarter.
- Criteria change. SourceX's who-qualifies page says criteria follow each program and can move; a cohort introduced under one version is not directly comparable with the next.
- Stage lag. Dashboards show where a case stands, not why. An open case can be weeks from a decision or months.
- Selection. Offices that log carefully look busier than offices that do not. Audit the logging before comparing the activity.
- Your rows are not the program's. The partner results research guide explains which results SourceX itself will cite; a platform's counts never stand in for them.
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.
Before an office's next ask, the partner making it should register, check the company against who qualifies on that day and work from the current program terms, so next quarter's row starts from clean, dated records. More guides for platform teams are in the guides library.
An office-by-office referral report is a program document, not an assessment of SourceX as a business; anyone weighing an investment in SourceX can request 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.