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
- How to sell a marketing agency: client data limits and records that may qualify
To sell a marketing agency, advisors should keep client campaign data and ad accounts out of scope, because they usually belong to clients, and focus on the agency's own proposals, project history and internal workflows, which may qualify for a data license alongside the sale.
Read → - How to sell a medical billing company, and what to do about its data
To sell a medical billing company, run a normal valuation and buyer process, and review its records in parallel. Claims data is PHI and is a red flag without authorization or de-identification, but non-PHI administrative workflow records may be licensable directly to SourceX for AI training, with client consent and counsel review.
Read → - How to sell a medical supply distributor and what to do with its records
Selling a medical supply distributor means preparing clean financials, mapping customer and supplier contracts, choosing among strategic, private equity and search buyers, and passing diligence. Separately, B2B order, quoting and service records may be licensable for AI, while patient-level DME records are protected health information and stay out.
Read → - How to sell a property management company: tenant data, owner data and operating records
To sell a property management company, advisors should separate tenant personal data and owner data, which generally stay out, from the company's own maintenance, vendor and operations workflows, which may qualify for a data license after de-identification alongside the sale.
Read → - How to sell a SaaS company, and what to do with the records beyond ARR
To sell a SaaS company, prove recurring revenue quality and code ownership, choose among strategic, private equity and search-fund buyers, then run a managed process through LOI, diligence and closing. Owners with 50+ full-time employees at peak (contractors excluded) can also license engineering, support and product records directly to SourceX before or apart from the sale.
Read → - How to sell a software development company, and what you actually own
To sell a software development company, prove revenue visibility, low client concentration, a stable delivery team and clean contracts, then run a focused process with IT services acquirers and PE-backed platforms. Client code usually belongs to clients and stays out of any data license, while the firm's own estimates, process records and internal engineering work may qualify.
Read → - How to sell a software testing or QA services company, and what its records are worth
To sell a QA services company, show sticky client revenue, a stable bench and a process that survives the founder. Client-owned test assets stay with clients, but the firm's own defect-triage, staffing and delivery records may be licensed directly to SourceX for AI training as a separate source of proceeds.
Read → - How to sell a telecom company, and what its network operations records are worth
Selling a telecom or managed network services company usually means preparing financials and contracts, engaging a sell-side advisor, running a buyer process and clearing any regulatory consents. Separately, the company's own operations records, such as NOC tickets, provisioning workflows and support histories, may be licensable to SourceX; subscriber and consumer records stay out of scope.
Read → - How to sell a translation or localization company, and what to do with its records
To sell a translation company, prepare recurring client revenue, a repeatable delivery process and clean asset ownership. Alongside a sale, the firm's own project, vendor and quality records can be licensed with SourceX for AI training, but translation memories contain client content and qualify only with client consent.
Read → - How to sell a trucking company, including the records most buyers overlook
To sell a trucking company, set the deal structure, assemble equipment, safety, customer and financial files, then run a confidential process with a broker who knows carriers. Before marketing, check whether the carrier's dispatch, maintenance and safety-coaching records could be licensed with SourceX; a carrier with 50+ full-time employees at peak can do that whether or not it sells.
Read → - How to sell a wholesale distribution business and get value from its order history
To sell a wholesale distribution business, document margin by customer and product line, secure supplier line cards against change-of-control risk, clean up inventory and rebate accounting, then run a competitive process. The distributor's order, purchasing and customer-service records are a separate asset that may be licensed to SourceX when rights are clear.
Read → - How to sell an accounting practice, and what a firm can and cannot license
To sell an accounting practice, owners prepare clean financials and a segmented client base, choose between an upstream merger, a PE-backed platform, internal succession or a book sale, and plan the client transition. Client tax and financial records cannot be licensed for AI; at most, a larger firm's own methodology and workflow records, stripped of client information, might be.
Read → - How to sell an e-commerce business, and where consumer data limits licensing
To sell an ecommerce business, owners rebuild channel-level financials, document inventory and supplier, 3PL and platform contracts, check what the privacy policy allows for customer data, then run a process with strategic or financial buyers. For AI data licensing, consumer personal data is a red flag, but a larger company's merchandising, fulfillment and support workflows may qualify.
Read → - How to sell an engineering or architecture firm, and which project records it owns
To sell an engineering or architecture firm, choose the route first: internal transition, ESOP, or sale to a larger A/E firm or PE-backed platform. Then document backlog, retention of licensed staff, project margins and claims history. Separately, the firm's own design-process, QA and proposal records may be licensable with SourceX, while client deliverables follow each contract.
Read → - How to sell an IT consulting or systems integration firm, records included
To sell an IT consulting company, prove that revenue, delivery capability and client relationships will outlast the founders: clean utilization and rate data, signed backlog, client concentration, platform partner status and documented delivery methods. Separately, the firm's own project records, internal tickets and playbooks may qualify for a data license signed before the LOI or kept apart from the sale.
Read → - How to sell an IT value-added reseller: the records question
To sell an IT value-added reseller, advisors should treat quoting, configuration, order and support records as a separate asset from the business sale: sort what the company owns from customer and vendor material, then consider a data license for the owned workflow records alongside the transaction.
Read → - How to sell an MSP business, and what to do with its ticket and PSA history
To sell an MSP, prove the quality of recurring managed services revenue, clean up PSA and RMM data, and approach acquirers through an advisor. An MSP with 50+ full-time employees at peak (contractors excluded) can also license its own ticket histories, time entries and runbooks directly to SourceX, before or apart from the sale. Client-owned data stays out.
Read → - How to sell client contracts when closing a B2B services firm, and what you keep
You can usually sell or transfer a closing services firm's client relationships, but each contract's assignment and change-of-control terms decide whether clients must consent, and most clients expect to be asked. Client files follow the clients or go back to them; the firm's own operating records may stay licensable with SourceX if it had 50+ full-time employees at peak.
Read → - How to sell to private equity portfolio companies through operating partners
To sell to private equity portfolio companies, win one company on merit, prove the result in the sponsor's own metrics, then ask the operating partner to recommend you across the portfolio. A referral, such as introducing companies to SourceX, is often an easier first ask than a vendor pitch: no separate charge, and nothing binds the company until it signs.
Read → - How to separate a shared Google Workspace or Microsoft 365 tenant after buying a business
To separate a shared Google Workspace after a business sale, first agree in the purchase documents which users, domains, shared drives and mailboxes belong to the company you bought. Then set up a new tenant under that company's billing, migrate under a transition services agreement, move the domain last and keep a verified record of everything that moved.
Read → - How to separate buyer contacts from supplier introductions: a two-lane route map for a venture network that knows AI developers and record-holding companies
Sort every contact by what the company would do in a data deal. A company that would acquire or use licensed data to train or evaluate models is a buyer contact: it can submit its own request on sourcex.si, and the referral terms describe no reward for that introduction. A company holding records it created and could license is a supplier introduction, the only kind the referral program rewards, once its CEO wants the conversation. Keep the two lanes in separate threads, because neither side's details may cross to the other.
Read → - How to separate editorial judgment from referral compensation: a nine-clause editorial conflict disclosure policy that keeps whoever could be paid out of coverage calls, fixes comparison criteria before anyone checks who pays, and leaves the piece free to criticize SourceX
Separate them by settling coverage before compensation can touch it, and by handing every editorial call to someone who gains nothing from a reward. Put it in a short written policy: who holds the partner account, who decides what is covered and how, which decisions a reward may never influence (inclusion, ranking, tone, criticism, corrections) and what the reader is told. Then disclose the connection on every piece that mentions SourceX, before the first mention, and keep the freedom to criticize it.
Read → - How to separate legal advice from a data referral discussion: a role separation conversation guide that names your hat before you speak, stops at the first legal question and records where each question went
Hold them as two conversations, even when one person is in both. Before you mention SourceX, say which role you are speaking in. The moment the client asks a legal question about licensing its records, stop the referral talk and send that question where legal work belongs: the firm's engagement, if it covers it, or the company's other counsel. Whether you may take part or be paid is a third question, for your firm's ethics counsel. A disclaimer names the hat; it does not do the review.
Read → - How to separate owned content from customer-supplied material: a content-origin screening table that asks who made each layer and whether metadata can split it
Separate by origin, not by system. For each family of records, ask who made each layer: employees, contractors, customers, licensed vendors or the software itself. Then ask whether the company can tell those layers apart from metadata it already keeps, such as who created or uploaded an item, without anyone reading the files. The referral brief records the origin mix as the company describes it and how cleanly it splits. Rights are settled in SourceX's review, never by the partner who makes the introduction.
Read → - How to separate paid IT work from a referral arrangement: a four-box scope map that keeps the introduction off the client's invoice, out of its ticket queue and away from its records
Run two agreements side by side and never let them touch. The client's service contract covers the work it pays you for: tickets, projects, migrations, advice about its systems. The SourceX Channel Partner Agreement covers the introduction, which you never bill, never log in the client's ticket queue and never carry out with admin rights. Any reward comes from SourceX, not from the client. One kind of task belongs to neither agreement: exporting, counting or sampling the client's records for SourceX. Nobody on your team does it.
Read → - How to separate procurement relationships from licensing permission: a 12-line checklist for corporate venture teams that keeps purchasing leverage, supplier files and spend data out of every data introduction
Treat the purchasing relationship as off limits and start from zero with the supplier's CEO. Being a supplier's large customer gives a corporate contact names, contracts, spend data and leverage, and none of it is permission to raise data licensing or to describe the supplier's records. Ask only outside any live sourcing event, from someone who is not the supplier's buyer, using facts any outsider could know, and say in writing that the answer has no bearing on purchasing. Only the supplier's CEO can then open the door.
Read → - How to separate public research files from private referral notes: a research-and-referral workspace map with two stores, one permitted direction of travel and a quarantine shelf, so a fund's published research never reveals which companies it introduced
Keep two stores and one rule about direction. The public research file holds only what anyone could cite, each item with its link and the date you read it, and it is built to be published. The private referral note holds what a CEO said for the purpose of an introduction and the dated status that followed, and it is never published. A public fact may be copied into a note with its source. Nothing from a note may travel back into research, a market map or a post. Anything that fits neither store goes on a quarantine shelf for counsel.
Read → - How to separate research participants from referral leads: a two-track event registration design with its own consent, owner, list and withdrawal for each track, and a no-join rule so a founder who answers your research never becomes a lead by default
Run research and referral interest as two tracks that share nothing but the event seat. Each track gets its own tick box, its own wording, its own owner, its own list and its own withdrawal. Neither is a condition of attending, and neither is inferred from the other. Research answers never become a contact list, and a request to hear about SourceX reaches the research only as a count. If you are tempted to compare the two person by person, report them side by side instead.
Read → - How to set a referral fee policy for your advisory firm
To set a referral fee policy, decide whether outside fees belong to the firm or the individual, list which engagements are off limits, require written disclosure to the client, assign an approver, and keep a register. CPA, CFO and M&A firms should check their professional rules and independence obligations first.
Read → - How to set stay bonuses for key employees during the sale of a business
Offer stay bonuses to the few people whose departure would stall the sale, then draft a short agreement with trigger, amount, timing and good-leaver terms. Add the controller, IT administrator and long-tenured operations staff, because diligence answers and system exports depend on them.
Read → - How to shape an AI roadmap for a mid-market company: build, buy or license out
An AI roadmap for a mid-market company should sort each initiative into three columns: buy (AI features in vendor tools), build (custom work on proprietary workflows) and license out (letting AI developers train on the company's historical records for a one-time payment). Most first-year items belong in buy; license out needs no internal AI team.
Read → - How to spot a growth metric that does not belong in an intro: an eight-check definition review that keeps only the numbers the program reads and the CEO will confirm
A growth metric belongs in an introduction only if it informs a fit fact, carries a stated definition, period and source, and the company's CEO would confirm it as written. Revenue growth, valuation, round size, user counts and fastest-growing ranks fail the first test because SourceX's screening reads none of them, and repeating them turns a data introduction into an investment pitch. Headcount and record counts can pass, once their definitions match what the program counts.
Read → - How to spot a permission window during governance cleanup: seven authority-documentation readiness signals that show when the company's records name its CEO and its record-holding entity, counsel has closed the work and no deal is running, so one question can reach the CEO
A governance cleanup is a company's own housekeeping: officer appointments recorded, past board actions ratified, dormant entities closed, the entity chart brought up to date. While it runs, the CEO and counsel are busy and a licensing question is noise. When it closes, and before the next financing or sale begins, there is often a window in which the records show plainly who holds the CEO office and which entity holds the operating records. That tells you whom to ask. It never changes who decides, which is the CEO, or whether the company fits.
Read → - How to spot a potential specialist exception without promising approval: an evidence brief that sorts ten fit signals into seen, confirmed and SourceX's call
A potential specialist exception is a company below SourceX's baseline of 50 full-time employees at peak whose own records run unusually deep in one kind of work. You spot it from dated public clues, confirm the facts with the company through someone who already knows its CEO, and then ask SourceX one question. Never tell the owner the company is approved or "a fit": SourceX's screening page says smaller specialists can still be considered, and only SourceX decides whether one is.
Read → - How to spot useful operating history without knowing revenue: a public-history signal checklist that reads award, inspection and web-archive footprints as questions
You do not need revenue to spot useful operating history. SourceX screens on full-time headcount at peak, years of the company's own records, rights and an authorized CEO, and none of those is a sales figure. Look instead for dated public evidence that a company has done documented, repeated work for years: a federal award history, a workplace inspection record, archived versions of its website, its own dated publications. Treat each one as a question for someone who knows the company, never as proof of ownership, quality or demand.
Read → - How to start a holding company to acquire businesses, and decide who owns the data
To start a holding company to acquire businesses, choose a structure with counsel, form a parent that owns each acquisition in its own subsidiary, line up financing for the first deal, and set an operating model. Decide early which entity owns each subsidiary's records and who can sign a data license.
Read → - How to Start Making AI Data Referrals with Your Existing Network
To begin making AI data referrals, screen your network 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) meeting SourceX's baseline criteria, identify the authorized data licensing sponsor within those companies, and then make a direct introduction to SourceX.
Read → - How to state data language without guessing from headquarters: a language evidence note that gives each record stream its language, share, basis and source
Headquarters tells you which language rule may apply, not what language the records are in. State language per record stream: the language, written as a standard tag such as en-IN or es-419, the share the company reports, how that share was measured, who measured it and on what date. Mark what is estimated or unknown, keep notes on translation and mixed-language content, and let SourceX measure the dataset actually offered. No records leave the company.
Read → - How to stop employees selling your company's work files to AI firms
Remind staff in writing what they agreed to, update confidentiality and acceptable-use policies, restrict bulk export rights and watch downloads at offboarding. Company work product is generally the employer's, so an individual cannot authorize a sale. The legitimate route is a company license approved by an authorized sponsor.
Read → - How to study referral friction without collecting company records: a journey interview protocol that rebuilds each introduction from the people who carried it, writes down events, waits and obstacles, and strikes whatever a speaker volunteers about the company's records
Interview the people who carried each introduction, never the company's files. A journey interview with the relationship owner and the platform lead, plus the CEO or someone the CEO names if the CEO agrees, rebuilds the path as dated events, waits and obstacles in the speaker's own words. A written capture boundary decides what goes into the study file, and a strike rule removes anything a speaker volunteers about the company's records, headcount or systems. This is the method; no results exist.
Read → - How to talk about potential company payouts responsibly: a sentence for each deal stage, from first mention to the first installment, and the number you never say
Talk about how a company's payout gets set, never about how large it might be. Before review nobody has a figure: SourceX's terms say indicative ranges and unpaid amounts are not a payout, and the company's net payout is fixed in a short Dataset Deal Confirmation, together with the exact dataset and terms. So match each sentence to the stage the deal has actually reached, leave every figure to SourceX and the company, and say in one plain line that SourceX may pay you a reward, separately.
Read → - How to talk to business owners about AI without hype: scripts for M&A advisors
Talk to business owners about AI in plain words tied to their own company: what it means for their value, what buyers will ask in diligence and whether their records are an asset, since AI developers license real operational records. Promise no price or deal, disclose any referral reward, and ask permission before introducing the company to SourceX.
Read → - How to tell a client their company does not qualify, and keep the relationship
Tell a client they don't qualify by leading with the decision, naming the one reason that decided it (size, history, rights, exportability or sponsor), saying what would have to change, and offering one useful next step. Deliver it within days and in your own words, ideally by phone, then confirm the reason briefly in writing.
Read → - How to tell employees the company is licensing its records to SourceX
Tell employees once the scope and the de-identification and redaction rules are agreed, and before any data preparation starts. In plain words, say which systems and years are licensed, what is excluded, how names and personal details are handled, that the company keeps ownership, and who answers questions. A short note plus a staff FAQ keeps trust concerns from stalling the deal.
Read → - How to test a data supply thesis through founder conversations: three predictions written before the first call, a coding sheet for every answer and checkpoints that can end the test early
Split the thesis into three predictions a founder can confirm or contradict: companies in your segment keep years of work records, those records are the company's own, and the CEO wants a licensing conversation once it is explained. Write down, before the first call, how many contradictions end each prediction. Then hold short conversations in blocks of four, ask about systems and ownership before licensing comes up, code each answer against the predictions and read the tally at every checkpoint. Stop the moment a written threshold is crossed.
Read → - How to test a referral calculator without anchoring on the maximum: a balanced scenario usability study that shows the zero, the floor and the large case side by side, then judges the tool by the introductions people make afterward
Test two versions of the calculator in your own materials on the same kind of introducer, and judge them by what those people do next. Version A is the one you use now. Version B opens on an empty input beside five worked cards from the published terms, a zero, a floor and a large case among them, every result marked Illustrative. A short moderated session measures anchoring; a 120-day count of introductions reaching a verified application is the primary measure. Nothing has been run, so no results exist.
Read → - How to test a referral CTA without creating false urgency: an accurate CTA variant test that audits every closing ask before it is sent, changes one thing at a time and counts a clear no, a withdrawn yes and a CEO who felt rushed beside every agreement
Test only closing asks that would still be true if the CEO waited a month. Run every candidate through a five-gate audit covering time, scarcity, value, approval and a truthful description of the next step; pair two survivors that differ in one respect; and judge them on informed decisions rather than clicks. Agreed introductions and clear declines count for a version, while a CEO who felt rushed, a yes later withdrawn or a request that ignores a stated fit condition counts against it. Nothing in SourceX's published terms or screening page gives a company a date to apply by, so no CTA may imply one.
Read → - How to test a referral workshop against one-to-one office hours: a matched-cohort event test that pairs similar founder cohorts, flips a coin inside each pair and scores both formats on next steps the CEO asked for, founder trust and host hours
Do not compare the two formats on whoever happens to sign up. Pair founder cohorts that resemble each other, flip a coin inside each pair, and give one cohort a group workshop and the other private 20-minute office hours, with the same host, the same facts and the same month. Then compare the cohorts on next steps a CEO asked for in writing, on founder trust from a short anonymous survey, and on host hours per next step. No results from this design exist yet.
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