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
- Insurance commission record chain: the keys that carry a statement line from policy to journal entry
An agency connects its statement-to-reconciliation records by mapping which field each system uses for the same thing. The policy number is the natural key from placement to statement line. The statement number bridges the agency system and the reconciliation tracker, and the journal entry number bridges the tracker and the ERP. Most chains hold until a cancellation lands on a later statement, because the ERP rarely carries the policy number and the first reconciliation is already closed.
Read → - Intangible asset monetization strategies for private, non-tech companies
Private companies monetize intangible assets in five main ways: licensing them, selling or assigning them, contributing them to a partnership, packaging know-how as a service, or borrowing against them. For mid-sized non-tech companies, years of operational records are the intangible most often overlooked, and a data license turns them into a one-time payment while the company keeps ownership.
Read → - Integration cutover reconciliation: what to inventory before a legacy application sunset
Before a legacy application is switched off, inventory the reconciliation trail of its cutover: every version of the field mapping, the import and validation logs for each load, the count reconciliations, and the exceptions that someone accepted in writing. Note where each record lives, how long it is kept and who owns it, because run logs in ETL tools can expire within weeks. A systems integrator records only metadata and introduces the implementation director plus the executive who owns the data.
Read → - Interchange dispute retention timeline: what disappears first when a dispatch platform is upgraded
Before an interchange or dispatch platform upgrade, inventory each record class behind exception resolution: where it sits, how many years it covers, who owns it, what ends its life and on what documented date. The softest records disappear first. Tracker pairings can break at cutover, a departed dispatcher's mailbox can be permanently deleted 30 days after the account is removed, and old platform access ends with the vendor contract. Accounting records usually last longest. Keeping any of it is the records owner's decision, not the partner's.
Read → - Interchange exception resolution: the records that show how a missing handover was settled
The records that explain an interchange exception are the handover messages (driver and dispatcher replies), the equipment records (interchange receipts, tracker events, the provider's billing timeline), the delay decisions written down at the time, and the dispute file with the credit or rebill that settled it. Together they show the gap, the evidence, the decision and the money that moved. A partner asks the operations director how complete those files are, then introduces the executive who can authorize a licensing discussion.
Read → - Intercompany reconciliation hard case, step by step: one shipment booked in two different periods
The records that explain an intercompany reconciliation exception are the two entity entries that disagree, the reconciliation item that caught the gap, the evidence used to decide which side was right, the approved correcting entry with its reason code, the elimination that then cleared, and any rule changed afterwards. Together they show a problem, a judgment and a checked result. The worked case below is Illustrative and follows one shipment that a parent and its subsidiary booked in different months.
Read → - Intercompany reconciliation records: what to inventory before a multi-entity ERP rollout
Inventory the history that explains each intercompany difference, not just the balances: the paired invoices and bills with their journal references, the entity and account mappings, the reconciliation items with reason codes, the correcting entries and who approved them. A multi-entity ERP rollout often carries only opening balances, so ask which of these move, which stay in the old system and when it is switched off. Then introduce the controller's executive sponsor if the company qualifies.
Read → - Intercompany reconciliation system map: the keys that join both entities' records into one case
Rebuilding one intercompany case across systems takes five keys: a document number shared by both entities' postings, a counterparty code read through the mapping that applied at the time, a match item ID quoted by the fix, a journal reference the consolidation picks up, and an approval ID tied to that fix. Every key sits in a different system with a different owner. Lose one and the case scatters into postings nobody can pair.
Read → - Introducer agreements: what UK and international partners should know
An introducer agreement is a contract paying a person a fee for introducing a business opportunity. Outside the US, SourceX partners work as referral partners under the program terms. UK-style introducer rules apply mainly when the introduction concerns a regulated product, so check your own regulator and adviser.
Read → - Introducing data licensing during an email migration: An advisor playbook
Advisors can identify companies with valuable data during email platform migrations, helping them monetize historical information. This playbook guides you through assessing fit, preparing the introduction, and making a referral while adhering to strict privacy and scope boundaries.
Read → - Introducing Data Licensing During Founder Retirement: An Advisor's Playbook
Advisors can strategically introduce data licensing to founders considering retirement, ensuring a fit with SourceX's criteria and adhering to a structured process. This approach helps founders unlock value from their company's data assets while protecting privacy and operational integrity.
Read → - Inventory discrepancy hard case, step by step: two bins printed with the same location label
The records that explain an inventory discrepancy exception are the count variances that raised it, the recount that confirmed it, the investigation note that named the cause, the movement history that proved which stock went where, the approved adjustments with their reason code, and the follow-up count that showed the fix held. The worked case below is Illustrative: two bins carry the same printed label, so a short count and an over count cancel out at site level.
Read → - Inventory discrepancy investigations: what to inventory before a warehouse consolidation
Before a warehouse consolidation, inventory the discrepancy investigations as linked records: cycle counts, movement logs, approved adjustments and the incident tickets that explain them. Note which systems hold each, the years covered, who owns them and when old-site access ends. A WMS consultant should keep this at metadata level and introduce the warehouse director, who can bring in the people with authority to license.
Read → - Inventory discrepancy system map: the keys that join warehouse, device, ERP and write-up records
Rebuilding a stock variance case across systems takes five keys: the storage location as it was named on the day, the item number, the task ID of the count or pick that touched the stock, the order or receipt number behind a movement, and a write-up reference quoted on the correction. Each key lives in a different place, from the warehouse system and handheld devices to the ERP and wherever investigators write. If one is missing, the case breaks into records that no longer point at each other.
Read → - Invoice processing rollouts: where AP automation advisors find rejected-invoice trails worth an introduction
Often yes, but the rollout is where that history gets lost. Many AP systems record a rejected invoice with the approver's reason, a duplicate flag or a matching discrepancy, then the new tool migrates only open and posted invoices. Before cutover, ask the company's authorized owner one metadata question: do the records retain rejected invoices and the reasons for rejection? If they do, and the company wants to explore licensing, introduce its decision-maker to SourceX through the referral route.
Read → - Invoice-to-payment data linkage: which purchase order version did the reviewer see before the payment run?
A company connects invoice-to-payment records by carrying the purchase order number and its version from procurement into receiving, invoice verification, any review file and the payment run, and by noting which version each person actually looked at. In a setup with SAP Ariba for ordering, SAP for receipts and invoices, and SharePoint for review files, the weak join is the version. When a changed order never reaches the person approving the bill, the bill is correct and still gets held.
Read → - Is a referral fee based on gross revenue, net revenue or collected fees?
A referral fee is calculated on whatever base the agreement defines: gross revenue (everything billed), net revenue (after listed deductions) or fees actually collected. SourceX's base is the Actual Supplier Payout: eligible licensing compensation SourceX actually pays the referred company, excluding separately itemized taxes and expense reimbursements. On a company's first qualifying transaction partners earn the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; repeat transactions agreed within 12 months pay 15%, and a transaction qualifies from USD 100,000 of Actual Supplier Payout, subject to any signed Schedule A or addendum. SourceX funds rewards separately; they do not reduce the company's payout.
Read → - Is AI training fair use, and what does it mean for licensed business data?
There is no blanket answer: in the US, whether AI training is fair use is decided case by case, weighing four factors against the facts of each lawsuit, and the litigation is still moving. Licensed business records largely avoid the question, because the buyer trains under express permission in a signed license rather than relying on a fair-use defense.
Read → - Is an association's referral income taxable as UBIT or excluded as a royalty?
It depends on how passive the arrangement is. A tax-exempt association can owe tax on income from an unrelated trade or business it regularly carries on, but royalties are generally excluded under IRC 512(b)(2). Payments for active promotion or services, such as per-introduction referral rewards, tend to fall outside that exclusion, so structure the arrangement with tax counsel.
Read → - Is data referral work worth a platform team's time? A zero-revenue model that counts hours per qualified introduction
Judge it on hours and founder usefulness, not on rewards. Model the pilot with zero referral revenue, because a reward becomes payable only after a referred company completes a licensing deal and is paid, which no one can schedule inside a one-quarter test. The work earns more time if founders say the conversation told them something useful and the team reaches a qualified introduction in fewer hours than its other founder services take. Stop when hours per qualified introduction climb while usefulness stays flat.
Read → - Is employee keystroke and screen monitoring legal, and can captures be licensed?
Employee keystroke and screen monitoring is often legal in the US when the employer owns the systems and gives any notice a state requires, but licensing the captures is a separate decision. Screens expose personal and customer data, so SourceX scopes them strictly, and many companies license structured logs instead.
Read → - IT support for trucking companies: when a TMS upgrade is the moment to introduce SourceX
An MSP that supports trucking companies can introduce a carrier to SourceX when it has 50+ full-time employees at peak, years of TMS, EDI and dispatch records, and clear rights. A TMS upgrade or cloud move is the natural moment, and driver and shipper data stay out of scope.
Read → - ITAR and EAR technical data: why controlled records stay out of a data license
ITAR technical data and EAR controlled technology are export-controlled engineering information about defense or dual-use items, and a deemed export can occur even inside the United States. Controlled records therefore need to stay out of any data license. A defense-adjacent manufacturer may still license non-controlled commercial records once its export lead confirms the separation.
Read → - Joiner-mover-leaver redesign: the role-change decisions identity consultants can help a company keep
Often only partly. A disabled account looks the same whether the person left or changed roles, so the distinction lives in HR status changes, service desk tickets and approved access exceptions, not in the identity platform's log alone. Before a joiner-mover-leaver redesign, identity management consultants can ask the company's authorized owner: can the owner distinguish role transfers from employee departures? If the records can show it, and the company wants to explore licensing, introduce its decision-maker to SourceX.
Read → - Kadrey v. Meta: what did the fair use ruling decide, and what did it leave open?
As publicly reported, in June 2025 a federal trial court ruled for Meta on fair use in Kadrey v. Meta, largely because the authors did not prove market harm. The court said the ruling does not make AI training lawful in general, so the decision is narrow and not binding on other courts.
Read → - Keep usage analytics out of your customer referrals: a 12-signal evidence map for SaaS partnership teams
Choose which customers hear about SourceX from evidence the customer gives you or the public record shows, never from what your product observes. Usage events, record counts in a tenant, feature adoption and support-ticket content were collected to run the service. Using them to rank customers for another company's program can step outside the purposes your contracts and privacy commitments set, and it tells customers you watch their accounts. Send one neutral invitation to a whole segment, let interested CEOs opt in, and confirm fit with them directly.
Read → - Knowledge handover gaps system map: where each record lives and the keys that join one gap
Reconstructing one knowledge handover gap takes four joins across at least four systems: the handover checklist line to the process page, the page version to its date, the page to the ticket where the exception was recorded, and that ticket to the client deliverable accepted after the fix. The page version history is the hinge, because it is the only record that dates when the documented process changed. Below is a system map with each record, its linking key and its owner, plus one fully joined Illustrative case.
Read → - Knowledge handover gaps: what to inventory before a practice acquisition
Before a practice acquisition, inventory the records that show where documented processes depended on undocumented exceptions: the handover checklists, the questions new owners raised that the documents could not answer, the page versions that changed afterward, and the deliverables accepted once the gap was closed. Note which system holds each, who owns it, and the date old spaces or projects may be archived or purged. A knowledge management advisor records metadata only and introduces the operations director with the owner who can authorize a licensing discussion.
Read → - Knowledge transfer from a retiring owner: how to capture decisions
To transfer knowledge from a retiring owner, name a project owner, list the decisions only the owner makes, record each as context, options, choice and outcome in company systems, shift approvals gradually and keep all archives. Start 12 to 24 months before handover; decisions with outcomes help successors and are valuable records.
Read → - Lab result correction histories: what to inventory before a LIMS replacement
Before a LIMS replacement, inventory each lab result correction as a chain rather than a flag: the instrument's raw data file, the result as first entered, the audit trail entry for the change, the reviewer's comment, the original and amended reports, and any corrective action. For each class, record the system that holds it, the years covered, whether it belongs to the lab or its clients, and the date legacy access ends. Then introduce the laboratory director and the executive who can authorize a data discussion.
Read → - Lab result correction system map: where each record lives and the IDs that join one correction
Rebuilding one corrected lab result means following four identifiers through four systems: the sample ID, the instrument run or batch ID, the report number with its amendment suffix, and the nonconformance or corrective action (CAPA) number. Units and method version travel with the run, and the reviewer and approver travel with the audit trail. Lose the unit or method context and the rebuilt history can be wrong in the very way the original error was. Below is a system map with each record, its key and its owner, plus one fully joined Illustrative correction.
Read → - Lead generation agencies: Become a SourceX data referral partner
Lead generation agencies can expand their services by referring 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) with extensive data assets to SourceX for licensing opportunities. Partners facilitate an introduction and earn a share of the actual supplier payout, without handling any data or managing the deal.
Read → - Lead with why this company, not the reward figure: a six-slot relevance worksheet, a name-swap test that exposes generic openers, and one message rewritten both ways
A personalized referral message names something only this company has: a record type, how many years it covers, the system it lives in and a dated event the owner told you about. The reward belongs in one disclosure line later in the message, never in the opening, because the reward figure is the partner's money, not a value for the company. If another company's name could be dropped into your first sentence without changing a word, the message is not personalized yet.
Read → - Lease abstraction correction worked case: the CAM exclusion a partial amendment erased
The lease abstraction records that explain an exception are the ones that show which words of a clause survived an amendment, how the abstract got that wrong, who approved the abstract, how the error surfaced and who approved the fix. In the Illustrative case below, an amendment replaced one sub-clause of a CAM provision, the abstract was rewritten as if the whole clause had changed, and a landlord bill three years later exposed the gap. Each step left its own record.
Read → - Lease abstraction corrections: what to inventory before a lease system migration
Before a lease system migration, inventory the records that show how each lease abstract was corrected: the executed leases and amendments, every abstract version with its change date and editor, the review notes, and the approved summary that accounting and accounts payable relied on. Note the years covered, the system holding each record, who owns it and the date the old tool goes read-only. A partner collects only that metadata and introduces the head of lease operations and the person who can authorize a licensing discussion.
Read → - Lease abstraction system map: the keys that join leases, amendments, abstract versions and rent records
Reconstructing one lease abstraction correction takes five links across at least three systems: lease to amendment, amendment to clause, clause to abstract version, abstract version to approval, and approved summary to the bill or payment that relied on it. The lease repository holds executed documents, the lease platform holds versions and approvals, and lease accounting or accounts payable holds the money. If any linking key is lost, the case reads as a change with no reason.
Read → - Legacy ERP data archiving: keep it live, archive it read-only, export it or delete it?
Legacy ERP data archiving after a migration comes down to four options: keep the old system live, freeze it as a read-only archive, export the history to a warehouse or open files, or delete it once retention duties end. Choose per record set, weighing ongoing cost, audit access, retention rules and whether the history could later be licensed.
Read → - Legal entity rationalization: which entity can license which records
After subsidiaries are merged, rights to historical records generally sit with the surviving or successor entity, but only counsel can confirm for a given structure. Advisors should map each record set to the entity that created it, the system that holds it and the CEO who decides for it today (once a company is acquired, the acquirer's CEO).
Read → - Lender motions to appoint a receiver: keeping the borrower's records as collateral
A secured lender usually asks a court to appoint a receiver over an operating business after default, citing the loan documents and the risk to its collateral. If the proposed order expressly covers books, records, cloud systems and admin credentials, and lets the receiver preserve and market them with court approval, the records become recoverable collateral, not a casualty.
Read → - Lender-owned company: a first-100-days playbook for the new board
A lender-owned company playbook turns the lenders' transition plan into a 100-day list for the new board: secure control and cash first, inventory systems, records history and data rights by day 60, and decide by day 90 whether a SourceX data license belongs in the recovery plan and which officer signs as authorized sponsor.
Read → - Leveraging Annual Client Reviews for SourceX Referrals
Annual client reviews offer a natural opportunity for accountants and consultants to identify companies with valuable data assets. This guide outlines how to recognize qualifying companies, understand timing for introductions, clarify data ownership, inventory potential archives, explain referral earnings, and identify roadblocks, ensuring a smooth and compliant referral process.
Read → - Liability management transactions in the 2026 middle market: who approves asset recoveries
A liability management transaction is an out-of-court restructuring, such as an amend-and-extend, debt exchange or priority financing, that changes a borrower's debt without a bankruptcy filing. Because no court approves asset decisions, monetizing an asset such as a data license needs board, lender and counsel sign-off under the credit documents before any introduction to SourceX.
Read → - License reclamation exceptions: what to inventory before a license true-up
Before a license true-up, inventory the records behind each reclamation exception: the assignment history (who held the license and when), the usage evidence checked before removal, the reclamation candidates a rule produced, and the approval or objection that decided each case. For every class, note the system, how far back it goes, the owner and when the underlying evidence expires. A software asset consultant collects only that metadata and introduces the asset management head and whoever can authorize a licensing discussion.
Read → - License reclamation system map: the keys that join candidates, sign-in evidence, tickets and true-ups
Reconstructing one license reclamation exception takes four joins across at least three systems: account to device, candidate to ticket, ticket to evidence, and decision to the next true-up. The asset manager holds candidates and statuses, the identity system holds the usage signals, the service desk holds objections and approvals, and procurement holds the true-up worksheet. Each join depends on one linking key surviving an export: the user principal name, the candidate number, the ticket number and an exception reference.
Read → - License reclamation worked case: the shared reception computer that looked like an inactive user
The license reclamation records that explain an exception are the ones that capture a disagreement: a rule proposed a removal, someone objected, a second signal was checked and an authorized person decided. In the Illustrative case below, a shared reception computer looked like a dormant user because the rule read only interactive sign-ins. Each step, from the rule's verdict to the next true-up, left its own record, and the sequence is what turns a removal list into evidence of judgment.
Read → - LIMS replacement: are initial results, corrections and released versions still identifiable?
During a laboratory system replacement, ask the lab owner or quality lead one metadata question: after cutover, will each result still show its initial value, every authorized correction with reason and approver, and the version that was released? If all three remain identifiable and linked, the lab holds a review history worth assessing, and you can offer to introduce its decision-maker. If the migration plan loads only the current value, that history may be lost when the old system is switched off.
Read → - Liquidity planning for business owners: a pre-liquidity guide for wealth advisors
Liquidity planning for business owners starts years before any event: map household cash needs, entity and tax structure, estate and gifting moves, and the routes to cash short of a full sale. A data license with SourceX is a separate, company-level event with its own tax questions, and any referral relationship should be disclosed before the introduction.
Read → - Loan document exception closure: what to inventory before a document system consolidation
Before consolidating loan document systems, inventory what shows how each documentation exception was opened and cured: the closing checklist, the exception note, every generated version of the affected documents, the e-sign envelope records with their event history, and the cure that closed the item. Record where each lives, how many years and loans it covers, and when the old e-sign account or imaging repository is retired. A document automation consultant collects only this metadata and introduces the lending operations head with an executive who can authorize a licensing discussion.
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