The referral experiment that tracks negative feedback: a positive-and-negative outcome ledger that gathers reactions from every place a founder might voice them, flags a yes given out of obligation as a warning, and reads harm as events because a small network cannot measure it as a rate

Short answer

In a venture network the most telling negative feedback rarely arrives as a complaint. It reaches a deal partner at a board meeting, hides inside a founder's polite yes to an investor, or shows up as an agreed introduction that never becomes an application. Track it with a two-sided ledger for every company contacted: positive entries on one side, negative entries on the other, and a warning flag on any yes that looks given for the fund's sake. Gather reactions from every channel a founder uses, read each negative as an event, and keep flagged yeses out of any win. No results are published here.

Visual briefFull-size diagram
Five channels on the left, deal partner, events, LP owner, check-back and relationship owner, feed arrows into an open two-column ledger. The positive column lists a clear no and two yes entries, each yes carrying an orange warning flag, yes for the fund and then went quiet; the negative column lists not free to decline and read as endorsement. A tag at the foot reads flagged yeses never win.
Illustrative ledger layout. The codes and channels are this page's design; nothing has been logged.

This page is for growth leads on venture platform teams running small tests of how the network talks about SourceX. Complaint coding is one part of trust measurement; this design covers the larger share founders never put in writing.

Why the worst feedback in a venture network is polite

A fund is not a neutral sender. A founder who depends on its follow-on support, board seat or introductions has reasons to keep every exchange smooth, so a suggestion from an investor can be accepted to avoid friction rather than out of interest. That is a reasoned concern about the setting, not a measured rate, and it shapes the ledger in two ways.

First, some positive outcomes carry a warning. A yes followed by "happy to help the fund" or by weeks of silence is not the same evidence as an eager yes. Second, the founders most uneasy about an approach are the least likely to say so to the person who made it. Feedback has to be gathered from the places it actually surfaces.

The partner quality scorecard rates introducers on company feedback over time, and the failed introductions field guide classifies breakdowns after the fact. This ledger is the outcome record kept during one experiment, built so its decision rule can see what politeness hides.

The positive-and-negative outcome ledger

Hypothesis the ledger tests in any experiment it joins. H0: the version under test produces no more negative entries or warning flags than the current one. H1: it produces more, in which case no gain in yeses can carry it. Unit: one company, reached through one CEO someone in the network knows personally, assigned to an arm at random before contact.

Each code is one entry a ledger keeper can log. One company can carry several.

CodeKindDefinitionRead
P1PositiveThe CEO asks in writing to be introduced, or says the company will applyDay 30
P2PositiveThe CEO declines in writing in a way that shows the message was understoodDay 30
W1Warning on a positiveA yes accompanied by a sign of obligation, such as "anything for the fund"When logged
W2Warning on a positiveThe CEO agreed, then neither applied nor replied by day 45Day 45
W3Warning on a positiveAfter agreeing, the CEO asked someone at the fund whether taking part was expectedWhen logged
N1NegativeA complaint about the approach, to anyone at the fundWithin a week
N2NegativeThe CEO says, when asked, that declining did not feel freeDay 21
N3NegativeA misreading: the company qualifies, the fund endorses SourceX, someone gets special access to its data, or the fund can decide for itWithin a week
N4NegativeThe CEO learns of an introduction they had not agreed toSame day
N5NegativeThe relationship owner reports strain with the founder after the askDay 30
0NeitherNo answer by day 30Day 30

N3 and N4 follow SourceX's own screening guidance: a line such as "our companies qualify" implies an acceptance nobody has given, and an introduction the decision maker did not know about is usually not a fit.

Ledger rules. One dated line per entry, with the experiment arm, the channel it came through and the code. A CEO's own words are kept only with their agreement; otherwise the line holds the code alone. No company records, headcounts or files, no names in any report, and nothing goes to SourceX. Board knowledge never enters: what the fund learned through a board seat or information rights stays where it was learned.

Where founders voice negatives: the collection map

Fix the channels before launch, and log only what arrives through them.

ChannelWhat tends to surface thereWho logs itRule
Deal partner or board memberRemarks made in passing at meetingsThe partner, within a weekLog the code, never the board discussion around it
Platform events and programsComments to program staffProgram leadSame week, code only
LP or co-investor who owns the companyConcerns raised by the ownerThe colleague who holds that relationshipOnly what the owner chose to share
Day-21 check-backAnswers to two optional questionsThe check-back senderNo reminder, ever
Relationship owner at day 30Whether anything changedLedger keeperOne question per relationship

Two lines are never crossed. Nobody monitors private founder groups, and nobody asks one founder to report on another.

A check-back that makes declining easy

At day 21, someone with no stake in the outcome sends every contacted CEO, including those who never replied, one message. It states, only if the fund will stand behind it, that a no to SourceX has no bearing on the fund relationship, and asks two optional questions: "Did you feel free to say no?" and "Did anything about how this reached you feel unwelcome?" A "no" to the first is N2. No reminder follows; a second nudge to collect feedback about pressure is itself pressure.

Events, not rates, in a small network

Email platforms show how small a negative signal can matter. Google's sender guidance asks bulk senders to keep the spam rate users report below 0.1% and never to reach 0.3% (our paraphrase). Those figures govern bulk mail delivery, not referral messages, but the lesson carries over: when the line that matters sits at a few reports per thousand, a platform team writing to forty founders cannot estimate a rate. It can only notice events.

So every negative entry and every warning flag gets a short written review, and the stop rules below are counts, not percentages. A clean ledger from forty founders is weak evidence that nothing went wrong.

Stops triggered by ledger entries

EntryAction
Any N4 surprised CEOStop that sender's introductions until a written review closes
Any N1 or N2Pause the arm it came from and reread its message with someone outside the test
Any N3 misreadingFix the wording in every arm, log the change and restart the count
Two warning flags of any kind in one armPause that arm; review whether the ask leaned on the fund relationship
Anything about a company reaching someone outside the conversationStop the experiment

A positive entry never lifts a stop.

The decision rule: flagged yeses never win

Write the margins as numbers before launch, and apply three steps in order.

  1. Harm gate. Version B can be adopted only if it has no more N entries and no more warning flags than A, and no N4 at all.
  2. Clean outcomes. Count P1 and P2 entries that carry no warning flag. B must exceed A by the pre-set margin; as an Illustrative form, at least three more per 30 founders.
  3. Introduction floor. On unflagged P1 alone, B may not trail A by more than the pre-set margin, for example two per 30.

Anything else is inconclusive and the version in use stays. Flagged yeses are reported in full beside the result. They are excluded from winning because a yes the founder did not feel free to refuse measures the fund's leverage, not the message.

Silence, declines and partial answers

Every company contacted keeps its line. A written decline is P2: the founder understood and chose. Silence is code 0, neither column, and stays in the denominator. A founder who asks to be removed keeps a coded line with no detail. Check-back answers come only from those willing to give them, so report how many answered beside every N2 count.

Random assignment between arms supports reading a difference in entries as caused by the version, for this network and period. Differences between senders, sectors or relationship types are descriptive only.

One page of the ledger (Illustrative)

Illustrative. Invented entries for generic companies, showing the format only.

LineCompany codeArmDayCodeChannelNote
1C-04A6P1AskerCEO asked for the introduction
2C-09B8P1 + W1AskerAgreed, adding that he was glad to help the fund
3C-11B9P2AskerDeclined; systems move this year
4C-07B14N3Deal partnerFounder thought the fund had pre-cleared the company
5C-07B14ActionLedger keeperWording fixed in both arms; count restarted
6C-02A45P1 + W2Ledger keeperAgreed on day 5, no application or reply since

Lines 2 and 6 stay in the report but out of the outcome test. Line 4 changes the message for everyone before line 5 is logged.

Where the ledger can mislead

  • Unvoiced harm. Even with five channels, most unease goes unsaid.
  • Uneven reporting. Partners who pass on remarks diligently make their arms look worse. Report entries by channel.
  • Over-reading warmth. A W1 flag rests on a judgment about tone. Have a second keeper code flags blind and report agreement.
  • Small numbers. Most comparisons will be inconclusive; the zero-transaction learning review shows what can still be learned.
  • Publication pressure. The retrospective outline shows how to publish the negative column and every flag in full.
  • A borrowed benchmark. Gmail's thresholds describe bulk email; no published threshold exists for referral messages.

Methods note. The codes, channels, stops and decision rule were written on 2026-10-28 from SourceX's screening page and program terms, with Google's sender guidance used only to show how small a negative-feedback line can be. Message tests such as the eligibility messaging test can carry this ledger as their outcome record. SourceX publishes no results from it.

What the ledger never decides about a company

The ledger records how founders reacted to being asked; it never judges whether a company fits. Each company's CEO makes the call on talking to SourceX and signs if it goes ahead. SourceX's screen asks for at least 50 full-time employees at the company's peak, with contractors left out, a multi-year history of its own records, rights to license them and relevance to a live program. 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. Whoever submits introductions signs the SourceX Channel Partner Agreement first, and each introduction concerns one company whose CEO agreed to it.

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 first message of any network test, register, agree the collection channels and the check-back wording, confirm fit questions against who qualifies, and read the program terms that govern every introduction the test produces.

Keeping this ledger is referral work. Evaluating SourceX as an investment is a separate decision; materials for that are requested through the SourceX investor overview.

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.

  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 would a founder's yes count as negative feedback?

It does not count as negative on its own. It is logged as a positive entry with a warning flag when the founder signals the yes was given for the fund's sake, or agrees and then goes quiet. Flagged yeses are reported in full but never counted toward a version winning, because a yes the founder did not feel free to refuse says more about the relationship than about the message.

Should the platform team watch founder group chats for reactions?

No. The ledger takes only what founders or the fund's own people choose to report through the agreed channels. Monitoring private founder spaces, or asking founders to report on each other, would create the very distrust the ledger is meant to catch.

Does the ledger go to SourceX?

No. It stays with the platform team, names companies only by code in any report and holds no company records, headcounts or files. SourceX hears only from companies whose CEOs choose to apply.

Sources

  1. refer.sourcex.si/who-qualifies
  2. refer.sourcex.si/terms
  3. support.google.com/mail/answer/14229414
  4. sourcex.si/investors

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