Coding how new partners explain data licensing before any training: a study design with its writing prompt, codebook, double-coding rules and reporting plan, published before a single explanation is collected

Short answer

Nobody has coded how SourceX partners explain data licensing before training, and this page reports no findings. It publishes a design for doing so: newly approved partners who consent write, before opening any onboarding material, the reply they would send a CEO who asks what licensing with SourceX would involve. Two coders, working blind, score every reply against a frozen codebook of accurate elements and misstatements keyed to SourceX's published pages. Results appear only after the collection window closes and every reply is coded.

Visual briefFull-size diagram
An Illustrative coding sheet: a partner's reply written before training sits on the left as gray lines; two coder columns each hold code chips, and who decides and license, not sale match across them with green links, while promised fit, coded by coder A only, meets a dashed not coded chip from coder B and an orange link to a third reader; boxes on the right read codebook v1.0, frozen, and findings, not yet.
Illustrative coding of one invented reply, to show the procedure. No real explanation has been collected or coded.

The study needs SourceX's help, because only SourceX knows when a partner's account is approved and whether onboarding has started. It involves no company and no company record, and it changes nothing about how any introduction is reviewed or credited.

Why a baseline of untrained explanations is worth having

For many CEOs, a partner's explanation is the first description of SourceX they hear. If that description promises fit, calls a license a sale or offers privacy assurances SourceX does not make, the CEO starts from a wrong picture that someone later has to correct. Training can only aim at those errors if someone knows which ones come naturally.

A baseline answers that and nothing more. It does not measure whether onboarding works: that takes a comparison over time, like the nine scenario cards scored on day 0 and day 30 in the onboarding experiment, or a chapter-level pilot like the enablement test before a network rollout. How executives read partner material is studied separately in the executive comprehension interview.

Four research questions, written so that no answer is assumed:

  1. Which elements of SourceX's published description do untrained partners include without being prompted?
  2. Which misstatements appear, and in how many replies out of all coded replies?
  3. Do partners who rate themselves confident make fewer misstatements? (Described, never treated as cause.)
  4. Do elements and misstatements differ by the kind of practice a partner comes from?
TermMeaning in this study
ExplanationThe partner's written reply to the prompt, up to 200 words
ElementA point SourceX's own pages state, present in the reply in any wording
MisstatementA claim that contradicts SourceX's pages or the program's rules
AbsentAn element the reply leaves out; recorded, never scored as an error
Before trainingAfter account approval, before any onboarding session, partner material or welcome sequence

The frame is every partner whose account is approved during one entry window of two quarters. Each receives one invitation within two days of approval, from a researcher who works outside partner management, and one reminder.

  • Consent covers the purpose, the coding, quotation only with separate permission, and withdrawal up to a dated analysis freeze.
  • No consequences. The invitation says plainly that taking part, declining or writing something inaccurate has no bearing on the account, attribution or any reward.
  • Excluded before invitation: partners who already began onboarding, returning partners who held an earlier account, and SourceX staff.
  • Size. Everyone who consents in the window. If fewer than 60 replies are coded, the report gives code counts only, with no breakdown by group.
  • Nothing about companies. The prompt names no company, and coders delete any company name a partner volunteers before coding.

The writing prompt and two follow-up items

Partners see the prompt once, with a 15-minute limit:

A CEO you know well asks you: "What would licensing our data with SourceX actually involve for us?" Write the reply you would send, in your own words, in no more than 200 words. Please do not look anything up while you write.

The prompt mentions no reward, no privacy question and no exclusivity, so that what partners raise on their own can be seen. Two items follow the reply, never before it: how confident the partner is that the reply is accurate (1 to 5), and which of these they had read before writing: SourceX's public site, the program terms, a colleague's description, or none.

The explanation codebook

Each code is defined by meaning, not wording, and each element is keyed to a SourceX page as it read on the day version 1.0 was frozen.

CodeWhat it recordsDefined asKeyed to
E1What is licensedBusiness records the company created itselfSourceX's screening page
E2The useAI training and evaluationSourceX's FAQ
E3License, not saleThe company keeps its original recordsFAQ: "deals are licenses, not sales of your originals"
E4Exclusive for AI trainingThe selected data is not licensed to anyone else for that purposeSourceX's FAQ
E5No obligation to lookApplying and checking fit commit the company to nothing, and it can declineFAQ: "Applying and the fit check create no obligation."
E6Who decidesThe company's CEOThe program's rule, on the screening page
E7SourceX decides fitFit is settled in SourceX's own reviewSourceX's screening page
E8The partner's interestThe partner may be paid by SourceX, separately from the companySection 4 of the terms
M1Promised fitSays the company qualifies or will be acceptedScreening guidance is not a promise
M2Sale framingSays the company sells its data or gives up ownershipE3's source
M3Money promisedStates a payout, a range or a certainty of payment for the companyFAQ: a profile does not mean an offer or payment
M4Privacy overpromisePromises anonymity or no risk of re-identificationFAQ: "No method is perfect"
M5Named buyerNames a particular AI lab as SourceX's customerFAQ: customers described only as AI labs, model developers and research teams
M6Records requestedAsks the CEO to send files, samples, exports or system lists to the partnerProcess page: partners need not export, upload or describe confidential records
M7Wrong deciderSays a fund, a board, a manager or the partner approvesE6's source
M8Effortless-money framingDescribes licensing as money that asks nothing of the companyFAQ: preparing a delivery may need someone who can export files

A reply that coders cannot read as on-topic, or that is blank, gets a disposition in the ledger below, not a code. Keeping it out of the code categories matters for the reliability figures, as the next section explains.

Two coders, blind, with agreement computed once

Coding open-ended answers is common and often reported too thinly to check. A 2024 review by Conry-Murray and colleagues found human-coded open-ended data in 21% of articles across four top psychology journals, with only about a third of those reporting enough to replicate or evaluate the coding. The same authors set out phases for doing it properly (defining the data and units, writing a coding manual and training coders, then establishing reliability), warned that Cohen's kappa can be inflated by testing reliability repeatedly or by changing categories, for instance by adding a missing-data category, and published a preregistration template (our paraphrase of the article's abstract). This design follows them:

  1. Unit. The whole reply. Each code is marked present or absent for that reply.
  2. Training on invented replies. Coders practice on 20 replies written by the research team, never on real partners' words.
  3. Freeze first. Codebook version 1.0, the prompt and this analysis plan are dated and preregistered before any real reply is read.
  4. Blind and independent. Both coders code every reply without seeing the partner's practice type, confidence rating, reading history or each other's work.
  5. Agreement once. Agreement is computed per code, a single time, on the full set, and reported whatever it is. It is never recomputed after a code is redefined.
  6. A third reader. Disagreements go to a third reader, whose decisions are logged with a reason.
  7. Late codes. A code added after the freeze carries a dated memo and is reported as exploratory.

Counting every partner, including those who wrote nothing

The ledger appears in full in the report, so readers can see who is missing before they read any frequency.

Ledger lineCount
Accounts approved in the windowNot yet counted
Excluded before invitation, with reasonsNot yet counted
InvitedNot yet counted
DeclinedNot yet counted
No reply after the reminderNot yet counted
Consented, then blank or off-topicNot yet counted
Coded repliesNot yet counted
Withdrawn before the freezeNot yet counted

Code frequencies are reported as counts over coded replies, in the form "n of N coded replies contained M1", always beside the ledger and never as a share of all partners.

Reporting rules, and the claims the report will refuse to make

As of 2026-10-27, no reply has been collected. When the window closes, the report will give:

  • for each code, the number of replies containing it and the agreement figure for that code;
  • breakdowns by practice type only where a group has at least 15 coded replies;
  • the confidence ratings set beside misstatement counts, described as an association and nothing more;
  • quotations only with the writer's separate permission, stripped of anything that identifies them;
  • released alongside: the prompt, the consent text, the codebook with its version history, the invented training replies, the ledger and the analysis script.

It will never say that a practice type causes a misstatement, or that any training fixes one. A difference between groups of volunteers is a difference between those volunteers. Partners receive aggregate results only; SourceX's partner team never sees an individual reply.

Code familyReplies with at least one codeAgreement between coders
Elements E1 to E8Not yet collectedNot yet computed
Misstatements M1 to M8Not yet collectedNot yet computed

Ways the explanation study could misread partners

  • Writing is not talking. A written reply may be more careful than what a partner says over coffee.
  • The prompt shapes the answer. A question about "what it would involve" invites process talk and may under-sample reward or privacy claims.
  • Who volunteers. Confident partners may consent more often; the ledger shows the gap but cannot close it.
  • The key is SourceX's own wording. A partner who gets a point right in plain words must be credited, which is why codes are defined by meaning.
  • Pages change. If a SourceX page changes during the window, replies are still coded against version 1.0's dated key, and the change is reported.
  • Prior exposure. Partners who read the public site before writing are not untrained in every sense; the reading item records it.

Checking your own explanation in the meantime

Write your own explanation for a CEO you know, then check it against the eight elements and the eight misstatements above. If it promises fit, calls the deal a sale or offers files to anyone, rewrite it. The one-sentence explanation guide and the two-minute founder outline are tested starting points; other designs sit in the guides hub.

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.

Partners who want their explanation to hold up should register, sign the Channel Partner Agreement before introducing anyone, check each company against the screening criteria and read the program terms in full.

  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

Could my written explanation affect my partner account or a future reward?

No. Coders see replies without names, SourceX's partner team never sees an individual reply, and taking part, declining or writing something inaccurate has no bearing on approval, attribution or any reward.

Why a blank page instead of multiple-choice questions?

A multiple-choice item shows partners the options; a blank page shows what they would actually tell a CEO, including mistakes nobody thought to list. Scored scenario cards suit a before-and-after test of onboarding, which is a separate design.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. sourcex.si/faq
  4. journals.sagepub.com/doi/10.1177/25152459241275217
  5. refer.sourcex.si/how-it-works

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