The packet supports the guide to cross-tool identity resolution, which follows one hospital customer through four systems. Partners do not build it. Knowing its contents shows what a company's records must be able to produce later, under SourceX's agreement with the company.
Six documents in assembly order
| Document | What it shows | Who prepares it | |
|---|---|---|---|
| 1 | Cover sheet | Headcount, main systems, acquisitions and migrations, authorized contact | Introducer with the owner |
| 2 | System inventory | Each system holding customer records, its native ID format, years covered and retirement date | IT or finance systems |
| 3 | Crosswalk description | Which systems the mapping covers, its columns, row count, who maintains it | Revenue or sales operations |
| 4 | Merge log summary | Merges per year, whether retired IDs and dates were logged, gaps in the log | CRM administrator |
| 5 | Matching rule statement | How links and merges were decided, by year, and whether uncertain matches were held | Data steward |
| 6 | Rights notes | Customer or vendor terms per source system, personal data present, consents needed | Legal |
The order follows the logic of a review. The inventory names what could be joined; the crosswalk and merge log show what was joined; the rule explains why; the rights notes decide whether joined records can be used together.
What goes in each pocket
1. Cover sheet. Peak full-time headcount (contractors excluded), the ERP, CRM, help desk and any billing tools, acquisitions with dates, and the person who can authorize a licensing discussion.
2. System inventory. One row per system: name, record type, native ID format, years covered and, for retired tools, the retirement date and whether the data was kept. A retired billing tool that closed in 2021 belongs here even though it holds no new activity.
3. Crosswalk description. Not the file. Its columns (for example ERP number, CRM account, legacy billing ID, link basis, date), roughly how many rows, and which systems it leaves out. A two-column crosswalk with only old ID and new ID should say so, because it records that a link was made but not why.
4. Merge log summary. Counts of merges per year, which system logs them, and whether the retired ID survives. If the CRM kept only surviving records before a given year, the summary states the year.
5. Matching rule statement. Whether links were made on exact keys, scored evidence or judgment. Salesforce describes exact matching, which treats non-identical strings as non-matches, alongside fuzzy methods such as edit distance and Jaro-Winkler; the Fellegi-Sunter approach documented by Splink adds per-field weights into one score. The statement says which applied, when, and whether uncertain matches were held for review or merged.
6. Rights notes. Whether help desk records came from service contracts with stricter confidentiality than sales records, whether personal data appears, and whether a parent company must consent.
The resolution task and its acceptance check (Illustrative)
Reviewers often test the packet against one worked decision. This one uses four fictional records for a regional hospital group: an ERP account, a CRM account, a retired billing account and a help desk organization keyed on the email domain.
Task specification. "Given these four records, decide which describe the same legal customer. Link only on a shared tax ID, a recorded cross-reference, or at least two agreeing contact fields with no conflicting purchase order entity. Hold everything else for review."
Contents the case must be able to produce:
- ☐Each candidate record with its system, identifier and creation date
- ☐The field values compared, as they stood on the decision date
- ☐The rule or person that made each decision, with the date
- ☐Any merge log entry showing surviving and retired IDs
- ☐Downstream confirmation: payments applied, contracts referenced, or a dispute that broke the link
| Candidate link | Evidence available | Expected decision | Pass condition |
|---|---|---|---|
| ERP to CRM | Same tax ID; CRM stores the ERP number | Link | Link names the tax ID |
| ERP to legacy billing | Address and phone agree; no conflicting entity | Link | Link names both fields |
| ERP to help desk | Email domain only, shared by three affiliated clinics | Hold | Not merged |
| Help desk to clinics | Same domain, different purchase order entities | Hold | Not merged |
Acceptance check. The case passes only if the ERP, CRM and legacy billing records are linked, the help desk organization is not merged into the hospital group without a confirming key, and every link names its evidence. A resolution that merges all four because the domain matched fails, even if three of the links are correct, because it would misattribute the clinics' records.
What the packet cannot settle
The packet shows whether links can be checked. It cannot show how many links survive checking, whether a buyer wants linked customer histories, what de-identification is required or what the company would be offered. Mercor, for example, says on its own data page (checked October 18, 2026) that it works with enterprises to anonymize and contribute operational data to AI labs. That is one company's description of its business, not evidence that a specific company's linked records would be licensed. Buyer identities are also usually kept private; why AI labs and data users are confidential explains why.
Nothing in the packet contains records, customer names or the crosswalk file. Companies about to retire a tool should keep mapping files and logs before cancelling; exporting data before cancelling SaaS covers that.
Before suggesting a packet
The company must have 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license the records and an authorized contact. 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. Screen first with the identity resolution qualification scorecard, and describe weak spots with the gap analysis for identity resolution. Sales and CRM workflows covers the wider record family, and other categories 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 owner can describe the company's systems, crosswalk and merge history for the cover sheet, register as a partner, confirm who qualifies and read the terms before you make the introduction.