The partner FAQ experiment that removes repeated questions: a before-and-after question count with a control code, an eight-answer FAQ that restates SourceX's published pages in your own words and adds no rule, and verified applications as the measure that decides

Short answer

An FAQ can stop the same questions arriving from every CEO you contact, but only an honest count shows whether it did. Log and code every question for at least three equal periods, publish a dated FAQ whose answers restate SourceX's terms and fit page in your own words, then log three more periods with the same codes. Keep the FAQ if covered questions fall, a control code stays level and verified applications per contacted company do not drop. No partner or SourceX results for this study are published yet.

Visual briefFull-size diagram
An empty counting grid: five of the eight covered question codes (who decides, company paid less, records needed, do we fit, are you paid) and one scheduling control row, each crossed by three before periods and three after periods, split by a vertical line marking the dated FAQ; beneath, the primary measure reads verified applications per contacted company.
A design with empty cells. No partner or SourceX results for this study are published.

This is a design for a partner's own outreach materials. The FAQ is yours; the rules in it are SourceX's. Every answer repeats what the program terms, who qualifies and how it works already say, and an answer that cannot point to one of those pages is cut.

The hypothesis, and the measure that outranks the question count

Hypothesis. Publishing an FAQ with every outreach message lowers the number of covered questions per contacted company, without lowering the share of contacted companies that reach a verified application.

The two halves are not equal. An FAQ that cuts questions by putting CEOs off has failed, however quiet the inbox becomes. So the measure that decides is qualified, not convenient:

RoleMeasureWhat never counts
PrimaryVerified applications credited to your introduction, per contacted company, read at the same age for every companyPage views of the FAQ, link clicks, opens
MechanismCovered questions per contacted company per periodA question the FAQ does not answer
ControlScheduling and logistics questions per contacted company per periodAnything the FAQ addresses
Unwanted effectsMisreadings, declines that cite the FAQ, questions about its wording, records sent to youSilence, which is not agreement

Verified applications come from the stage shown on your partner dashboard, which SourceX says displays each referral's stage and its reward status. Credit goes to the first valid introduction within the 90-day window when the company submits a verified application (terms, section 2), so read each company's outcome no earlier than 90 days after it was contacted.

The question-frequency before-after study

ElementSpecification
UnitA company whose CEO received your standard outreach message
PeriodsEqual lengths, for example two weeks; at least three before the FAQ goes out and three after
The changeFAQ version 1, dated, linked from every outreach message from a fixed start date; nothing else in the message changes that day
Question logEvery question from a contacted CEO or their staff, by email, call note or chat, logged the day it arrives
CodingOne code per question from a codebook frozen before period one; the same company asking the same code twice in a period counts once
Covered codesThe eight questions the FAQ answers (below)
Control codeScheduling and logistics: when to talk, who else joins, which time zone
New codesAny question created by the FAQ's own wording, logged separately
FloorAt least five contacted companies in every period and twenty across each side; if a period falls short, every period is lengthened by the same rule, decided in advance
Second coderA colleague blind-codes one question in five; disagreements are reported, not quietly fixed

The three-and-three rule comes from published study-design guidance. Cochrane's Effective Practice and Organisation of Care group (EPOC) suggests leaving out interrupted time series studies that lack a clearly defined point when the intervention happened and at least three data points before and three after it (paraphrase). A partner's FAQ test is a small interrupted series: one dated change, counts on either side.

The control code is the check on everything else. If covered questions and scheduling questions both fall after publication, fewer conversations or a quiet season probably did it, not the FAQ.

The FAQ: eight answers in the partner's words, each with its source

The wording below is Illustrative, written for this page; yours should sound like you. The source column is not optional. Before publishing, read each answer against its page on the day you date the FAQ.

Covered codeThe question as CEOs ask itAnswer, in the partner's wordsWhere SourceX says it
C1Who decides whether we talk to SourceX?You do, as CEO. Neither I nor anyone else can make that decision for your company.Who qualifies: "Under the program, opening a licensing discussion and signing for the company fall to the CEO."
C2Does your reward come out of what we would be paid?No. My reward, if there is one, comes from SourceX and leaves your payment untouched.Terms, section 4: "The referral reward is paid separately by SourceX and is never deducted from the supplier's agreed compensation."
C3Do you need to see our records?No. I will never ask for files, samples or logins. What your company shares is decided between you and SourceX.How it works: "You do not need to export, upload, or describe confidential records."
C4Could our company be a fit?Possibly; SourceX decides in its review, under the criteria of the specific program. See the location sentence below the table.Who qualifies: screening profile and "SourceX applies the criteria of the specific program, not one universal minimum."
C5Are you paid, and when?Yes, I may be. Nothing is earned when you reply, meet or sign; a reward follows only a completed, paid licensing deal and SourceX's own conditions.Terms, section 5: "A lead, meeting or signed agreement alone does not earn a payable reward."
C6What would SourceX pay us?I cannot say, and I will not guess. Your company and SourceX agree commercial terms directly.How it works: the company agrees commercial terms with SourceX
C7We have been in touch with SourceX before. Does that matter?Please tell me. It does not change who decides for your company; it can mean no partner is credited for the introduction.Terms, section 3: a relationship "includes any earlier lead, account or email correspondence between SourceX and the company, however it began."
C8What happens if we say yes?I submit one introduction, your company applies itself, and SourceX reviews it. Whether to go ahead stays your decision.Who qualifies: "The company applies itself at /apply"; how it works: the company controls whether to proceed

C4 in full. The answer adds the screening facts from who-qualifies in plain words: roughly 50 or more full-time employees at the company's peak and several years in operation (some programs set higher thresholds, and smaller specialists can still be considered); documentation the company created itself; and the right to license it without breaching client confidentiality, employee privacy or contracts with others. Personal consumer data, scraped data, material that belongs to clients and one-off files are usually not a fit. On location it quotes the page word for word: 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. For how the English share is counted it links the English-language guide rather than explaining it.

What the FAQ never contains. A new criterion, a reward figure, a promise of fit, a description of how SourceX prices offers, or anything about a specific company. Its footer carries the date, the terms version (2026-10-22.2 on the day this page was checked) and the updated date shown on who-qualifies, plus links to all three pages and to SourceX's own FAQ. Before any of this goes out, you have signed the Channel Partner Agreement, which section 1 of the terms requires before you submit an introduction.

Measuring understanding and the effects nobody wants

A falling question count is not the same as understanding. Three further lines show whether the FAQ informed people or only quieted them:

  • Misreadings. A CEO who writes "so we qualify" or "SourceX has approved us" read the FAQ as a verdict. One is a stop rule; see below.
  • Shift in kind. Good FAQs move questions from the basics to specifics: from "who decides?" to "how do we count our English share?". Log new codes and read them alongside the totals.
  • Declines that cite the FAQ. A CEO who says the FAQ made it sound complicated or risky is an unwanted effect. Record that it happened, not the private reasons behind it.

Questions that need someone else's answer, such as a company asking whether a particular contract restricts its records, go to a backlog rather than into the FAQ; the founder-question backlog and the question owner board show two ways to run one.

Minimum duration and stop rules

Three periods on each side is the floor, not the target. Do not publish the FAQ partway through a period, and do not change your outreach message, your list rule or your sending volume at the same time; any of those would arrive with the FAQ and take its credit.

Stop, withdraw or restart when:

  • SourceX publishes a new terms version or changes who-qualifies. Withdraw the FAQ the same day, re-date it against the new pages, and start a new after-series. An answer that no longer matches a live page is worse than no answer.
  • A CEO reads the FAQ as a promise of fit or payment. Withdraw, rewrite the answer that caused it, re-date it and restart the after-series.
  • Anyone sends you files or records because of the FAQ. Do not open or keep them, tell the company you do not need them, and fix the wording before the FAQ goes out again.
  • Contact volume in an after-period changes by more than half compared with the before-periods. Keep counting, but report that period separately.
  • Never stop because the early after-periods look good.

Reading the before and after columns

CountBefore, periods 1 to 3After, periods 1 to 3
Companies contactedNot yet collectedNot yet collected
Covered questions per contacted companyNot yet collectedNot yet collected
Control questions per contacted companyNot yet collectedNot yet collected
New questions about FAQ wordingNot applicableNot yet collected
MisreadingsNot yet collectedNot yet collected
Verified applications per contacted companyNot yet collectedNot yet collected
Records sent to the partnerNot yet collectedNot yet collected
What the counts showReading
Covered questions drop at the publication point and stay down, control questions stay level, applications do not fallKeep the FAQ, and re-date it whenever SourceX's pages change
Covered and control questions fall togetherDo not credit the FAQ; something else changed
Covered questions fall and applications fall tooThe FAQ may be putting CEOs off; rewrite before keeping it
Covered questions do not moveNobody reads it, or it answers the wrong questions; check which codes persisted
New wording questions or misreadings appearRewrite those answers, re-date, and run a fresh after-series

Read the primary measure as counts first. With the numbers most partners have, the application guard can catch a collapse but not a small decline, and the five-replies page explains why small totals cannot settle a close call. Say that limit in the write-up rather than claiming the FAQ was neutral.

Where a before-after count can mislead

  • No concurrent comparison. Anything else that changed at the publication date, a conference, a news story or an update to SourceX's pages, moves the counts too. The control code and the three-and-three periods narrow the doubt; they do not remove it. A stronger version alternates outreach batches with and without the FAQ link, using the hold-constant approach for everything else.
  • Coding drift. Whoever codes learns what the FAQ covers and may start filing questions differently. The frozen codebook and the blind second coder exist for this.
  • Some questions are good. A CEO who asks three careful questions may be the most serious prospect you have. The aim is to remove repetition, not curiosity.
  • The FAQ ages. SourceX may publish new versions of its terms (section 11). A dated FAQ shows when it was last true; an undated one cannot.

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.

Start the question log this week and draft the FAQ only from what it shows: register as a partner if you have not, check every answer against who qualifies and the program terms on the day you date it, and find related designs 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

Why not just link SourceX's own FAQ instead of writing one?

Link it as well. A partner FAQ earns its place only by answering the questions your own contacts keep sending, in the order they ask them, with a source under each answer. If your coded log shows SourceX's page already covers them, the experiment is to add that link and count again.

Who should code the questions?

One person, using a codebook frozen before the first period, and a second person who codes a sample blind so you can see whether the codes drift. Change the codebook only between studies, never in the middle of one.

What if the FAQ draws new questions?

Give them their own code and count them. New questions about the FAQ's wording are an unwanted effect and point to an answer that needs rewriting; new questions that go deeper, such as how to count the share of English records, often mean the basics landed.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. refer.sourcex.si/how-it-works
  4. epoc.cochrane.org/sites/epoc.cochrane.org/files/uploads/Resour…

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