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
- Loan document exception records across systems: a map of the loan system, e-sign, exception log and repository
Three keys rebuild a loan document exception across systems: the loan number, the document version identifier and the e-sign envelope identifier. The exception note is the bridge, because it is the one record that should cite all three. Around it sit four systems: the loan origination or documentation system, the e-sign account, the closing checklist and the document management repository. If one key was never written down, or lived only in a system being retired, the correction no longer points to the problem it fixed.
Read → - Loan document exception worked case: the guaranty signed after the note changed
The records that explain a closed loan document exception are the checklist item that failed, the exception note saying why, the document versions on both sides of the change, the signature events and the cure. In the Illustrative case below, a guarantor signed a genuine guaranty at the original loan amount after the note had been regenerated at a higher one. Without the superseded versions and the envelope histories, the file would show a fix but not the problem it fixed.
Read → - Logistics exception histories: separate company knowledge from client data with a field-by-field origin screen that asks who wrote each entry, who supplied it and whom it describes
A logistics exception history, meaning the delay, damage, shortage and claim records plus how each one was resolved, can signal a company worth introducing. But a single record usually blends the company's own judgment with shippers' order data, carriers' status updates and consignees' personal details. Screen each field by origin before anything else: who wrote it, who supplied the facts, and whom it describes. Introduce the company when its own resolution work is substantial, its CEO wants the conversation and the client and personal layers can be left out or cleared in review.
Read → - Long-horizon task data: one procurement issue traced across 41 days and four systems
Long-horizon task data is a record of work that runs through many dependent steps over days or weeks, where later steps only make sense in light of earlier ones. A procurement issue that moves from request to approval, shipment, inspection and settlement is a plain business example. For an introducer, the question is whether a company can link those steps across its systems for real cases, with outcomes, and whether someone can authorize a license discussion. Volume of transactions alone does not establish that.
Read → - Long-horizon tasks: why AI agents need records of multi-week projects
Long-horizon tasks, which span many dependent steps over days or weeks, are where AI agents struggle and where training examples are scarce, because project trails with handoffs, revisions and outcomes stay private. Engineering, construction, consulting and software firms often hold such records across several systems.
Read → - Longer hold periods in private equity: how to keep creating value when the exit slips
When a private equity exit slips, value creation has to come from levers that need no sale: pricing, cost, add-ons, recapitalizations and, for some companies, a one-time data license. A license brings cash into the portfolio company without new equity or debt, and the company keeps ownership of its records and approves price and terms before signing.
Read → - Low effort is not low accountability: a responsibility and follow-through matrix for platform teams running an introduction-only referral program
An introduction-only program is low effort by design. The platform team never exports, uploads or describes a company's records, and SourceX runs the agreement, rights review, data preparation, delivery and payout. It is not low accountability. Whoever signs the Channel Partner Agreement answers for confidentiality and for the people acting for the fund, every founder asked is owed an honest outcome, and every message carries a disclosure. Give each duty a named owner and a test for done, book referral income at zero, and stop when loops are left open.
Read → - Lower middle market M&A outlook for 2026: what sell-side advisors can plan around
The 2026 lower middle market M&A outlook rests on a large, aging owner base: McKinsey expects about six million US small and medium-size businesses to face ownership transitions by 2035. Few owners exit through a sale, so advisors should plan for selective, slower processes and give clients with deep operating records a licensing option that does not depend on closing.
Read → - Lower middle market value creation: levers that fit 50-500 employee companies
Lower middle market value creation works best with levers a lean sponsor team can run: pricing discipline, a monthly close and KPI pack, sales process basics, procurement, working capital, management upgrades, add-on acquisitions and systems consolidation. One-time levers such as data licensing fit companies with 50+ full-time employees at peak (contractors excluded) and years of records.
Read → - M&A advisor business development ideas for the months between mandates
The best M&A advisor business development ideas give owners a specific reason to take your call before they are ready to sell: revisit lost pitches and paused processes, cover sponsors with aging holdings, run annual owner reviews, watch for triggers, and offer a SourceX data licensing introduction that can pay the company without a sale.
Read → - M&A advisor value-added services: adding a records and data-rights review
The M&A advisor value-added services that set a firm apart help a client whether or not the deal closes: readiness work, quality-of-earnings preparation, buyer mapping and a records and data-rights review. That review prepares the client for AI diligence questions and can surface a SourceX data licensing opportunity, a one-time payment that leaves ownership with the company.
Read → - M&A Advisor's Playbook: Introducing Data Licensing During a Business Sale
Advisors can strategically introduce data licensing opportunities to their M&A clients, ensuring client approval and adhering to SourceX guidelines. The process involves a structured fit check and a secure, client-approved introduction.
Read → - M&A broker exemption under section 15(b)(13): who it covers and what it does not
Exchange Act section 15(b)(13), effective March 29, 2023, exempts M&A brokers from SEC registration when they effect securities transactions solely to transfer ownership of an eligible privately held company (prior-year EBITDA under $25 million or gross revenues under $250 million), subject to conduct conditions. It does not address data-licensing introductions.
Read → - M&A referral fees: how sell-side advisors pay referral sources, and who can accept them
An M&A referral fee is usually a negotiated share of the sell-side advisor's success fee, paid only after the referred client's transaction closes and the advisor collects. Who may receive it depends on registration and professional rules: FINRA member firms face limits on paying unregistered people, and CPAs, lawyers and advisers must check their own codes.
Read → - Maintenance escalation closure: what to inventory before a property management transition
Before a property management transition, inventory the records that show whether a maintenance job was actually fixed: resident reports, work orders with their full status history, contractor visit notes and invoices, escalations, and the completion checks that verified the repair. Note the years covered, the system holding each record, who controls it under the management agreements and the date access ends. A property systems consultant gathers only that metadata and introduces the operations director, plus whoever can authorize a licensing discussion.
Read → - Maintenance escalation records across systems: a map of the property platform, work order tool, vendor portal and accounting
Four keys join a maintenance escalation across systems: the unit and asset identifier that ties repeat requests to the same place and equipment; the parent or related work order reference that ties a reopen to the job before it; the vendor job number that ties a contractor visit to its invoice; and the approval reference that ties an escalation to the person who authorized it. They usually span four places: the property management platform, a work order or CMMS tool, the contractor's portal and accounting. If any key lived only in a system that is going away, the chain falls apart into unrelated tickets.
Read → - Maintenance escalation worked case: one roof leak, four work orders and the fix that held
The maintenance escalation records that explain how an exception was handled are the ones that connect a job marked done to evidence that it stayed done: each resident report, each work order with its status history, the contractor notes and invoices, the escalation note that records who decided to change course, and the completion check after the fix. In the Illustrative case below, three work orders were marked complete before a roof leak was solved. Only the linked sequence shows a diagnosis narrowing to the real cause.
Read → - Maintenance work orders: questions before referring the company, answered on a one-card context test of whose asset, whose hands, whose method, whose system and whose copy
Refer a company for its maintenance work orders when they describe its own equipment, worked on by its own technicians, in a system it runs, and its CEO wants the conversation. Before that, answer five context questions on one card: whose asset, whose hands, whose method, whose system and who else keeps a copy. A work order that points elsewhere on one question is not ruled out. That part gets described separately, and SourceX's rights review decides what it can include.
Read → - Maintenance-to-resident-resolution records across Yardi, AppFolio and Outlook: one joined timeline from request to confirmation
A property manager connects maintenance-to-resident-resolution records by following one shared key, usually the work order number, from the resident's request through vendor dispatch and invoice to the resident's own confirmation, which often lives only in email. Yardi or AppFolio holds the work order and vendor steps; Outlook often holds the resident's last word. A referral partner can describe how those links are made, and where they fail, without opening a single record.
Read → - Management buyout process: where records, rights and a data license fit
A management buyout runs from intent through valuation, financing, diligence and close, and a data license can fit at three points: before signing, between signing and close, or after closing. The incoming team must approve the exclusive term, so advisors should test seller, management and counterparty signatures first.
Read → - Management contract transitions: who controls the historical work orders, and when to introduce the owner
After a management contract transition, the historical work orders are controlled by whoever the management agreement and the system contract say controls them: often the outgoing manager's maintenance system holds the history, the property owner holds rights to property-level records, and the incoming manager starts fresh. Ask the authorized owner of the records which of those is true before access ends. If that company is eligible and wants to explore licensing, introduce its decision-maker to SourceX.
Read → - Management fee offsets and referral fees: what sponsors need to check in the LPA
It depends on the LPA. A management fee offset cuts the fee investors pay by an agreed share of fees the manager or its affiliates receive in connection with portfolio companies. Whether a third-party referral reward is caught turns on the fee definitions, who receives it and any side letters, so ask fund counsel first.
Read → - Management fee offsets and referral income: what PE firms should check first
A private equity management fee offset reduces the management fee LPs pay by a share of the fees the adviser, GP or affiliates earn from portfolio companies, as the LPA defines them. Whether a referral reward tied to a portfolio company is caught depends on that definition, who receives it and the firm's conflict rules, so ask fund counsel first.
Read → - Management presentation questions buyers ask, and how to answer the AI and data ones
In a management presentation, buyers ask about strategy, growth drivers, customers, margins, the team, operations and technology, and now about AI: where it is used, what it could displace, and what data the company owns and may use. Strong answers cite documents; a scoped or signed data license turns the data question from aspiration into fact.
Read → - Management services agreements: how to treat referral income from a portfolio company
A management services agreement is the contract under which a sponsor charges a portfolio company for advisory services. It does not automatically cover a third-party referral reward, so fund CFOs should check the MSA, LPA offset language, conflicts policy and disclosures with counsel before anyone registers as a SourceX partner.
Read → - Manufacturing business succession planning: options, timing and the records worth keeping
Manufacturing succession usually runs through family transfer, management buyout, ESOP, third-party sale or wind-down. Exit planners can also check whether a plant with 50+ full-time employees at peak holds licensable office records, such as quoting, purchasing, quality and ERP histories, before systems change or ownership passes.
Read → - Manufacturing companies in financial distress in 2026: which records can be recovered
Manufacturing companies in financial distress in 2026 often overlook a recoverable asset: years of quality, engineering change, supplier and order-exception records. Through SourceX, a manufacturer with 50+ full-time employees at peak can license them while keeping ownership. Customer specifications and controlled technical data are restricted, and the board, lenders or a court-appointed fiduciary must approve.
Read → - Map operating records without asking for the records: a twelve-question interview for portfolio CEOs, and the offers to turn down on the spot
Company data referral discovery means learning what records a company keeps without seeing any of them. A platform lead asks the CEO twelve metadata questions in four blocks: the work the records capture, their shape, whose they are, and whether the CEO wants a licensing conversation at all. The answers fill one line of a record map. Board packs and information-rights material stay out of it, and any sample, screenshot, export or login the CEO offers is turned down on the spot.
Read → - Map the companies already in your network: a 20-company screening exercise
To map potentially eligible companies in a network, list the companies you already know, then screen each on four facts: at least 50 full-time employees at peak, a qualifying location, years of its own operational records in a named system, and a decision-maker you can reach. Sort them into three buckets: ask the owner, find facts first, or not a fit now. The output is a short list of conversations, not a forecast of income. An afternoon with twenty companies is a reasonable first pass.
Read → - Mapping referral friction from a CEO's yes to a submitted application: a twelve-code friction taxonomy and a consented journey study, with stages, logs and reporting rules set before any company is followed
Friction research follows companies from the moment a CEO agrees to a conversation until a verified application, or until the company stops, and gives every obstacle a stage, a family and a verdict on whether it should be removed at all. SourceX has published no such study, and this page reports no results. It sets out the design: six stages defined by dated events, twelve friction codes in six families, a short journey log kept with consent by the company's own contact, an exit interview for stalled cases, and analysis rules that keep every stopped or missing company in the count.
Read → - Marketplace-appeal-to-resolution records across Amazon Seller Central, the ERP and the helpdesk: joining an appeal to its evidence and decision
A marketplace seller connects appeal-to-resolution records by tying four things to the listing's SKU and to dates: the issue the marketplace raised, the documents the seller submitted, the internal discussion in its helpdesk, and the final decision. The weak point is usually the documents. If an appeal cited a product document that had already been superseded, only a dated revision history in the ERP or document store can explain why the appeal failed. A partner can describe whether those joins exist without reading any of them.
Read → - Measure growth in qualified introductions, not logo counts: a cohort calculation that counts each company once, and only after it passes the fit facts
Growth in a referral channel means more companies that pass the fit facts and are introduced with their CEO's knowledge, not more logos on a slide. A logo count rises whenever someone pastes a portfolio list into a CRM. Count each company once, in the quarter its introduction was recorded, and report three numbers per quarter: companies introduced with the CEO's knowledge, companies passing every known fit fact, and verified applications. Growth is the change in the second number, read beside the third.
Read → - Measure the time from permission to a qualified introduction: a stage-time cohort that treats a withdrawn yes as an ending, not a slow case
Start the clock on the day the company's CEO says they want the conversation, and stop it when SourceX credits the company's verified application to you. Every other ending stays visible: a CEO who withdraws, or a company SourceX already knew, closes the row as an ending rather than counting as a slow case. For one quarter's cohort, report how many companies were credited by day 30, 60 and 90, and print the denominator, the closed rows and the open rows beside each figure.
Read → - Measuring trust in AI data referrals across professional networks: a twice-yearly CEO survey design with a fixed trust core, a randomized three-wording disclosure test and a misreading count, with no wave fielded yet
Treat AI data referral trust research as a survey you design and publish before anyone answers, not as a reading you can quote. Ask CEOs in partner networks the same 0-to-10 trust questions every six months, then show each an Illustrative introduction ending in one of three disclosure wordings, assigned at random, and count who misreads who pays, whether SourceX vouched for anything and who decides. Every invitee, breakoff and screen-out stays in the report. No wave has been fielded, so no results exist.
Read → - Measuring whether a new partner cohort's introductions improve with practice: a cohort learning measurement plan that compares each partner's later introductions with their own first, keeps silent partners in the count and publishes no curve until the cohort closes
No one has measured whether SourceX partners get better at introductions with practice, and this page publishes no curve. It sets out how to measure it: follow every partner approved in one quarter for twelve months, grade each introduction on a ladder of dated outcomes, and compare each partner's later introductions with their own first, so that strong partners who simply stay active do not pass for learning. Partners who never introduce anyone stay in the count. Results wait until the cohort closes.
Read → - Medical billing company data: denial notes, PHI and what an RCM company can license
Medical billing companies usually cannot license denial and appeal notes as they stand because they contain PHI handled as a business associate. Records de-identified to the HIPAA standard, with contractual rights confirmed, or non-PHI operating records such as playbooks and internal tickets are the realistic starting points for a SourceX introduction.
Read → - Member introductions in CEO peer groups: etiquette, disclosure and group norms
Good peer group introduction etiquette comes down to four habits: ask the member privately before suggesting anything, keep introductions out of meeting time, disclose any reward you could receive (including a SourceX referral share) in writing, and let the member decide without pressure. Chairs can write these habits into group norms so trust in the room survives.
Read → - Merchant settlement reconciliation across provider, bank, billing and ledger: a system map of linking keys
Five references join one merchant settlement reconciliation item across systems: the payment provider's transaction or refund ID; the payout ID that ties a group of transactions to one bank deposit; the retailer's own order or invoice number, which joins the provider record to billing; the ledger journal number; and the adjustment ID that records who explained a difference. Those references live in five places, the provider portal, the bank statement, the billing system, the general ledger and the month-end close file, and the chain breaks wherever one system stopped storing its key.
Read → - Merchant settlement reconciliation exceptions: the records that explain how a variance was closed
The merchant settlement reconciliation records that explain an exception are the ones that show four things together: the amount the ledger expected, the amount the processor actually settled, the reason for the gap and the person who approved the fix. In practice that means processor batch and settlement files, bank payout records, the ledger journals they were matched against, the reconciliation workpaper and the adjustment log with its approver. A batch file alone shows only what settled.
Read → - Mercor vs SourceX data referrals: what the public terms actually disclose
Mercor and SourceX both describe a route for introducing companies whose workflow data could be licensed for AI work. SourceX publishes its default formula: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, with a USD 100,000 Minimum Transaction and written payment conditions. Mercor's data page describes a refer-a-company flow and a bonus paid once the company starts earning, but the page excerpts reviewed on 2026-10-18 state no amount. Ask for written terms before comparing expected earnings.
Read → - Meta's Scale AI investment: what it signaled about training data
Meta's 2025 investment in Scale AI is a publicly reported transaction that observers often cite when discussing how strategic training-data operations have become. It does not value any company's records. For PE operating partners it is context at most, not a pricing benchmark for licensing a portfolio company's data.
Read → - Meter correction dispute records across systems: a map of the keys that join one case
To reconstruct a meter correction dispute across systems, four links have to hold: a service point identifier that survives any device exchange, a dated record of which device and billing factor applied to each premise, a dispute ticket tied to the account and the specific bills it covers, and a corrected bill that names the bills it replaces. The head-end, billing system, customer service tool and field app each hold part of the case; the map below shows which part, the key that joins it and who owns it.
Read → - Meter correction disputes: what to inventory before a meter platform replacement
Before a meter platform replacement, inventory each correction dispute as a chain, not as a final balance: the interval and register reading history on both sides of each meter exchange, the meter and transformer records that set the billing multiplier, the field and investigation notes, and the approved adjustment with who signed it. Note which system holds each, the years covered, who administers it and when access ends. Then introduce the billing operations head and the executive who can authorize a data discussion.
Read → - micro1's $1 billion data commitment: what introducers should check next
micro1 announced on 2026-10-09 a commitment to spend $1 billion over 12 months acquiring and licensing enterprise operational data, financed with capital from Citi and Hercules Capital. For an introducer, it is a dated signal that at least one well-financed firm wants real company workflow data. It is not evidence that the money has been spent, that any particular company's records will be bought, or what a referral would pay. Those answers come only from a specific program's written terms and review.
Read → - Microsoft 365 tenant-to-tenant migration after an acquisition: keep the history
In a Microsoft 365 tenant-to-tenant migration after an acquisition, decide what happens to the acquired company's history before cutover: active, archive, shared and former employees' mailboxes, Teams chats, SharePoint and OneDrive files. Preserve what the migration will not carry, keep the old tenant until exports are validated, and screen deep histories for a licensing review.
Read → - Mis-pick recovery across warehouse, ticket and order systems: a system map of records and linking keys
Reconstructing one mis-pick recovery takes four keys that must match across systems: the order number, the SKU with its component-list version, a replacement reference that points back to the original order, and timestamps on a shared clock. The warehouse system holds the pick and ship events, the component list says what the box should contain, the ticketing tool holds the complaint and approval, and the order platform holds the replacement. Where any key is missing, the case breaks.
Read → - Mis-pick recovery records: what to inventory before a fulfillment contract renewal
Before a fulfillment contract renewal, inventory how mis-picks were recovered: pick and pack scans, kit or bundle records, customer complaints, reship approvals and the fix that stopped recurrence. Note which party holds each record (the 3PL's WMS or the brand's helpdesk), the years covered, who owns it and when access ends. A 3PL account advisor keeps this at metadata level and introduces the customer operations head, who can bring in the people with authority to license.
Read → - Mis-pick recovery, one hard case step by step: a passing scan and the wrong printed card
The mis-pick recovery records that explain an exception are the ones that connect a customer-visible problem to an authorized remedy and a checked fix: the pick and pack scans, the complaint ticket with its photo, the agent's reason tag, the replacement-order approval, the corrected component list and a later review showing the problem stopped. The Illustrative case below follows one wrong-insert recovery in order, with the decision and record at each step.
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