Does a personal introduction improve handoff completion? A choice-first handoff test that gives every CEO the route they prefer, randomizes only the CEOs with no preference and counts verified applications from the date of the CEO's yes

Short answer

Nobody has published whether a personal introduction completes more often than a link for SourceX introductions, and research from health care, where warm handoffs have been studied for years, points both ways. Test it on CEOs who have already said yes. Ask each one whether they would rather apply with your link or have you make the introduction, honor any preference, and randomize only the CEOs with none. Count a handoff as complete when the company's verified application appears within 90 days of the CEO's written yes. No results exist yet.

Visual briefFull-size diagram
A flow from a CEO's written yes to one question about the preferred route: CEOs who prefer the link or prefer an introduction go to two side lanes marked observed only, while CEOs with no preference meet a coin that splits them between a link handoff and a personal introduction, both ending at a verified application by day 90.
The protocol, not a result. No partner, founder or SourceX results for this handoff test are published.

This is for a platform or community lead whose team introduces portfolio and network companies and who has noticed that a CEO's yes does not always become an application. The step between the two is short, and it is where the choice of route either helps or gets in the way.

Two routes from a CEO's yes

SourceX's process page describes both: partners get a personal link and can also submit an introduction from their dashboard.

RouteWhat the partner does, the same day as the yesWhat happens nextThe written record
Link handoffSends the CEO a short note carrying the partner linkThe CEO starts the company's application when readyThe note, plus the company's own application once it files one
Personal introductionSubmits the introduction from the dashboard, naming the company and the CEO who agreed, then tells the CEO it is doneSourceX checks its own records before inviting an introduced company (terms, section 3)The dashboard submission, with the CEO's written yes kept in the partner's log

The sample Channel Partner Agreement accepts both as written records: section 1.2 allows a record made "through an authenticated portal submission, tracked verified application, email or mutually acknowledged introduction log" and says an oral introduction must be confirmed in writing. Section 2.2 lets SourceX communicate directly with a referred company and says the partner need not join every call or email, so the personal route does not turn the partner into a go-between for what follows.

Neither route changes three facts. Credit is decided by SourceX from dated records, never by a click. A company SourceX already knew is a duplicate whichever route reached it. And section 4 of the terms has SourceX pay any reward separately, so the company receives the same amount whichever route its CEO takes, with or without a partner.

This test starts where two others stop. Comparing personal links with resource pages randomizes CEOs before anyone has asked them anything; the advisory-firm handoff benchmark times handoffs across firms without changing them. Here every CEO has already agreed, and the only thing that varies is who takes the next step.

What warm handoffs in health care show, and what they cannot

Health care has asked a close cousin of this question, comparing warm handoffs with standard or fax referrals. The answers differ by setting. In a study of integrated behavioral health, a warm handoff did not significantly predict attendance at the first appointment once other factors were adjusted, while same-day scheduling predicted it more strongly; the authors called for a prospective comparison (our paraphrase). In a comparison among hospitalized smokers, patients linked by warm handoff enrolled in quitline treatment more often than patients referred by fax (our paraphrase).

Two lessons carry over. A personal handoff may matter most when the next step is something the person might put off alone, and timing may matter as much as the personal touch. So this protocol sends both routes on the same day as the yes, which keeps speed from masquerading as personality. The analogy stops there: a CEO weighing an application is not a patient, and nothing about anyone's health is at stake.

The choice-first allocation

  1. Ask one question with the thank-you for the yes. "Would you rather start the application yourself with my link, or have me make the introduction so SourceX gets in touch with you? Either is fine." Record the answer word for word.
  2. Honor any preference. A CEO who prefers a route gets it and joins a side lane: prefers link, or prefers introduction. Side lanes are reported but never pooled with the comparison.
  3. Draw only for CEOs with no preference. Tell them two routes are being compared and that they still decide everything; then a logged coin flip, made before you write, picks the route. A CEO who would rather not be in a comparison picks a route and joins a side lane.

Overriding a stated preference would cost more goodwill than any finding is worth, and the preferences are evidence in their own right. If nine CEOs in ten choose the same route, that may settle the practical question before the comparison does.

The handoff completion test protocol

ElementSpecification
QuestionAmong CEOs with no preference, does a personal introduction lead to more verified applications within 90 days of the yes than a link handoff?
UnitOne company whose CEO agreed in writing to explore SourceX
ArmsLink handoff; personal introduction
Side lanesPrefers link; prefers introduction
Held fixedSame-day send; the same note core in both routes (the CEO decides, SourceX decides fit, the partner may be paid by SourceX without reducing the company's payout, no files are needed); one identical check-in on day 30 if nothing has happened
Primary measureCompletion: the company's verified application appears in the dashboard within 90 days of the CEO's yes
Outcome categoriesCompleted; duplicate; no application by day 90; CEO withdrew
Secondary measuresDays from yes to application; questions the partner could not answer; partner minutes per handoff; check-back answers
Window and read dateYeses gathered over two quarters; read 100 days after the last randomized yes
AnalysisBy assigned route, whatever the CEO did next; every company stays in the denominator

Duplicates stay in the denominator as their own category, because the routes can reveal them at different moments: a submission prompts SourceX to check its records at once, while a link-route company that never applies is never checked. Report the category for both arms rather than dropping companies after the fact.

The CEO check-back, optional, sent on day 14 with two questions:

  1. Did the next step arrive when you expected? (yes; later than expected; not yet)
  2. Did anything about the handoff feel like pressure? (no; a little; yes)

What never travels in either route: files, exports, figures from board materials, an estimate of what the company could be paid, or anything the partner knows about another company. Section 4.2 of the sample agreement gives a partner no authority to share a supplier's records, and SourceX's screening page treats an introduction its decision maker never heard about as usually not a fit.

Report template, empty until the read date.

Count at the read dateLink handoffPersonal introductionPrefers linkPrefers introduction
CEOsNot yet collectedNot yet collectedNot yet collectedNot yet collected
Completed within 90 daysNot yet collectedNot yet collectedNot yet collectedNot yet collected
DuplicatesNot yet collectedNot yet collectedNot yet collectedNot yet collected
No application or withdrewNot yet collectedNot yet collectedNot yet collectedNot yet collected
Median days to applicationNot yet collectedNot yet collectedNot yet collectedNot yet collected
Check-back: felt any pressureNot yet collectedNot yet collectedNot yet collectedNot yet collected

How small numbers can fool you

A platform team might gather 20 or 30 no-preference yeses in two quarters. Before reading a gap, look at what chance alone produces. Suppose both routes truly completed half the time, a hypothetical rate rather than any SourceX figure. Two arms of 15 CEOs would still differ by four or more completions in about one run out of five, and by six or more in about one run out of 23.

So write down, before the first draw, the smallest gap that would change your default route. Publish rates only when each arm holds at least 15 randomized CEOs; below that, publish counts and the side lanes. Runs from later quarters may be pooled if the protocol and note core did not change.

Pause or stop when:

  • anything reaches SourceX before the CEO's written yes;
  • company files or exports are offered or sent to anyone;
  • a CEO reports pressure in the check-back: rewrite the note before the next yes;
  • SourceX publishes new terms: close the run and start a new one.

Never stop early because one route looks ahead after a handful of CEOs.

Reading the result

Result at the read dateReadingDefault route afterward
Personal introduction ahead by more than your preset gap; check-back answers no worseTaking the step for the CEO helps them follow throughOffer to make the introduction; keep the link for CEOs who prefer it
Link equal or aheadCEOs complete as well on their ownSend the link by default; it costs the partner less time
Most CEOs state a preferenceThe choice matters more than the routeKeep asking the question and let CEOs choose
Completion low in every laneThe stall is not the routeRevisit what the CEO heard before the yes, using the double opt-in pattern
Any guard eventA wording or consent problemFix it before reading anything else

Limits of comparing two handoff routes

  • Side lanes are not comparable. CEOs who state a preference differ from those who do not; their completion rates describe them, not the routes.
  • Effort differs. The personal route takes partner minutes the link does not. Record them so a small gain can be weighed against its cost.
  • SourceX's steps are part of the route. After a submission, whatever SourceX does is inside the personal arm and outside the partner's view; the test judges each route as a whole.
  • Analogy has limits. The health-care studies frame the question; they predict nothing about CEOs.
  • Programs move. Whether a company's records fit is decided in SourceX's review against current programs, and a completed application is not an accepted company or a payable reward.

Methods note. The protocol rests on SourceX's terms (version 2026-10-22.2, since replaced by version 2026-11-04), its screening and process pages and the sample Channel Partner Agreement, all read on 2026-10-28, with the two health-care studies cited as context. It measures route assignment, dashboard stages, timing, partner minutes and optional check-back answers. It does not measure demand for records, review outcomes or payouts, and it publishes no figures because none have been collected.

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 the next CEO says yes, register and sign the Channel Partner Agreement so either route is open to you, check the company's public facts against who qualifies and read the program terms on dated records; related test designs are in the guides hub.

Handoff routes are a referral question. Readers evaluating SourceX as an investment are a separate audience: the SourceX investor overview takes requests for materials, and SourceX discusses its own figures with investors one to one.

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

Does the route change who gets credit for the company?

Not by itself. Both routes leave a written record, and SourceX decides credit from dated records under section 2 of its terms; a link click alone does not decide it. A company SourceX already knew is a duplicate whichever route reached it.

Is it fair to put a CEO in a coin flip?

Only a CEO who said either route was fine, and who was told that two routes are being compared, goes into the draw. Any CEO who prefers one route gets it, and any CEO who would rather not be part of a comparison chooses their route and joins a side lane.

What if a CEO asks for a call with SourceX instead?

Tell them what SourceX publishes and nothing more: after an introduction, SourceX checks its records before inviting the company and may contact it directly. Do not promise a call, a person or a date on SourceX's behalf. Log the request; it is useful evidence about what CEOs expect.

Sources

  1. refer.sourcex.si/terms
  2. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  3. refer.sourcex.si/how-it-works
  4. pmc.ncbi.nlm.nih.gov/articles/PMC6037516
  5. pmc.ncbi.nlm.nih.gov/articles/PMC5031370
  6. refer.sourcex.si/who-qualifies
  7. 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