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.
| Route | What the partner does, the same day as the yes | What happens next | The written record |
|---|---|---|---|
| Link handoff | Sends the CEO a short note carrying the partner link | The CEO starts the company's application when ready | The note, plus the company's own application once it files one |
| Personal introduction | Submits the introduction from the dashboard, naming the company and the CEO who agreed, then tells the CEO it is done | SourceX 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
- 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.
- 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.
- 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
| Element | Specification |
|---|---|
| Question | Among CEOs with no preference, does a personal introduction lead to more verified applications within 90 days of the yes than a link handoff? |
| Unit | One company whose CEO agreed in writing to explore SourceX |
| Arms | Link handoff; personal introduction |
| Side lanes | Prefers link; prefers introduction |
| Held fixed | Same-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 measure | Completion: the company's verified application appears in the dashboard within 90 days of the CEO's yes |
| Outcome categories | Completed; duplicate; no application by day 90; CEO withdrew |
| Secondary measures | Days from yes to application; questions the partner could not answer; partner minutes per handoff; check-back answers |
| Window and read date | Yeses gathered over two quarters; read 100 days after the last randomized yes |
| Analysis | By 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:
- Did the next step arrive when you expected? (yes; later than expected; not yet)
- 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 date | Link handoff | Personal introduction | Prefers link | Prefers introduction |
|---|---|---|---|---|
| CEOs | Not yet collected | Not yet collected | Not yet collected | Not yet collected |
| Completed within 90 days | Not yet collected | Not yet collected | Not yet collected | Not yet collected |
| Duplicates | Not yet collected | Not yet collected | Not yet collected | Not yet collected |
| No application or withdrew | Not yet collected | Not yet collected | Not yet collected | Not yet collected |
| Median days to application | Not yet collected | Not yet collected | Not yet collected | Not yet collected |
| Check-back: felt any pressure | Not yet collected | Not yet collected | Not yet collected | Not 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 date | Reading | Default route afterward |
|---|---|---|
| Personal introduction ahead by more than your preset gap; check-back answers no worse | Taking the step for the CEO helps them follow through | Offer to make the introduction; keep the link for CEOs who prefer it |
| Link equal or ahead | CEOs complete as well on their own | Send the link by default; it costs the partner less time |
| Most CEOs state a preference | The choice matters more than the route | Keep asking the question and let CEOs choose |
| Completion low in every lane | The stall is not the route | Revisit what the CEO heard before the yes, using the double opt-in pattern |
| Any guard event | A wording or consent problem | Fix 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.