Does a shorter referral brief improve founder response? A brief-length experiment specification that keeps every line a founder needs to say no in both versions, moves only explanation behind SourceX's own pages, and counts a quick, informed no as a response

Short answer

Nobody knows yet, and the answer turns on what "response" means. If it means more yeses, a shorter brief can win by leaving out the conditions that make founders say no. Count decided answers instead: yes, no or not now, given within 14 days, with every founder who was sent a brief in the denominator. Keep every condition in both versions, shorten only the explanation, and let a count of late surprises veto the short one. No results exist.

Visual briefFull-size diagram
Two brief silhouettes side by side, a one-screen short brief and a two-page long brief, each carrying the same highlighted band of seven core lines; below them a response meter counts yes, no and not now as decided answers and leaves no reply and tell me more undecided, with an orange veto tag for late surprises.
Illustrative specification. Line counts and measures follow the design on this page; no founder, brief or result is shown.

This page is for a platform team that sends portfolio and network founder-CEOs a written brief about SourceX before anyone asks for a conversation, and suspects the brief is too long to be read.

What this test changes, and what earlier tests already cover

It varies one thing: the length of the first brief a founder receives, before any yes. Neighboring designs answer other questions. The long and short introduction test tests an email sent after a CEO has already agreed to hear more and judges it on qualified applications. The context-level evaluation varies how much detail a partner's brief to SourceX carries. The credibility protocol has executives score real briefs blind, and the eligibility messaging test changes framing while holding length steady.

Here the claims stay fixed and the word count moves. The new element is the measure: whether a founder reaches a decision, and whether a founder who decided quickly later finds a condition they missed.

Why shorter might help, and why it might not

The case for shorter has a respectable source. The Behavioural Insights Team's EAST framework advises, in paraphrase, that clearer, simpler messages can raise response rates and that a complex goal is better broken into simple steps. Simpler is not the same as shorter, though. A short brief that sends the founder to three linked pages may be harder work than one longer page that answers their questions in order.

Research ethics adds a caution. The Belmont Report, writing about consent to research, holds that how and where information is presented matters as much as the information itself (our paraphrase). A founder's yes to a conversation is not a research consent, but the point carries: a brief that is read and understood beats a brief that is merely complete.

Three predictions, written down before the send:

  1. Short wins. Busy founders decide faster on one screen, and late surprises do not rise.
  2. Long wins. Founders wary of anything about their company's data want the detail first and stay silent without it.
  3. No difference. The relationship owner's name matters more than the brief's length.

The decision core neither version may drop

Seven lines, identical in both briefs. Each is what a founder needs in order to say no correctly.

LineWhat it saysIts basis
1. What SourceX doesIt takes a license to a company's own records, dealing with the company itself, for training and evaluating AISourceX's process page
2. Who decidesThe company's CEO, not the fund and not the boardSourceX's screening page
3. Size and historyAt least 50 people on full-time payroll at the company's largest, contractors not counted, and years of records the company itself createdSection 1 of the terms; the screening page
4. Rights and placeRecords the company may license, not material belonging to its clients. 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 screening page
5. What is asked nowOnly a reply; if interested, the company applies itself and nobody at the fund sees its recordsSourceX's process page
6. The fund's interestThe fund could receive a reward from SourceX, which section 4 of the terms says "is paid separately by SourceX and is never deducted from the supplier's agreed compensation"Section 4 of the terms
7. What nobody knows yetFit, rights and any offer are settled only in SourceX's review; a one-word "no" ends the matter with no follow-upSourceX's process page; the fund's own commitment

The brief-length experiment specification

VersionLengthContents
ShortAbout 150 words, one phone screenThe seven core lines, then links to who qualifies, how it works and the terms
LongAbout 700 words, two pagesThe seven core lines word for word, then what direct licensing means, what SourceX's review looks at (operating history, documentation, data rights, relevance to current demand), the order of steps, one Illustrative company that fits and one that does not, and three questions founders often ask
SpecificationEntry
UnitOne founder-CEO of a portfolio or network company with a named relationship owner
Sampling frameEvery such founder on a list frozen on a date, minus companies with contact with SourceX you know of
Before assignmentFounders hear in a routine update that the team is trying two formats for optional program notes, and can step out before a set date
AssignmentWithin each owner's founders, alternate versions in a random order fixed by coin toss and written into the log before the first send
Held constantSender (the owner), subject line, send within one week, one identical check-in on day 7 to anyone who has not replied
Not measuredOpens, read time, clicks; no read receipts or tracking pixels in either version
Primary countFounders with a decided answer by day 14, per founder sent a brief
Secondary countsYes with no failed fit fact by day 14; verified applications on day 120, too few to decide anything and reported anyway
Guard countsCore surprises, detail questions, misreadings, anything sent to the team from company records
AnalysisEach founder stays in the version they were sent, replied or not

Fourteen days is our choice, long enough to cover a busy fortnight and short enough that the count reflects the brief rather than later events.

Method note. The seven core lines restate SourceX's terms, screening page and process page as checked on 2026-10-28; the measures come from the design's question, whether founders reach an informed decision. Nothing here measures demand for any company's records, record quality or payouts.

A decided answer is the response

Founder's position on day 14Counted as
Yes, wants a conversationDecided
NoDecided
Not now, with a date or a condition ("after the audit", "if we pass 50 full-time")Decided
"Tell me more" with no decisionUndecided
A colleague replied; the founder has notUndecided, routed to the founder
No replyUndecided

Core surprises are the veto count. At the first conversation, or in any later message, the founder says they did not know something one of the seven core lines states, for example that the fund could be paid, that contractors are left out, that the CEO decides, that client-owned material is usually not a fit, or that nothing is promised. Both versions carried those lines, so a gap means the short format buried them.

Detail questions are the expected cost of brevity: questions the long version answered and the short one left to a link, such as what the review looks at. They are reported, never a veto.

Misreadings are logged in the founder's own words: "so we qualify," "the fund is selling our data," "the reward comes out of what we're paid." Any record, sample or export sent to the team stops the test until the wording is fixed.

Rules for a small result, set before the first send

Illustrative sizing: 60 founders, 30 per version.

  • Adopt the short brief if it shows at least five more decided answers than the long one and no more core surprises.
  • Keep the long brief if it shows at least five more decided answers, or if the short brief logs two or more core surprises beyond the long one's count, whatever else it shows.
  • No verdict otherwise. Keep the long brief, because it tells founders more, and record that the test did not settle the question. Why a narrow split is not a result is worked through in avoiding a winner from five replies.
  • Stop early if a founder says the brief or its follow-up felt like pressure, if company records reach the team, or if the short version reaches three core surprises before day 14.

Descriptive and causal claims stay apart. The assignment makes the comparison fair for these founders and these two texts. A founder's explanation, "I said no fast because it fit on one screen," describes that founder; it does not explain the gap.

Publish what did not work. Report both versions' counts, the losing text, the founders who stepped out before assignment and the core-surprise log. If founders' understanding is the bigger worry, measure it directly with the founder comprehension pilot.

What the brief must never imply about fit

No brief, short or long, establishes that a company fits. The records are the company's own; its CEO decides whether to talk; demand, rights and scope are settled in SourceX's review. A brief that a founder reads as "the fund has checked us and we qualify" has failed whatever its length. Whoever submits an introduction after a yes is a registered partner who has signed the Channel Partner Agreement, and the company describes its own records when it applies.

Where this specification can mislead

  • Founders compare notes. Two founders who share a board member may show each other both versions; record it when you hear of it.
  • The owner matters more than the text. Alternating within owners balances them; it does not remove them.
  • One pair of texts. A better long brief or a worse short one would change the result. The test compares these two texts.
  • "Not now" can be a polite no. It counts as decided either way, which is the point of the measure.
  • Day 120 is thin. Too few applications to read is a finding about scale, not about length.

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 either brief goes out, the person who will submit introductions should register, read both texts against who qualifies and confirm the reward line still matches the program terms.

A brief-length test is about referral practice. A reader asking whether SourceX itself deserves investment is making another decision entirely, and can request materials 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 not just count how many founders say yes?

Because a yes count rewards whichever brief persuades best, including one that persuades by leaving things out. A decided answer, yes, no or not now, rewards the brief that lets a founder make up their mind, and a fast, informed no saves the founder's time and the owner's goodwill.

Can the short brief drop the reward disclosure to save space?

No. The fund's possible reward is one of the seven core lines both versions carry word for word. Dropping it would change what the brief claims, not just its length, and the test would no longer be about length.

We only have 20 portfolio founders. Is the test still worth running?

Run it as a learning exercise, not a verdict. With ten founders per version only a very large gap would clear the rule, so expect no verdict, publish the counts anyway and keep the version that produced fewer late surprises.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. refer.sourcex.si/how-it-works
  4. bi.team/wp-content/uploads/2015/07/BIT-Publication-E…
  5. hhs.gov/ohrp/regulations-and-policy/belmont-report/r…
  6. 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