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
- Entitlement exception, worked step by step: an acquired customer loses a feature after an account merge
The records that explain an entitlement exception are the plan history for each account, the approval that allowed a non-standard grant, the permission change that carried it out, the ticket that confirmed it worked and the billing amendment that settled it at renewal. In the Illustrative case below, an acquired customer lost a feature after an account merge. Seven decisions by seven roles, from the merge to the renewal, each left a dated record in one of four systems.
Read → - Environment reproducibility: recreating one inventory mismatch in an ERP sandbox, and the records that make it possible
Environment reproducibility means the starting conditions of a task can be rebuilt so that anyone repeating it begins from the same place and sees the same problem. In an ordinary inventory workflow, that means recreating one stock mismatch in a safe test copy of the ERP: the same posted records up to count day, the same software version and extensions, the same expected quantity, and a written note of anything that could not be copied, such as a live integration.
Read → - EOS annual planning: how implementers can put data assets on the Issues List
In an EOS annual planning agenda, a data asset question fits as a single Issues List item, handled through IDS like any other issue. Implementers should word it neutrally, run a three-question intro test, disclose any partner arrangement up front, and leave the final decision with the leadership team.
Read → - EOS Integrator responsibilities in a data licensing project
In a data licensing project the EOS Integrator typically sponsors the work: naming a steward, running the records inventory, coordinating rights review and keeping the weekly cadence. The Visionary, owner or another authorized representative still decides on exclusivity, approves price and terms, and signs. Nothing is binding until the company signs.
Read → - Equipment dispute system map: where each interchange record lives and the keys that join one move
Three keys carry nearly every reconstruction of a disputed equipment move: the equipment number (container or chassis), the load or booking reference, and the time of each handover at the gate. A fourth, the dispute ID, ties the money back to the argument. Each lives in a different system: the asset tracker knows equipment and time, the dispatch mailbox knows the reason, the provider's bill knows the charge, and accounting knows the credit. When one system drops its key, the dispute can no longer be followed from start to finish.
Read → - Equipment finance company acquisitions: which credit and servicing records can be licensed?
Sponsors can screen equipment finance and non-bank lenders for licensable credit approvals, collections workflows and servicing records. Confirm 50+ full-time employees at peak, several years of linked history, clear rights and guarantor privacy handling, then introduce the company to SourceX, which handles inventory, SourceX review, contracting and delivery.
Read → - ERP and CRM consultants: answering 'is exporting our data safe?'
Exporting CRM or ERP data for a license is safe when it happens late, narrowly and under the company's control: only after an executed agreement, by the company's own admins, within an agreed scope and redaction plan, through routes the software vendor's terms allow. The consultant who made the introduction should never run, receive or store the export.
Read → - ERP consolidation after acquisitions: what ledger and workflow history to keep
When consolidating ERPs after acquisitions, most teams migrate opening balances, open transactions and a short window of detail, then retire the acquired system. Before retirement, keep a complete, queryable archive of transaction detail and the workflow trail around it: approvals, match exceptions, credit holds, memos and change logs, none of which the trial balance shows.
Read → - ERP consolidation in a PE portfolio: assess each legacy archive before shutdown
When a PE portfolio consolidates add-ons onto one ERP, several legacy systems retire at once and their history usually migrates only in part. Operating partners should screen each entity's archive before decommission, confirming years of records, export access, rights and an authorized sponsor, then introduce qualifying companies to SourceX for a data licensing assessment.
Read → - ERP implementation SOW confidentiality: what may a partner say?
Implementation MSAs and SOWs usually treat client business information as confidential, so an ERP consultant making a SourceX introduction should share only basic fit information, and only with the client's permission. Never share records, configurations or project documents. This is general information; confirm with counsel.
Read → - ERP vendor selection: which decisions vanish in a clean-data migration?
A clean-data migration usually carries master data and open transactions into the new ERP, and leaves behind the record of how exceptions were decided: price overrides, credit-hold releases, three-way-match variances accepted, write-offs with reason codes. During vendor selection, ask which of those operational decisions would vanish if only clean data moved. If the answer is "years of them" and the company is eligible, introduce its owner to SourceX, with the reward disclosed.
Read → - Error localization: finding the step where a lab correction picked up the wrong unit
Error localization is finding the earliest step in a process where a record became wrong. In an ordinary business workflow, errors usually surface far from where they start: in this page's fictional laboratory case, a clinician notices an impossible glucose unit, but the unit was introduced one system earlier, by an interface template, after a technologist had corrected the number properly. Localizing the error means checking the value at each hop until the first bad one is found.
Read → - Estimating Referral Earnings in Client Conversations
In client conversations about potential SourceX referral earnings, focus on understanding their data licensing needs and clarifying SourceX's role. 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. Emphasize the referred company's control over what it approves for licensing under agreed terms.
Read → - EU AI Act Article 10: the data governance questions buyers ask suppliers
Article 10 of the EU AI Act requires providers of high-risk AI systems to apply documented data governance, with relevant, representative datasets and bias examination. The duty is the buyer's, but US data suppliers are asked for provenance, preparation logs, coverage and known gaps to support it. Counsel should read the current consolidated text.
Read → - EU AI Act training data summary: what it means if you license your company's data
The EU AI Act training data summary is a public document that general-purpose AI model providers must publish, using a Commission template, and licensed datasets are one section of it. The duty is the provider's, not the supplier's, but buyers may ask you for provenance, rights and redaction details to describe your dataset.
Read → - Evaluation holdouts in a freight audit workflow: one worked example from invoice to sealed test case
An evaluation holdout is a set of real, closed cases kept out of any training data and used only to test whether an AI system makes the right decision. In an ordinary freight audit workflow, that means sealing a batch of carrier invoices whose short-pay decisions have already been confirmed or reversed by the carrier, so an assessor can compare a model's call with the recorded outcome. The records each audit step leaves behind are what make the seal credible.
Read → - Exception handling records: the part of a workflow AI agents fail on
Exception handling records are the logged cases where a process failed, with who decided, what they decided and why. AI agents handle routine cases and escalate exceptions, so these dispositions and reasons are scarce training material. Operating partners can scan portfolio companies for them and introduce qualifying businesses to SourceX.
Read → - Exception routing calibration across systems: a key-by-key map of case, rule and review records
Four joins rebuild one calibrated case: case to the rule that sent it somewhere, case to the response clock it was given, case to each reviewer's label, and the reviewers' ruling to the edit it caused. A shared case ID carries the first three; a session ID cited in a change ticket carries the fourth. Expect three systems, sometimes four. The case side is usually intact. The links into the rule log and the label sheet are the ones that fail.
Read → - Exception routing calibration, worked step by step: a safety case misrouted to the warranty queue
The records that explain how an exception was handled are the ones that let someone replay it: the case as it arrived, the rule that fired and its version, the queue and SLA it got, the calibration sample that caught it, each reviewer's label, the ruling that settled their disagreement, and the rule change that followed. The worked case below follows one safety report misrouted to a warranty queue through those seven records, then shows how to recognize similar cases at a client.
Read → - Exception routing calibration: what to inventory before a routing engine replacement
Before replacing a routing engine, inventory the calibration history: the sampled cases reviewers re-checked, the routing labels they assigned, the reviewer decisions and baseline rulings, each version of the routing rules, and the SLA policy each case received. Record the years covered, which system holds each record, who owns it, and when the old engine or its logs go dark. Keep it at metadata level, then introduce the quality operations head to start the conversation.
Read → - Excluded assets in an asset purchase agreement: can the seller keep its data?
Excluded assets are the items an asset purchase agreement expressly leaves with the seller, such as cash, tax refunds, corporate records and named contracts. Data can be excluded too, or the seller can keep copies or take a license-back, but only if the point is negotiated before the APA is drafted and its asset definitions are fixed.
Read → - Excluded assets in an asset purchase: the records left behind in the seller entity
In an asset purchase, records the buyer does not take, often historical email, archives and closed-file history, stay with the seller entity as excluded assets. If the seller keeps the rights and the data, and someone can still sign for it, those records may be licensable with SourceX after closing, producing additional proceeds for the seller entity.
Read → - Exit planners and referral fees: how to disclose a reward and keep the owner in control
Exit planners should disclose a referral reward in writing before the introduction, inside the engagement documents the owner already signs, and say plainly that the owner decides. A dated clause, a one-line note at introduction and a closing record show the owner was informed and free to decline.
Read → - Exit planning for business owners: the steps, and where a data license fits
Exit planning for business owners means setting goals, valuing the company, choosing a route, fixing gaps, preparing the transition and, optionally, deciding whether to license its records. A data license sits beside a sale, transfer or recap, not in place of it, and the owner keeps ownership of the data.
Read → - Exit planning timeline: how long it takes, and when to raise data licensing
Exit planning commonly starts three to five years before a planned transition. Raise data licensing early, during discovery and value building, so any license is signed and documented before a banker or broker takes the business to market. After a letter of intent the buyer effectively shares the decision; during an earnout it belongs to the buyer.
Read → - Exit planning value acceleration: where business records fit as a non-operating asset
Value acceleration in exit planning raises transferable business value by closing gaps in earnings, management depth, customers and systems before a sale. Licensing a company's operational records sits beside that work as a one-time, non-operating source of proceeds, not an EBITDA lever: buyers will normalize it out, so planners should present it as cash, never as a higher multiple.
Read → - Expense policy exception review across systems: a map of the records and the keys that join them
Reconstructing an expense policy exception takes five joins: the expense report to the travel booking by booking reference, to the corporate card feed by transaction ID, to the HRIS by employee ID as of the trip date, to the policy library by version and effective date, and to payroll or AP by payment batch. The HRIS join breaks most often, because grade, cost center and manager are frequently overwritten when people change roles.
Read → - Expense policy exception review records: what explains a flagged expense and the decision on it
The records that explain an expense policy exception are the receipt, the policy version in force on the relevant date, the audit flag the expense system raised and the rule behind it, the employee's comment, the reviewer's note with the reasoning, the amount finally reimbursed, and any policy clarification that followed. Together they show a problem, an authorized decision and a checked result. A partner describes those record classes, systems and years at metadata level and introduces the finance leader who can authorize a licensing discussion.
Read → - Failed automation review: the run-to-repair question workflow automation agencies can ask
Often only partly, and a failed automation review is where you find out. When a workflow automation agency audits broken Zaps, scenarios or flows, it sees two halves of each incident: the failed run with its error, and the human repair, such as a corrected record, a changed step or a manual replay. If the company keeps both and can connect them, the owner may want an introduction to SourceX, which licenses approved business data for AI training and evaluation.
Read → - Failed automation to policy repair record chain: run IDs, ticket numbers and article versions, key by key
A company connects failed-automation-to-policy-repair records through a chain of keys. The run ID joins the failed run to its alert ticket, usually automatically. Ticket numbers then have to be typed into macros, article version notes and later tickets by people, which is where the chain weakens. A single version note that cites the first ticket can hold the whole history together; without it, the article change looks unrelated to any failure. Partners can map which keys exist, and from which year, without opening a run, ticket or article.
Read → - Failed-automation-to-policy-repair records: a metadata packet for failed runs, helpdesk repairs and knowledge base revisions
A referral partner can describe a company's failed-automation-to-policy-repair records without opening a run payload, a ticket or an article. The packet holds metadata only: which automation platform runs the workflows and how long it keeps run history, which helpdesk records the human repair, which knowledge base holds the operating instructions and their revisions, rough volumes, how each step is joined to the next and who owns each system. The gap to ask about is the workaround that never reaches the documented process.
Read → - False-positive closure across systems: a map of where each record sits and the IDs that join them
Rebuilding a false-positive closure takes five joins: the case to its alerts by alert ID, the alert to the detection by rule ID and version, the case to the change or request ticket by ticket number, the alert's account to the identity provider by user principal name, and any automated closure to the automation rule that made it by rule ID. Each key lives in a different system, and losing one leaves a verdict nobody can re-check.
Read → - False-positive investigation closure: what to inventory before a SIEM replatform
Before a SIEM replatform, inventory the records behind each closed false positive: the detection rule version that fired, the analyst's evidence and notes in the case manager, the closure verdict, and any exclusion or suppression the closure produced. Note which system holds each, the years covered, who owns it, and the real date old-platform access ends. Then introduce the company's SOC director, who can bring in the executive and counsel with authority to license.
Read → - Family business decision making: aligning shareholders on a data licensing decision
Family shareholders reach a sound decision on a data license when they work from one shared facts sheet, discuss it in a structured family meeting, and settle in advance who has authority to approve and sign. Because the company is not bound until it agrees price and terms and signs, the family can explore first and decide later.
Read → - Family business succession planning: where operating records fit in the plan
Family business succession planning moves a company's ownership, leadership and family wealth to the next generation or, if heirs decline, to a buyer. A complete plan also inventories what the business holds, including years of operating records, so the family can decide on a data license before control changes and while the founder still knows the systems.
Read → - Family business succession when the next generation does not want it
When children do not want the family business, owners can sell to an outside buyer, sell to management or employees, hire a non-family CEO, merge, or wind down. Licensing operational records is not a succession route, but for qualifying companies it can provide one-time proceeds while the family decides.
Read → - Family office direct investing: adding a data license to companies you own
Family office direct investing means the office buys stakes in private operating companies with its own capital, often control positions held for decades, instead of only committing to funds. For offices that own qualifying companies, licensing years of operational records to SourceX can bring in a one-time payment without dilution, new debt or a sale.
Read → - Family office direct investment risks and the records blind spot
The main risks of family office direct investing are thin deal teams, weak monitoring, concentration and limited board influence. A less discussed one is not knowing which records an owned company holds or who controls them. A records-and-rights map reduces that risk and shows whether a SourceX data license is possible.
Read → - Family office investment committee process for direct deals
A family office investment committee approves direct deals through a sourcing log, diligence plan, written memo, committee discussion, vote and regular monitoring. Adding a standing item on records and rights at owned companies lets the same committee review a SourceX licensing screen and name the sponsor who approves it.
Read → - Family office value creation when there is no operating team
Family offices without operating partners create value in owned companies through governance rather than headcount: an engaged board, a capable CFO, a steady reporting cadence and a few outside specialists. A data licensing introduction suits that model: the office makes one introduction, while SourceX acts as the company's direct licensing partner, licensing approved business data for AI training and evaluation. SourceX manages the agreement, rights review, data preparation, delivery and payout, subject to acceptance at Closing and agreed terms.
Read → - Family offices buying operating companies in 2026: what is driving it and what to check
Family offices buy operating companies directly because they can hold them indefinitely, which suits founders planning succession, and a large wave of owner transitions is coming. After closing, principals should add one item to the post-close checklist: whether the company's operating records could be licensed with SourceX without changing who owns the business or its data.
Read → - FCRA and staffing firms: background-check data in a data license
Staffing firms generally cannot license consumer reports or data derived from them, because the FCRA limits use to permissible purposes. Job orders, recruiter playbooks and client-service records may be licensable after redaction and a rights check. Counsel decides the scope, and SourceX agrees redaction requirements with the company first.
Read → - Feature flag incident rollbacks: the records that explain how a rollback exception was handled
The records that explain a feature flag rollback exception are the flag change itself (which flag, environment and targeting rule, who changed it and when), the incident messages that say why, the recovery check that shows whether it worked, and the postmortem that records the decision. Together they show the problem, the authorized action and the checked result. A partner asks the engineering director whether those records still link, then introduces someone who can authorize a licensing discussion.
Read → - Feature flag rollback records across systems: a system map of the keys that join one incident
To reconstruct a feature flag incident rollback, four keys have to survive across five systems: the incident ID (alert to incident to postmortem), the flag key (incident to flag change), the environment name (flag change to the exact rule edited) and a time window (flag change to the recovery check). The incident side is usually well joined. The weak link is between the incident and the flag platform, where the join often rests on timestamps alone. Ask the engineering director which keys exist, then introduce a decision-maker.
Read → - FERPA and EdTech vendors: which student records are excluded from a data license?
EdTech vendors generally cannot license student education records they hold under a school's authority, because use is limited to the purpose the school authorized. Their own engineering, finance, sales and support records may still be licensable after rights review and redaction. Counsel should confirm the position under FERPA, state law and district contracts.
Read → - Fiduciary duties of a sponsor-appointed director at a portfolio company
A private equity board designee owes fiduciary duties to the portfolio company, and in a corporation to its stockholders as a whole, while also owing duties to the fund as a sponsor employee. Scope depends on entity type, state and governing documents. Any personal or firm benefit, including a SourceX referral reward, needs disclosure, recusal where advised and compliance sign-off.
Read → - Field guide: identifying companies with internal knowledge bases for data licensing
Knowledge management advisors can identify eligible companies by focusing on entities based 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 50+ FTEs, deep operating records, and rights to license their data. Prioritize those with well-structured internal knowledge bases as prime candidates for data licensing with SourceX.
Read → - Field inspection notes: the referral questions about original work, and a ten-question checklist that sorts every line by who wrote it and who can say yes
Ask who wrote each part of the note before asking anything else. A field inspection note often combines an inspector's own observations with stock sentences from a comment library, text pasted from a code or manual, client drawings and photos of someone else's property. Only material the company itself created and has the right to license can be in scope, and SourceX asks the company to confirm that nothing was created or altered with AI for the sale. Your job as a specialist advisor is to find the CEO and ask bounded questions, never to read the notes.
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