Testing whether more follow-ups improve referral quality: a preference-aware study design in which each CEO caps the reminders, partners randomize only inside that cap, and no result is published until the cohort closes

Short answer

Nobody has measured whether extra follow-ups improve the quality of SourceX introductions, and this page reports no result. It lays out a study that could find out: each CEO decides how many reminders they will accept, partners randomize only where a CEO allowed more than one, and quality is judged by applications SourceX verifies that are still moving months later, read next to stop requests and complaints. Until that cohort closes, the evidence says reminders raise replies, which is a different thing.

Visual briefFull-size diagram
Three rooms of different heights, each with a ceiling line set by the CEO: the room marked none holds no envelopes, the room marked once or no answer holds one, both labeled observed only; the tallest room, marked up to twice, is split into arm A with one envelope and arm B with two, under a label reading randomized only here, and a footer reads quality not yet measured.
Study design only. Caps, arms and timings are settings the study would fix before enrolment; no follow-up has been allocated or counted.

What a partner can use today is the rule the study is built on: ask the CEO once how they want to be followed up, then never send more than they allowed.

Reminders raise replies; whether they raise quality is unmeasured

Survey research has studied reminders for decades. The 2023 Cochrane review of ways to raise questionnaire response reports that reminders by text or email were associated with higher response, an odds ratio of 1.60, and telephone reminders for postal questionnaires with an odds ratio of 1.96, with high heterogeneity across several strategies. A questionnaire returned is the whole goal of that research. A referral is different: a reminder that turns silence into a reluctant yes can produce an application that stalls, a CEO who feels pressed, or a company that later withdraws.

The program also limits what any follow-up can achieve. Under section 2 of the terms, credit goes to the first valid introduction of a new company only when that company submits a verified application inside the 90-day attribution window, decided from dated records; a link click alone decides nothing. The application is the company's own act. So the study treats credit as irrelevant and asks a narrower question: among CEOs who permitted it, does a second reminder change the share of introductions that turn into sound, lasting applications?

TermHow the study uses it
Follow-upAny message the partner starts about the introduction, by any channel, after the CEO's written yes and before the company applies, declines or reaches day 90
CapThe number of follow-ups the CEO agreed to: none, once or up to twice
Allocated CEOA CEO in the up-to-twice group who was assigned to an arm before any follow-up was sent
Quality applicationA verified application inside the window whose dashboard stage has moved past verification by day 120, from a company that sent no stop request or complaint
Harm signalA stop request, a complaint to the partner or to SourceX, or a CEO's note that the reminders felt like pressure

The cap question, asked once at the CEO's yes

The study begins only after a CEO has agreed in writing to look at SourceX. Reminders to an unanswered first ask stay outside it, because no permission exists yet; the stage rules in when to stop following up on an inactive referral already limit those to one.

In the message that thanks the CEO for the yes, the partner asks a single question and records the answer word for word:

ElementWording or rule (Illustrative)
The question"If the application hasn't come up again on your side, would you like me to check in not at all, once, or up to twice over the next two months?"
DefaultNo answer counts as once, the most cautious setting that still allows a reminder
BindingThe cap is a ceiling; the partner may send fewer follow-ups, never more
WithdrawalA stop request at any point lowers the cap to none from that moment
Study notice"I keep the dates of my follow-ups so I can learn how to follow up better. Tell me if you'd rather your company's dates were left out."
Never recordedWhy the CEO chose a cap, anything about the company's records, finances or plans

A CEO who asks to be left out still gets exactly the follow-ups they chose; only their dates stay out of the dataset. If the CEO's request for time names a later date, the requested-delay follow-up governs that row instead, and it leaves the study.

Randomization lives inside the permission

Three groups form at the cap question. Only one can be randomized.

GroupFollow-ups sentAssigned byWhat the study can say
Cap noneZeroThe CEODescriptive counts only
Cap once, or no answerOne, on day 21 if no applicationThe CEODescriptive counts only
Cap up to twice, arm AOne, on day 21 if no applicationA sequence drawn before enrolmentCompared with arm B
Cap up to twice, arm BOne on day 21, a second on day 45 if still no applicationA sequence drawn before enrolmentCompared with arm A

The allocation list is drawn in blocks for each partner before the first CEO enters, so every partner contributes to both arms and a skilled partner cannot tilt one side. Content is held constant: in both arms the day-21 note answers a question the CEO actually asked, as in the follow-up that adds a useful answer, and arm B's day-45 note is a short close that makes declining easy, in the spirit of making an ask easy to decline. Only the number differs.

Comparisons across groups stay descriptive. CEOs who allow two reminders may simply be keener than those who allow none, so a gap between groups says nothing about what reminders do.

Quality first, volume beside it, harm as a guard

  • Primary measure: quality applications per allocated CEO, arm B against arm A.
  • Volume: verified applications per allocated CEO, reported next to the primary measure and never instead of it.
  • Harm: stop requests and complaints per allocated CEO, plus any optional one-line note a CEO sends about how the follow-ups felt.
  • Protocol breaches: any CEO who received more follow-ups than their cap, counted and published.

Partners read their own dashboards, which show each referral's stage and reward status, and they record dates and stages only. No company records, documents or figures enter the dataset, and no partner asks the company anything for the study's sake. Whether a company's records fit a current program is settled in SourceX's own review, independently of how often anyone wrote. Random allocation spreads those decisions across both arms, so a gap in stage movement can be read at the level of the arms, but no single SourceX outcome is ever read as a verdict on one partner's follow-ups.

Enrolment floor, the day-120 read and the two stop rules

These are study settings, written into the plan before enrolment. Preregistration, as the Center for Open Science describes it, means setting out the research plan ahead of the study and lodging it with a registry, which keeps what was planned apart from what turned up later.

  • Entry window: two quarters of CEO yeses from consenting partners who have signed the Channel Partner Agreement.
  • Floor: no comparison is read unless each arm holds at least 40 allocated CEOs; below that, the report gives counts and stops.
  • Read date: day 120 after the last CEO enters, so every row has passed its 90-day window and the stage check.
  • Breach stop: one follow-up beyond a cap pauses enrolment until the cause is found and fixed.
  • Harm stop: if arm B's stop requests exceed arm A's by three or more at a monthly check, or a complaint about follow-up pressure reaches the partner or SourceX, arm B closes and every remaining CEO gets one follow-up at most.

Every CEO stays in the denominator

The report keeps every CEO who answered the cap question, including those who never replied again, those who declined and those whose companies turned out to be duplicates under section 3. A company SourceX already knew is reported as its own row, because no number of reminders changes that outcome.

Row in the reportCap noneCap onceArm AArm B
CEOs enteredPendingPendingPendingPending
Verified applicationsPendingPendingPendingPending
Quality applicationsPendingPendingPendingPending
Declined by the CEOPendingPendingPendingPending
No reply by day 90PendingPendingPendingPending
Duplicate under section 3PendingPendingPendingPending
Stop requests or complaintsPendingPendingPendingPending
Left the studyPendingPendingPendingPending

Only the arm A and arm B columns support a causal reading, and only for CEOs who allow two reminders. Released alongside: the registered plan, the cap question as sent, both follow-up texts, the allocation method, breach counts and every zero.

What each possible result would change

ResultWhat partners would doWhat it never justifies
Arm B raises quality applications, harm flatKeep offering "up to twice" as one of the CEO's optionsA second follow-up for CEOs who chose once or none
Arm B raises volume, quality flat or lowerKeep one follow-up as the norm; the extra applications did not holdCounting applications as success
Arm B raises harm signalsDrop the second follow-upArguing the volume was worth it
No clear differencePrefer the quieter arm, one follow-upRunning the test again until a difference appears

Ways this design could still mislead

  • A self-selected stratum. CEOs who allow two reminders differ from the rest, so a result inside that group may not travel to anyone else.
  • Partners compensating off the record. A partner in arm A who phones instead of writing breaks the contrast; calls count as follow-ups and are logged.
  • Small numbers. Even at the floor, a few applications either way can swing a rate; the report gives counts with every rate.
  • Stage lag. Dashboard stages may update after the read date; the report states the date each stage was read.
  • Moving programs. SourceX checks relevance to current data needs during review, and programs can change mid-cohort; a dated change is reported, not absorbed.
  • Being watched. Partners who know their follow-ups are counted may write more carefully in both arms, which narrows any difference.

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.

You can adopt the cap question before any study runs: register, sign the Channel Partner Agreement before submitting introductions, check each company against who qualifies and the program terms, and find related designs 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

Why not randomize follow-ups for every CEO who agreed to hear about SourceX?

Because a CEO who asked for no reminders, or for one, has already answered the question for their own company. The design only varies the number of follow-ups where the CEO allowed more than one, so nobody receives a message they did not permit.

If the second follow-up produces more applications, does that settle it?

No. The study reads volume and quality side by side. Extra applications that stall, or that come with more stop requests, would count against the second follow-up, and a lift in one group of CEOs would not license reminders beyond any CEO's cap.

Can a follow-up protect a partner's credit before the window closes?

No. Section 2 of the terms credits the first valid introduction only when the company submits a verified application within the 90-day window, and that application is the company's own act. Reminders cannot create it, which is why this study never counts credit as an outcome.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/how-it-works
  3. refer.sourcex.si/who-qualifies
  4. cochranelibrary.com/cdsr/doi/10.1002/14651858.MR000008.pub5/full
  5. cos.io/initiatives/prereg

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