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
- Call recording retention policy: what to keep, what to purge and what to list first
A call recording retention policy sets which calls and meetings are recorded, how long each category is kept, who can place a legal hold and how deletion runs. Before any automatic purge, the company should inventory what it holds, using counts, dates, notices and linked outcomes only, so leadership can still decide whether the archive has licensing value.
Read → - Call transfer recovery history before a CCaaS migration: the record classes and their last access dates
Before a CCaaS migration, inventory the records behind each transfer that went wrong: the routing histories that link one customer call across queues, the transcript segment for each leg, the CRM case the call belonged to and its final resolution. For each, note the years covered, who administers it and the date access really ends. Keep it at metadata level: the head of customer operations can usually answer, and the introduction goes to the executive who can authorize a licensing discussion.
Read → - Call transfer recovery system map: where each record lives and the IDs that join one case
Reconstructing a call transfer recovery takes four joins: each call leg to the leg it came from, every leg to the whole call, the whole call to the CRM case, and all of them to timestamps that agree across systems. The second and third joins decide everything. If legs share an initial call ID and the CRM case stores it, a reviewer can follow a lost-context transfer to its resolution; if the case holds only a phone number, the telephony history and the case history stay apart.
Read → - Can a former portfolio company still be referred? Yes, after a seven-check test of who controls it today
Yes. Leaving the portfolio does not take a company out of reach: funding status plays no part in eligibility, and a company the fund sold three years ago faces the same tests as one it holds today. What the exit changes is who can say yes and how much of what you know is still true. Before anyone contacts the company, confirm from dated evidence who controls it now, check that it still passes the fit tests, and let today's CEO decide whether the conversation happens.
Read → - Can a Pennsylvania CPA accept a referral fee? Rules, sources and disclosure steps
A Pennsylvania CPA can accept a referral fee only where both the state's rules and, for AICPA members, the AICPA Code allow it. The Code rules out commissions where the firm audits, reviews or performs certain other attest work for the client and requires permitted ones to be disclosed; Pennsylvania's CPA Law and State Board of Accountancy regulations may add requirements, so read them first.
Read → - Can a supplier in a corporate ecosystem be a referral candidate? Yes, on its own record: a screening sheet that splits what the supplier keeps into its own operations, work done for the corporate and the corporate's data
Yes. A supplier is its own company, and SourceX screens it like any other: a full-time workforce that reached 50 or more at its peak, a history of records produced in its own work, clear rights to license those records, and a chief executive who asks to talk. The corporate relationship supplies none of these. What it does create is a three-way split inside the supplier's records: some describe its own operations, some were produced while serving the corporate and may sit under that customer's terms, and some are the corporate's data. Sort that split before anyone asks.
Read → - Can an advisor network reveal companies your CRM misses? A five-state coverage audit that counts only the CEO relationships an advisor will use
Yes, but only a slice of what advisors know is a gap worth acting on. A fund CRM records the firm's own deal activity, so established, owner-led businesses that never sought venture money are thin in it, while operating advisors and venture partners often spent their careers inside such companies. Run each company an advisor names against the CRM, keep the rows where the advisor knows the CEO and will ask, then test the published fit facts before anyone contacts the company.
Read → - Can an unsigned data license count as a going concern management plan?
Usually not. Under the US GAAP going concern standard, ASC 205-40, management's plans are generally weighed on whether they are probable of being implemented and effective, and an unsigned license depends on a buyer and a counterparty's signature. Pursue it alongside financing, disclose it accurately and agree the wording with your auditor.
Read → - Can I explore a referral without uploading company files? Yes: an eight-step walk through the metadata-only start, and the one step where a record first leaves the company
Yes. Neither the introduction nor SourceX's first step needs a single file. The partner never handles records, and SourceX's fit check takes three screens with no files, passwords or API tokens, licensing or transferring nothing. The company describes its systems, its years of history and what could be exported, and that description is enough for an indicative licensing estimate. Records stay with the company through both signatures; data is first extracted only after the CEO signs a Dataset Deal Confirmation and SourceX gives the go-ahead.
Read → - Can two funds collaborate without promising a split reward? Yes: a twelve-line no-assumed-split checklist that names one introducer, writes down what the other fund contributes and decides before outreach whether any side agreement exists
Yes, and the program's design makes it the default. SourceX credits one partner per company and pays any reward to that partner alone, from its own funds; it has no mechanism for dividing a reward between firms, and no fund can promise another a share on SourceX's behalf. Two funds collaborate cleanly when they agree in writing, before anyone contacts the CEO, which fund introduces, what the other contributes, and that no share is owed unless a separate agreement signed by both says otherwise.
Read → - Can your client document abstention examples? Five questions for introducers
Ask five things: where the company records a stop when evidence is missing, whether it kept the incomplete package as it arrived, who receives escalations, whether clean cases are kept beside stopped ones, and who could authorize a licensing discussion. Abstention examples are records of a person correctly declining to act and escalating instead, such as a contract administrator who holds a renewal because an exhibit is missing. The answers show whether those records exist or only sound plausible.
Read → - Can your client document evaluation holdouts? Five questions for introducers
Ask five questions: do closed cases have locked close dates, is the final outcome stored with each case, has the archive ever left the company, can IT show who accessed it, and who could authorize a licensing discussion. Together they separate records that could actually support an evaluation holdout, a set of real cases kept out of training so an independent assessor can test an AI system, from an opportunity that only sounds plausible. None of them requires seeing a file.
Read → - Can your client document recovery loops? A five-question discovery card for introducers
A recovery loop is a run of attempts in which each failure is checked, diagnosed and fixed before the next try, until a pass condition is met. Ask a controller or IT lead five questions: where failed-run reports go, whether fixes between attempts are recorded, whether a written pass condition exists, how many such projects were archived, and who can authorize a licensing discussion. Three or more concrete answers suggest kept records rather than a theoretical opportunity.
Read → - Canceled SaaS seats and disappearing archives: an introducer's timing map
Before a seat is removed or a subscription lapses, an owner should verify four things for each system: the vendor's documented grace window for that exact plan, who can still export during it, whether any hold or retention policy keeps data longer, and who signs off on preservation. Windows checked on 2026-10-18 run from 20 days (a deleted Google Workspace user) to 120 days (a lapsed Microsoft 365 business subscription). An introducer's job is to flag the date, not touch the data.
Read → - Candidate ownership conflict history: what to inventory before a recruiting firm merger
Before a recruiting firm merger combines two candidate databases, inventory the records that show how ownership conflicts were settled: submission timestamps in each ATS and in each client portal, the client terms that define who represents a candidate, the firm's own representation confirmations, and the adjudication notes that record each decision. Note years covered, which instance holds each, who owns it and when either system's access ends. The commercial operations head can usually answer; the introduction goes to the executive who can authorize a licensing discussion for the merged firm.
Read → - Candidate ownership conflicts across ATS and client portals: a system map of records and linking keys
Reconstructing a candidate ownership conflict takes three joins: a person match between the two ATS instances that both held the candidate, a submission match between each ATS and the client portal on requisition and time, and a decision record that cites both submissions and the client clause it applied. If any join fails, the case falls apart into separate records that cannot explain each other. The map below shows where each record sits, which key links it, who owns it and where the link usually breaks.
Read → - Carve-out data separation: who keeps and can license the records after a divestiture
In a carve-out, who can later license historical records depends mainly on the separation documents: the purchase or separation agreement allocates records and intellectual property, and any transition services agreement governs data the seller keeps hosting. Advisors should settle ownership, post-closing access and licensing rights before closing so the right CEO can sign.
Read → - Cash application exceptions across bank feed, remittance and ERP: a system map of records and linking keys
Five linking fields carry a cash application exception from bank to ledger: the amount, value date and payer reference that tie a bank entry to its remittance; the invoice numbers and line amounts that tie the remittance to open items; the settlement ID that records how cash was applied; the case ID that carries a short amount into a deduction investigation; and the credit memo number that closes it. If any one of those fields lived only in a tool the company has retired, the case cannot be rebuilt.
Read → - Cash application exceptions retention timeline: what disappears first in a vendor switch
Before a cash application vendor switch, inventory the record classes the outgoing tool holds that the ERP does not, the years they cover, who owns each one, and the exact date access ends. Match logs and applier notes usually disappear first, at cutover; remittance images and deduction cases go when read-only access ends. Bank statements and ERP settlements tend to survive. Work backward from the end date, and leave every keep-or-delete decision to the controller and counsel.
Read → - Cash application exceptions: the records that show how a short payment was resolved
The records that explain a cash application exception are the ones that show the mismatch and the decision that resolved it: the bank entry, the remittance advice, the matching decision in the ERP, the deduction or dispute case, the approval at the right level, and the credit memo, rebill or repayment that closed the balance. Together they connect an initial problem to an authorized action and a checked result, which a matching rule alone never records.
Read → - Catalog correction records across systems: a map of PIM, marketplace and ticket keys
Five joins hold a catalog correction case together: product to listing, listing to rejection, rejection to correction ticket, correction to template change, and correction to accepted resubmission. The usual keys are the SKU mapped to a marketplace item ID, the SKU plus the issue date, a ticket ID that quotes the SKU or issue code, and a family or template ID. Each system holds only one side of each join, so a PIM export alone cannot reconstruct the case.
Read → - Catalog correction worked case: a compliant product rejected for inconsistent attributes
The records that explain a catalog exception are the ones that show a product moving from rejected to accepted, and why: the PIM version before the change, the marketplace rejection with its issue and attribute, the decision about what to fix, the version that fixed it, the resubmission that cleared, and any wider change that stopped it recurring. A clean catalog export shows only the end state. The correction history shows the judgment, and it usually sits in three systems.
Read → - Catalog correction workflow history: what to inventory before a catalog platform consolidation
Before catalog platforms are consolidated, inventory the record classes that explain each catalog correction: the listing versions before and after the change, the marketplace rejection with its reason, the ticket or note that assigned the fix, the approval, and the resubmission that was accepted. Record the years covered, which PIM and marketplace accounts hold each class, who owns them, and when the old platform stops giving access. Partners gather that metadata only and introduce whoever can authorize a licensing discussion.
Read → - Catalog rollout: the source, decision and scope question data governance advisors can ask
Often for the source, rarely for the other two. A catalog rollout makes a company list its record groups and connect scanners, which usually answers where records come from. Few owners can also say which business decision each group documents and what contracts permit for it. Data governance advisors can ask that three-part question while the catalog is being built. If the gaps can be closed and the company qualifies, the owner may want an introduction to SourceX, which licenses approved business data for AI training and evaluation.
Read → - Catalog-to-order-correction records across Akeneo, Magento and the ERP: matching orders to the right product version
A company connects catalog-to-order-correction records by matching each order's timestamp against two clocks: when the product attribute changed in the PIM, and when that change reached the storefront. When two catalog versions share one SKU, the order line alone cannot say which version the customer bought. Akeneo version history, Magento order dates and the ERP's correction records together can, and a partner can describe whether those clocks exist without reading any of them.
Read → - CCaaS procurement: can the company link call segments to final resolutions?
Sometimes, and CCaaS procurement is the right time to find out. A transferred call usually becomes several segments: IVR, first agent, a transfer, sometimes a callback days later. Linking them to the final resolution needs a shared contact ID across legs and, for later callbacks, a case or ticket number. Contact-center consultants can ask the owner whether that chain is intact before the old platform is retired. If it is and the company qualifies, the owner may choose an introduction to SourceX.
Read → - CCPA B2B exemption expired: are CRM and email contacts personal information?
Yes, they can be. California's temporary exemptions for business-contact and employee data ended on January 1, 2023, so names, work emails and direct lines in CRM, support and email systems may be personal information for covered businesses. Owners may need to pseudonymize those fields before records are licensed.
Read → - CCPA deidentified data: the three commitments a company must make
CCPA deidentified data must meet three conditions beyond removing names: the business takes reasonable measures against linkage, publicly commits not to re-identify, and contractually binds recipients to the same rule. Missing any one leaves the data as personal information. SourceX agrees de-identification requirements with the company before any data moves and de-identifies the data, through approved processing routes.
Read → - CCPA employee data exemption expired: what it means for licensing workplace records
The CCPA employee data exemption expired on January 1, 2023, so covered California businesses must treat staff and applicant information like consumer data. For a company licensing records, that means checking notices, excluding sensitive fields and agreeing de-identification rules before any work begins, with the company's own counsel deciding what applies.
Read → - CCPA risk assessments and AI training: the 2026 CPPA regulations
The CPPA's risk assessment, cybersecurity audit and automated decisionmaking regulations took effect January 1, 2026, with some deadlines phased in through 2028. A risk assessment may be needed for activities such as selling personal information or training automated decisionmaking technology, and de-identified scopes can reduce the burden. Counsel confirms what applies.
Read → - Centers of influence: how exit planners build a referral network around business owners
A center of influence (COI) is a professional who already advises the people you want to reach and can introduce you on trust, such as a business owner's CPA, attorney, banker or wealth advisor. For exit planners, a COI network built around owners of companies with 50+ full-time employees at peak makes a data licensing introduction a natural, low-pressure conversation.
Read → - CEO peer group meeting topics for 2026, with a ready-to-run AI and company data block
A strong 2026 CEO peer group meeting topic is what a company's internal records are worth to AI developers. Run it as a 60-minute block: the facts on data licensing, a records walk, a rights round on customer contracts and employee notices, an explore-park-pass decision for each member, and an opt-in follow-up instead of a pitch.
Read → - CFO priorities for 2026: AI agents, data quality and the records inventory behind both
CFO priorities for 2026 come down to three linked goals: moving AI agents from pilots into daily finance work, fixing the data quality and access those agents depend on, and adding capacity without adding headcount. The systems-and-records inventory agents require also shows whether historical records could be licensed with SourceX, a separate decision that belongs to the owner.
Read → - Chain-of-thought data: why business memos and analyses qualify
Chain-of-thought data is written reasoning with visible steps, and business memos, root-cause analyses, reconciliations and design documents qualify because experts write them to justify decisions that are later checked against outcomes. Partners look for functions that document their working and record results.
Read → - Change approval records: introduce the process owner first, then the CEO, using an approval workflow owner map that names who writes, who stores and who decides at every step of a change
Change approval records show how a company decides to alter its systems: the request, the risk assessment, the approval or rejection, the work itself and the review afterward. The first conversation belongs with the change process owner, usually a change manager or head of IT service management, because only that person can say who wrote each step, which tool holds it and what came from vendors or clients. The process owner informs and sponsors; the CEO decides whether the company discusses licensing. Map owners at metadata level and request no tickets.
Read → - Change collision records across systems: a key map from ServiceNow to on-call and CMDB
Five keys rebuild a clash between two approved changes: the change number, which ties each change to its approval, its conflict result and later its rollback; the CI ID, which ties a change to the components it depends on; the service name, which ties those components to what monitoring watches; the alert ID, which ties monitoring to the incident; and the incident number, which ties the response to the correlated change and the review. ServiceNow holds the change and configuration side, monitoring and on-call tools hold the response side, and the review often sits in a wiki. Break any one key and the case becomes unrelated tickets.
Read → - Change collision recovery history: what to inventory before an ITSM consolidation
Before an ITSM consolidation, inventory the records that explain how change collisions were caught and undone: change requests with their approvals and planned windows, conflict detection results, CMDB dependency records and their history, monitoring alerts and change events, rollback approvals and post-incident reviews. Note years of coverage, the owner of each source and the date old instances lose read access. Keep it at metadata level, then introduce the decision-maker through the service delivery director.
Read → - Change collision worked case: two approved changes, one outage, one rollback
The records that explain this kind of failure are the ones that show two changes passing review separately, the failure they caused together, the decision about which one to roll back, and the fix to the process afterward: both change requests and their approvals, the conflict check result, the monitoring alert, the incident with its correlated recent changes, the emergency rollback approval, the restore time and the post-incident review. Each change record looks clean alone. The value is in the set.
Read → - Change of control and assignment: what happens to a data license when the company is sold
A change of control clause in a license agreement decides whether a sale of the licensor triggers notice, consent or termination. As a general rule, in a stock sale a data license stays with the company and binds the new owner, while in an asset sale it must be assigned, often with the licensee's consent. Wording and governing law decide.
Read → - Channel revenue is not supplier payout: a money-flow map of the five amounts in a data-licensing introduction, and the one your firm can count
Supplier payout is the compensation SourceX actually pays your client for its licensed data. It belongs to the client and never passes through your firm. Channel revenue, for a SourceX partner, is a different payment: a reward SourceX funds separately, worked out on the company's first qualifying transaction as the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap. It exists only once the payment conditions in the program terms are met; before then, any figure is an estimate. Count the reward as your revenue, never the payout and never the price the data sold for.
Read → - Chapter 11 plan books and records destruction: drafting an assessment window
Liquidating chapter 11 plans often let the liquidating trustee or plan administrator destroy the debtors' books and records after a set period or once the case closes. Counsel can add a short carve-out that preserves electronic operational records until they have been assessed for licensing, and spell out who may authorize a license once the records vest in the trust.
Read → - Chapter 11 preparation checklist: the pre-filing records review for CROs
A chapter 11 preparation checklist should include a records review: map every system and its retention settings, stop deletions, read the privacy policy for limits on transferring personal information, identify records that could be licensed as non-core assets, and plan the court approval and lender consent a license would need after filing.
Read → - Chargeback evidence assembly across systems: a map of the records and keys that join one dispute
Five keys reconstruct a card dispute across systems: the payment provider's dispute ID, the charge or transaction ID, the retailer's order number, the shipment tracking number and the support ticket ID. The payments platform holds the first two, order management holds the order number and tracking, the delivery tracking tool holds the scans, and the support desk holds the ticket. A case is fully joined when every hop still carries its key and the card-issuing bank's outcome is stored against the dispute.
Read → - Chargeback evidence assembly records: when the delivery record contradicts the customer
The records that explain a chargeback exception are the customer's first claim, the evidence that answered it and the issuer's decision: the dispute record with its reason code and deadline, the order history, the carrier's delivery scan, any later customer messages, the evidence packet the merchant submitted, and the adjudication result. Joined case by case, they show how a disputes team tested a claim against the record and what the issuer accepted.
Read → - Chart of accounts redesign: map legacy history before collapsing it
Redesign a chart of accounts by building an old-to-new crosswalk, archiving the full old ledger and mapping history instead of summarizing it away. The crosswalk also shows how many years of records and subledgers exist, a fit signal a CFO can raise with the owner.
Read → - Check language coverage before suggesting global fit: a three-group country sort and a five-line attestation for multinational portfolios
Do not tell a multinational portfolio that SourceX works everywhere. The published rule sorts companies into three groups: the U.S., Canada and the EU qualify on location; nine further markets qualify only when at least 70% of the data is in English; everywhere else is not on the list. Sort each operating entity first, then ask its team to attest, in writing and from their own counts, how much of the data they would offer is English. You never sample records yourself.
Read → - Chief AI officer at a PE-backed portfolio company: from AI adoption to data assets
A chief AI officer at a PE-backed portfolio company usually owns internal AI adoption, but should also ask the outbound question: which of the company's own records AI labs and data buyers would license. The AI leader maps systems, rights and customer promises; the CEO, CFO and counsel decide; SourceX handles qualification, rights review, buyers and delivery.
Read → - Chief revenue officer at a PE-backed company: a new revenue line
A data license at a PE-backed company is usually run by the CEO or CFO, not the sales team. The chief revenue officer supplies CRM history and call recording notices, protects customer relationships, and keeps the one-time revenue out of bookings, ARR and quota.
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