Does a company's cross-tool identity resolution data qualify? A scorecard for linked customer records

Short answer

Score the company on three gates and seven criteria. The gates are 50+ full-time employees at peak, rights to license the records and an authorized contact. The criteria test whether its systems are actually linked: operating history, cross-reference fields, kept migration maps, merge logs with retired IDs, a shared strong key, recorded link decisions and downstream confirmation. A strong fit stores another system's ID in its CRM, kept the old-to-new mapping when it replaced a tool, and logs every merge. Ask; never request the files.

Visual briefFull-size diagram
A vertical gauge from 0 to 14 with weak, borderline and strong bands; as seven criteria on the right are checked in turn, a pointer climbs the gauge and settles at 13 for a fictional 540-person staffing firm, in the strong band.
Illustrative score for a fictional company. A high score sorts the introduction; it does not predict acceptance or a reward.

This scorecard is part of the guide to cross-tool identity resolution, which follows one hospital customer across four systems. Here the question is narrower: does a particular company hold linked records worth an introduction, and how strong is the fit?

Scoring rules and bands

Each criterion earns 2 points for a strong answer, 1 for borderline and 0 for weak. Seven criteria make a maximum of 14. Gates are pass or fail and are not added in.

ScoreBandWhat to do
12 to 14StrongIntroduce; the company likely holds links with their basis recorded
7 to 11BorderlineIntroduce with the weak criteria named; review will size the usable share
0 to 6WeakLinks are mostly guesswork or lost; clear up the open questions first

Why the basis of a link matters so much: methods differ. Salesforce's documentation describes exact matching, which treats non-identical strings as non-matches, alongside fuzzy methods such as edit distance and Jaro-Winkler. The Fellegi-Sunter model, documented by the UK Ministry of Justice's Splink project, scores each pair from per-field agreement weights. A link made by an exact tax ID and one made by a weak name score are very different evidence, and the scorecard rewards companies that recorded which was which.

Three gates before any points

GatePassFail
Size50+ full-time employees at peak, contractors excludedUnder 50, or mostly contractors
Rights to licenseThe company controls its CRM, ERP and help desk records, and customer or vendor terms allow reuse discussionsA parent group, franchisor or client controls the records
Authorized contactA named CEO who can open a licensing discussionNobody with that authority identified

Documented operating history is also required; a company with none fails outright, and depth is scored below. English share is a fourth gate outside the U.S., Canada and the EU: 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.

Seven criteria for linked records

CriterionStrong (2)Borderline (1)Weak (0)Question to ask
Operating historyFive or more years of customer history across the main systemsHistory broken by a system changeUnder two yearsWhich years does each customer system cover?
Cross-reference fieldsCRM or help desk stores the ERP customer numberStored for key accounts onlyNo system stores another's IDDoes any system hold another system's ID?
Migration maps keptOld-to-new ID mapping kept for every replaced toolKept for the latest migration onlyDeleted after go-liveWhen a system was replaced, was the mapping kept?
Merge logsRetired ID, surviving ID and date logged on each mergeLogged in one systemDuplicates deleted with no traceWhen two records merge, is the retired ID logged?
Shared strong keyTax ID, contract or customer number on most records in each systemOn some recordsNoneIs there a key that appears in every system?
Link decisions recordedLinked and held-for-review statuses keptLinks kept, no statusLinks made silentlyAre uncertain matches marked, or just merged?
Downstream confirmationPayments, contracts or disputes tie back to the linked recordPayments onlyNothing confirms a linkDoes anything later prove a link was right?

Ask in that order. If no system holds another's ID and no mapping was kept, the later answers carry little weight. The company qualification checklist covers the general screen behind these rows.

Three Illustrative companies, scored

Each company is fictional, and the answers came from one call with an operations or finance lead.

Criterion540-person staffing firm, two acquisitions150-person software reseller85-person dental clinic group, Australia
Operating history221
Cross-reference fields210
Migration maps kept210
Merge logs211
Shared strong key221
Link decisions recorded100
Downstream confirmation211
Total13 of 14, strong8 of 14, borderline4 of 14, weak

The staffing firm absorbed two regional agencies and kept the client mapping files from both integrations. Its CRM stores the billing system's client number and logs every merge. It loses one point because uncertain matches were merged by a coordinator without a status, so a reviewer cannot tell confirmed links from judgment calls.

The software reseller has a shared customer number in its ERP and CRM, but the help desk is keyed on email domain and the old billing tool's mapping was kept only in part. Borderline, with the help desk and pre-2020 billing named as open items.

The clinic group has patient and payer records in separate practice systems with no cross-references, and merges are done by deleting duplicates. Patient records also bring health privacy questions that the rights review would have to weigh. It passes the gates, but the fit is weak until linkage evidence turns up.

When to raise it, and what the score cannot show

Identity questions come up naturally during consolidation work, so CRM consolidation after an acquisition is a good moment to ask, as is the diligence work described for cross-border M&A advisors. A company about to retire a tool should keep its mapping files; exporting data before cancelling SaaS covers why.

The score cannot show how many links hold up when checked, whether linked records were collected under terms that permit joining them, whether any buyer wants them or what the company would be offered. Mercor, for example, says on its data page (checked October 18, 2026) that it works with enterprises to anonymize and contribute operational data to AI labs; that describes one company's business, not demand for any particular archive. Only SourceX's review settles fit.

Next, the evidence gaps page for identity resolution shows how to describe weak rows, and the review packet contents list shows what the company would prepare. More record families are under data types.

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.

If the company clears the gates and its linkage answers land it in the strong or borderline band, register as a partner, confirm who qualifies and read the program terms before you introduce its decision-maker.

  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

Is owning several systems enough to score well?

No. Several systems with no recorded links score poorly on linkage. The scorecard rewards evidence that someone joined the records and wrote down why, not the number of tools.

Who in the company can answer these questions?

Usually the revenue operations, finance systems or data lead. Most can answer from memory in a short call. If nobody can, that itself is a borderline signal on several rows.

Does a recent CRM consolidation help or hurt?

It often helps, because consolidation projects produce mapping files and merge logs. It hurts only if those files were deleted after go-live, so ask whether they were kept.

Sources

  1. moj-analytical-services.github.io/splink/topic_guides/theory/fellegi_sunter.html
  2. help.salesforce.com/s/articleView
  3. mercor.com/data
  4. refer.sourcex.si/terms

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