Known, conditional and thesis are kept apart throughout. Program facts come from the published terms and the who-qualifies page. Anything about effort by size is a question until logged data answers it. This study can also run as an added outcome inside the cohort of the partner quality study, which already reports results by company profile; it adds workload, which that method does not measure.
Terms used in the workload-by-size study
| Term | Meaning here |
|---|---|
| Touch | One dated action by the partner about one introduction: a message, call, meeting, forwarded question or disclosure |
| Authorized yes | The CEO agrees to be introduced to SourceX |
| Size band | Peak full-time headcount band, contractors excluded |
| Screening failure | An introduction stopped because a published fit fact fails, before or after submission |
| Open case | An introduction with no final status at the cutoff; reported, never dropped |
Four questions the study is built to answer
Each is stated as a question because no data answers it yet.
- Do introductions to larger companies need more touches before an authorized yes? The thesis says yes, because a partner's contact at a 1,000-person company is less often the CEO.
- Do companies near the 50-employee line produce more screening failures per introduction? Peak full-time headcount is easy to misjudge when contractors and part-timers are mixed in, so the smallest band may carry the most wasted touches.
- Is it the number of people between the partner and the CEO, rather than headcount itself, that drives touches? If so, size is only a proxy, and the study should say so plainly.
- Does elapsed time to a verified application grow with size even where touches do not? Large companies may need fewer partner actions but more calendar days.
The workload-by-size study design
| Element | Specification |
|---|---|
| Sampling frame | Every introduction begun by a consenting partner in a fixed entry window, for example two calendar quarters, counted from its first touch whether or not it was ever submitted |
| Strata | Peak full-time bands of 50-99, 100-249, 250-499, 500-999 and 1,000+, plus a row for below 50 or unknown |
| Size measure | Peak full-time headcount, contractors excluded, as the partner understood it at first touch; corrected after SourceX review, with both values kept |
| Staffing firms | Only the firm's own full-time employees count; placed workers on assignment at clients do not, and both numbers are recorded |
| Instrument | A touch log filled in at the time of each touch, never from memory at the end |
| Primary outcome | Touches from first touch to an authorized yes |
| Secondary outcomes | Days from first touch to a verified application; distinct people contacted at the company; screening failures per band; partner minutes, optional and flagged as self-reported |
| Cutoff | One date, for example 180 days after the entry window closes, on which every status is read once |
| Analysis | Medians and interquartile ranges by band; open cases treated as censored for touch and time outcomes; no cell published with fewer than ten introductions |
| Not measured | Time spent by the company or by SourceX, record quality and reward amounts |
The bands follow the U.S. Bureau of Labor Statistics, whose Business Employment Dynamics program publishes firm data in nine size classes, from 1 to 4 employees up to 1,000 or more; the study uses the five classes at or above 50. Published classes make the strata reproducible. They match the program's measure in form only: BLS counts employees, while the program counts full-time employees at peak and excludes contractors.
The touch log. One row per touch. This template is the reusable part of the design.
| Field | Allowed values | Why it is there |
|---|---|---|
| Study ID | A random code per introduction, never the company's name | Keeps the log anonymous |
| Size band | One of the six bands above | Stratifies the analysis |
| Date | The date of the touch | Builds elapsed time |
| Touch type | Message, call, meeting, forwarded question, disclosure, terms read | Separates kinds of effort |
| Counterpart role | Relationship owner, CEO, other executive, SourceX, own colleague | Counts the people between the partner and the CEO |
| Minutes | The partner's own estimate, optional | Rough effort, marked as self-report |
| Stage after touch | Asked, listening, authorized yes, submitted, verified application, declined, screening failure, withdrawn | Places each touch on the path |
Disclosure is logged as a touch like any other. The FTC's endorsement guidance expects material connections to be disclosed clearly and close to any shared link, treats "Paid link" as adequate and "Commissionable link" as probably not clear, and expects companies running affiliate networks to tell affiliates how to disclose. In a one-to-one introduction, telling the CEO that you may earn a reward is part of the work, and the guide on whether you have to disclose a referral fee covers professional rules.
Consent. Partners opt in, may stop at any time, and log roles rather than names. No company records enter the log. For introductions that end in a no, the log keeps only the band, the touches and the outcome.
Count stalled and declined introductions as workload too
The study answers its question only if the failures are counted with the successes.
- Every introduction that began enters the frame at its first touch, including those where the relationship owner declined, the CEO said no, or the partner gave up.
- Screening failures are workload. An introduction that turns out to be a 46-person company is logged in the below-50 row with every touch it consumed.
- Partner attrition is reported. A partner who stops logging has their open introductions censored at their last touch, and the count of such partners is published.
- Non-participation is reported. The number of invited partners who declined to log is published, because those who log may be more organized than those who do not.
- Descriptive is not causal. Company size travels with industry, partner type and how directly the partner knows the CEO. Differences between bands are descriptive. If counts allow, results are also split by relationship type (direct to the CEO, or through an intermediary), and any adjusted model is named in advance.
The results are published in this shape, with nothing filled in until the data exists:
| Band (peak full-time) | Introductions | Reached authorized yes | Median touches to yes | Median days to verified application | Screening failures | Still open |
|---|---|---|---|---|---|---|
| Below 50 or unknown | Not collected | Not collected | Not collected | Not collected | Not collected | Not collected |
| 50-99 | Not collected | Not collected | Not collected | Not collected | Not collected | Not collected |
| 100-249 | Not collected | Not collected | Not collected | Not collected | Not collected | Not collected |
| 250-499 | Not collected | Not collected | Not collected | Not collected | Not collected | Not collected |
| 500-999 | Not collected | Not collected | Not collected | Not collected | Not collected | Not collected |
| 1,000+ | Not collected | Not collected | Not collected | Not collected | Not collected | Not collected |
Time to an authorized yes is a time-to-event outcome with open cases, so it is analyzed the way the stage duration method treats stage times, not by averaging only the finished introductions.
Two cases that would break the thesis (Illustrative)
Illustrative. Both cases are generic companies with invented facts, and neither implies how a real introduction would end.
A large company with a short path. A 1,200-person regional distributor is still run by its founder as CEO, and the partner has known him for a decade. One message, one call, an authorized yes. If cases like this are common, headcount is standing in for distance to the CEO, question 3 is the real finding, and the advice becomes "map the path, not the payroll".
A small company with a long tail. A 60-person agency's CEO says yes within a day. After submission, peak full-time headcount turns out to be 46 once contractors are excluded, and the introduction ends as a screening failure. Small company, fast yes, wasted touches for everyone. If this pattern concentrates in the smallest band, the practical rule is to confirm peak full-time headcount before the first CEO conversation; how to count full-time employees shows how.
How a result would change a partner's decisions
- If touches climb steeply with band: for large companies, start with whoever is closest to the CEO and budget more time per introduction.
- If screening failures cluster in the 50-99 and below-50 rows: check peak full-time headcount before asking anyone.
- If no pattern appears: size is not a workload signal; rank companies by how directly you know the CEO instead.
- The recommendation changes if relationship type explains more of the variation than size does, if the 1,000+ band never reaches ten introductions, or if open cases make up most of a band at the cutoff.
Limits
- Logging changes behavior. People work differently when they record their work, and that can shorten or lengthen paths.
- Minutes are soft. Self-estimated time is unreliable, which is why touches are the primary unit and minutes are optional.
- Thin large bands. Introductions to 1,000+ companies may be rare; if the band stays below ten after two quarters, merge it with 500-999 and say so.
- Size known late. The band at first touch is a partner's estimate; both the estimate and the reviewed value are published.
- Only the partner's side. The company's time is a different question, discussed in how much management time data licensing takes.
A measurable next step. Pilot the touch log with a small group of consenting partners for one quarter, then publish only the number of introductions per band, before any medians, to show whether the cells will reach ten.
Which companies are in scope
The bands start at 50 because the program does: introduced companies need 50+ full-time employees at peak, contractors excluded, plus documented operating history, rights to license the records and an authorized contact. SourceX's who-qualifies page notes that some programs set higher thresholds and smaller specialists can still be considered, which is why the below-50 row exists. 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 CEO authorizes a licensing discussion and signs for the company; other executives can own records and sponsor the idea. Partners never handle records, and discovery stays at metadata level: which records, roughly how many, how many years, which system and who administers it. What stays unknown until SourceX reviews a company: whether its records match current demand, what the rights review finds and what any license would cover. The poor-fit guide lists the patterns that end introductions early, whatever the company's size.
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.
Until workload data exists, size is a screening fact rather than a reason to skip a company: register for a partner link, confirm peak full-time headcount against who qualifies and read the program terms before your first touch. Related study designs are collected in the guides hub.