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
- Choose a ten-company pilot before a portfolio-wide launch: a selection matrix, an hours budget that assumes no reward, and the result that means stop
Pick ten companies that let the pilot answer two questions, whether founders find the conversation useful and how many platform hours it costs, rather than ten chosen for the largest imaginable payout. Choose them with a matrix of known fit facts, relationship path, founder bandwidth and dated events, plus two composition rules. Budget hours stage by stage with reward income set to $0, fix the decision date now, and stop if fewer than three of the ten CEOs want a conversation.
Read → - CIO at a PE-backed company: migrations and archive decisions
A CIO at a PE-backed company should run an exportability and retention check on every system before it is migrated, archived or deleted, because licensable history cannot be recovered once an archive is gone. Keep a restorable export with a named owner, then let the company apply later.
Read → - CIO peer groups: how to discuss data licensing with IT leaders
A CIO peer group can discuss data licensing through a 60-minute educational roundtable: members describe their systems and oldest archives, review rights and export realities, and opt in to a private introduction if their company has 50+ full-time employees at peak, years of records and an authorized sponsor.
Read → - CIPA lawsuits over AI call analytics: what they mean for companies holding call recordings
CIPA lawsuits allege that AI call, chat and meeting vendors act as unauthorized third-party eavesdroppers, often on a theory that the vendor could use conversation data for itself. Licensing de-identified historic recordings under an executed agreement is a different arrangement, but caller notices, consent and contracts still decide what counsel allows into scope.
Read → - Claim denial routing across systems: a map of the records and keys that rebuild one unpaid claim line
Six keys rebuild an unpaid claim across systems: the claim number, the line number, the payer's reason codes on each line, the routing rule ID with its version, the case ID with queue assignment timestamps, and the 835 file that closed each line. The billing system holds claims, lines, codes and 835 files; the work-queue tool holds cases, queues and the rule that fired; the authorization tracker and ticket tracker hold the fixes and rule changes. Without the rule version, nobody can tell a rule error from a staff choice.
Read → - Claim denial routing exception, worked step by step: one denial with two causes and the records each decision left
The records that explain a claim denial routing exception are the line-level denial reasons on the first payment advice, the routing log showing which rule version sent each line where, the hand correction that fixed a misroute, the rule change log with its approver, and each later payment advice that proved whether a fix worked. In the worked case below, those five records show a two-cause denial, a rule that read only one cause, an 18-day detour, and the rule change that closed the gap.
Read → - Claim denial routing history: what to inventory before a denial management rollout
Before a denial management rollout, inventory three things: the denial reasons as received on each claim line, every version of the routing rules that assigned denials to work queues, and the resolved cases showing what fixed each cause. For each, note the system that holds it, the years covered, the owner and the date the old tool goes read-only. Ask the revenue cycle head for that metadata, and introduce the executive who can authorize a data discussion. Licensing depends on rights, de-identification, qualification and the proposed use.
Read → - Claim question to closure across the claims system, mailboxes and document library: an introducer's record map
A referral partner can describe a claims organization's question-to-closure history entirely from metadata: which system holds the claim and its copy of the policy, where questions and evidence requests travel (usually email), where the received documents are filed, how far back each goes, which identifier ties them together, and who owns each step. No claim file is opened. The case to test is a claim where the relevant endorsement never appeared in the case view.
Read → - Claim-question-to-closure record chain: the keys that link policy, claim, email and letters end to end
A company connects claim-question-to-closure records by following five keys in order: the policy number and endorsement dates in the policy system, the claim number and loss date in the claims system, the conversation ID on each email thread, the claim-number folder in the document library, and the version number on each coverage letter. The links usually hold inside each system and fail at the hand-offs. The weakest is the policy copy, which can be taken before a late endorsement is processed.
Read → - Claims document completeness review exception examples: a worked wrong-version attachment case
The records that explain a completeness exception are the ones that show each decision in order: the claim's version history, the checklist as it stood when the file was marked complete, the missing-item request that reopened it, and the receipts that closed it again. The hard test is an attachment that belongs to a different claim version. Below is one Illustrative case worked step by step, showing who decided what, which record captured each decision and how to spot the same pattern at a client.
Read → - Claims document completeness review records across systems: a system map with linking keys
Four keys rebuild a claims document completeness review across systems: the claim number, the claim version or revision date, the request identifier and the date each document was received. The claims system holds the checklist and the revision history; the document repository holds what arrived; correspondence holds what was asked for. The claim version is the join that usually fails, because many repositories file a document against the claim and nothing finer. Below is the map, then one Illustrative file joined end to end.
Read → - Claims document completeness review: what to inventory before a claims platform replacement
Before a claims platform replacement, inventory the three records that show how each claim file was made complete: the submission checklist, every missing-item request with its date, and the final receipt that closed the gap. For each, note which claim version the document was attached to, the system that holds it, the years covered, the owner and the date old-platform access ends. Then introduce the executive who can authorize a data discussion; licensing depends on rights, qualification and the proposed use.
Read → - Clarification behavior: when a business record shows someone stopping to ask
Clarification behavior is the habit of stopping to ask for missing or conflicting information before acting, instead of guessing. In an ordinary business workflow it shows up when an employee sees two facts that cannot both be true, such as two different discount approvals for the same customer, puts the work on hold, asks the person with authority which one stands, and acts only on the answer. The record of that pause, question, answer and outcome is what makes it useful.
Read → - Classification corrections exception examples: a pump sold for a new purpose, worked step by step
The records that explain a classification correction are the ones that tell its story in order: the moment sales changed what a product was for, the analyst who asked, the broker who reasoned it through and cited a ruling, the director who said yes, the corrected filing and the fixed part record. A new code alone shows that something changed, never why. Below is one Illustrative story, a pump sold for a new purpose, told step by step with the person and the record behind each decision.
Read → - Classification corrections history: what to inventory before a broker platform migration
Before a broker platform migration, inventory the record classes behind each classification correction: ruling references, broker notes, revised entries and the product facts that changed. Note the years each system covers, who owns each class, which records are still inside a customs clock, and the date old-platform access really ends. Keep the inventory at metadata level. The compliance director can usually supply it; the introduction goes to the executive with authority to discuss licensing.
Read → - Classification corrections records across systems: a system map of entries, notes, rulings and approvals
Rebuilding a classification correction across systems needs identifiers that each system shares with the next: entry number plus line, part number, ruling number and timestamps that sort correctly. Four systems are involved: ERP product master, mailboxes, broker platform and ACE filing software. Each stores one piece in its own fields. Without common identifiers, a single correction splits into four records that no query can reconnect. Below is the field-level map, then one Illustrative join.
Read → - Clearance-to-release record chain: linking rights exceptions, edit versions and signed releases by version ID
A company connects clearance-to-release records with one key that all three systems share: title plus edit version. The rights exception should name the version it restricts, the media asset manager already tracks versions and who approved them, and the signed release should name the version and territory it authorizes. Title names alone join loosely, because restrictions apply to particular cuts. In most chains the weak link is the release form, which names the show but not the cut.
Read → - Clearance-to-release records across rights manager, media asset manager and e-sign: does the territory restriction survive to the release?
A partner can note, from a conversation with the head of post-production or rights, which systems hold each step from rights exception to approved edit to release authorization (usually a rights manager or clearance log, a media asset manager and an e-signature tool), the years and rough number of titles each covers, who administers them, and whether a territory restriction is carried into the final release record or left behind in the rights system. Nothing is opened or copied; review comes later.
Read → - Client advisory services examples, from cash forecasting to a data asset review
Common client advisory services examples include outsourced controller work, cash flow forecasting, budgeting, KPI dashboards, pricing analysis, fractional CFO support, systems selection, exit readiness and succession planning. A newer example is a data asset review: a metadata-only map of which systems hold years of records a client might license to SourceX, without the firm handling any content.
Read → - Client Conversations: Business Data Inventory Preparation
In client conversations, focus on understanding their data assets, explaining SourceX's role in licensing, and clarifying that they maintain full control over what is licensed. Your role is to help them identify potential licensing opportunities.
Read → - Client SOP change adoption exception example: a conflicting-update case worked step by step
The records that explain an exception are the ones that, read in order, show a conflicting instruction arriving, the delivery teams splitting, the problem being caught, an authorized decision and a confirmed fix. For client SOP change adoption that means the client's change emails, each SOP version with its publish date, agent read confirmations by version, QA reviews and scoring review notes, and the client's written ruling. The worked case below follows one conflict through all of them, then shows how to spot similar cases at a client.
Read → - Client SOP change adoption history: what to inventory before a client process transition
Before a client process transition, inventory the records that show how each client SOP change was adopted: the SOP version history, the agent acknowledgments for each version, the QA results scored against it, and the client instruction that triggered the change. Note the years covered, the system and owner of each, which services contract governs it, and the date the outgoing team loses access. Stay at metadata level: the delivery director can usually answer, and the introduction goes to the executive who can authorize a licensing discussion.
Read → - Client SOP change adoption system map: the keys that join knowledge base, LMS, QA and email records
Rebuilding client SOP change adoption across systems takes four joins: the client's request to the procedure revision it produced, that revision to the agents who confirmed it, the revision to the quality criteria in force that day, and each agent to the team they sat on at the time. Each join needs a shared key, such as a change request number, a version number, an agent ID or an effective date, or at least a reliable timestamp. The map below names the system, record, key and owner for each, then traces one Illustrative case through all five systems.
Read → - CLM migration: what to preserve before cutover and when to raise data licensing
Before a CLM migration, preserve full contract version history: redlines, approval logs, clause library revisions and intake requests, not just signed PDFs. Cutover is also the right moment for an implementation consultant to introduce a qualifying company to SourceX, which handles inventory, SourceX review and delivery while the partner never touches contracts.
Read → - Closing a title agency: which records to keep and which to assess for licensing
When closing a title agency, first lock down the records it must retain for states and underwriters, then assess whether separate agency-owned workflow records can be licensed with the right approvals. Partners only introduce the agency and never handle closing files, escrow records or consumer data.
Read → - Closing a US subsidiary of a foreign company: assess the records first
When closing a US subsidiary of a foreign company, assess the records before systems are decommissioned. A wound-down company can still qualify for SourceX if its data still exists and an authorized person agrees, so pause deletion, name a custodian and screen years of history, rights and authority before cancelling subscriptions.
Read → - Closing an engineering firm: retention duties and the records that can be licensed
Closing an engineering firm triggers state-board and contract retention duties for sealed documents, but the firm's own QA/QC checklists, proposals, standards and lessons learned may be licensable. Client-owned instruments of service stay out. Advisors should raise licensing before servers are archived, and introduce qualifying firms to SourceX.
Read → - Cloud migration and legacy data: what to do with the archives left on-prem
In a cloud migration, active data moves and legacy shares, databases and backups are usually retired with the hardware. Consultants should list those stores before decommissioning and ask the owner whether to archive them or have SourceX assess them for data licensing, since deletion is irreversible.
Read → - CMMS migration: how to preserve maintenance history before cutover
A CMMS migration should carry or archive the full maintenance history, not only the asset register, PM schedules and open work orders. Before cutover, export closed work orders, failure codes, technician notes, parts usage and attachments, and verify the counts. That archive protects reliability analysis and, at a qualifying company, can support a data license with SourceX.
Read → - Coding how new partners explain data licensing before any training: a study design with its writing prompt, codebook, double-coding rules and reporting plan, published before a single explanation is collected
Nobody has coded how SourceX partners explain data licensing before training, and this page reports no findings. It publishes a design for doing so: newly approved partners who consent write, before opening any onboarding material, the reply they would send a CEO who asks what licensing with SourceX would involve. Two coders, working blind, score every reply against a frozen codebook of accurate elements and misstatements keyed to SourceX's published pages. Results appear only after the collection window closes and every reply is coded.
Read → - Commissioning punch list closure exception example: every tracker block passes, the plant-wide stow test fails
The records that explain an exception during startup testing are the failed run, the open item raised against it, the root-cause note, the approved fix, the repeat run that passed and the owner's sign-off on the closed item, all tied together by one item number. The hardest and most instructive version is a plant-wide test that fails after every unit passed on its own. The worked example below follows one such case on a solar tracker field, names who decided each step and which record kept it, and ends with signals that a client has similar cases.
Read → - Commissioning punch list closure history: what to inventory before commissioning closeout
Before commissioning closeout, inventory how each commissioning issue was found and closed, not only the signed completion: component and system test results with every attempt, the issues log entries that recorded failures, the corrective work, the retest that passed and the accepted completion naming who signed it. Note which system holds each record, the projects and years covered, who owns them under the contract and when project access ends. Then introduce the executive who can authorize a data discussion; licensing depends on rights, qualification and the proposed use.
Read → - Commissioning punch list closure system map: the keys that join tests, issues, fixes and acceptance
Rebuilding punch list closure across systems takes four keys: an equipment tag that every system uses, a test record that keeps each try rather than only the pass, an issue ID that ties a failure to its fix and its proof, and a sign-off that lists what it covers. Test forms and issues usually sit in a commissioning (Cx) platform or spreadsheets; drawings, field changes and sign-offs sit in document control. The map below names system, record, key and owner, then joins one Illustrative case end to end.
Read → - Common concerns about licensing company data, answered
Owners worry most about privacy, employees, customers, lawsuits, control, payment and timing. Each concern has a specific control in the licensing process: agreed redaction, exclusions, rights review, written terms and the company's right to decline. This guide answers twelve concerns in two sentences each and links to the full page.
Read → - Comparing referral handoffs across advisory firms: a peer-set study design that times each step from the CEO's written yes to the company's own application, checks what each handoff carried and kept out, and publishes no reading until five firms fill a peer set
No benchmark exists for how advisory firms hand off SourceX introductions, and this page does not invent one. It specifies a study that could build one fairly: firms grouped into peer sets by type and size, each handoff timed from the CEO's written yes to the firm's submission and to the company's own application, checked for what it carried and what it kept out, and reported only as peer-set ranges once at least five firms contribute to a set. Until then there are no readings to quote.
Read → - Complaint-to-product-change record chain: the keys that join Intercom conversations, Linear issues and Notion policy pages
A company connects complaint-to-product-change records by keeping a key at every hop: the conversation carries a link to the product issue, the issue names the policy page it changes, the policy page has dated versions, and the help article has its own version history that can be lined up against the policy edit. Five hops, five keys. Where a hop has no key, the chain survives only as a guess from dates and wording.
Read → - Complaint-to-product-change records: a sample metadata packet for an introduction
A referral partner can describe a complaint-to-product-change history with metadata alone: how many conversations were linked to product issues, over what period, where the product decision is written down, whether the policy page and the help article keep version history, and who owns each step. The test that tells you whether the chain explains itself is simple to ask about: when the decision changed, how long did support keep sending customers the old help article?
Read → - Complaint-to-retention-decision data linkage: matching one customer from support case to save offer to credit note across two legal entities
A company connects complaint-to-retention-decision records by matching one customer across three tools: the helpdesk case (Freshdesk), the account record where the save offer or churn reason was logged (HubSpot), and the accounting entry that carried the decision out (Xero). The keys are an email domain, a company record with dated property changes, and a ledger contact. A referral partner can describe those keys, their years and their owners without reading a ticket or an invoice. The trail splits when one customer is billed by two legal entities.
Read → - Component-to-defect-disposition record chain: the lot, batch and work order keys from SAP EWM receipt to QMS disposition
A company connects component-to-defect-disposition records by writing an identifier into every hop: the supplier lot onto the receiving batch, the parent batch onto any batch split from it, the batch onto each work order that consumes it, and the work order onto each nonconformance report. With those pointers in place, a reviewer can walk from a disposition back to a supplier lot, or from a supplier lot forward to every affected work order. One hop without its identifier stops the walk in both directions.
Read → - Component-to-defect-disposition records in SAP EWM, MES and QMS: tracing a nonconformance back to its batch
A referral partner can describe a manufacturer's component-to-defect-disposition records without opening one: which system records material movements (SAP EWM, for example), which records production batches (an MES), which records nonconformance reports and their disposition (a QMS), the years each covers, how many reports exist, which batch or lot number links them, and who owns each step. The case to test first is a relabeled component, because relabeling can cut the link to the original batch.
Read → - Composition agreements with creditors: can data license proceeds help fund one?
A composition agreement is an out-of-court deal in which creditors accept a partial payment in full settlement of their claims. 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.
Read → - Computer-use agents and business software: why click-level workflow records are scarce
Computer-use agents are AI systems that operate software the way an employee does, and learning that takes examples of real multi-step work: what was done, in which tool, with what outcome. Those records mostly live inside companies in ERPs, helpdesks and trackers, not on the public web, which makes permissioned workflow data scarce.
Read → - Concentrated wealth in a private business: moves before an exit
When most of a client's net worth is one private company, diversification starts before any sale: build outside liquidity, reduce owner dependence and size spending to what the business can support. For companies with 50+ full-time employees at peak, licensing operational records can be one optional, non-core liquidity input.
Read → - ConnectWise to HaloPSA migration: what ticket history comes across and what to preserve
In a ConnectWise or Autotask to HaloPSA migration, current clients, contacts and open tickets usually move, while closed-ticket notes, time entries, status history and attachments may arrive partly or flattened. Run a pilot import, archive the source export before the old contract ends, and check client contracts before any licensing talk.
Read → - Construction claims consultants: how to make introductions outside disputes
A construction claims consultant can introduce a contractor to SourceX when the contractor has 50+ full-time employees at peak, years of exportable schedules, logs and change orders, and no dispute or litigation hold on those records. Records from active matters and privileged material are never part of an introduction.
Read → - Construction company succession planning: paths, records and rights
Construction company succession planning means choosing among family transfer, management buyout, strategic sale, investor sale or wind-down, then protecting the records the next owner needs. Contractors also hold bids, change orders and job-cost histories that may be licensable, once ownership by clients and subcontractors is checked.
Read → - Construction safety consultants: safety records, prequalification and referrals
A construction safety consultant can introduce a contractor to SourceX when it has 50+ full-time employees at peak and years of exportable safety plans, inspections and investigations. Worker medical, testing and injury details stay out, and the consultant never handles the records, only the introduction.
Read → - Construction technology advisors: the data introduction hidden in project closeout
Only the ones whose records still point to each other. On most projects, an RFI raises a design question, a change event or potential change order prices it, and a signed change order fixes the cost and time outcome. Under AIA's G716, an RFI by itself authorizes no change in cost or time, so the commercial outcome lives in the change order. At project closeout, construction technology advisors can ask the contractor's owner this metadata-level question and, if the company appears eligible and wants to proceed, introduce its decision-maker to SourceX.
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