What a declined referral can teach the next partner: a consent-first case protocol that builds each lesson from the introducer's own steps, uses only what the company chose to share and holds every case back until an identification check passes

Short answer

No lessons from declined SourceX introductions have been collected or published, and this page offers none. It sets out a protocol that could produce them. Each case is built from the introducing partner's own dated steps, adds only what the company chose to share and agreed others may read, never records a private reason, and stays unreleased until a second reader confirms the company cannot be recognized. Fit remains SourceX's decision in its own review; the lessons concern what partners themselves controlled.

Visual briefFull-size diagram
An Illustrative decline case card with five rows: company name and private reasons are covered by gray bars marked never recorded; what the CEO shared is marked with permission; the partner's own steps and where it ended are marked used. An arrow crosses a line labeled identification check on its way to a box reading lessons: none published yet, with a note that SourceX decides fit.
Illustrative case card. The protocol has not been run; no case has been written or released.

The partner who learns most from a decline is rarely the one who received it. The protocol exists so that one partner's ended introduction can change how a different partner asks a different CEO, without exposing the company that said no.

Five endings that get called a decline

"Declined" covers outcomes decided by different people, and each allows a different lesson.

EndingWho decidedWhat a partner can learnWhat a partner must not infer
The CEO said noThe companyHow the ask was framed, timed and disclosedWhy the CEO said it, unless the CEO chose to say
SourceX's review ended itSourceXWhich published checks the partner confirmed before askingSourceX's reasons beyond what it chose to share
Duplicate under section 3SourceX, from its recordsWhether the partner asked the CEO about earlier contact with SourceXThat the partner was at fault for SourceX's history with the company
The company withdrew after applyingThe companyWhat the CEO understood about the effort involvedAnything about the company's internal reasons
No replyNobodyAlmost nothing; silence is not an answerA reason of any kind

Two program facts shape every case. Section 7 of the terms says partners never receive access to other partners' records, applicant documents or confidential buyer information, so a case can never be built from SourceX's review file. And a company that applied now has a relationship with SourceX, which section 3 treats as a duplicate for any later partner. The next partner's lesson is therefore about other companies, never a second attempt at this one.

Whose information a case may hold

A case draws on three sources and no others.

  • The partner's own records: their messages, the dates they sent them, the public facts they checked and the claims they made. These belong to the partner, which is why most lessons live here.
  • What the company chose to share: words the CEO volunteered to the partner and then separately agreed may be used, without the company's name, in a case for other partners.
  • The ending as the dashboard shows it: the stage reached and the date, nothing more.

Everything else stays out: the company's name and identifying details, any private reason the CEO mentioned, company records of any kind, anything the partner knew through a board or advisory seat, and anything about SourceX's assessment that SourceX did not itself tell the partner. For keeping a firm's own decline log tidy, the seven-code decline record already stores what a no permits without storing why; this protocol starts where that log stops and asks what other partners could learn.

The anonymized decline case protocol

StepWhat happensWho does itGate before the next step
1. Cool-offWait at least 30 days after the dated endingThe introducing partnerThe ending is recorded and the partner agrees to take part
2. One permission askAsk the CEO once whether anything they shared may be used, unnamed, in a learning case; offer to show the draftThe introducing partnerA clear yes; silence or hesitation means the case uses partner-side facts only
3. DraftFill the case template below from the three permitted sourcesThe introducing partnerNo field holds anything outside those sources
4. Identification checkA second reader who knows the network tries to name the company from the draftA reviewer who never saw the original messagesIf the company could be recognized, coarsen or cut until it cannot
5. Blameless reviewPartner and reviewer agree the wording about the partner's steps; the company's decision is never treated as an errorPartner and reviewerEvery sentence describes a step or a question, not a verdict
6. Release in batchesCases go to the partner library at least five at a time, with the full disposition countThe study leadThe batch passes step 4 as a whole
7. WithdrawalA CEO or partner who withdraws permission has the case removedThe study leadRemoval is logged by date

The identification check borrows an idea from the UK Information Commissioner's Office, whose anonymisation guidance describes a motivated intruder test: asking what practical steps a person determined to identify someone would reasonably be likely to take (our paraphrase). The protocol applies it to companies, and it is a rule about what this library publishes, not a statement about how SourceX handles any data.

The blameless review follows the logic Google's SRE book sets out for postmortems: assume everyone acted in good faith on what they knew, and look at the process rather than the person (our paraphrase). Here it cuts both ways. The partner is not blamed for a company's decision, and the company's no is never written up as a mistake to be overcome.

The case template

FieldWhat goes inWhat never goes in
Company profileA headcount band (50 to 99, 100 to 249, 250 to 999, 1,000 or more), a broad sector family and the clause of SourceX's geography sentence it falls underName, city, products, ownership or any distinctive fact
Relationship pathHow the partner knew the CEO: former client, board seat, peer group, second-degreeThe connector's name
Partner's stepsA dated list: public checks, the ask, the reward disclosure, the CEO's answer, any submissionMessage text that would identify the company
Partner's own claimsThe partner's sentences about fit or process, quoted from their own messagesAnything the CEO wrote, unless approved for the case
EndingOne of the five endings, with the dashboard stage and dateSourceX's internal reasoning
Company's shared wordsOnly text the CEO approved for the caseAny private reason, even one the CEO later mentions
Controllable observationOne thing the partner could have checked or said differently, written as a questionA judgment of the company or of SourceX
Next-partner questionOne question another partner can ask themselves before their own next askAdvice to retry this company

Sampling frame and the full denominator

The frame is every introduction by a consenting partner, who has signed the Channel Partner Agreement, that reached a dated ending during one study year. Cases where the company gave no permission still count; they appear in the disposition table and, if the partner agrees, as partner-side-only cases.

DispositionWhat the report shows
Endings in the frameCount by ending type
Partner declined to take partCount only
CEO gave permissionCount; case may use approved words
CEO declined or did not answerCount; partner-side facts only, or no case
Failed the identification checkCount; held back or rewritten
ReleasedCount, in batches of five or more

No figures exist yet for any of these rows.

Reading the cases without turning them into verdicts

Two coders tag each released case for partner-controllable steps: whether the CEO heard about SourceX before anything was submitted, which published checks the partner confirmed before asking, whether the ask predicted an outcome only SourceX can decide, whether the reward was disclosed, and whether the partner asked the CEO about earlier contact with SourceX. The report gives counts of each tag by ending, with the coders' agreement rate.

Those counts describe the cases, nothing more. A tag that appears often among introductions SourceX ended does not show that it caused them; companies, programs and timing differ. The report never ranks reasons for declines, because it never holds them. Where several partners' cases point to the same unclear published check, the next move is the one in criteria before content: test whether partners read that check the same way.

One case, drafted and corrected (Illustrative)

First draft: "A 140-person freight brokerage in Columbus, run by its founder, said no because a sale is being negotiated. I had told the CEO their dispatch records would be a perfect fit and that they would qualify easily."

After review: "Company profile: 100 to 249 full-time staff, logistics services, U.S. clause. Path: former client. Steps: public headcount check on day 0, ask on day 2 with the reward disclosed, CEO's answer on day 6. Ending: the CEO said no at the ask. Company's shared words, approved for the case: 'Not something for us this year.' Partner's own claim: 'your records would be a perfect fit.' Controllable observation: did the ask predict a result that only SourceX's review can reach? Next-partner question: does my ask describe the published checks rather than forecast the answer?"

The city, the founder detail and the sale came out: the first two narrow the field, and the sale is the company's private reason. What stayed is the partner's own sentence, which is the part another partner can actually use.

What the next partner can take, and what stays behind

  • Can take: a sharper ask, an earlier question about prior contact with SourceX, a habit of describing the checks instead of predicting them.
  • Cannot take: a rule that a sector or size band "doesn't fit". SourceX's screening page says a company that misses one program may suit another later.
  • Cannot take: the company itself. Its CEO's answer stands, as the respectful close describes, and any later introduction would be a duplicate.
  • Cannot take: SourceX's criteria beyond what its pages publish.

Where a decline case library misleads

  • Consent shapes the sample. CEOs who agree to share may have left on better terms than those who did not.
  • Small batches. Five cases in one niche can still point to one company; the identification check runs on the batch, not only the case.
  • Memory. Partners reconstruct steps after the ending; only dated messages count as steps.
  • Hindsight. Knowing the ending colors the observation; coders tag steps without seeing the ending field.
  • Moving programs. A case from one year may describe criteria that have since changed.
  • Who volunteers. Partners who share their declines may already be the more careful ones.

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 your next ask, register and sign the Channel Partner Agreement, describe the published checks on who qualifies instead of predicting the outcome, reread the program terms on duplicates, and log your own endings in the way the respectful decline log sets out; more designs sit 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

Can the next partner introduce the company that declined?

Not for credit, and usually not at all. A company that applied already has a relationship with SourceX, which section 3 of the terms treats as a duplicate not credited to a later partner, and a CEO's no stands until the CEO reopens it. The lessons in a case are for other companies.

What if the CEO told the partner the real reason in confidence?

It stays out of the case, even if the CEO later agrees that the case may be written. Permission covers only the words the CEO approves for the case, and a private reason is never one of them.

Will the cases explain why SourceX turned companies down?

No. Partners see a dashboard stage, not SourceX's review file, and section 7 of the terms keeps applicant documents away from partners. Cases describe what the partner did and could control; fit remains a decision SourceX makes in its own review.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. refer.sourcex.si/how-it-works
  4. sre.google/sre-book/postmortem-culture
  5. ico.org.uk/for-organisations/uk-gdpr-guidance-and-resou…

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