This hub offers practical guides and best practices for advisors looking to successfully introduce companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English) to SourceX, a direct licensing partner for approved business data for AI training and evaluation. Here, you'll discover step-by-step instructions and strategic insights for introducing companies to SourceX, which licenses data directly from companies and manages the agreement, rights review, data preparation, delivery and payout, subject to acceptance at Closing and agreed terms. These resources are designed to help you navigate the process efficiently, focusing on companies with 50+ full-time employees at peak. Unlock the potential of valuable data partnerships by leveraging these comprehensive guides.
Practical guides to successful company data introductions
Short, task-focused guides on identifying suitable companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English), recognizing valuable proprietary data, and making an introduction the decision maker will welcome.
- Step 1Share your linkSend your personal link to a company you know.
- Step 2Company appliesThe company applies itself at /apply.
- Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
- 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
What kind of companies should I introduce to SourceX?
You should focus on introducing companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English) that have 50 or more full-time employees at peak. These are the companies that can unlock the potential for valuable data partnerships with AI labs and data buyers.
What is the purpose of these guides?
These guides offer practical instructions and strategic insights for advisors to successfully introduce companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia to SourceX. They help navigate the process efficiently and identify valuable proprietary data for AI labs and data buyers.
Who benefits from SourceX data introductions?
AI labs and data buyers benefit from approved business data that SourceX licenses directly from companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia for AI training and evaluation. Advisors can also benefit by introducing companies to SourceX as their direct licensing partner.
What kind of information do these guides provide?
These guides provide step-by-step instructions and best practices for identifying suitable companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia. They help in recognizing valuable proprietary data and making introductions that decision makers will welcome, facilitating data transactions for AI.
Related pages
- How to model a one-time receipt, like a data license, in a 13-week cash flow forecast
- 2021-vintage private equity funds: what to do with companies bought at peak multiples
- 3PL and logistics M&A in 2026: what buyers want and what sellers should preserve
- 3PL valuation multiples in 2026: what buyers pay for in a logistics business
- A/E industry M&A trends in 2026, and what selling firms should prepare
- Acquiring a business from a retiring owner: assessing decades of records before they go
- Proof-of-delivery disputes: the records that explain how a delivery exception was handled
The records that explain a proof-of-delivery dispute are the ones that show what the adjudicator saw, which rule they applied and what happened next: the route scan, the delivery photo or signature, the support ticket, the client's delivery rule, the adjudication note, the credit or denial, and any follow-up check. A scan alone shows a claim of delivery. The full chain shows a decision, which is what makes it useful evidence of how exceptions were handled.
Read → - Proposed US federal bills on AI training data transparency: what partners should know
Proposed federal AI training data transparency bills would require AI developers to disclose, or let copyright owners discover, what material trained their models. They are proposals until enacted, so check congress.gov for current status. Whatever passes, buyers prefer suppliers that can document where licensed data came from and on what rights basis.
Read → - Pros and cons of selling or licensing company data to SourceX
The main advantages of licensing company data to SourceX are that the company keeps ownership, receives one net payout paid once, and is bound only when it signs. The main drawbacks are an exclusive AI-training term, inventory and approval work, categories lost to rights review, and no assurance that any buyer will select the data.
Read → - Protecting Your Referral Credit Across Websites
To protect your referral credit when an introduction spans multiple websites, the key is clear, documented communication. Ensure the referred company clearly indicates you as the referrer early in their process.
Read → - Protocol deviation resolution exception example: one late visit worked through step by step
The records that explain a protocol deviation are the ones that let a reader follow each judgment in order: the protocol version and amendment in force, the site activation date, the departure itself, the first classification, the review that challenged it, the corrected classification and root cause, the corrective action and the analysis decision that followed. In the Illustrative case below, the useful evidence is not "deviation closed" but a visit date read two ways and a documented correction.
Read → - Protocol deviation resolution history: what to inventory before a research system migration
Before a research system migration, inventory every link a deviation record depends on: the protocol version and amendment in force on the date of the event, the deviation log entry and its classification, the investigation and corrective action, any IRB or sponsor correspondence, and the effect on the analysis population. Record which system holds each, how many years exist, who owns it and when legacy access ends. Then introduce the executive who can authorize a data discussion.
Read → - Protocol deviation resolution records across systems: a system map of the keys that join one case
Five keys reconstruct protocol deviation resolution across systems: study and site number, participant study ID, visit identifier, the protocol version or amendment in force, and the deviation or CAPA number. Data capture holds the visits, the quality system holds deviations and corrective actions, the document file holds protocols and activation letters, and statistics files hold analysis decisions. If any key is missing, each system tells part of the story and nothing joins them.
Read → - Public records vs licensable company data: a rights trace through one company's own records
No. Being able to see a business record, in a public portal, a review site or a court docket, does not give anyone permission to license it. Permission belongs to whoever created and holds the material, under its own contracts. A useful rule of thumb for partners: trace each record to its author. Records the company authored and keeps in its own systems may be licensable after review; records it can merely see, or that others wrote about it, are not the company's to license.
Read → - Purchase order mismatch resolution exception example: an approved quantity change that never reached AP
The records that explain a purchase order mismatch are the ones that show what each system believed at each moment and who settled the difference: the PO and every revision with its approval, the receipt and any override note, the invoice and the hold it triggered, the case or email that asked why, the correction to the PO, and the release with its reason. In the Illustrative case below, a correct invoice was held for ten days because an approved change never reached the ERP.
Read → - Purchase order mismatch resolution records across systems: a system map from PO revision to hold release
Three links reconstruct purchase order mismatch resolution across systems: a PO number and line number that both the procurement suite and the ERP share, a revision number on every change, and a reference from each hold release back to whatever justified it, such as a case number or the corrected revision. With those, a held invoice rebuilds by ID from approval to payment. Without them, someone matches by supplier, date and quantity, and some cases will not match at all.
Read → - Purchase order mismatch resolution: what to inventory before a procure-to-pay rollout
Before a procure-to-pay rollout, inventory purchase order mismatch history as linked evidence: every PO revision with its approval, the receipt events posted against each line, the invoice holds the match produced, and the correction or release note that cleared each one. Record which system holds each piece, how many years it covers, who owns it and the date the old procurement module will be retired. Then introduce the procure-to-pay head, and through them the person who can authorize a licensing discussion.
Read → - Purchase price allocation: when acquired data is recognized as a separate intangible asset
In a purchase price allocation under ASC 805, acquired data is recognized apart from goodwill only if it is identifiable: it arises from contractual or legal rights, or it could be separated and sold, transferred or licensed. Databases and customer lists can qualify; ownership gaps and confidentiality limits can defeat it. Confirm each judgment with your auditors.
Read → - QA scoring redesign: why CX analytics advisors should ask whether initial and adjudicated scores are both kept
Sometimes, and a QA scoring redesign is when it gets decided. Many contact centers keep a first evaluator score, an agent dispute and an adjudicated or calibrated decision, but a new scorecard often carries forward only final scores, mapped to new criteria. CX analytics advisors can ask the company's authorized owner one metadata question: are initial scores and adjudicated decisions both retained? If yes, and the company wants to explore licensing, introduce its decision-maker to SourceX.
Read → - Quality assurance exceptions: a specialist referral conversation, run on a QA-history permission checklist that shows whose say each part of an exception file depends on
A quality assurance exception file is worth raising with a client's CEO when the company's own people wrote its core: the investigation, the corrective action and the check that the fix worked, measured against the company's own specifications. Before raising it, run each part of the file through a permission checklist. Some parts the company can decide about alone, some wait on a contract, some belong partly to customers or suppliers, and the originals stay where regulation keeps them. The CEO decides whether to talk; SourceX's rights review settles the rest.
Read → - Quality scoring disagreement, worked step by step: one split QA score and the records each decision left
The records that explain a scoring exception are the ones a split decision leaves behind: the call snippet both reviewers cited, each reviewer's score and comment, the calibration session where the split was raised, the adjudication note with the rule applied, the corrected score, and the dated form change that followed. Together they show a rule being interpreted, not just applied. A partner asks the quality director how many such splits exist and how far back, then introduces the executive who can authorize a licensing discussion.
Read → - Quality scoring disagreements history: what to inventory before a QA vendor change
Before a QA vendor change, inventory the records behind scoring disagreements: calibration sessions, each reviewer's score for the same interaction, the call snippets they cited, the adjudication notes that settled the split, and the form versions in force at the time. Note which platform holds each, how many years are covered, who owns them and when the old vendor's access ends. Keep it at metadata level, then introduce the quality director, who can bring in the executive with authority to license.
Read → - Quality scoring disagreements system map: which system holds each record and which key joins them
Rebuilding a quality scoring disagreement takes four joins: the contact center's interaction ID stored on each evaluation, the snippet timestamps that place reviewer comments on the recording, reviewer and adjudicator IDs that survive staff turnover, and the form version in force on the session date. A fifth link, from the interaction to the customer account, brings in the context a ruling may depend on. With those keys, one split decision can be followed from the call to the ruling to the changed form.
Read → - Quantity-to-progress-claim record chain: the revision and claim keys that join model, takeoff, claim sheet and ERP
A contractor connects quantity-to-progress-claim records by writing a reference at every hand-off and checking it survives: the model revision on each quantity export, the revision on each line of the claim sheet, the claim number in the ERP, and the measurement date on any adjustment. Most hops carry a natural key. The hop from claim sheet back to model revision does not, because a person types the sheet, and that gap is where one installed item can be billed under two revised models.
Read → - Quantity-to-progress-claim records across Autodesk, Excel and the ERP: a sample metadata packet for an introduction
A referral partner can describe a contractor's quantity-to-progress-claim history without opening a model, a spreadsheet or a claim. The useful facts are metadata: which model platform holds the revisions and since when, how quantities are extracted, where monthly claim sheets are built and whether each month's sheet is kept, which ERP holds certified claims, whether sheets record the model revision they used, and who owns each step. The case to flag is one quantity counted in two revised models.
Read → - Quarterly Referral Planning for Professional Advisors
A quarterly referral planning process for advisors involves reviewing existing networks against SourceX's company baseline, strategically planning introductions, and tracking the status of open referrals. This systematic approach helps maximize referral opportunities and ensure timely follow-ups.
Read → - Quasi-identifiers and re-identification risk in workplace data
Quasi-identifiers are ordinary fields, such as job title, office, project name and timestamp, that identify a person when combined. Removing names alone does not de-identify emails or tickets. Generalizing precise values, suppressing rare combinations and testing group sizes reduce the risk. Under a SourceX license, SourceX de-identifies the data, through approved processing routes, before it is used or shared.
Read → - Questions LPs ask GPs about AI in 2026, and how to answer them
LPs ask GPs about AI in four areas: where AI is deployed across the portfolio and what it has changed, how AI risk is governed, how the firm itself uses AI, and whether AI creates new revenue or threatens existing businesses. The best answers are specific, evidence-backed and staged, and describe new revenue such as data licensing without projecting proceeds.
Read → - QuickBooks Desktop discontinued: what to do with old company files
When a client's QuickBooks Desktop version is discontinued, confirm the exact version and its dates with Intuit, find every company file, make backups and test a restore, then choose between a supported Desktop product, a migration or a read-only archive. Export a standard report pack to open formats, and review what the history is worth before archiving it.
Read → - QuickBooks to NetSuite migration: what to do with the history left behind
Many QuickBooks to NetSuite migrations load balances and a limited window of detail, leaving older history in the QuickBooks file. For a company with 50+ full-time employees at peak, the owner should decide what happens to it before the file is retired, including whether a SourceX assessment of its licensing value is worthwhile.
Read → - R&D credit for AI development projects: what the records show and what to do next
AI development can support an R&D credit claim in some cases, depending on the facts and the tax rules. Credit studies examine experiment logs, evaluations and engineering decisions, and the same evidence shows how deep a client's records are, which an adviser can raise with SourceX separately and with permission.
Read → - R&D credit for architecture and engineering firms: funded research and who owns the work
For architecture and engineering firms, an R&D credit study turns on who funds the work and who holds substantial rights in it. The same contract review shows which records the firm owns and which belong to clients, so an adviser learns early whether a permissioned licensing introduction to SourceX could make sense.
Read → - R&D tax credit documentation: what to keep, and how it doubles as a records inventory
R&D tax credit documentation should tie every claimed cost to a specific project and to evidence of the technical work: design documents, tickets, code reviews, test results, and wage allocations with a stated method. Check the current Form 6765 instructions for the tax year. The same records also show whether a company holds engineering history AI developers license.
Read → - R&D tax credit for manufacturers: which process records a study uses
A manufacturing R&D credit study draws on engineering change orders, trial run logs, nonconformance and CAPA records and BOM revision history. For advisers, the same records show how deep a client's operational history runs, which is the first screen in a SourceX licensing introduction raised separately and with permission.
Read → - Rate parity exception review history: what to inventory before a channel contract renewal
Before a channel contract renewal, inventory the records that explain each past rate parity exception: the dated rate snapshots, the rate plan and inclusion definitions behind each price, the channel mapping, the distribution terms in force on that date, and the correction or decision that closed the case. Note the years each covers, the system and owner, and when access to the outgoing channel manager or shopping tool ends. Partners collect only that metadata and introduce the person who can authorize a licensing discussion.
Read → - Rate parity exception review system map: where each record lives and the codes that join one case
The rate plan code is the spine of every price-gap case. Every other record joins to it: the snapshot through the channel's room or rate name and the stay date, the channel mapping through the channel product ID, the rate plan definition through its effective dates, the direct price through the stay date, the distribution terms through channel, market and effective dates, and the correction record through a case ID. With those keys a flagged gap can be rebuilt end to end; without mapping history and rate plan versions it cannot.
Read → - Rate parity exception, worked step by step: a cheaper-looking package and the records each decision left
The records that explain a rate parity exception are the ones that let a reviewer compare like with like: the dated rate snapshot that raised the flag, the rate plan definitions with their inclusions, the channel mapping, the distribution terms in force that day, the decision that closed the case and the correction that followed, checked by a later snapshot. A flagged price gap is often a mapping error or two different products, not an undercut, and only that chain tells them apart.
Read → - RCM company acquisitions: separating BAA-bound data from firm-owned records
For an RCM acquisition, PE teams should set aside provider-client PHI and screen for firm-owned operating records such as payer-rule libraries, appeal playbooks and QA methods. Preserve those exports before platform consolidation, and introduce companies that pass the screen to SourceX.
Read → - Rebate claim reconciliation exceptions: the records that explain a disputed rebate
The rebate records that explain an exception are the ones that let someone repeat the calculation: the contract tiers with effective dates, buying-group membership dates, invoice-line purchase history, the claim as submitted, the approval note citing the governing clause, and the credit memo or deduction that settled it. Together they show the problem, the authorized action and the checked result. A pricing systems advisor describes them at metadata level and introduces the commercial finance head.
Read → - Rebate claim reconciliation records across systems: a map of the keys that join one claim
Reconstructing a rebate claim needs four joins: the customer account to the agreement in force on each invoice date, the agreement to the eligible invoice lines, the claim to its approval, and the approval to the money that moved, whether a credit memo or a deduction a customer took on a payment. The rebate tool, the ERP, receivables and the claim file each hold one part. A partner maps which keys exist where, at metadata level, and introduces the commercial finance head.
Read → - Recommending a vendor to a client: an ethics checklist for business lawyers
When a lawyer recommends a vendor such as SourceX and takes no fee, the main ethics questions move from fee rules to confidentiality, conflicts and documentation: get the client's consent before sharing its identity, confirm you hold no personal interest, record the recommendation in a file memo and suggest independent review of the terms. State rules vary.
Read → - Recovery loops workflow example: three import runs from a $143,580 shortfall to a signed reconciliation
A recovery loop is a run of attempts in which each failure is checked, diagnosed and fixed before the next try, until a defined check passes. In an ordinary business, it looks like a migration team importing open receivables three times: the first run lands $143,580 short, the second $18,400 over, and the third matches the legacy control exactly before the controller signs off. The valuable record is the whole sequence, not the clean final number.
Read → - Recruiting firm acquisitions: can the owner link original placement terms to later guarantee decisions?
Sometimes, and an acquisition is when it gets tested. A recruiting firm's fee terms usually sit in client agreements, its placements and guarantee periods in the ATS or back office, and its refund, replacement and goodwill decisions in emails, credit notes and manager approvals. If those are still linked, the owner holds a record of how guarantee terms were actually applied. Ask before systems are consolidated. If the firm is eligible and interested, introduce its decision-maker to SourceX.
Read → - Reducing cloud storage costs: what to check before deleting old data
To reduce cloud storage costs without regret, tier or archive old data before deleting it, and run a one-page value check first. Cleanup programs hit the oldest data first, which is often the long operational history AI labs and data users value. Fractional CFOs can approve deletions only after an owner confirms what is being removed.
Read → - Referral agreement audit and reporting rights: what a partner can reasonably expect
A referral partner's audit and reporting rights come from the signed agreement and program terms, not from a general law. Expect status by stage and a payout statement showing how each reward was calculated, and negotiate any inspection right before signing. For SourceX partners, a referred company's first qualifying transaction pays the greater of USD 50,000 plus 5% of the Actual Supplier Payout (eligible licensing compensation SourceX actually pays the referred company, excluding separately itemized taxes and expense reimbursements) and 15% of it, repeats within the 12-month Repeat Window pay 15%, with no cap, subject to any signed Schedule A or addendum.
Read → - Referral agreement tail provisions: are you still paid after the agreement ends?
A referral agreement tail provision keeps your right to be paid for introductions made during the agreement when the deal closes or the money arrives after it ends. For SourceX introductions, that depends on the signed partner agreement and published terms, so confirm the attribution window, survival wording and payment condition in writing instead of assuming an M&A-style tail.
Read → - Referral attribution vs contact protection: two timelines that never merge
No. Contact protection and the 90-day attribution window run on separate clocks and answer separate questions. Attribution decides whether your introduction is credited: the first valid introduction of a new company within 90 days is credited when that company submits a verified application. Protection comes from the partner agreement and guards qualifying contacts you introduced during its term for six months after the agreement ends. The program terms say it directly: the 90-day window does not extend because contact protection under the agreement continues.
Read → - Referral expected earnings calculator: a spreadsheet you fill with your own odds, with no built-in conversion rate
Work out two numbers per company and keep them apart. The completed figure is what you would receive if a deal closes: on the company's first qualifying transaction, the greater of USD 50,000 plus 5% and 15% of the Actual Supplier Payout you assume. The expected figure is that amount multiplied by your own odds that the company gets through every stage. The USD 50,000 floor applies once per referred company and is a minimum on one transaction, never a forecast. This guide builds a spreadsheet that holds both, with every probability left for you to enter.
Read → - Referral fee clawbacks: when a paid reward can be reversed
A referral fee clawback is a contract term that lets the payer recover a fee already paid when the underlying revenue is later refunded or reversed. Search your agreement for refund, offset and overpayment language. For SourceX, the published terms and your signed partner agreement control, not this guide.
Read → - Referral fee disclosure rules for CROs, trustees, assignees and receivers
Restructuring professionals should assume any referral reward tied to an estate or distressed client must be disclosed, may need court approval and, in some fiduciary roles, should be declined. The answer depends on your role, the retention or appointment order, bankruptcy rules on connections and compensation, and any ethics code that binds you as a lawyer, CPA or turnaround professional.
Read → - Referral income for fractional CFOs: how vendor programs compare
Fractional CFOs earn referral income mainly from cost-reduction firms that share a slice of client savings, service and software vendors that pay a bounty or a recurring share of billings, and one-time introduction rewards such as SourceX's data-licensing program. Because you see and often approve client spending, choose by conflict risk first and disclose every arrangement.
Read → - Referral partner, reseller or service provider: choose the role you will actually perform, by who pays you, whose side you are on and what you may touch
Pick the role by the work you will actually do and by who pays for it. A referral partner introduces a company's CEO and steps back, and is paid by the program. A service provider does work for the client and is paid by the client. A reseller buys and sells on its own paper, which a SourceX data license does not allow, because the company licenses directly to SourceX. Holding the first two roles at once is possible only with disclosure and a client who agrees, and sometimes the honest choice is to stay small or decline.
Read → - Referral reconciliation system map: the referral ID and dated mappings that join four systems
Two things rebuild a referral across systems: a referral ID that survives every hop, from request to appointment to ticket to returned report, and location and provider mappings kept with their effective dates. With both, the referral intake, the scheduling platform, the service desk and the report inbox can be stitched into one case. Without them, matching depends on patient details, which a de-identified history cannot use.
Read → - Referral reward 60-day payment conditions: a timeline that applies each prerequisite without restarting the clock
If a payment condition is still outstanding on day 60, the reward is paid promptly once that condition is satisfied, and no new 60-day period begins. The 60 days run from the later of two anchor events, the Acquisition Partner’s final written acceptance of the complete, validated dataset and completed handoff of that dataset, and the five other prerequisites do not move that anchor. The practical answer is to clear your own conditions early and raise SourceX-side ones in writing.
Read →
Free resources
- Business succession planning assessment — Ten questions on successor, transition and documentation.
- NPV calculator — Net present value with a discounted cash flow table.
- Time value of money calculator — Future and present value with optional regular payments.
- All free tools · MCP resource center
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