Does verifiable rewards data qualify? A company data qualification scorecard for introducers

Short answer

Ask about six criteria. Four are gates the company must pass: 50+ full-time employees at peak, documented operating history, rights to license with an authorized contact and, outside the U.S., Canada and the EU, at least 70% of the data in English. Two are scored, because they decide whether the records can support verifiable rewards: record depth (years of the workflow) and linkage (rule, action and outcome tied together). Pass every gate and score well on both, and the company is a strong fit to raise with the owner.

Visual briefFull-size diagram
A scorecard gauge with weak, borderline and strong zones whose needle settles in the strong zone as six criteria are checked: size, history, rights, record depth, linkage and English share.
Illustrative scoring. The scorecard helps an introducer decide whether to ask the owner; SourceX's review decides fit.

This scorecard is part of the reinforcement learning with verifiable rewards guide. For what a checkable workflow looks like in practice, see the worked freight dispute example.

Why a scorecard instead of a yes or no

Verifiable rewards depend on a rule that can mark a result right or wrong. The Tulu 3 paper defines the method as rewarding a model only when a verification function confirms its output is correct. DeepSeek-R1 applies the same idea with rule-based accuracy rewards, requiring answers in a fixed format so a rule can check them. For a business archive, that translates into a practical test: did the company keep the rule, the action and the outcome together, for long enough, with the authority to license them?

Few companies are all yes or all no. A scorecard lets an introducer separate a promising archive from a theoretical one without asking for a single record.

The six criteria

CriterionTypeQuestion to askWho answers
Company sizeGateDid the company have 50 or more full-time employees at its peak, not counting contractors?Owner or HR
Operating historyGateIs there a documented operating history behind these records?Owner or CFO
Rights and authorityGateDoes the company control the records, and who can authorize a licensing discussion?Owner and counsel
Record depthScoredHow many years does the workflow cover, and roughly how many items a year?Controller or COO
LinkageScoredAre the rule in force, the action and the final outcome tied together by reference?Controller or process owner
English shareGate where relevantOutside the U.S., Canada and the EU, is at least 70% of the data in English?Owner or IT

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.

Strong, borderline and weak fits

Linkage is the criterion that most often decides the outcome, so it has the most detail below.

CriterionStrongBorderlineWeak
Record depthFive or more years of one workflow, consistent volumeTwo to four years, or a system change midwayUnder two years, or only current-year data
Linkage: supporting documentsAttached to the transaction itselfStored in a shared drive with a reference numberIn inboxes or paper files
Linkage: rule in forcePolicies and limits kept with effective datesCurrent version only, but changes loggedOverwritten with no history
Linkage: approvalsNamed person and timestamp, distinct from preparerNamed but sometimes the same personShared logins or no approval record
Linkage: outcomeReversals, credits or reopenings linked to the original itemOutcomes recorded but matched by date or amountOutcome not recorded
RightsCompany owns the records; counsel sees no blocking contract termsSome counterparty terms need reviewRecords held or owned by a third party

Illustrative scoring. A fictional 600-person medical supplies distributor reports eight years of customer pricing overrides, each attached to an approved price exception form with a named approver, a policy table with effective dates, and credit notes linked to the original invoice. All gates pass, depth is strong and linkage is strong on four of four lines: raise it with the owner. A fictional 140-person engineering firm with three years of change orders, approvals by shared login and no outcome field passes the gates but is borderline on depth and weak on linkage: note it honestly and let the owner decide whether to proceed.

Reading the result honestly

  • All gates pass, depth and linkage mostly strong: a candidate worth introducing if the owner opts in. Describe the answers plainly in the introduction.
  • Gates pass, linkage mixed: still worth a conversation, but say which links are missing. The evidence gaps analysis shows how to word that.
  • Any gate fails: stop. A company below 50 full-time employees, without rights, or outside the geography rule is not eligible, however good the records.

Scores are a screening aid. They do not estimate value, predict acceptance or imply that any buyer wants a particular workflow. What stays unknown until SourceX reviews it: rights to the records, which entities and years are in scope, how personal and counterparty details are de-identified, and whether any buyer wants the record type. Partners collect answers and never handle ledgers, forms or exports.

Asking the questions without making it an audit

Ask the gates first, briefly, so you do not spend an hour on records a company cannot license. Then ask depth and linkage as curiosity about how the workflow runs: "When someone approves a price exception, where does the approval live?" sounds like interest; "Please confirm your approval controls" sounds like an audit and closes the conversation.

Before raising licensing, disclose that you are a SourceX referral partner and may receive a reward, paid separately by SourceX and never deducted from the company's payout. Sign the Channel Partner Agreement before submitting anything. The company qualification checklist covers the baseline in more detail, the introducer guide to operational data licensing explains the wider process, why finance data is valuable gives background, and customer referral versus partner programs explains where this program sits.

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 a company passes every gate, scores well on depth and linkage and the owner agrees, register as a partner, confirm it on who qualifies and read the program terms.

  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

Can a company score strong on linkage but fail the scorecard?

Yes. Size, rights and an authorized contact are gates, not points. A 30-person firm with perfectly linked records does not meet the 50 full-time employee baseline, however good its archive.

Who should answer the scorecard questions?

The controller, CFO or COO for the record questions, and the owner or counsel for rights. Nobody needs to open a system; each answer is a yes, a no, a range or a name.

Should I share my score with SourceX?

You can summarize it in the introduction as plain answers, for example years covered and whether approvals are named. Do not present the score as a valuation or a prediction of acceptance.

Sources

  1. refer.sourcex.si/terms
  2. arxiv.org/abs/2411.15124
  3. arxiv.org/abs/2501.12948

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