How much context should an introduction carry? A brief-detail controlled evaluation design that assigns four levels of detail by partner and scores each introduction for usefulness, corrections and oversharing, with no results yet

Short answer

This has not been measured for SourceX introductions, so this page offers no answer. It sets out a controlled evaluation that could: partners are assigned, each as a whole, to one of four levels of detail for the brief that travels with an introduction, from a bare link to a brief holding the CEO's own outline of the company's records. Every introduction is then scored three ways at once: questions the first call still had to ask, facts the CEO had to correct, and anything that should never have been written down. Nothing will be reported until the read date.

Visual briefFull-size diagram
A rotary dial labeled brief detail with four positions, 0 link only, 1 the route, 2 fit facts and 3 record outline, and an orange zone past position 3 marked never: records, board-seat facts, you qualify; the dial has no pointer and reads no setting chosen, and three score bars beside it, repeat questions, CEO corrections and oversharing, read not measured.
No level has been chosen and nothing has been measured. The dial shows the four levels the evaluation would assign.

The design is for SourceX together with partners who opt in. It needs SourceX's first-call notes and the partners' briefs, and it changes nothing about how any company is reviewed.

More detail can save a call and still cost an introduction

The case for a fuller brief is simple: if the first conversation already knows the company's size, history and systems, it can start further along. The case against is quieter. Every line a partner writes about someone else's company is a line that can be wrong, and every extra field is room for things a partner should never pass on: a file, a figure learned in confidence, a guess about fit written as if it were settled. SourceX's screening guidance says fit questions are answered from a conversation with the relationship holder, "never from files, samples or logins," and its process page says partners do not need to export, upload or describe confidential records.

So "better" cannot mean "more useful" alone. The evaluation treats an introduction as better only when it saves effort without adding corrections or oversharing, and it measures all three together. That is what separates it from the long-versus-short email experiment, which compares two notes to a CEO and counts applications.

Four levels of brief detail

Each level adds lines to the one below it. Every line at levels 2 and 3 carries a tag saying the CEO stated it, and the CEO sees and approves the brief before it reaches SourceX.

LevelWhat the brief containsWho supplies each line
0. Link onlyNothing beyond what the company enters when it applies through the partner's linkThe company
1. The routeCompany name, the CEO's name, how the partner knows the CEO, the date of the CEO's yes, and the partner's stake disclosedThe partner
2. Fit factsLevel 1, plus peak full-time headcount with contractors left out, years in operation and location, as the CEO stated themThe CEO, quoted by the partner
3. Record outlineLevel 2, plus the record types, the systems holding them, the years each spans and who runs each system, as the CEO described themThe CEO, quoted by the partner

Out of bounds at every level: records, samples, screenshots or exports; anything the partner learned through a board or advisory seat, which may prompt a question to that company's own CEO but never travels further; customer names; the partner's view of what the records are worth; and any statement that the company qualifies. How to write a volume line honestly at level 3 is covered in when record volume is unknown, and labelling estimates in the estimate field guide.

Assignment by partner, not by introduction

The unit of assignment is the partner. Partners who opt in are grouped by type (investor, adviser, services firm) and by how many introductions they made in the previous two quarters, then assigned to a level by a draw recorded before the entry window opens. Each partner uses the brief template for their level for the whole window.

ElementSpecification
Unit of assignmentOne registered partner who has signed the Channel Partner Agreement
Unit of analysisOne introduction submitted from that partner's dashboard
StrataPartner type crossed with prior volume (low, high)
Entry windowTwo quarters, fixed in advance
Follow-upEach introduction followed for 120 days from submission: the 90-day attribution window plus time for review
AnalysisEvery introduction analysed at its partner's assigned level, whether or not the partner followed the template
AdherenceA reviewer records, for each brief, whether it matched the assigned level

Because outcomes are grouped by partner, the analysis has to account for that clustering, and the report would follow the CONSORT extension for cluster randomised trials published in the BMJ in 2012, which the CONSORT group cites in its reference list. In practice the number of partners per level matters more than the number of introductions: the plan is at least ten partners per level, and results would be reported as intervals, never as single figures.

Three scores for every introduction

ScoreHow it is countedWho counts it
Repeat questions (primary)Questions SourceX's first call had to ask whose answers the assigned level was meant to carry, from a fixed list per levelSourceX's intake reviewer, using the list
CEO corrections (guard)Brief lines the CEO changed, at approval or on the first call, divided by lines writtenThe partner logs approval edits; SourceX logs first-call corrections
Oversharing (guard)Any out-of-bounds item in the brief or attached to itA reviewer who does not see the partner's name
Verified application (secondary)The company applied and SourceX verified the application within the follow-up periodSourceX's dated records
Partner minutes (secondary)Time the partner spent writing the brief, self-reportedThe partner

Level 0 carries no brief, so its repeat-question list is empty by definition; it serves as the floor against which the fuller levels are compared on corrections, oversharing and applications.

Decision rule, written before the window opens. A level is preferred over the level below it only if it cuts repeat questions by a margin set in advance, while corrections per line and oversharing do not rise. Any oversharing in a level disqualifies it until its template is rewritten, whatever its other scores show.

Floor, read date and stop rules

  • Floor: ten partners per level. Below that, the report shows raw counts per level and no comparison.
  • Read date: 120 days after the last introduction in the window is submitted. Nothing is compared before it.
  • A file, sample or export arrives at any level: that level pauses, the material is not kept and the template is rewritten before the level resumes.
  • A brief repeats something learned in a board or advisory seat: the brief is withdrawn and the partner's level pauses.
  • A brief says the company qualifies, or that SourceX sent the partner: the template for that level is rewritten.
  • A new terms version or a revised screening page: the window closes, templates are re-dated and a new window opens.

Every introduction stays in the count

Introductions the CEO never approved a brief for, introductions that went unanswered, and companies that declined all stay at their partner's assigned level. A company SourceX already knew is a duplicate under section 3 of the terms and credited to nobody, but its brief is still scored, because brief quality is the subject. Nothing leaves the count after assignment.

Count on the read dateLevel 0Level 1Level 2Level 3
Partners assignedNot yet countedNot yet countedNot yet countedNot yet counted
Introductions submittedNot yet countedNot yet countedNot yet countedNot yet counted
Briefs the CEO approvedNot applicableNot yet countedNot yet countedNot yet counted
Repeat questions per introductionNot applicableNot yet countedNot yet countedNot yet counted
CEO corrections per line writtenNot applicableNot yet countedNot yet countedNot yet counted
Introductions with any oversharingNot yet countedNot yet countedNot yet countedNot yet counted
Verified applicationsNot yet countedNot yet countedNot yet countedNot yet counted
DuplicatesNot yet countedNot yet countedNot yet countedNot yet counted
Still open on the read dateNot yet countedNot yet countedNot yet countedNot yet counted

Because levels are assigned by draw, a difference between them on these scores can be read as an effect of the level for the partners in the study. Differences inside one partner type, one industry or one company size are descriptive only: the draw did not balance those subgroups, and they are too small to carry a conclusion.

Released with the results: the four templates, the per-level question lists, the draw record, adherence rates and the full table above, zeros included.

What the evaluation cannot tell you

  • Skill differs by partner. With ten partners per level, one unusually careful writer can tilt a level. Stratifying the draw helps; it does not remove the risk.
  • The intake reviewer knows the level. A brief's length gives it away. A fixed question list per level limits how much judgment enters the primary score.
  • Being watched changes writing. Partners in a study may write more carefully than they normally would, at every level.
  • The approval step helps everyone. Having the CEO approve each brief may cut errors at all levels and shrink the differences between them.
  • One program, one process. Results would describe SourceX's intake as it ran in the window, not introductions in general.

A brief that holds up until the evidence exists

Until results are in, the defensible default is the shortest brief that names the route and quotes the CEO for anything else, with every out-of-bounds item left out. The facts, questions and permission entry keeps each line attributed to who said it, and the language-evidence brief shows the same discipline applied to record language.

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 writing any brief, register and sign the Channel Partner Agreement, confirm the company against who qualifies with its CEO's own answers, and keep the program terms version beside the brief; other study designs sit in the guides hub.

  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

Is this the same as testing a long email against a short one?

No. A length test compares two notes sent to a CEO and counts applications. This evaluation varies what information travels with the introduction itself and scores what each level costs as well as what it saves: wrong facts the CEO has to correct, and material that should never have been written down.

Why assign whole partners to a level instead of individual introductions?

A partner asked to write a bare brief on Monday and a detailed one on Tuesday will carry habits from one to the other, blurring the comparison. Assigning each partner to one level for the whole window keeps the levels apart, at the price of needing enough partners rather than just enough introductions.

Could a partner at level 3 attach a sample to make the brief clearer?

Never, at any level. Level 3 holds only the CEO's own outline of record types, systems and years. Files, samples, screenshots and exports are out of bounds, and if one arrives the evaluation pauses that level and the material is not kept.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. refer.sourcex.si/how-it-works
  4. consort-spirit.org/referencesc

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