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
- Before and after: what a standalone seller portal export loses about a rejected marketplace appeal
A single-system marketplace appeal export, taken from the seller portal alone, keeps the outcome and loses the reason. It can show that a listing was blocked, an appeal went in, a rejection came back and a second appeal succeeded. It usually cannot show which product document revision each appeal cited, whether a newer revision already existed, or what the team discussed before trying again. That context sits in the ERP's document history and in the helpdesk, joined to the portal only by SKU and by dates.
Read → - Before and after: what a standalone work order export loses about whether a repair held
A single-system maintenance export usually loses the resident's side of the story. A work order export from the property system shows that a request was opened, assigned to a vendor and marked completed. It can lose whether the resident agreed the problem was fixed, whether the same fault came back under a new work order number, and who finally decided the job was resolved. Those facts often sit in vendor notes and in a shared Outlook mailbox, joined to the work order only when staff paste its number into a reply.
Read → - Before AP automation goes live: a retention timeline for duplicate payment recovery records
Before an AP automation rollout, inventory five record classes behind duplicate payment recovery: captured invoices with their rejected and resubmitted versions, match results, supplier correspondence, credits and refunds, and close notes. For each, note the years covered, the system, the owner and the date access actually ends. The explanatory records disappear first, usually at contract end or when staff accounts are removed, while posted payments stay in the ERP. Keeping anything is the company's decision under its own retention policy.
Read → - Before downgrading Slack or changing Teams retention, check your message history
Downgrading Slack to the free plan limits how much message history people can see and search, and Slack's help center sets the current window and how older messages are treated. Before switching plans or shortening Teams retention, have the workspace owner export what the company may need, so a subscription saving does not erase years of records.
Read → - Before plan consolidation: a retention timeline for entitlement exception records
Before customer plans are consolidated, inventory four things: which record classes exist (plan histories, permission changes, support tickets, legacy contracts), how many years each covers, who owns each system, and the date after which each stops being reachable. Event-level history goes first. Stripe events are retrievable through its API for 30 days, and Okta's System Log query returns 90 days. Zendesk archives most tickets about 120 days after closing but keeps them reachable. The acquired product's billing system ends on whatever date the company sets.
Read → - Before store consolidation: a retention timeline for store transfer discrepancy history
Before store consolidation, inventory the records that live only at the closing stores and the context that lives only with the people leaving. Central data, such as transfer orders, shipment postings and inventory adjustments, usually survives a closure. Local evidence often does not: receipts held on store registers, discrepancy emails in store mailboxes, local tracking sheets and the managers who knew why a count was off. For each, record the years covered, the owner, and the date it stops being reachable.
Read → - Before you reject a software subscription in chapter 11: the export checklist
Before rejecting a software subscription under section 365, export the records it holds, verify the export, confirm the vendor's retention terms and set the rejection effective date after the export is done. Rejection usually ends access quickly, and a short export step keeps years of records available for the sale, the wind-down or a SourceX license.
Read → - Benchmark contamination controls enterprise workflow example: seven steps through an accounts payable archive
In an ordinary business workflow, benchmark contamination controls are a short run of record-keeping steps: choose a process with checkable outcomes, list candidate cases by ID and date, trace where each case has been, check outside recipients, search for public copies, confirm the final outcome, and band every case with a written reason. Each step leaves a record. Four of those records carry the signal an AI-data review looks for. The Illustrative example below follows one accounts payable archive through all seven steps.
Read → - Benchmark contamination: why never-published business data matters for AI evaluation
Benchmark contamination happens when the questions or answers in an AI test set end up in a model's training data, so a high score may reflect memory rather than skill. Because most public benchmarks sit on the open web, developers value never-published material, including internal business records, as clean, held-out evaluation data.
Read → - Benchmark freshness: why a recent private code change with a reproducible test is worth more than an old public fix
Benchmark freshness means an evaluation task is new enough, and private enough, that the AI model being tested cannot have seen it or its answer during training, while still carrying a test that can check a solution. In an ordinary software team, the freshest material is a recent change to a private codebase that fixes a reported problem and adds a test that fails before the fix and passes after it, in a build that can still be run.
Read → - Best AI data referral programs (2026): a directory sorted by what you want to refer
There is no single best AI data referral program; there is a best fit for what you want to refer. To introduce a company's CEO, SourceX publishes a per-company formula (the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap) and micro1 accepts smaller firms. To refer individual specialists, Mercor publishes a rate. To license your own datasets, Defined.ai and Toloka run partner tracks. Each entry below links to a full comparison.
Read → - Best industries for search funds, and which hold licensable records
Search funds favor stable, fragmented service businesses such as B2B services, software, IT services and distribution. Several of these also keep years of operational records across many systems, which AI labs and data users may license. Size matters: the baseline is 50+ full-time employees at peak, contractors excluded.
Read → - Best paying referral programs for consultants in 2026, compared by what they really pay
The best paying referral programs for consultants use a clear payout basis, scale with the size of the client problem, credit the first introducer clearly and never set the consultant's advice against the client's interest. Compare consulting marketplaces, software partner programs, cost-reduction firms and data licensing on those four points before headline rates.
Read → - Best referral programs for accountants and CPA firms, compared on ethics and payout
The best referral programs for accountants are the ones a CPA firm can accept within its professional rules: they involve only non-attest clients, allow written disclosure of the fee and solve a real client problem. Compare accounting software and fintech, tax-credit, cost-reduction and data-licensing programs on payout trigger, recurrence and disclosure before payout size.
Read → - Biotech wind-down: licensing quality and lab records beside the IP sale
In a biotech wind-down, the company's own quality and lab records, such as SOPs, deviation and CAPA files and lab-notebook metadata, can sometimes be licensed beside the IP sale if the board or liquidator approves. Patient-level clinical data stays out unless consent permits the use and the data is de-identified. Export validated systems before their subscriptions end.
Read → - Booking change to final bill record chain: which identifier joins each hand-off, from channel sale to invoice
A company connects booking-change-to-final-bill records by following the identifiers each hand-off stores. Software writes most of them: the channel manager issues one ID that survives every later amendment, and the property system files it beside its own number. People write the rest, by typing a room, a date or a reason. Mapping which keys are machine-written and which are typed shows where the chain will hold and where someone would have to rebuild it by hand.
Read → - Booking-change-to-final-bill records across PMS, channel manager and guest messaging: the evidence chain and a metadata packet
A partner can note, from one conversation and without opening a single record, which systems hold each step from amended booking to guest agreement to final charge (usually a PMS, a channel manager and a guest messaging tool), how many years and roughly how many stays each covers, who administers each, and which links are carried by a reservation number versus rebuilt by staff. The case to flag is a change that reached only one distribution channel. Licensing value is decided later, by review.
Read → - Books and records questions on the statement of financial affairs
The statement of financial affairs asks who kept, audited and now holds a debtor's books and records. Read as a records map, those sworn answers show where archives sit and who controls access, which is the starting point before any SourceX fit check for the estate.
Read → - BPO and contact center owners facing AI repricing in 2026: options and data limits
AI is disrupting BPOs and contact centers in 2026 because agents that resolve routine contacts shrink the seats, hours and handled contacts outsourcers bill for. Owners can reprice, sell, merge, narrow or wind down. Licensing is a narrow side option: client interaction records belong to clients, but a BPO's own SOPs, QA frameworks and internal operations may qualify through SourceX.
Read → - Brand standard exception approvals across systems: the joins between audit platform and franchise portal
Five links let someone follow a brand standard exception from start to finish across systems: a location identity that survives resales, a standard reference naming the manual version, a finding ID carried into the exception request, a variance ID shared by the franchise portal and the audit platform, and an expiry date tied to a re-inspection. With those joins, inspection records, exception requests and final decisions read as one case. Without them, each system looks complete and the story is lost.
Read → - Brand standard exception approvals hard case: a coastal franchise location wins a conditional variation
The records that explain how a franchisor handled a brand standard exception are the inspection findings that flagged the problem, the franchisee's exception request with its evidence, the decision and its conditions, and the next inspection that should record the variation as approved rather than as a failure. Linked by a location identifier, they show a reviewer why the standard was set aside, who allowed it, on what terms, and whether the terms were kept.
Read → - Brand standard exception records retention timeline: what to keep before a franchise system transition
Before a franchise portal or audit platform is replaced, inventory the variance register and the records that explain it: superseded manual versions, closed inspection findings, approved, denied and expired exception requests, and the conditions and expiry dates on each decision. Migrations load active locations, current standards and open items, so these drop first. Note each record class's system, years covered, owner and the old system's access end date, and leave the decision to keep any of it to the franchisor's executives and counsel.
Read → - Brief-to-client-acceptance records in Asana, Google Drive and Gmail: what the client actually approved
A company connects brief-to-client-acceptance records by keeping one project reference across the Asana task, the Drive files and the Gmail thread, and by recording which version of each file the client had in front of them when they said yes. The brief version, the delivered work and the acceptance message each sit in a different system. The case that breaks the chain is common: the client approves an attached report, but its linked appendix lives in Drive and keeps changing after approval.
Read → - Broker commission reconciliation hard case, step by step: a mid-term cancellation and a disputed chargeback
The records that explain a broker commission reconciliation exception are the original placement, the carrier statement that paid the commission, the later statement that took part of it back, the producer chargeback, the dispute about it and the decision that settled it. Together they show a problem, a judgment, an authorized adjustment and a checked result. The worked case below is Illustrative and follows one mid-term cancellation from placement to final producer statement.
Read → - Broker commission reconciliation history: what to inventory before a brokerage acquisition
Before a brokerage acquisition, inventory the three records that explain broker commission reconciliation: placement records showing what was bound, at what premium and rate, and who produced it; carrier commission statements with their reconciliation status, including later return commissions; and the dispute resolutions that settled differences. Record which system holds each, the years covered, the owner and the date old-system access ends after conversion. Then introduce whoever can authorize a data discussion: the owners before closing, usually the acquirer after it.
Read → - Broker commission reconciliation system map: the five keys that join placement, statement, producer and ledger
Following one commission case across a brokerage's software takes five identifiers: the policy number with its term, the carrier's sheet and line number, the internal item ID assigned when lines are matched, the producer code, and the journal reference in the ledger. The dispute trail, where arguments about the case live, has no system key at all. When every identifier is carried forward, a reversal can be walked back to the policy it undoes; when one is dropped, it reads as a stray negative number.
Read → - Budget season conversations with clients: a playbook for fractional CFOs
Run budget season as four conversations: an assumptions kickoff, revenue and department reviews, a scenario session and a final approval. When an owner hunts for one-time cash, a data license can be raised as an option to explore, with a fit check and the owner's permission, but it stays out of the approved budget until a license is signed.
Read → - Budget season for fractional CFOs: finding one-time cash
One-time cash sources for a business include collecting receivables, selling idle assets, renegotiating vendor terms, financing and, for companies with years of records, a data licensing review. The last is an upside scenario: it takes several steps, depends on rights and SourceX's current data needs, and no amount is promised.
Read → - Build a referral opportunity map from metadata, without reading client content
A partner can collect metadata about a company's records without reading them: which system holds them, what kind of record it is, the years covered, an approximate count, who owns the system and who can authorize a licensing discussion. Each answer comes from the owner, is dated and names its source. Record contents (tickets, emails, files, customer names) stay closed. That eight-column inventory is enough for SourceX to judge whether an introduction is worth a conversation.
Read → - Build a watchlist of operational change, not unicorn rankings: seven families of dated events that move records or change who controls them, each with a source, a fit question and an expiry
A referral watchlist should follow dated events that change what happens to a company's records or who controls them, not valuation rankings. Seven families cover most of them: system retirements and migrations, acquisitions and integrations, site closures and mass layoffs, ownership and leadership changes, retention changes, wind-downs, and headcount milestones. Log each event with a primary source, the fit question it raises, an expiry date and the person who owns the CEO relationship; SourceX's screening ignores round size, press coverage and growth.
Read → - Build an event brief that makes eligibility boundaries clear: a seven-line qualification sidebar printed in the same words on the invitation, the registration page, the speaker notes and the follow-up, so no one mistakes a seat for a fit
An investor event about data partnerships carries two different eligibilities, and the brief has to keep them apart. Who may attend is the host's choice. Which companies might fit SourceX depends on its published screening facts and is settled only in SourceX's own review, after the company's CEO chooses to apply. Put those facts, what attendance does not mean, what the host collects and who could be paid into one short sidebar, and print it in the same words everywhere the event appears.
Read → - Building a US company referral practice from an international network
To build a company referral practice, leverage your international network to identify qualifying companies, then connect with their authorized sponsors. Rewards are the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, subject to any signed Schedule A or addendum. The USD 50,000 floor applies once per referred company, to its first qualifying transaction; further qualifying transactions first agreed within 12 months of the first qualifying Closing pay 15%. Actual Supplier Payout means eligible licensing compensation SourceX actually pays the referred company, excluding separately itemized taxes and expense reimbursements. 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. SourceX funds rewards separately; they do not reduce the company's payout.
Read → - Building an exit planning team: who does what, and who raises data licensing
An exit planning team usually combines a transaction attorney, a CPA or tax adviser, a wealth adviser, a broker or banker and an exit planner who runs the timeline. For data licensing, the team should name one introducer early, because SourceX credit goes to the first valid referrer.
Read → - Bundle inventory reconciliation history: what to inventory before a bundle pricing rollout
Before a bundle pricing rollout changes bundle definitions, inventory the records that explain each bundle reconciliation: every version of each bundle definition with its effective dates, the component movements recorded by the commerce platform and the ERP, the cycle counts that exposed variances, and the approved stock corrections with their reasons. Note the span, system and owner of each, and the date old definitions or tools will be replaced. Partners collect that metadata only and introduce the person who can authorize a licensing discussion.
Read → - Bundle inventory reconciliation system map: which system holds each record and the keys that join them
Reconstructing a bundle inventory reconciliation takes five joins: the order line to the bundle definition version live on the order date, that version to its component SKUs and quantities, the component movements in the commerce platform to those in the ERP (usually through a SKU-to-item lookup), the cycle count to the variance it produced, and the variance to the approved correction. The first join is the one most often missing, because a storefront usually keeps only today's recipe and seldom stores earlier ones with their dates.
Read → - Business listing not selling? What brokers can offer the owner next
When a business listing is not selling, diagnose before you relist: compare price with SourceX review, test the deal structure and check whether the right buyers are seeing it. While the relaunch runs, a qualifying company with 50+ full-time employees at peak can also explore licensing its operational records directly to SourceX, with the owner's permission.
Read → - Business owners without a succession plan: what the data says and how to open the talk
Business owners without a succession plan are often putting off a conversation that feels like announcing their exit, rather than ignoring the risk. McKinsey's 2026 research finds more than half of US small-business owners are over 55. Advisors can open the topic by asking what records the company holds, a question that needs no commitment to sell.
Read → - Business records vs personal data: what a bankruptcy estate can license
In a bankruptcy sale, a company's own operational records, such as SOPs, tickets, internal email and decision logs, are mainly a question of ownership and contracts, while consumer personal data is restricted by section 363(b)(1) when the debtor's privacy policy barred transfers. Estates whose value is mainly consumer data or PHI are a poor fit for SourceX.
Read → - Buy-and-build IT integration: what to do with each add-on's legacy systems
In buy-and-build IT integration, treat each add-on's legacy systems as an archive decision before a shutdown decision: log every system's history, confirm which entity owns the records and who can authorize their use, verify complete exports before cutover, then decommission. Add-ons with qualifying records can be introduced to SourceX one entity at a time.
Read → - Buy-sell agreement valuation updates: what to refresh and which assets get missed
A buy-sell agreement valuation update resets the price owners would pay for an interest on death, disability, retirement or exit, through a re-signed certificate of agreed value, a recalculated formula or a fresh appraisal, as the agreement specifies. During each update, advisers should also list intangibles the number ignores, including operational records that may be licensable.
Read → - Buy-side due diligence: how to identify and document a target's data assets
In buy-side due diligence, identify a target's data assets by recording four facts beside the usual IT and privacy work: which systems hold records, how many years they go back, whether they can still be exported and whether the target has the rights to license them. The note lets the sponsor weigh a data license as a post-close value lever.
Read → - Buyer diligence preparation data referral opportunity: a business broker's playbook from data room to introduction
Decision records are the ones in which a named person chose between options and the result was kept: discount approvals tied to won or lost deals, credit memos with reason codes, service tickets with a diagnosis and fix, change orders with customer sign-off. A contact list shows who the company sells to; it never shows how the company decides. When an owner starts preparing for buyer diligence, a business broker is already sitting beside those records, which makes this a natural moment for a metadata-level introduction.
Read → - Buyer diligence preparation: a 15-minute owner meeting that finds decision records, not contact lists
The records that show decisions are the ones where a named person chose between options and the outcome was kept: a credit approved for a stated reason, a quote revised and then won or lost, a ticket diagnosed and closed, a change order signed. A customer contact list shows who the company sells to, not how it decides. In a 15-minute meeting during buyer diligence preparation, a business broker can find out which kind the owner holds and offer an opt-in introduction.
Read → - Buying a business with 50+ employees: what changes from a small-business deal
Buying a business with 50 employees moves you from an owner-operator deal to a managed company. Valuation shifts from SDE to adjusted EBITDA, financing usually combines senior debt, seller notes and equity, a management layer must be retained, and the target runs many systems holding years of records. Diligence should cover those records and the rights attached to them.
Read → - Buying a failing competitor as an add-on: what to do with its records
Buying a distressed competitor as an add-on often means an asset purchase, sometimes through a court-supervised or accelerated sale, aimed at customers and people rather than archives. Factor the target's records in anyway: name the systems you want, keep them readable through integration, then check whether the combined business qualifies to license its records directly to SourceX.
Read → - California CPA commission and referral fee disclosure rules
California CPAs answer to the California Accountancy Act, where Business and Professions Code section 5061 addresses commissions and referral fees, and AICPA members also follow the AICPA Code. The California Board of Accountancy's enforcement FAQ says a licensee "still is prohibited from accepting any fee or commission solely for referral of a client to a third party", so this guide does not treat written disclosure as enough. Read section 5061 and the Board's regulations with your own counsel; if a reward is ruled out, the client can still apply directly with no referral link.
Read → - California's AI training data transparency law (AB 2013), explained
AB 2013 is California's Generative AI Training Data Transparency Act, reported to take effect January 1, 2026. It requires developers of generative AI systems offered in California to post high-level documentation about their training datasets. Suppliers that license records are not the posting party, but buyers have reason to favor data with clear origin and rights.
Read → - Call center closing: what a BPO keeps after a client exits, and what can be licensed
When a call center closes after a client exits, recordings and transcripts usually belong to the client, but the BPO's own training curricula, QA rubrics, WFM forecasts and coaching playbooks may be licensable. Turnaround advisors should sort ownership and check access before systems are decommissioned, then introduce qualifying BPOs 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