# Referral follow-up consent experiment | SourceX

Canonical: https://refer.sourcex.si/guides/the-follow-up-experiment-that-honors-no-contact-preferences
Last updated: 2026-11-04

A follow-up experiment honors no-contact preferences when those preferences are settled before randomization and outrank it: anyone who has said no or asked not to be contacted leaves the list before the draw, every arm sends at most one follow-up, and any no ends contact from the whole network at once. Inside those limits this design tests one thing: whether announcing that single follow-up in the first ask, with a one-word way to cancel it, changes qualified introductions, clear answers and objections. No result exists yet.

## The stage the other follow-up tests leave out

Two published designs already study follow-ups, and both begin after a CEO has said yes. [The follow-up count study](/guides/do-more-follow-ups-improve-referral-quality) asks the CEO how many reminders they will accept, and [the timing test](/guides/a-follow-up-timing-test-that-respects-founder-preferences) lets the founder name a window. Before any yes there is an earlier, harder stage: a first ask with no answer. Nobody has stated a preference, so a partner who sends a reminder is guessing what the CEO wants.

The stage rules in [when to stop following up on an inactive referral](/guides/when-to-stop-following-up-on-an-inactive-referral) allow one follow-up there. This experiment keeps that limit and asks whether the one follow-up should be announced in advance, so the CEO can see it coming and cancel it, or simply sent.

| Term | How this page uses it |
|---|---|
| First ask | The partner's first message to a CEO about SourceX |
| Announcement | One added line in the first ask saying when the single follow-up will come and how to cancel it |
| Skip | A one-word reply that cancels the follow-up and leaves the question with the CEO |
| No-contact register | One shared list of companies nobody in the network may contact about SourceX |
| Clear answer | Any reply that settles what happens next: yes, no, skip or later with a date |
| Qualified introduction | A CEO's written yes that leads to a verified application inside the 90-day window, with no published fit fact failing |

## Preferences come first, and they are settled before the draw

The network keeps a single register: company name, date added and the words the CEO used. Nothing else. Before allocation, every company in the frame is checked against it and against four other conditions.

| Who leaves the frame before the draw | Why | Recorded as |
|---|---|---|
| Any company whose CEO has told any member no about SourceX | A no binds the network, not just the person who heard it | A count, no names |
| Any company that asked not to be contacted about outside offers | A stated preference outranks the study | A count |
| A company going through a breach, layoffs, a dispute or the loss of a leader | [A crisis is a poor moment for this ask](/guides/why-a-crisis-is-usually-a-poor-moment-for-promotional-outreach) | A count |
| A company wound down or in a formal process | SourceX's screening page says the CEO alone may not be enough there; whoever controls the estate decides | A count |
| A company already asked about SourceX by anyone in the network | It is no longer a first ask | A count |

Excluded companies are never replaced from outside the frame and never contacted for the study's sake. The report gives the number excluded under each reason and nothing more.

## The preference-respecting test protocol

Partners draw nothing themselves. A list made before the first ask assigns each CEO to arm A or B in blocks by partner, so every partner sends both versions and a partner's warmth cannot tilt one side.

| Step | Arm A, announced | Arm B, standard |
|---|---|---|
| First ask, core | Identical in both arms: why this company, one sentence on what SourceX does, that the CEO decides, the partner's reward disclosed, and a no that takes one reply | Identical |
| Added line | "If I don't hear back, I'll send one short note on [date], then stop. Reply 'skip' and I won't send it." | None |
| Days 0 to 13 | Replies handled by the table below | Same |
| Day 14 | One short follow-up to CEOs with no reply, unless they replied skip | One short follow-up to CEOs with no reply |
| After day 14 | Nothing more from anyone in the network; the row closes on day 90 unless the CEO writes | Same |

The reward line in the core matters for trust in both arms. Section 4 of the terms says, "The referral reward is paid separately by SourceX and is never deducted from the supplier's agreed compensation." SourceX has also confirmed that a company receives the same amount with or without a partner, so the disclosure can say plainly that the partner's reward costs the company nothing. The follow-up text itself should answer something the CEO might need, in the manner of [the follow-up that adds a useful answer](/guides/the-follow-up-that-adds-a-useful-answer), and it is the same in both arms.

| Reply | What happens next | Register |
|---|---|---|
| Yes | The CEO goes forward; the partner signs the Channel Partner Agreement before submitting; the company applies itself | No entry |
| No, or not interested | The row closes; no message from any member | Added within one business day |
| Skip (arm A) | No follow-up; the row stays open for the CEO to reopen | No entry |
| Later, with a date | The CEO's date governs; the row leaves the comparison and is counted apart | No entry |
| Stop, or remove me | Treated as a no, and the CEO is taken off any network mailing | Added within one business day |
| Silence after the follow-up | The row closes as no reply | No entry; nobody writes again |

Reading a hesitant reply correctly is its own skill; [the difference between skepticism and a genuine no](/guides/the-difference-between-skepticism-and-a-genuine-no) covers the cases that are hard to call. When unsure, treat the reply as a no.

## A legal floor is not this protocol's standard

Whether a personal note from a partner counts as commercial email under U.S. law is a question for your own counsel, not this page. For commercial email, the FTC's compliance guide says: "You must honor a recipient's opt-out request within 10 business days." It also says, "Any opt-out mechanism you offer must be able to process opt-out requests for at least 30 days after you send your message." The protocol's one-business-day, network-wide rule is a study setting chosen for courtesy. It does not interpret the law, and meeting it says nothing about whether any law applies to you.

## Measures, floor and stop rules

- **Primary:** qualified introductions per CEO allocated, arm A against arm B, read on day 120 so every row has passed its 90-day window.
- **Clear answers:** the share of CEOs in each arm who gave a clear answer by day 30.
- **Negative feedback:** replies objecting to the follow-up or the announcement, and complaints to the partner, the network or SourceX.
- **Breaches:** any message after a no, skip or stop; any second follow-up; any drawn company later found on the register.

Partners record dates and stages only, reading stages from their own dashboards, which SourceX's process page says show each referral's stage and reward status. No company records, figures or documents enter the study.

These are study settings, labeled Illustrative and fixed before the first ask: no comparison is read until each arm holds at least 40 CEOs; one breach pauses every first ask until its cause is fixed; three replies objecting to the announcement line close arm A; and any complaint that reaches SourceX pauses the study for review.

## Every drawn CEO stays in the report

| Row | Arm A | Arm B |
|---|---|---|
| CEOs allocated | Pending | Pending |
| Yes | Pending | Pending |
| No or stop | Pending | Pending |
| Skip | Pending | Not offered |
| Later, with a date | Pending | Pending |
| No reply after the follow-up | Pending | Pending |
| Duplicate under section 3 | Pending | Pending |
| Qualified introductions | Pending | Pending |
| Objections and complaints | Pending | Pending |
| Breaches | Pending | Pending |

Exclusions before the draw are reported once, above the table, by reason. A company that turns out to have earlier contact with SourceX stays in its row: under section 3 a company with "any earlier lead, account or email correspondence" is a duplicate, and no wording changes that. Only the arm comparison supports a causal reading about the announcement; the reasons CEOs give for saying no are description.

## What each result would change

| Result | What changes | What it never justifies |
|---|---|---|
| Qualified introductions level, more clear answers, objections flat | Adopt the announcement: more preferences on record and fewer unwanted notes | A second follow-up for anyone |
| Fewer qualified introductions in arm A | Keep the standard ask, still with one follow-up at most | Treating a skip as a no to be worked around |
| More objections in arm A | Drop the line | Blaming the CEOs who objected |
| No difference anywhere | Adopt arm A; a tie goes to the version that sends fewer unwanted notes | Running the test again until it differs |
| Any breach | Fix the process first; nothing is read until it is fixed | Excluding the breached rows |

## Where this design can mislead

- **Skip as a soft no.** Some CEOs may use skip to decline politely. The qualified count is there to show whether that costs introductions.
- **Late returns.** A CEO who skips may write months later. Returns after day 120 go in an addendum, not the main reading.
- **A register nobody checks.** It works only if every member checks it before writing; log each check.
- **Small numbers.** Forty per arm detects only large gaps; report counts beside every share.
- **Moving criteria.** SourceX's criteria follow each program and can change mid-study; a dated change is reported, not absorbed.

## What the first ask must keep true

The ask can describe fit, never confirm it. A company needs 50 or more full-time employees at its peak, contractors excluded; operating records it created and kept; rights to license them; and a CEO who agrees to the discussion. 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 partner asks nothing about the records beyond, perhaps, what kind exist; files, samples and logins stay with the company. Whether the records fit a current program and whether contracts limit their use are settled in SourceX's review, after the company applies.

## 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.

Build the register before the first ask goes out. When a CEO says yes, the partner can [register](/register), confirm the company against [who qualifies](/who-qualifies) and read the [program terms](/terms) before anything is submitted.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://refer.sourcex.si/how-it-works
- https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business
