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
- Scheduling exceptions: find the operating business behind the records with a six-layer screening map that separates the company whose day broke from the vendor, client or franchisor holding the log
A scheduling exception record shows where a planned appointment, shift or delivery window broke and what the business did next. Before you refer anyone, find the operating business behind the record: the company whose crews, staff or customers the exceptions describe, which is often not the company whose software or desk holds the log. Trace each layer of the record to its owner, describe what you know at metadata level, and take the question to that company's CEO. The record type alone never settles rights, fit or demand.
Read → - Scope creep adjudication across systems: a map of the IDs that join email, PSA, CLM and billing records
Reconstructing a scope creep decision needs four joins: the client request to the project and task where the work was logged, the task to the change request that named the drift, the change request to the SOW version it produced, and that SOW version to the billing line or contract limit it changed. The change request is the hinge, because it is the only record that refers to both the delivery and the contract. Where any join is missing, the decision becomes a pile of unconnected hours and amendments.
Read → - Scope creep adjudication history: what to inventory before a PSA migration
Before a PSA migration, inventory the records that show how out-of-scope work was decided: every SOW version, the client requests that triggered a review, the change requests and their approvals, and the hours logged against the work before and after the decision. Note which system holds each, how they link, and the date the old PSA becomes read-only or is switched off. A partner collects only metadata and introduces the delivery director together with the executive who can authorize a licensing discussion.
Read → - Scope creep adjudication, a worked hard case: how a weekly favor became a change order
The scope creep records that explain an exception show four things in order: the original commitment, the informal request that broke it, the decision someone made about it, and what happened afterwards. In practice that means the signed SOW versions, the client's request, the time logged against the work, the change request with its approver and reason, the amended SOW and a later note on the outcome. A change order alone shows a price; the full chain shows why the firm chose it.
Read → - Screening Companies in Client Conversations
To effectively screen a company, ask specific questions about their size, operating history, data licensing rights, and internal sponsorship. Clearly explain that SourceX is the company's direct licensing partner for approved business data used in AI training and evaluation, emphasizing that the company approves the data and licensing scope, subject to acceptance at Closing and agreed terms.
Read → - Search fund boards: who sits on them, how they run, and what needs their approval
A search fund board of directors usually includes the searcher who became CEO, several investors from the search and acquisition rounds, and often an independent director with industry experience. It approves budgets, senior hires, debt, add-ons and contracts outside the ordinary course, which is why a data license belongs on its agenda before anything is signed.
Read → - Search fund CEO first-year mistakes, including retiring old systems too early
Common search fund CEO mistakes in the first year are letting the seller stay central, misjudging the inherited team, hiring too fast, changing too much at once, and shutting off old systems before checking what their history is worth. The last can rule out a later data license with SourceX.
Read → - Search fund exit: the records and AI questions the next buyer will ask
A search fund exit is the sale or recapitalization that returns capital to the searcher-CEO and the investors who backed the search, usually after several years running the company and often to a private equity buyer. Buyers now ask what records the company holds, who owns them and whether any are licensed for AI training.
Read → - Search fund first 100 days: a post-close plan that maps systems first
A search fund first 100 days plan should secure cash controls and admin access in week one, meet every employee and top customer in month one, set KPI baselines and a board rhythm by day 60, and inventory every system and archive before any tool is cancelled. Change little until you understand how the business really runs.
Read → - Seat compression and AI: how PE-backed SaaS companies are repricing
AI puts pressure on seat-based pricing because customers can do the same work with fewer human users, so per-seat revenue can fall while value rises. PE-backed SaaS companies respond with hybrid, usage and outcome pricing. Mature companies can also license approved historical product, support and engineering records directly to SourceX for AI training and evaluation, subject to acceptance at Closing and agreed terms, for a one-time payment reported outside ARR.
Read → - Secondary buyout due diligence: what the next sponsor will ask about data and AI
In secondary buyout due diligence, the buying sponsor tests how much value the first owner left, and data and AI questions are now part of that test: which records the company holds, whether it owns the rights, and whether any have been licensed. A documented records inventory, and any executed license, answers those questions with evidence.
Read → - Section 174A explained: domestic R&E expensing, elections and the records behind them
Section 174A lets businesses deduct domestic research or experimental expenditures, including software development, in the year paid or incurred for tax years beginning after 2024, while foreign research stays on 15-year amortization. Transition elections cover 2022-2024 balances. The tickets, commits and design documents gathered to support it also show advisers which clients keep deep engineering histories.
Read → - Section 363(f) free-and-clear sales and IP licensees: what survives when a licensor files
A section 363(f) sale lets a trustee sell estate property free and clear of other parties' interests, but courts disagree on whether that can strip an intellectual property licensee's rights. Section 365(n) separately lets many IP licensees keep their rights when the license is rejected. Data licensees face extra uncertainty because raw data may fall outside the Code's IP definition.
Read → - Section 506(c) surcharge: who pays to preserve records that are lender collateral?
A section 506(c) surcharge lets an estate charge a secured creditor's collateral for the reasonable, necessary cost of preserving it, but DIP orders often waive that right. If records are collateral, the trustee should settle who funds preservation before systems lapse, because a SourceX license needs intact, exportable records.
Read → - Section 542 turnover of debtor records to a trustee: electronic records and passwords
Section 542 requires whoever holds estate property to turn it over to the trustee, and section 521(a)(4) requires the debtor to surrender recorded information, including books and records. For electronic records, real turnover means access: the domain registrar, identity provider, cloud and email admin accounts and backup keys. Without them, no records assessment or license can start.
Read → - Sell-side data room checklist: what carries over to a licensing inventory
A sell-side data room index already contains much of what a data licensing inventory needs: systems, years in use, owners and retention notes. The company's own team can reuse folder titles and answers, not documents, to seed a metadata-only inventory, and its advisor can help the CEO decide whether to explore a license alongside the sale.
Read → - Sell-side M&A process steps, and where a data licensing track fits
A sell-side M&A process runs through preparation, teaser and NDA, CIM, buyer outreach and indications of interest, management meetings and LOI, confirmatory diligence, signing and closing. A separate data license fits best during preparation, when it brings cash and a documented asset; after an LOI or signing it needs the buyer's consent and full disclosure.
Read → - Seller transition period after a business sale: capture where the records live
A seller transition period typically lasts a few months to a year, set in a transition or consulting agreement. New owners should use it to map every system the company has used and where its archives live, because that knowledge leaves with the seller and decides whether the records can later be licensed.
Read → - Selling a business to a search fund: what the searcher asks and how records help
Selling to a search fund means negotiating with an investor-backed first-time CEO who diligences operations, customers, people and systems closely and usually wants a longer seller transition. A documented records inventory, or a data license with a disclosed scope, can reassure the searcher that the company understands what it owns.
Read → - Selling a business to an independent sponsor: process, risks and data license timing
Selling a business to an independent sponsor means dealing with a buyer that raises equity deal by deal after signing an LOI, so financing takes longer than with a fund. During that window, an owner may sign a data license, if it is disclosed to the sponsor and reflected in the purchase agreement.
Read → - Selling a business with outdated technology: what buyers discount and what to keep
Buyers discount outdated systems only for the cost, risk and integration work they must absorb, so most owners should document and export rather than migrate mid-process. Old archives may also hold multi-year records that AI developers license, so keep admin access and a full export before anything is retired.
Read → - Selling a construction company: where a data license fits in the sale
When selling a construction company, its estimating archive, project records and job-cost history may support a separate AI data license before, alongside or instead of the sale. Advisors screen for 50+ full-time employees at peak, years of records and clear rights, raise it early so the sale is not delayed, and introduce qualifying owners to SourceX.
Read → - Selling a government contracting business: where a data license fits in the deal
When selling a government contracting business, a sell-side advisor can raise data licensing as a separate source of proceeds, but only for corporate records the company owns: proposals, capture files, finance and internal operations. Contract deliverables and controlled information stay out. Time any license around novation and disclose it in diligence; SourceX runs the licensing process.
Read → - Selling a market research company: which data assets advisors should flag
When selling a market research company, advisors can flag methodology libraries, codebooks and annotation records as possible licensing candidates, while treating respondent data and client reports as out of scope until consent and contracts permit. Buyers will ask for the consent trail early in diligence.
Read → - Selling a payroll company or PEO: which data assets advisors should flag
In a payroll company or PEO sale, advisors can flag the firm's own operating records, such as playbooks and redacted support history, as possible license candidates while keeping client payroll and employee data out. Sort the records, confirm the 50+ employee baseline and coordinate timing with deal counsel.
Read → - Selling a software company: separating customer data from licensable internal records
In a software company sale, data customers put into the product is governed by their contracts and the company's privacy promises, and is usually not licensable for AI training. Internal records the company created itself, such as code reviews, issue histories, incident reviews and support playbooks, may be licensable with SourceX, before or after closing, if contracts allow.
Read → - Selling a staffing company: which data assets to document before the sale
Before selling a staffing company, document its job orders, placement and fill history, recruiter workflows and client service records as potential data assets, and screen out candidate personal data and client-owned records. An agency with 50+ full-time employees at peak and years of ATS history may support a separate AI data license alongside or before the sale.
Read → - Selling an environmental consulting firm: data assets advisors should flag
When selling an environmental consulting firm with 50+ full-time employees at peak, advisors can flag its internal project, review and QA records as a possible licensing asset, separate from client-owned reports and lab data. Check engagement confidentiality, decide timing relative to closing, then introduce the firm to SourceX.
Read → - Selling an HVAC or home services company to private equity: records, rights and timing
When selling an HVAC company to private equity, expect buyers to diligence maintenance agreements, technician productivity, job margins and the field-service platform. Before a roll-up migrates those systems, an owner whose company has 50+ full-time employees at peak (contractors excluded) can have dispatch, job and pricebook histories assessed for a SourceX license, with homeowner personal data excluded.
Read → - Selling an MSP: licensing operational records alongside the sale process
When selling an MSP, an advisor can run a separately negotiated data license on the MSP's own operational records, such as service tickets, runbooks and project histories, beside the sale. Client-owned data must be carved out, the license disclosed to bidders, and the introduction made before an acquirer migrates the PSA and RMM and retires the old systems.
Read → - Selling software and source code in bankruptcy, and the engineering history beside it
Source code is usually sold in bankruptcy as part of an intellectual property package through a court-approved sale, or by the assignee in an ABC, after ownership, open-source and customer-code checks. The engineering history around it, meaning commits, pull requests, tickets and design docs, is a separate asset that AI labs and data buyers may license for training coding agents.
Read → - Selling your business to a holding company: what happens to your records
When a holding company buys your business, the records usually go with it, so the new owner decides about licensing them after closing. If you want a say, raise it before you sign: ask which systems transfer, who decides on customer data, and whether to preserve exports before old tools are retired.
Read → - Separate a company referral from an investment introduction: a two-activity boundary diagram for funds that may both introduce companies to SourceX and look at SourceX as an investment, with five crossings kept shut: pay, information, conditions, audience and endorsement
Treat them as two activities that share nothing but SourceX's name. A company referral puts a company's CEO in touch with SourceX as a possible data supplier, under the referral terms and the Channel Partner Agreement, and its only reward base is what SourceX actually pays that company. An investment introduction concerns SourceX as a company to invest in: it starts at SourceX's investor page and earns nothing under the referral program. Keep pay, information, conditions, audience and endorsement from crossing, and take compensation questions to counsel.
Read → - Separation planning for carve-out advisors: can the owner say which records belong to the separated company?
Usually yes, but only if someone asks before Day 1. In separation planning, an owner can identify which records belong to the separated company by sorting each record set by the legal entity that employed the staff, held the customer contract and paid for the system. Corporate carve-out advisors can prompt that sort with one question. If the separated company looks eligible and the owner wants to explore licensing, the advisor introduces its decision-maker to SourceX.
Read → - Service credit adjudication hard case: a partial outage that hit only one tier, step by step
The records that explain how a SaaS company handled a service credit exception are the ones that capture each decision, not just the money: the status incident, the incident review that limited the outage to one tier, the SLA version in force, the availability worksheet, the customer's claim, the approval and the credit note. In the Illustrative case below, a 140-minute outage hit only Enterprise customers, and three of its seven steps were judgment calls a credit note alone would never show.
Read → - Service credit adjudication history: what to inventory before an SLA policy redesign
Before an SLA policy redesign, inventory every record a past credit decision depended on: status platform incidents with their affected components, each SLA version with its effective dates and tiers, customer claim requests, approval threads, and the credit notes in billing. Note years of coverage, owners and when old versions might be overwritten. Keep it at metadata level, then introduce the person who can authorize a licensing discussion, usually through the commercial operations head.
Read → - Service credit adjudication system map: the keys that join status incidents, SLA tiers, claims and credit notes
Reconstructing a service credit decision takes five joins across at least five systems: the status incident to the affected component, the component to the customer accounts that use it, the account to the SLA version on its order form, the customer's claim to the approval, and the approval to the credit note and the invoice it reduced. Each join needs a shared key, usually an incident ID, an account ID, an SLA version label, a ticket number or an invoice ID. Where a key was never copied across, the case breaks at that point.
Read → - Service dispatch histories: who knows the full operating story? Rarely one person, so a ten-question sponsor interview maps which role holds each stage of a job before anyone asks the CEO
Usually nobody holds the whole story. The dispatcher knows why a job moved, the technician knows what was found on site, and billing or warranty staff know whether the fix held. The person to find first is a sponsor who can walk one job from call to invoice and name who owns every stage, often a service operations director or dispatch manager. That sponsor narrates; the CEO decides whether the company discusses licensing its records. Run the conversation at metadata level and leave every record where it is.
Read → - Service recovery approvals hard case: two teams promise a guest two different remedies
The records that explain how a hotel company handled a service exception are the ones that capture every promise and the decision that settled them: the issue log entry, the guest messages in which each team made its offer, the manager's approval choosing one remedy, the folio adjustment showing which remedy was actually applied, and the follow-up reply. Joined by a reservation number, they show a reviewer what went wrong, who decided and how the outcome was checked.
Read → - Service recovery approvals history: what to inventory before a guest messaging migration
Before a guest messaging migration, inventory the records that show who promised a guest what, who approved the remedy that was actually given, and how the property checked it: the messaging threads with timestamps and staff names, the complaint or service request records, folio adjustments with their reason codes, and the follow-up that closed the case. Note the years covered, the system and owner for each, and the date the old messaging tool stops being readable.
Read → - Service recovery approvals system map: joining guest threads, service requests, outlet checks and folio credits
Three keys rebuild a hotel service recovery decision across systems: the reservation or room number, the timestamp of each message and posting, and the staff member who acted. With them, a guest messaging thread, a property system service request, a point-of-sale comp and a folio credit line up into one case. Without them, the promise and the remedy look like unrelated events. The weakest link is usually the messaging tool, which holds the written promise but is often keyed to a phone number rather than a stay.
Read → - Service request to scope resolution, before and after: what a PSA-only export loses about a no-charge trial
A single-system export loses the reason for the scope change. The PSA export shows a request that never closed, the time tracker shows effort nobody charged for, and the contract system shows an amendment with no visible cause. Each is accurate and each looks complete. Only when the three are joined on a shared project code does the record explain itself: a short no-charge trial that ran far past its window, an account review that caught it, and a priced amendment that settled future work while the earlier effort was written off.
Read → - Service-request-to-scope-resolution record chain: the keys that join a PSA request, time entries and a contract amendment
A services firm connects its service-request-to-scope-resolution records by carrying one project or work order number from the client request, through the task codes and time entries, into the contract record, and by filing each amendment against its parent agreement. The request-to-hours join is usually strong because the PSA and time tracker share project codes. The hours-to-contract join is usually weak, because contracts are filed by client and agreement number while hours are filed by project.
Read → - Service-request-to-scope-resolution records: a sample metadata packet for PSA, time tracking and CLM
A partner can note, without opening a ticket, a timesheet or a contract, which systems hold each step from new client request to delivery effort to agreed scope change (often a PSA, a time tracker and a contract lifecycle management tool), the years and rough volumes each covers, who administers them, and whether a request, its hours and its amendment share a project or work code. The case to flag is a free pilot task that quietly became permanent delivery work.
Read → - ServiceNow consultants: the data introduction hidden in ITSM consolidation
Often, but not reliably. In ServiceNow, an incident is tied to the change that caused it through a field on the incident record, and the rollback reasoning sits in the change's backout plan, work notes and review. An ITSM consolidation can keep the tickets and still drop those links. ServiceNow consultants can ask the company owner this metadata-level question before cutover and, if the company appears eligible and wants to proceed, introduce its decision-maker to SourceX.
Read → - Shadow AI in portfolio companies: uncontrolled leakage vs a deliberate data license
Shadow AI is employees sending company data to unapproved third-party AI tools, with no scope, contract or payment. A deliberate license with SourceX is the controlled alternative: the company chooses the records, approves price and terms, agrees redaction rules, signs an agreement and is paid. They are different decisions and should not be confused.
Read → - Shared mailbox retention: why sales@, support@ and ap@ are records
Shared mailbox retention means deciding how long role inboxes such as ap@ and support@ are kept, because they hold complete workflows that personal inboxes do not. MSPs and finance advisors should list them, sign off keep or discard with the owner, preserve before purging, and describe them only at a high level.
Read → - Sharing a business contact's details across borders: GDPR basics
A work email naming a person is personal data under the GDPR, so sharing it with a third party needs a lawful basis and minimal data. For introductions, the simplest route is to ask the person first, share only what they agreed to, keep a record and step back.
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