The mistake this page catches is the observed number that measures the wrong thing: a payroll count, a founding year or a storage figure, each real, easy to get and close to what SourceX screens for, and none of them the screening quantity itself.
Observed means the right quantity, not just a real number
Take headcount. In the U.S., an employer's quarterly Form 941 asks on line 1 for the "Number of employees who received wages, tips, or other compensation for the pay period," and the instructions tie that to the pay period including March 12, June 12, September 12 or December 12, depending on the quarter. A CFO can read the figure off a filed return in a minute. It is observed.
SourceX's check is different: 50 or more full-time employees at the company's peak, contractors excluded. Line 1 counts employees paid in one pay period, and nothing in its wording separates full-time from part-time staff. So "63 on payroll in the pay period including September 12, 2023" is an observation about payroll and an estimate about the fit fact. The same gap opens for any payroll headcount that does not split out full-time staff.
The fix is not to distrust the number. It is to say what it measures, and then either label the fit fact as an estimate built from it or ask the CFO for the full-time count itself.
The minimum context, gathered from the company
Before labeling anything, collect a short set of facts from the CEO or a person the CEO names: the operating entity, its country and the main language of its records, full-time headcount at peak and the year, the record types and the systems that hold them with their start years, who owns the records, known constraints and any earlier contact with SourceX. That is metadata; none of it needs a file, and no documents travel with an introduction.
A portfolio operations analyst often holds better numbers already, from board packs or monitoring reports. Those are observations by the fund, not statements by the company, and they stay out unless the CEO restates them. The layout of the finished page is in the one-page brief a founder can approve; this page is about the label on each number.
The estimate-versus-observed field guide
Seven numbers a founder brief tends to carry, each with what the check asks, the figure that usually stands in for it, when the right figure counts as observed and an Illustrative label for when it does not.
| Fit number | What the check asks | Observed figure that passes for it | Counts as observed when | Label when it does not (Illustrative) |
|---|---|---|---|---|
| Full-time staff at peak | Full-time employees at the company's peak, contractors excluded | Payroll headcount for one pay period, such as Form 941 line 1 | The CFO or HR lead reads the full-time count for the peak year from payroll | "55 to 60 full-time at the 2023 peak: 63 on payroll less part-time staff; assumes about 5 part-time; CFO, 20 Oct 2026" |
| Operating history | Years of the company's own records that survive | Founding or incorporation year | An administrator reads the date of the earliest surviving record in each system | "Records from about 2014: founded 2006, ERP replaced in 2014, older data not confirmed migrated; operations manager, 20 Oct 2026" |
| Record volume | Records of each type, per system | Storage size, or the newest ticket number | An administrator runs a count report and dates it | "4 TB on the file server, per the IT provider; record count not known" |
| English share | Share of the data in English, where location makes it a test | Headquarters country or website language | Never fully: a sample is observed, the share it implies is not | "About 95% English in the ticket system: support lead's sample of 200 tickets, 21 Oct 2026; other systems not sampled" |
| Own versus client material | How much the company created itself | "We wrote all of it" | Rarely before review | "Company view: staff-written work orders; some specifications come from customers; SourceX's rights review decides" |
| Earlier contact with SourceX | Any application, relationship, lead, account or email correspondence | The CEO's memory | Never from the company side alone | "None known to the CEO as of 20 Oct 2026; SourceX checks its own records" |
| Value, payout or reward | Nothing: it does not belong in a brief | A calculator or portal figure | Not before payment | Leave it out |
Three rows need a word more.
English share. Location is a fact, not an estimate. 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. Where the language test applies, a company's sample is the best a brief can carry, so say how big it was and which systems it covered.
Earlier contact. The terms treat any earlier application, relationship, lead, account or email correspondence with SourceX as making a company a duplicate. A CEO cannot see every email a colleague ever sent, so the honest label is always "as far as the CEO knows."
Money. The program terms say estimates in the portal or calculator are projections, not promises, and that indicative ranges and unpaid supplier amounts are not Actual Supplier Payout. A value or reward figure in a founder brief is a projection dressed as a fact; estimated versus payable referral commission shows the difference.
One naming collision to avoid: for some companies, estimates are the records. A contractor's takeoffs and bid estimates can be the licensable material, as construction estimating records explains. The labels here apply to your estimates about a company, never to the estimates it produces as its work.
A label has five parts
Auditors have a working anatomy for estimates. The PCAOB's standard on auditing accounting estimates treats an estimate as a measurement that generally involves subjective assumptions and measurement uncertainty, and has the auditor test the methods, data and significant assumptions behind it. A referral brief needs a fraction of that rigor, but those three nouns become the middle of a label: the method, with the inputs it used, and the assumption. Put the range in front and who and when behind, and every estimate fits one line of five parts:
[range] [unit]: [method] from [inputs]; assumes [the one assumption that moves it most]; [who], [date].
| Weak line | Why it misleads | Labeled line (Illustrative) |
|---|---|---|
| "About 60 employees" | Payroll or full-time? Now or at peak? | "55 to 60 full-time at the 2023 peak: 63 on payroll less part-time staff; assumes about 5 part-time; CFO, 20 Oct 2026" |
| "Records go back 20 years" | A founding year presented as archive depth | "Founded 2006; ERP records from 2014; earlier records not confirmed; operations manager, 20 Oct 2026" |
| "At least 300,000 work orders" | "At least" claims a floor nobody counted | "250,000 to 350,000 work orders: about 100 per working day, 250 days a year, 12 years; assumes steady volume; service director, 20 Oct 2026" |
| "Mostly English" | An adjective with no basis | "About 95% English in the ticket system: sample of 200 tickets; other systems not sampled; support lead, 21 Oct 2026" |
The third row shows its arithmetic so a reader can fix an input instead of distrusting the line: 100 × 250 × 12 is 300,000, and the range allows for the daily rate being off by about a sixth either way.
Five working rules keep labels honest:
- Round to the method. An estimate built from a per-day rate never carries more than two significant figures.
- Ranges stay ranges. Copying a midpoint into the next document deletes the uncertainty.
- "At least" needs an observed floor. Without a count behind it, write a range.
- Name one assumption. The one that would move the number most, not every caveat you can think of.
- Upgrade a range that straddles a threshold. If headcount could be either side of 50 full-time at peak, ask for the full-time count before the introduction. If the range clears the threshold, it can travel as an estimate.
Upgrading is usually cheap: a payroll total, an earliest-record date or a count report takes someone at the company minutes and exports nothing. Ask for the figure, never for the document behind it. Volume has its own set of honest forms in when record volume is unknown.
Constraints and open questions take different labels
Not every uncertain line is an estimate. A constraint is a known limit, written as the company stated it: "two customer contracts restrict sharing of specifications." An open question names who can close it: the CEO, the company's counsel or SourceX in review. Neither gets a range, and neither should be softened into an estimate that might come out fine. The grid in recording what you do not know about a dataset gives every open line a status and an owner.
Handing over the labeled brief, and the first-call agenda
The CEO approves the labels as well as the numbers. "55 to 60 full-time" and "58 full-time" are different statements, and the CEO should see which one goes out under the company's name. The relationship owner then sends the approved page with a dated, written introduction. The person who submits signs the SourceX Channel Partner Agreement first; a partner who signed it under the old name, Channel Partner Non-Circumvention and Non-Disclosure Agreement, keeps the version they signed. Under the terms, credit attaches when the company files a verified application, and it goes to the earliest valid introduction made inside the 90-day attribution window.
A 30-minute first call can then run on the labels:
- Who decides (3 minutes): the CEO as authorizer, and the company contact the CEO named.
- The estimates (10 minutes): which ones SourceX needs upgraded, and who at the company can read each figure.
- Constraints and open questions (10 minutes): taken in order of owner, counsel's questions last.
- What review covers (5 minutes): fit, rights and relevance, which SourceX checks itself.
- Next step and date (2 minutes).
No records, samples or screens are shared on the call.
Where the field guide can mislead
- Observed figures fail too. A count report can include test or voided records; a sample can be unrepresentative. "Observed" means someone read it from a source, not that it is right.
- Labels do not establish fit. A perfectly labeled brief for a company whose records belong to its clients is still a poor fit, and SourceX applies each program's own criteria, so a no from one program says nothing final about the next.
- Too many caveats. A label that runs to a paragraph hides the number. Keep each to one line and move the rest to the open-question list.
- The fund's own knowledge. The analyst may know the label is wrong from board materials. The remedy is a word with the CEO, not a quiet edit.
- Effect not measured. Whether labeled briefs move through review faster or more often succeed has not been measured, and SourceX has not published figures. A platform team can test it: for each brief, record the number of estimates, how many review asked to upgrade, and how many turned out outside their stated range.
Methods note. The field guide is built from SourceX's published screening profile and program terms (version 2026-10-22.2, since replaced by version 2026-11-04), the wording of Form 941 line 1 and its instructions, and the PCAOB's standard on auditing accounting estimates, all checked on 2026-10-27. All example labels are Illustrative. It does not measure review outcomes, demand for any company's records or record quality, which only SourceX's review assesses.
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 every number on the founder's brief carries its label and the CEO has approved both, open a partner account through registration, hold the confirmed facts up against who qualifies and read the program terms before the brief goes out. More portfolio guides are in the guides hub.
Labeling a founder's brief is referral work; deciding whether SourceX itself merits an investment is a separate exercise, and investor materials can be requested 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.