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
- Customer contract data use restrictions to check before licensing company records
Customer contract data use restrictions usually decide what a company can license. Before licensing records for AI training, counsel should read each customer agreement's definitions, confidentiality, data use, aggregated-data, ownership and return-or-destroy clauses, keep customer-owned information out of scope, and check privacy promises. The contract text controls, and this is general information, not legal advice.
Read → - Customer escalation recovery exception examples: a worked case where one critical issue spans three product teams
The records that explain an escalation exception are the ones that tie the warning to the response and the result: the health signal that dropped, the ticket that framed the problem, each team's fix, the executive updates that set commitments, the remedy finance approved, and the renewal or churn decision at the end. The hard case is a critical issue that spans several product teams, because no single queue owns it. Below is one such case worked step by step, all Illustrative, followed by how to recognize similar cases at a client.
Read → - Customer escalation recovery records across systems: a map of the keys that join helpdesk, success platform, CRM and email
To reconstruct a customer escalation recovery across systems, you need four kinds of link: an account identifier shared by the helpdesk, success platform and CRM; ticket numbers quoted in engineering issues and billing approvals; timestamps that line up across systems; and executive updates that name the account or ticket. With those keys, a health signal, three tickets, two fixes, a credit and a renewal become one case. Without them, they are unrelated documents. This page maps each system, its records, the key that joins it and its owner, then walks one fully joined Illustrative case.
Read → - Customer escalation recovery records: what to inventory before a customer platform renewal
Before a customer success platform renewal, inventory the record classes that show how at-risk accounts were recovered: health score changes, escalation tickets, executive updates and the renewal decision that followed. Note which system holds each class, how many years it covers, who owns it and when access to the old platform really ends. Keep the inventory at metadata level, then introduce the person who can authorize a licensing discussion, usually through the customer success director.
Read → - Customer onboarding histories: what can a partner say publicly? Ten sample sentences sorted into post it, CEO-approved wording only and never, with the reason each one lands there
In public, talk about onboarding records as a category and about how the referral program works, and stop there. Anything that names or could identify a client, says its records exist or are available, describes its customers or its onboarding method, or hints at a deal stays private, and reaches anyone only in wording the client's CEO has approved in writing. SourceX's own deal terms say neither side publicizes a deal. A partner who is not even a party to it has less reason still.
Read → - Customer profitability analysis: joining ERP, CRM and support data step by step
Run a customer profitability analysis by taking revenue and direct cost from the ERP, adding cost to serve from CRM activity and support tickets, and ranking contribution margin by customer. The join also shows a fractional CFO how many systems and years a client keeps, a fit signal that stays inside the company.
Read → - Cutover reconciliation system map: which system holds each record and the key that joins them
To reconstruct a cutover reconciliation you need five links: the mapping version stamped on each load run, the run ID on the import log, the run ID and count name on each reconciliation, the ticket key cited beside every count gap, and the approver and date on each accepted exception. Those keys join records held in five or six different systems. Lose the first link and nobody can say which rules produced which numbers.
Read → - Cyber insurance renewal questionnaire: what the answers tell brokers about data assets
A cyber insurance renewal questionnaire already asks about systems, backups, retention, cloud vendors and incident response, and some answers reveal years of well-kept operating records. Commercial brokers can note those signals, then raise a SourceX introduction with the owner in a separate conversation after binding, without using or sharing any underwriting information.
Read → - Cybersecurity services roll-ups: a data licensing screen for PE teams
In a PE roll-up of MSSP and MDR firms, the SIEM and SOAR platforms you retire hold years of triage history that a qualifying company may license. Screen for separable process records, then exclude client logs, CUI and CMMC-scoped work. Companies need 50+ full-time employees at peak and an authorized sponsor.
Read → - Data as collateral: what secured lenders should know about borrower records
Borrower records can fall within a secured lender's collateral, typically through an all-asset lien covering general intangibles, but their value depends on ownership, privacy promises and whether anyone can still export them. Because many credit agreements restrict exclusive licenses of collateral, a borrower usually needs lender consent before licensing records, which can turn a license into a negotiated paydown source.
Read → - Data assets in an ABC: how an assignee can sell or license company records
In an assignment for the benefit of creditors, a company transfers its assets, including databases and system archives, to an assignee who holds them in trust and liquidates them for creditors. Subject to state law and the assignment document, the assignee can sell or license those data assets, but privacy promises, client contracts and system shutdowns limit what remains.
Read → - Data break to repair, before and after: what a Snowflake-only export loses about a pipeline fix
A Snowflake-only export keeps what ran and when: query text, start and end times, the user or role that ran it. It loses almost everything that explains a repair: which dbt test failed and how many rows it caught, the Jira ticket that diagnosed the cause, the commit that changed the model, the rerun that passed, and whether finance accepted the corrected number. Query history records execution. The reasoning that turns a rebuild into a repair lives in dbt artifacts, Jira and often a chat thread.
Read → - Data governance for PE portfolio companies: a minimum viable set of four controls
Data governance for a private equity portfolio company can start with four controls rather than a data office: a named owner for every system, a written retention schedule, quarterly admin access reviews and a rights register showing who created the records and what contracts allow. The same four documents are the base of a defensible data license.
Read → - Data license indemnification clauses: what counsel should check before a client signs
A data license indemnification clause decides who pays when licensed records turn out to infringe someone's rights, break a privacy promise or leak. For a company licensing records to an AI developer, counsel should tie each indemnity to a specific warranty, cap it sensibly, match security duties to real controls and check how insurance responds.
Read → - Data licensing in cross-border due diligence: what a foreign buyer will ask
A foreign buyer's due diligence on a US target should be expected to ask whether the company has licensed records for AI training, to whom, on what exclusivity and for how long, what was delivered, whether personal data was involved and how the payment was booked. Sell-side advisers should have the agreement, inventory, delivery record and rights analysis ready.
Read → - Data licensing introductions during a CRM migration
A CRM migration can surface sales and customer workflow histories. Migration access is not licensing permission. The company decides whether to go ahead, and rights and privacy questions are worked through in SourceX's rights check with the company before any records are considered.
Read → - Data licensing introductions during a founder retirement
Founder retirement can prompt a review of operating archives and decision-making authority. A founder’s personal access does not itself establish permission to license company records. The introduction needs a current authorized sponsor.
Read → - Data licensing introductions during a helpdesk migration
A helpdesk migration can prompt a review of support archives and knowledge bases. These records may include personal, confidential or third-party information. Share broad context only and leave assessment and permissions with the company and SourceX.
Read → - Data licensing introductions during a restructuring
A restructuring may reveal company-controlled archives, but approval authority and rights must be clarified first. Do not present a possible data license as assured funding or a substitute for professional restructuring advice.
Read → - Data licensing introductions during a software consolidation
Software consolidation can reveal operating records spread across current and legacy tools. A useful introduction describes systems and history without exporting records. Consolidation is not a reason to combine sensitive data or expand access.
Read → - Data licensing introductions during an acquisition integration
Acquisition integration can surface inherited operating archives and changing access responsibilities. First establish who controls the records and who can approve an introduction. Acquisition alone does not establish licensing rights or SourceX's current data needs.
Read → - Data licensing introductions during an email platform migration
An email migration can reveal operating history, but mailboxes may contain personal, privileged or third-party information. Introduce an authorized company contact without sharing messages. Migration access does not establish a right to license email content.
Read → - Data licensing introductions during an ERP replacement
An ERP replacement can surface finance, procurement and operations histories that may merit assessment. Their presence does not prove SourceX's current data needs or licensing eligibility. Start with an authorized contact and a system-level description.
Read → - Data mapping for privacy compliance that doubles as data licensing prep
Data mapping for privacy compliance means recording every system that holds personal information, the categories inside it, its owner, its purpose and how long data is kept. Add two columns, years of history and export route, and the same map covers most of the data inventory a company completes before licensing records directly to SourceX.
Read → - Data monetization consulting: where external data licensing fits and when to refer it
Data monetization consulting usually focuses on internal analytics, pricing and data products sold to customers. Licensing operational records directly to SourceX for AI training is a separate route with its own rights review, buyers and contracts. Consultants can keep advising on the first two and refer suitable US clients to SourceX, which manages licensing from rights review to delivery and payment.
Read → - Data monetization trends in 2026 and where AI data licensing fits
Data monetization in 2026 follows three trend lines: using data inside products and operations, sharing it under privacy-preserving controls, and licensing records directly to SourceX for training and evaluation. The third suits mid-size operating 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 deep, rights-clear records; SourceX manages that licensing, and referral partners make the introduction.
Read → - Data referral conversion benchmark: how to count introductions that reach a paid data deal
A company-data referral conversion study should fix its cohort first: every introduction credited by a verified application within a stated date window. That group is the denominator, and nobody leaves it. The endpoint should be a completed, paid data handoff, not a meeting or signature. Choose one observation cutoff, report every case as converted, declined, withdrawn or still open, and publish the range the open cases allow instead of quietly dropping them.
Read → - Data referral partner quality study: comparing partner roles by rate, not by count
Compare partner roles by the share of each role's introductions that reach the same milestone within the same time window, not by how many companies each role introduced. Fix the cohort age (for example, every introduction at least 180 days old), use introductions as the denominator, show an interval beside each rate, and split by company profile before ranking. A role that sends many companies will always lead on count; it leads on quality only if its rate holds up.
Read → - Data referral program vs AI training jobs: choose the right route
An AI training job pays a person for their own time: rating model outputs, writing examples, reviewing answers, usually at an hourly rate per project. A company-data referral pays an introducer for connecting a qualifying company that then licenses its business records. At SourceX, the reward on a company's first qualifying transaction is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, and it is paid only after the data is accepted and paid for. One sells your hours; the other introduces someone else's records.
Read → - Data referral rejection reasons study: a taxonomy and reporting standard for declined introductions
A referral program should report declined introductions the way clinical and systematic-review standards report exclusions: state the eligible sample first, code each decline with one primary reason from a written taxonomy, record the stage where it happened, and show the counts in a flow from entry to outcome. Attribution outcomes, such as duplicates, and companies that withdrew are reported separately, because neither is a judgment about the company's records.
Read → - Data referral renewals and repeat licenses, worked through: installments, parallel licenses and reductions with no cap per company
There is no cap to reset. Under the default SourceX terms a company's first qualifying transaction pays the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; a renewal or repeat license first agreed within 12 months of the first Closing pays 15% of its Actual Supplier Payout, with no ceiling on the total. The USD 50,000 element is counted once per referred company. Only a signed Schedule A or addendum can set different terms. The three worked scenarios below show the arithmetic for installments, parallel licenses and reductions, and the tracker shows how to keep count.
Read → - Data referral stage duration benchmark: measuring time per stage while deals are still open
Measure stage duration from dated status changes, one stage at a time, for a fixed cohort. Cases that have not left a stage by the cutoff are still informative: count them as censored at the cutoff rather than dropping them or pretending they finished. Then report the Kaplan-Meier median and percentiles with the number of cases at risk. If fewer than half the cohort has finished a stage, say the median is not yet reached.
Read → - Data synergies in M&A: operational value versus licensing value
Data synergies in M&A are gains from combining two companies' records. Operational synergies improve the business itself, while licensing value comes from granting AI developers rights to pre-acquisition records. Licensing needs separate tests for records, rights, consents and authority, and belongs outside the base-case synergy model.
Read → - Data-break-to-repair data linkage: joining a failed test, its fix and the verified report
A company can connect its data-break-to-repair records when a shared identifier runs from the failed test, through the ticket and the code change, to the rerun and the report someone signed off. In a Snowflake, dbt and Jira stack, the warehouse holds the queries, the model layer holds the test results, and the tracker holds the reasoning. A referral partner can describe that chain, its dates and its gaps at the metadata level, without reading a row of data. The weakest point is the change that passes every test yet alters what a number means.
Read → - Day 1 readiness in M&A: which data decisions to defer and which to block
A Day 1 readiness plan should block irreversible actions on the acquired company's legacy systems and defer every licensing decision. Integration leads can add a one-line hold with a review date, run a short records inventory in the first 60 to 90 days, then decide system by system.
Read → - De minimis asset sale procedures in chapter 11: when a records license fits the order
De minimis asset sale procedures are case-specific chapter 11 orders that let a debtor sell lower-value assets on short written notice instead of filing a separate motion each time, usually with value tiers and liens attaching to proceeds. A records license fits only if the order reaches licenses, the price sits within a tier and no exclusion applies.
Read → - De-identified workflow data utility: keeping the links an AI needs without promising anonymity
De-identification can keep a workflow intact by replacing each identifier with a consistent token, so the ticket, the work order, the notes and the invoice still point to the same case without naming the customer. Dates can be shifted by a fixed offset that preserves intervals, and free text can be masked in place. None of this makes data anonymous: linked tokens and remaining details still carry re-identification risk, which is managed through context, contracts and review rather than promised away.
Read → - De-identifying free text under HIPAA: emails, notes and tickets
De-identify free text under HIPAA by classifying sources, excluding patient-facing queues, running entity detection, replacing identifiers consistently, reviewing samples by hand, and choosing Safe Harbor or Expert Determination. Free text fails quietly because identifiers hide in sentences. SourceX agrees redaction requirements with the company before any work begins.
Read → - Deal killers in due diligence, and the records problems behind them
The most common deal killers in due diligence are earnings that do not hold up, customer concentration or churn, undisclosed liabilities, owner dependence, and records problems: unclear code or IP ownership, missing contracts, deleted archives and privacy consent gaps. The records problems matter twice, because they also decide whether a company can ever license its data.
Read → - Defect closeout verification exception examples: a worked case of a repaired ceiling stain that came back next door
The defect closeout records that explain an exception are the linked ones: the punch item with every status change, the before and after repair photos attached to each step, the rejection when a fix was not accepted, the test that proved the real cause was fixed, and the acceptance record that names the root cause. The hard exception is a repaired defect that reappears in a linked area, because only the linked history shows what actually went wrong. Below is one such case, Illustrative and built for this page, worked step by step, followed by how to recognize similar histories at a contractor.
Read → - Defect closeout verification records across systems: a map of the location, item and subcontract keys that join one defect
To reconstruct defect closeout verification across systems, you need four links: a location key that means the same room in every system, an item ID that survives reopening, a photo-to-item link that survives export, and an acceptance record that lists the item IDs it covers. A fifth, the subcontract or back-charge number, ties the defect to who paid for it. The inspection platform and the project system rarely share all of these, so this page maps which system holds each record, the key that joins it, who owns it, and what one fully joined Illustrative case looks like.
Read → - Defect closeout verification: what to inventory before asset handover
Before asset handover, inventory the full life of each defect, not just its final closed status: the punch item with every status change and reopen, the repair photos before and after, the acceptance record with who signed it and when, and any link between items that share a root cause. Note which system holds each, the projects and years covered, who owns them and when access ends. Then introduce the executive who can authorize a data discussion; licensing depends on rights, qualification and the proposed use.
Read → - Deliverable acceptance revisions exception example: a rejected revision worked step by step
The records that explain a deliverable exception are the acceptance criterion in the contract, the revision that missed it, the reviewer comment that named the miss, the response that set out the fix, the corrected revision, and the signed acceptance. Kept together and dated, they show what went wrong, who decided each step and how the result was checked. The case below is Illustrative: one report that passed every format check and still failed acceptance.
Read → - Deliverable acceptance revisions system map: which system holds each record and which key joins them
Reconstructing deliverable acceptance revisions takes four systems and four shared keys. The project platform holds milestones under a deliverable ID; document control holds each revision under that ID plus a revision number; the contract file holds criteria and acceptance under a contract line item; finance holds the milestone invoice under the same line item. A case is fully joined when every record carries a key another system shares. Each missing key is a gap to note, not a reason to stop.
Read → - Deliverable acceptance revisions: what to inventory before contract closeout
Before contract closeout, inventory the records that explain each accepted deliverable: the contract milestones and acceptance criteria, every submitted revision, the reviewer comments that sent a revision back, the response to each comment, and the acceptance record itself. Note the years covered, the project platform and document control system holding each, the owner, any retention clause, and the date project workspaces are archived. Keep discovery at metadata level, then introduce the program operations director.
Read → - Demurrage invoice appeals exception example: a customs hold that changed the charge window, step by step
Six records explain this kind of exception: the arrival and gate-out events, the free-time clause, the inspection hold and its lifting, the bill, the written challenge and the credit that settled it. Read in date order, they show when the goods could legally leave, when charges started, which days the importer contested and what the shipping line conceded. The Illustrative case below follows one box whose free days ran out while inspectors held it.
Read → - Demurrage invoice appeals system map: the identifiers that join terminal, clearance, inbox and ERP records
Five shared identifiers stitch one demurrage dispute together: the container number, the bill of lading number, the customs entry number, the carrier's invoice number and the service contract number, with the ERP's own vendor bill and credit memo IDs tying the ledger entries to each other. Each identifier sits in some of the five places that hold the case, never in all of them. The fragile join is usually the inspection hold, recorded only in a clearance agent's message whose entry number appears nowhere in the ledger.
Read → - Demurrage invoice appeals: what to inventory before a port vendor change
Before a port vendor change, inventory the three records that explain each demurrage appeal: the container events from the port or terminal portal, the free-time terms from the tariff or service contract, and the appeal outcome booked in the ERP. Record which system holds each, the years covered, who owns them and when portal access ends. Then introduce the executive who can authorize a data discussion; whether the records can be licensed depends on rights and qualification.
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