# Referral email test scored on qualified replies | SourceX

Canonical: https://refer.sourcex.si/guides/the-email-test-that-measures-qualified-replies-instead-of-opens
Last updated: 2026-11-04

Count replies, not opens, and count only the replies that pass four checks: the CEO who decides wrote it, it shows the reader understood the offer, it asks for a next step, and it carries no sign of pressure or misreading. Send only to CEOs you know, compare your current note with one changed note assigned by coin flip, and have two readers score each reply without knowing which note produced it. No partner has published results; this page is the method.

The test runs on a partner's own one-to-one outreach, inside the email tool the partner already uses. It needs no purchased list, no tracking pixel, no link tracker and no lookup of who at a company read what. It also never tells a company it qualifies: SourceX decides fit in its own review.

## Why an open is the wrong thing to count

There are two reasons, one technical and one about the program. Apple's Mail support pages say Mail Privacy Protection hides the reader's IP address, fetches remote content in the background when a message arrives rather than when it is viewed, and stops senders from seeing whether a message was opened (paraphrase). Under those conditions an "open" can be logged for a note nobody read, and a note that was read may never register at all.

The program reason weighs more. Nothing in SourceX's terms pays for attention. Section 5 says "A lead, meeting or signed agreement alone does not earn a payable reward," and an open comes long before any of those. The first outcome that you and SourceX can both stand behind is a written answer from the person who decides, and the dated email that carries an introduction afterward is itself evidence: section 1.2 of the sample Channel Partner Agreement lists email among the written forms an introduction record can take. Measurement starts at the reply.

## Who may receive a test email

Only CEOs you know personally or through work, written to one at a time from your own address. No bought, rented or scraped lists, and no messages to someone at a company because a tool guessed their title. SourceX's screening page lists an introduction the decision maker knew nothing about among the cases that rarely fit, and the CEO is the person who decides whether the company talks to SourceX at all. A note to a stranger cannot be honest about the relationship behind it, and it measures the list rather than the message. Whether a business message falls under commercial email law is its own question, answered in [whether CAN-SPAM applies to a one-to-one B2B email](/questions/can-spam-b2b-email-rules); this page does not restate it.

## The reply-quality evaluation rubric

Score every reply on four checks. Each check is pass, fail or unclear, and the reader copies the words in the reply that decided it.

| Check | Passes when | Fails when (Illustrative wording) |
|---|---|---|
| 1. Decider | The CEO wrote it, or forwarded their own written answer | "I run operations; I'll mention it to our CEO" (log it, but it is not the CEO's answer) |
| 2. Understanding | The words fit the offer: SourceX licenses the company's own records, SourceX reviews fit, the company decides, and you may be paid by SourceX | "So we're approved?" or "How much comes out of our payment for your fee?" |
| 3. Next step | Asks for the introduction, the link or a conversation with SourceX, or asks something only a next step can answer | "Interesting, thanks for thinking of us" |
| 4. No harm signal | No complaint, no request to stop, no attachment or record sent, no reading of the note as an endorsement | "Please take me off whatever list this is" or a spreadsheet attached "to save time" |

A **qualified reply** passes checks 1, 3 and 4 and does not fail check 2. An unclear check 2 still counts, because a question about how the program works is often the reason a CEO asks for the next step.

The second failing example under check 2 needs a straight answer whenever it appears. The reward never comes out of the company's payment: section 4 of the terms says it "is paid separately by SourceX and is never deducted from the supplier's agreed compensation", and SourceX pays it from its own share, so the company receives the same amount whether or not you are involved.

Each reply then lands in exactly one category:

| Category | Rule | How it counts |
|---|---|---|
| Qualified yes | Passes the rubric | The primary outcome |
| Informed no | The CEO declines and check 2 passes | A good result for trust, tallied separately and never chased |
| Delegated or unclear | Check 1 fails or check 3 is unclear | Neither; send one reply at most, then leave it |
| Misread | Check 2 fails | An unwanted effect; correct it in your answer |
| Harm signal | Check 4 fails | An unwanted effect and a possible stop rule |
| No reply | Nothing within 21 days | Counted in the denominator only |

Store a decline as a code rather than the CEO's private reasons; [the decline record guide](/guides/how-to-record-a-company-s-decline-without-keeping-its-private-reasons) sets out one scheme.

**Scoring blind.** Two readers score each reply separately from a sheet holding only the reply text and its date, with the subject line and the note's identity removed. They settle disagreements by discussion and log how often they agreed before discussing. If first-pass agreement falls below eight replies in ten, a working threshold of our choosing, rewrite the definitions before comparing anything.

## Code the replies you already have, before sending anything

Before the test, apply the rubric to the last 20 to 40 replies your existing introduction notes received, straight from your own inbox. Three things come out of that exercise: a baseline share of qualified replies for the note you send today; the checks where the two readers disagree, which shows which definitions to tighten; and the most common failure, which tells you what the changed note should try to fix.

If misreadings dominate, the change is probably one sentence on who decides and who reviews. If delegated replies dominate, the note may be reaching the wrong person, and no wording test will fix that. Keep the coding sheet to codes and dates; the replies themselves stay in your mailbox.

## Two notes, one change, assigned by coin flip

| Element | Specification |
|---|---|
| Unit | One CEO you know, contacted one to one |
| Note A | The note you send today, unchanged |
| Note B | Note A with one change, chosen from the baseline's most common failure |
| Both notes | True; say SourceX reviews fit and the CEO decides; say you may be paid by SourceX; never say or imply that the company qualifies |
| Assignment | A logged coin flip per CEO before you write, never your hunch about which company fits |
| Exclusions | Companies you already know have been in touch with SourceX, removed before assignment |
| Follow-up | None, or one identical follow-up for both notes on day 10 |
| Reply window | 21 days from each send |
| Primary measure | Qualified replies per CEO emailed, by note |
| Later measure | Verified applications credited to your introduction and not closed on day 120, read from your dashboard |

Keep the disclosure sentence identical in both notes so that it is not the thing being tested; [whether you have to disclose a referral fee](/questions/do-i-have-to-disclose-a-referral-fee) covers how to word it.

## How many CEOs, how long, and what stops the test

Fix the floor before the first send: at least 25 CEOs per note, or one full quarter, whichever ends later. Below 25 per note, report counts without percentages. Partners who pool their sends must use both notes word for word, the same rubric and the same window. At these sizes a gap of one or two qualified replies is noise.

Stop the whole test, not only the next send, when:

- a CEO asks you to stop writing: remove them for good, and pause if a second request arrives for the same note;
- a reply shows a CEO believes the note said the company qualifies or was approved: rewrite before anything else goes out;
- anyone sends records, exports or attachments about the company: keep nothing, tell the sender, and fix the wording;
- SourceX publishes a new terms version: check both notes against it and begin a new window;
- you catch yourself steering note B toward the companies you like best: restart with a fresh coin flip.

A note pulling ahead is never a reason to stop.

## Reading the two columns

| What you see | How to read it | What to do |
|---|---|---|
| More qualified replies under B, with no rise in misreads or harm signals | The change helped interested CEOs act | Adopt B |
| More replies of every kind under B, harm signals included | The change raised attention, not quality | Keep A, or rewrite B and test again |
| More informed noes under B, qualified replies level | B helps poor-fit CEOs rule themselves out | Adopting it is a judgment you state as one |
| A gap of one or two replies | Too small to read | Report counts and keep A |

Then wait for the later measure. A qualified reply is a CEO asking to talk, not a company that fits. Credit is earned by the earliest valid introduction of a company new to SourceX, inside the 90-day window, and only when that company files a verified application; only one partner is credited per company; and where introductions overlap, SourceX's duplicate review decides from dated records. Report every CEO emailed in both columns, the silent ones included. For what makes the note itself feel trustworthy, the [five-factor message study](/guides/what-makes-a-company-introduction-feel-trustworthy) is the companion design.

## What a qualified reply still cannot tell you

- **Fit.** The note can describe the published facts: a full-time headcount that peaked at 50 or more, contractors left out; years of the company's own records; the right to license them; a location and language matching [who qualifies](/who-qualifies); and a CEO who wants the conversation. Only SourceX applies them, and whether the records match a current program, what the rights review finds and what a license would cover stay unknown until it does.
- **Records.** A partner asks at metadata level, about record types, rough years and systems, and never for files, samples or logins. Nobody collects company data for SourceX.
- **Relationship strength.** CEOs you know well reply more, whatever the note says. The coin flip balances that only when there are enough sends.
- **Replies outside email.** A CEO who calls instead of writing gets the same category, logged the same day with the date, and a written confirmation afterward.
- **Your own sign-up.** Introductions can be submitted only after you sign the SourceX Channel Partner Agreement, so sign before the window opens.

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

When a CEO's qualified reply asks for the next step, [register as a partner](/register) if you have not, hold the company up against [who qualifies](/who-qualifies) again and go through the [program terms](/terms) before you introduce anyone. More partner test designs are collected in the [guides hub](/guides).

## Sources

- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://support.apple.com/guide/mail/use-mail-privacy-protection-mlhl03be2866/16.0/mac/14.0
- https://refer.sourcex.si/who-qualifies
