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
- One release, read twice: what a standalone rights, asset or e-sign export loses in clearance-to-release
Most of the meaning is lost. Each system, exported alone, tells a confident but partial story: the rights manager knows a restriction exists, the media asset manager knows two cuts exist and who approved them, and the e-sign tool knows someone authorized "the film" on a date. Only when the three are joined by title and version does the record show a decision: a restriction found, a clean cut made for one territory, and a release that should have named it.
Read → - Operating partner at a small private equity firm: covering a portfolio with a lean team
An operating partner at a small private equity firm covers the portfolio by triaging where personal time changes outcomes, running a few repeatable screens, and handing the rest to outside specialists and programs that do the work. One such program is a SourceX data licensing introduction, which costs the company nothing upfront and starts with a 15-minute screen.
Read → - Opsgenie end of life: preserve alert and incident history before you migrate
Atlassian is retiring Opsgenie, so teams must move alerting and on-call to another tool, such as Jira Service Management or Compass. Before cutover, confirm what history the migration carries, export alerts, incidents, notes and postmortems to storage the company controls, and keep Opsgenie readable until counts reconcile. Years of incident history can justify a licensing conversation.
Read → - Orderly liquidation value of intangibles: how records are appraised
Orderly liquidation value is the estimated price an asset would fetch in a sale over a reasonable marketing period. Operational records usually get little or no value because buyers and comparables are scarce. A documented licensing route, verified inventory and clear rights are evidence a lender can offer.
Read → - Outage verification system map: the keys that join calls, events, work orders and meter checks
Reconstructing a verified outage restoration takes five links: the call ID that ties each trouble call to an outage event, the event ID that ties the event to a work order, the asset ID that ties the work order to the device actually repaired, the parent-child event link that ties a nested outage to the closure it contradicted, and premise or meter IDs with timestamps that tie each restoration check to the customers it covered. Each link lives in a different system and usually has a different owner. Lose the parent-child link and a hidden second failure looks like an unrelated outage.
Read → - Outage work order verification: fault reports, crew actions and restoration checks to keep through an outage system migration
Before an outage system migration, inventory the three records that prove whether a restoration actually held: the fault reports that opened each event, the crew actions and work order closures, and the restoration checks (callbacks, meter readings, field confirmation) that verified customers were back. Note which system holds each, the years covered, who owns them and the migration cutover date. Then introduce the operations director and identify who can authorize a data discussion; licensing depends on rights, qualification and the proposed use.
Read → - Outcome-linked demonstrations: a repaired pump, its final inspection, and the records that tie the work to the result
Outcome-linked demonstrations are records of a skilled person doing a multi-step task, joined to independent evidence that the task succeeded. In an ordinary repair shop, that is a pump overhaul: the complaint, the teardown findings, the coded cause and remedy, the repair, the bench test and the inspector's signed release, all under one work order number. For a referral, what matters is whether the company kept the steps and the verified result together, and who can authorize a licensing discussion.
Read → - Outside business activity rules for registered reps who want to earn referral fees
A registered representative who wants to earn referral fees outside their broker-dealer should get written clearance from the firm first. FINRA Rules 3270 and 3280 still apply, and the SEC approved replacement Rule 3290 in September 2026 with an effective date still to be announced, so treat a SourceX referral as reportable until compliance says otherwise.
Read → - Outsourcing accounting: what happens to the in-house finance records?
When accounting is outsourced, the in-house team's workflow records stop growing and get archived, usually still owned by the company. The best moment to screen them for AI data licensing is before knowledge transfer ends and old tools are retired. SourceX can qualify companies with years of records and 50+ full-time employees at peak.
Read → - Outsourcing customer support: what happens to your in-house ticket history
In an outsourcing customer support transition plan, the company keeps its own in-house ticket history, while the BPO's records about other clients stay out of scope. Owners should settle ownership in the contract, export the archive before the old help desk is cancelled, and screen it for licensing value first.
Read → - Overlooked intangible assets in chapter 7: what trustees should look for
Intangibles that chapter 7 schedules commonly miss include domain names, social and phone identities, customer contracts, software and code, and years of email, CRM, support-ticket and document archives. Trustees who ask about systems and admin access at the 341 meeting can preserve these records and, where the company qualifies, license them directly to SourceX before accounts lapse.
Read → - Owner information needs before an internal forward: an interview study design that rebuilds each time a CEO passes a partner's referral link to colleagues, with its sample, guide and codes published before any answer
Nobody has studied this for SourceX introductions yet, and this page reports no answer. It publishes the design of a study that could: consented interviews with CEOs who received a partner's referral link, drawn from four groups, namely owners who passed it to colleagues and applied, owners who passed it on and stopped, owners who applied without involving anyone, and owners who declined or never answered. Each interview rebuilds every internal forward in order and codes what the owner needed settled first. Findings will appear only after the interviews close.
Read → - Partial-credit evaluation: scoring a vendor onboarding that collected every document but missed final approval
Partial-credit evaluation scores a multi-step task by how far an attempt got, not only by whether it finished. In an ordinary business workflow, it separates a vendor onboarding that collected the tax form, insurance certificate and bank details but never got the controller's approval from one that did nothing at all. For a referral, what matters is whether the company records each step separately, with its own date and approver, and who can authorize a licensing discussion.
Read → - Partner Field Guide: Finding Companies with CRM Records and Deal Outcomes
RevOps consultants can leverage their understanding of data and business operations to identify companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English) with extensive CRM records and documented deal outcomes, which often hold valuable data for licensing. Focus on companies that meet SourceX's baseline profile for successful referrals.
Read → - Partner Field Guide: Finding Companies with Data Licensing SOPs and Runbooks
Operations consultants can find 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) by focusing on those with 50+ employees and established operational processes like SOPs and runbooks, indicating maturity for data licensing. Partners can operate from anywhere and do not handle company data.
Read → - Partner Field Guide: Finding Companies with Document Revision Histories
Collaboration consultants can identify 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) for data licensing by looking for established organizations with 50+ employees, robust internal content management, and a clear need to monetize their historical data, all while adhering to the SourceX company baseline. Partners never handle company data directly.
Read → - Partner Field Guide: Finding Companies with Private Codebases for Data Licensing
To find suitable companies, focus on entities based in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English) with 50+ full-time employees and established operating records, possessing rights to license their data, and an authorized sponsor. CTOs and venture advisors are uniquely positioned to identify these firms within their networks.
Read → - Partner Field Guide: Finding Companies with Quality Inspection Records for Data Licensing
SourceX licenses business data directly from companies and pays them for it. We are their counterparty from agreement through delivery and payment. These companies can generate significant referral rewards for partners.
Read → - Partner Field Guide: Finding Companies with Workplace Chat Archives
MSPs and operations advisors can identify companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English) with 50+ full-time employees, existing for years, with workplace chat archives by focusing on specific industry sectors and their digital communication practices. These companies can potentially license their data directly to SourceX, earning you a referral reward.
Read → - Partner Field Guide: Finding Data-Rich Companies Using Engineering Cues
Engineering consultants can identify potential 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) for SourceX by looking for indicators of robust data practices like pull requests and code reviews. Focus on companies with 50+ full-time employees, established operating records, and clear data licensing rights.
Read → - Partner field guide: Finding enterprise email archives
IT advisors can identify companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English) with extensive enterprise email archives by looking for established organizations with 50+ employees and a history of robust data retention policies. Focus on the company's operational history and the clear chain of data ownership required for licensing.
Read → - Partner Field Guide: Unearthing Data Licensing Opportunities from RFP Archives
To find companies with valuable RFP and proposal archives for data licensing, focus on 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) meeting SourceX's baseline criteria: 50+ FTEs at peak, established records, data licensing rights, and an authorized sponsor. These archives can contain unique, structured data perfect for AI labs and data buyers.
Read → - Partner Field Guide: Unearthing Helpdesk Ticket Data for AI Licensing
To find companies with valuable helpdesk ticket threads for AI data licensing, focus on organizations based in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English) with 50+ full-time employees, extensive operating records, and a clear need to monetize their structured customer interaction data. CX and support advisors are uniquely positioned to identify these companies.
Read → - Partner field guide: Unlocking field service work order data for AI
To find companies with field service work orders for data licensing, focus on organizations based in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English) with 50+ employees and a history of operations, seeking those with the right to license their data and an authorized sponsor. SourceX licenses structured historical data directly from these companies for AI training and evaluation, so they can monetize it.
Read → - Partner Field Guide: Unlocking Value from Month-End Close Workpapers
Finance advisors can identify potential SourceX referrals by looking for companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English) with 50+ employees, established operating records, and rights to license their month-end close workpapers. These companies must have an authorized sponsor and meet the SourceX baseline criteria.
Read → - Partner Guide: Using Program Insights in Client Conversations
When discussing SourceX with potential referral companies, focus on identifying suitable candidates by asking about their data assets and licensing interests, and clearly explain how SourceX licenses data directly from the company without dictating terms. Emphasize that all decisions remain with the company.
Read → - Partner playbook: turning a client's failed AI pilot into a metadata-level data introduction
A failed enterprise AI pilot shows, in writing, where generic software lacked the company's context, and that points to the records of people handling those cases correctly: escalation queues, staff corrections and years of workflow history. The window is short. Once the vendor environment is shut down and the project team disbands, that knowledge fades. This playbook covers the trigger, the signals, the records a wind-down puts at risk, and the conversation that leads to a metadata-level introduction, without asking for a single file.
Read → - Partner results research
Partner results research helps evaluate the program based on permissioned, verified records. It requires specific inputs and clear interpretation, avoiding unverified outcomes. This research cannot predict future deal success, which depends on acceptance at Closing and agreed terms.
Read → - Partnering with SourceX: A guide for SaaS companies and advisors
SourceX is a direct licensing partner for SaaS companies, licensing approved operational data for AI training and evaluation, subject to acceptance at Closing and agreed terms. Advisors can introduce qualifying companies to SourceX through our referral program.
Read → - Partnering with SourceX: Your AI Data Partner Program Guide
The SourceX Partner Program enables individuals and organizations to introduce companies with valuable operational data to SourceX, their direct licensing partner for AI training and evaluation, and earn referral rewards subject to program conditions. This guide outlines the benefits and process of becoming a SourceX partner.
Read → - PCI DSS and call recordings: how to remove card data before licensing
To remove card data from call recordings, map every system holding audio and transcripts, detect spoken card numbers in text and audio, redact them, test a sample for misses and document the result. PCI DSS expects stored card data to be protected and security codes not to be retained after authorization.
Read → - PE-backed CPA firms and APS: which entity can accept a referral reward?
In an alternative practice structure, the CPA-owned attest firm and the investor-backed services company are separate legal entities, but ethics and independence rules treat them as connected. A workable default is that only the services company accepts referral rewards, under a written policy cleared by the independence team, and only for clients the attest side does not attest for.
Read → - PE-backed franchise platforms: which franchisor records to screen for licensing
On a PE-backed franchise platform, screen franchisor-owned records such as support tickets, training history and field audit notes, and leave franchisee data out. The 50+ full-time employee baseline is counted at the franchisor entity, not across franchisees. Check the records before brand systems are consolidated.
Read → - Peer advisory group chairs: referral fees and member confidentiality
A peer advisory group chair can accept a referral reward only if the introduction starts with the member, the reward is disclosed in advance, and nothing said in confidence in the group is used. Check the organization's chair agreement first, because many bar or require approval of paid referrals.
Read → - Performance alert investigations: what to inventory before an asset operator handover
Before an asset operator handover, inventory each performance alert as a complete investigation: the telemetry window around the alert, the checks and actions taken, the work order if there was one, the confirmed cause and how the fix was verified. Note which system holds each record, how many sites and years it covers, who owns it under the operations agreement and when the outgoing operator loses access. Then introduce the executive who can authorize a data discussion; licensing depends on rights, qualification and the proposed use.
Read → - Performance alert system map: joining telemetry, analyst notes and work orders into one investigation
Reconstructing a performance alert investigation takes five joins: an asset identifier that the monitoring platform and the maintenance system both recognize, a time window that ties high-resolution telemetry to the alert, a link from the alert to any work order, a recorded cause with its verification result, and the version of the expected-output model in force when the alert fired. Each sits in a different system, usually with a different owner. Weather-only cases often never reach the maintenance system, so without the monitoring side many investigations disappear from the record.
Read → - Permission-aware agents: what an account change with a second approver teaches, and the records that prove it
Permission-aware agents take an action only when the authority for it is in place, and stop or ask when it is not. In an ordinary business workflow, that is an account change that needs a second approver: the technician requests elevated access with a reason, cannot approve his own request, waits for a manager, and acts inside a one-hour window. For a referral, what matters is whether the company kept the request, the approval, the action and the outcome, and who can authorize a licensing discussion.
Read → - Personal emails in work mailboxes: excluding them before licensing
Exclude personal emails from a work mailbox archive in layers: check the acceptable-use policy, drop sensitive mailboxes, filter by correspondent domain, relationship and topic, mask identifiers, then sample-review each department. No filter is perfect, so human review and counsel sign-off come last. SourceX agrees redaction requirements with the company before any work begins.
Read → - Physical AI and robotics data: does warehouse operations data count?
Mostly not. Physical AI and robotics training relies on sensor data such as camera, lidar and motion traces, a different market from warehouse workflow records. SourceX focuses on documents, tickets, emails and workflow records with outcomes, which logistics and manufacturing companies often hold even if they have no robot data.
Read → - Placement guarantee disputes across ATS, CRM and accounting: a system map of records and linking keys
Reconstructing a placement guarantee dispute takes five joins across usually three or four systems: the placement to its job order and fee terms, the placement to any correction of its start date, the client's claim to the placement, the evidence that the role changed to that claim, and the decision to the credit note or replacement placement. The ATS typically holds the first two, a CRM or shared inbox holds the claim and the change evidence, and accounting holds the credit.
Read → - Placement guarantee disputes: what to inventory before an ATS migration
Before an ATS migration, inventory the records that show how each disputed placement was decided: the guarantee clause that applied, the start date and any later change to it, the record of what changed in the role, the client's refund or replacement claim, and the credit or replacement the firm agreed. Note years covered, which system holds each, who owns it and when old-system access ends. Then introduce the operations director.
Read → - Plan administrators and wind-down debtors: turning surviving records into a late recovery
A plan administrator or wind-down debtor can treat surviving business records as a late recovery: confirm authority under the confirmed plan and trust agreement, locate email, ERP, CRM and ticketing archives the asset buyer did not take, check the debtor's privacy promises, then introduce the estate to SourceX, which runs inventory, SourceX review, contracting and delivery.
Read → - PLM migration consultants: ECO and BOM histories before cutover
PLM migration consultants should recommend archiving full ECO, BOM revision and workflow history before cutover, because it protects the manufacturer's own engineering records and may be licensable. Customer-owned drawings and export-controlled data limit any license. Consultants screen size and rights, then introduce qualifying manufacturers to SourceX.
Read → - Policy system migration: are the policy versions linked to the decisions they caused?
Sometimes, but a policy system migration is when you find out. In a well-run legacy system, each policy version (the original bind, each endorsement, each renewal) sits beside the referral note, rating change or coverage decision that caused it. Some migration plans convert only the current term and archive the rest, which can separate the versions from the decisions. Ask the authorized owner whether those links exist and survive cutover. If the company is eligible and interested, introduce its decision-maker to SourceX.
Read → - Portfolio company CEO summit agenda ideas, with a 30-minute data licensing session
Strong portfolio company CEO summit agendas mix peer benchmarking, AI in operations, pricing, talent and exit readiness with one practical new idea. A 30-minute data licensing session fits well: explain how licensing operational records works, run a private screening exercise at the tables, and finish with an opt-in follow-up instead of a pitch.
Read → - Portfolio company marked down: what to do next, including a records check for the board
After a portfolio company markdown, treat the write-down as a trigger for a structured board review: explain the drivers, rebuild the value creation plan, protect cash and systems, and add one agenda item on whether the company's operating records could be licensed. Screen size, history, system breadth and rights before deciding whether a SourceX introduction belongs in the revised plan.
Read → - Portfolio data licensing and reputational risk: a sponsor's guide to doing it cleanly
Reputational risk in private equity portfolio company data monetization comes mostly from four sources: consumer personal data, client-owned records, health information and silent use without notice. Sponsors remove most of it with an authorized company sponsor, a scoped AI-training license, de-identification agreed before work begins and delivery only after an executed agreement.
Read → - Portfolio operations review: finding companies with 50 staff at peak and years of records
In a portfolio operations review, the companies worth a data conversation are those that reached 50 full-time employees at their peak, contractors excluded, and still hold several years of records across their systems. Peak counts, so a company that has since shrunk can pass. Screen with what the platform team already knows: peak headcount, founding year and main systems. Then ask each founder, never the fund, whether they want an introduction 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