How to test which company fit questions partners can answer: a screening question usability study that walks each published question with a partner, logs the step where it stalls and records whether the partner could answer, never the answer itself

Short answer

Take the five pre-introduction questions SourceX publishes on its who-qualifies page and walk partners through them one at a time, each thinking of a company they already know: did they understand the question, do they know the answer, do they know whom to ask, or does it stall? Record the step reached and the seconds taken, never the answer and never the company. Add think-aloud interviews with a few partners to learn why a question stalls. Nothing has been collected yet, so this page publishes the method and no results.

Visual briefFull-size diagram
Questions 1 to 5, taken one at a time, meet a four-step staircase descending left to right, labeled 1 understood, 2 answer known, 3 knows whom to ask and 4 stalls, the last step outlined in orange; a side note says question 6, relevance, is SourceX's to check and any answer counts as an over-claim; two boxes beneath read logged, the step reached and the seconds taken, and never logged, the answer or the company; a footer says results are not published.
The stages are this page's study design; no partner has been measured, so the staircase carries no counts.

It is for the research or content lead of a partner program, at SourceX or at a network whose members are registered partners. The point is practical: once you know which question stalls, you know which explanation to rewrite and which conversation with a CEO to prepare for.

The six questions under test, quoted from who-qualifies

SourceX's page lists five questions to settle before any promotion, "answered from a conversation with the relationship holder, never from files, samples or logins". The study adds a sixth, taken from the same page's screening profile, as a control: it is a question SourceX says it answers itself.

#Question as SourceX publishes itWho can answer it
1"What was full-time headcount at its peak, and when?"The company, through the relationship holder; the page adds that contractors are excluded
2"When do the company's own records start, and in which systems?"The company
3"Who created the records, and does any of them belong to clients?"The company
4"Where is the company, and what language are its records in?"The company; the language condition is explained in SourceX's English-language guide
5"Does the CEO know about the idea and want the conversation?"The CEO
6 (control)"Relevance to SourceX's current data needs."SourceX, which "checks this during review"

The page also says to mark each answer pass, unknown or fail with a date, and that "Unknown is not a fail; it is a question for the relationship holder." The study borrows that spirit: an unknown is a stage to measure, not a mistake to hide.

Four stages, two failure codes

A question is "hard" when a partner cannot get it to a usable state. The study defines four stages a question can reach, plus two codes for answers that go wrong in a different way.

Stage or codeDefinitionWhat it tells you
1. UnderstoodThe partner restates the question in words consistent with the published wordingThe question reads clearly
2. Answer knownThe partner already knows the answer from the CEO or the company's own statementNo extra conversation needed
3. Knows whom to askThe partner does not know the answer but can name the person who does and could ask themOne conversation away
4. StallsThe partner neither knows the answer nor knows whom to askThe question is hard for this partner
MisreadThe restatement contradicts the published wordingA comprehension problem, not a knowledge gap
Over-claimOn the control question, the partner says they can answer itConfusion about what SourceX decides

One rule protects the companies. If the only reason a partner "knows" an answer is something seen through a board or advisory seat, the study codes it as stage 3, with the CEO as the person to ask. Knowledge from that seat can prompt one question to that company's own CEO and nothing more, so it never counts as an answer in hand.

The study's headline measure for each question is the share of partners who stall or misread, shown with its count and denominator. Time to reach a stage is secondary.

The screening question usability study

The design has two parts. Part A measures where each question stalls across many partners; Part B explains why, with a few.

ElementPart A: structured walk-throughPart B: cognitive interviews
WhoEvery partner in the frame who agreesEight to ten partners per round, two rounds, spread across role families
FormatOnline, about 20 minutes, aloneVideo call, about 45 minutes, with a trained interviewer
The companyOne the partner already knows, chosen privately and never named or describedThe same rule
For each questionRestate it in your own words; pick the stage reached; time is logged automaticallyThink aloud while answering, then scripted probes such as "What does peak mean to you here?" and "Who would you ask, and how?"
OrderQuestions 1 to 6 shuffled for each partnerFixed, so interviews compare
Between roundsNot applicableRevise the study's explanation sheet, never the published questions, and test the revision in round two

Cognitive interviewing is the established tool for Part B. The National Center for Health Statistics' questionnaire research center uses it as its primary method for evaluating survey questions, examining how people interpret a question, where they answer it incorrectly and whether answers from different groups are comparable (paraphrase). Those are exactly the three things a fit question can get wrong for a partner.

What the study records, and what it refuses to hold

RecordedRefused
The stage reached, per questionThe company's name, sector or location
The partner's restatement, with any company detail removedHeadcount figures, record dates, system names
Seconds per questionClient names or anything a client owns
Role family and months since signing the Channel Partner AgreementLanguage shares or other answers the company would give
The kind of tie to the chosen company: portfolio, client, former colleague or otherAny record, file, screenshot or sample

The refusals are not caution for its own sake. Section 4.2 of SourceX's Channel Partner Agreement reads: "This Agreement gives Partner no authority to share a supplier's inventory, records, raw data or personal information, or to access extraction systems." A study that collected answers would be asking partners to do what that sentence withholds. If a partner types a company fact anyway, it is deleted before analysis.

The frame is every partner with a signed Channel Partner Agreement on a fixed date. Everyone is invited to Part A; Part B draws from Part A volunteers, chosen to spread across investors, advisers, consultants and others. The consent screen states the purpose, that no company information is wanted, that results are reported only as group counts, and that the partner may stop at any time.

Every invitation ends in one disposition, and every disposition is reported:

DispositionTreatment in the results
Completed all six questionsCounted per question
Stopped part-wayCounted for the questions answered; the stopping point reported
No company in mindReported as its own outcome
DeclinedCounted in the invited total
Never respondedCounted in the invited total

A partner who cannot think of a single company in the network is not noise. Dropping them would make every question look easier and every network look richer than it is.

The report this study will publish

Results: not published. No partner has taken part yet. When the study runs, the report will show, for each question, the count at each stage and code against the number who answered it and the number invited; median seconds per question; restatements coded as misreads, quoted only after company details are removed; and, from Part B, the themes interviewers heard, each with the number of interviews in which it came up. Groups with fewer than 10 answers appear as raw counts only.

QuestionUnderstoodAnswer knownKnows whom to askStallsMisreadAnsweredInvited
1, peak headcountNot yet collectedNot yet collectedNot yet collectedNot yet collectedNot yet collectedNot yet collectedNot yet collected
5, CEO knows and wants itNot yet collectedNot yet collectedNot yet collectedNot yet collectedNot yet collectedNot yet collectedNot yet collected
6, control (over-claims)Not applicableNot applicableNot applicableNot applicableNot yet collectedNot yet collectedNot yet collected

Differences between role families are descriptive. An adviser who stalls less on question 3 may simply know different companies; the study cannot say that the role causes the difference. The wider practice of reporting every attempt, failures included, follows the research blueprint for company data introductions, and a related design on how company size changes effort is in how company size affects referral workload.

What a hard question would justify, and what it would not

  • Question 1 stalls or is misread. Rewrite the partner-facing explanation of "peak" and of leaving contractors out, and tell SourceX if its own wording is the source of the confusion. Never change the size test or invent a workaround.
  • Questions 2 to 4 stall. These belong to the company. The fix is a better question for the CEO's team, or pointing the CEO to the company fit checker so the company can screen itself.
  • Question 5 stalls. The only remedy is a conversation with the CEO. No study finding makes an introduction acceptable without one.
  • The control draws over-claims. Partner materials should say plainly that relevance is SourceX's call, made in review.

The limits are real. Partners may pick an easy company to think about. Restating a question well is not the same as acting on it well. And the results describe one version of SourceX's published questions, on the dates the study ran.

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 every question for a company you know has reached stage 2 or 3 and its CEO wants the conversation, register as a partner, take the questions from who qualifies as published and read the program terms before anyone contacts the company. A study on what makes the introduction itself credible is in what makes a company introduction feel trustworthy, and more designs sit in the guides library.

  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 does the study never ask for the company's actual headcount or record dates?

Because the study is about the questions, not the companies. Knowing that a partner could answer the headcount question is enough; the figure itself would turn a research file into a list of company facts no CEO agreed to share.

What if a partner cannot think of any company to use?

That is recorded as an outcome, not dropped. A partner with no company in mind is telling you something about the network, and leaving them out would make every question look easier than it is.

Could the results justify changing SourceX's fit criteria?

No. A hard question may need a clearer explanation in partner materials, or a note to SourceX that its wording confuses people. The criteria themselves are SourceX's, and a partner study never rewrites them.

Sources

  1. refer.sourcex.si/who-qualifies
  2. refer.sourcex.si/terms
  3. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  4. cdc.gov/nchs/ccqder/index.html

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