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
- Unlock Data Referral Income from Your Intercom Projects
Customer operations consultants can identify ideal SourceX referral candidates during Intercom project work by looking for companies in eligible countries with 50+ peak employees, established records, and data licensing rights. On a company's first qualifying transaction, rewards are the greater of USD 50,000 plus 5% and 15% of the compensation SourceX actually pays the company you refer, with no cap.
Read → - Unlock new revenue: Data licensing for BPO clients
Advisors can introduce BPO clients to data licensing by focusing on its potential to monetize operational data without impacting existing services. SourceX licenses approved business data directly from companies for AI training and evaluation, managing the agreement, rights review, data preparation, delivery and payout, subject to acceptance at Closing and agreed terms.
Read → - Unlock new revenue: QuickBooks clients as data licensing opportunities
Accountants and implementation partners working with QuickBooks clients are uniquely positioned to identify companies suitable for data licensing. By understanding key client characteristics, you can refer them to SourceX and earn a reward based on the compensation SourceX actually pays the company.
Read → - Unlock Referral Opportunities During Microsoft Outlook Projects
Microsoft 365 advisors can spot SourceX referral opportunities 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+ peak employees, years of operational data, and clear data licensing rights during Outlook project engagements. This identifies companies that may want to license their data directly to SourceX.
Read → - Unlock referral rewards: A guide for Confluence consultants
Knowledge management consultants can identify SourceX referral opportunities 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+ peak employees, years of operational records, and rights to license their data. You can earn the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap. Actual Supplier Payout is the eligible licensing compensation SourceX actually pays the referred company, excluding separately itemized taxes and expense reimbursements, subject to any signed Schedule A or addendum.
Read → - Unlock referral rewards: Gmail projects and data licensing opportunities
Workspace administrators can identify potential data licensing referral opportunities 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+ peak employees, a history of operations, and intellectual property rights during their Gmail project engagements. These are key indicators for SourceX's enterprise data licensing services.
Read → - Unlock referrals: Network opportunity discovery in client conversations
To use network opportunity discovery in client conversations, focus on open-ended questions about their network's data needs and pain points, sharing SourceX's value proposition without overcommitting. Always clarify that SourceX controls the engagement scope and no work proceeds without direct company approval.
Read → - Unlock value: Data referrals for HubSpot implementation partners
CRM implementation partners working with HubSpot can identify referral opportunities by recognizing clients with a strong operational history, significant employee count, and valuable data assets that can be licensed. Partners can earn referral rewards based on the Actual Supplier Payout when a referred company licenses approved data directly to SourceX, subject to the program's terms and payment conditions.
Read → - Unmatched referral worked case: a sleep study sent to a lab that had moved
The records that explain a referral exception are the referral request as submitted, the unmatched-queue entry with its reason code, the service desk ticket and approved mapping change that fixed the cause, the rebooked scheduling event carrying the original referral ID, and the returned report that closed the loop. In the Illustrative case below, a sleep study was sent to a site that had moved. Seven dated records, made by five different people, tell the whole story.
Read → - Usage billing corrections across systems: a map of the keys that join meter, CRM, case and credit
To reconstruct a usage billing correction across systems, five keys have to survive: the subscription ID that ties meter events to an invoice line, the subscription or contract number that ties a CRM amendment to the plan change, the invoice number on the support case, the case number on the credit approval, and the case or approval reference on the credit note. Where every key is present, a correction rebuilds by ID. Where one is missing, someone matches by date and amount, and the chain weakens.
Read → - Usage billing corrections: the records that explain a plan change that overlapped a billing period
The usage billing records that explain an exception are the ones that show the problem, the authorized fix and the checked result: the meter events behind the disputed charge, the contract amendment or plan change that altered the price, the dispute case where the customer raised it, the approved credit decision with its calculation, and the credit note that settled it. A partner asks the finance operations head which of these exist and who owns them, then introduces the person who can authorize a licensing discussion.
Read → - Usage-to-revenue-correction record chain: the keys that link meter, contract, credit note and journal
A company connects usage-to-revenue-correction records by carrying one key through every step: the subscription or contract identifier from the usage record, through the amendment, invoice, payment and credit note, to the journal entry that adjusts revenue. Adjacent steps usually link well through invoice and credit note numbers. The chain breaks where the contract amendment never enters billing with its own identifier and effective date, and again where a later-period journal carries only memo text.
Read → - Usage-to-revenue-correction records: a sample metadata packet for Stripe, Chargebee and NetSuite
A referral partner can describe a company's usage-to-revenue corrections without opening an invoice: which system recorded the usage, which one issued the credit, which one posted the ledger adjustment, the date range and rough count of corrections, the field that links them, and who owns each step. The test that matters is a contract amendment whose effective date falls before the billing change, because that is where the three systems stop agreeing.
Read → - Utility billing disputes across systems: a map of the meter, space, lease and charge keys
To reconstruct a utility billing dispute across systems, five keys have to survive from meter to correction: the meter ID, the space ID that meter serves, the allocation rule version in force for the period, the lease ID whose clause sets how the space is billed, and the charge ID that ties the tenant's challenge to the approved credit. When the dispute follows physical work, a sixth key matters: the completion date on the maintenance work order. If any join breaks, the case becomes a pile of documents instead of a record of a decision.
Read → - Utility billing disputes retention timeline: what to inventory before a utility vendor switch
Before a utility billing vendor switch, inventory the records the outgoing vendor holds and the property ERP does not: dispute tickets and their notes, dated meter-to-space maps, allocation rule versions and meter read history. Those tend to disappear first, at contract end or when read-only access closes, while invoices and credits stay in the ERP without the reasoning that links them. For each class, note the years covered, the owner, the deletion date and who must approve keeping it.
Read → - Utility billing disputes: the meter, allocation and correction records that explain each exception
The utility billing records that explain how a dispute was handled are the ones that let someone redo the arithmetic: the meter reading and the meter-to-space map, the allocation rule in force on that date, the dispute ticket, and the approved correction with the credit it produced. Together they show the initial problem, the authorized action and the checked result. A partner asks the finance director which of these exist and who owns them, then makes the introduction.
Read → - Value creation office at a portfolio company: structure and tracking
A value creation office is the small team that turns a sponsor's plan into owned, dated, gated initiatives. It can log a SourceX data licensing review as a low-load, one-time-benefit workstream with four gates: qualification, inventory, terms and SourceX review, led by the CEO or CFO as sponsor.
Read → - Value creation without multiple expansion: which levers still carry PE returns
Without multiple expansion, private equity returns have to come from operating improvement: revenue growth, pricing, margin, cash conversion and add-ons that are properly integrated. Every lever must show up in EBITDA or cash a buyer will accept. A one-time data license can add non-dilutive cash from records a company already holds, but it is not run-rate EBITDA.
Read → - Value-added services fractional CFOs can offer beyond the monthly close
The value-added services that deepen a fractional CFO engagement are the ones tied to decisions the owner already faces: cash forecasting, pricing and margin work, board reporting, financing readiness, revenue recognition reviews, exit preparation and a systems and records review. That last review can also show whether a client's operating history could be licensed to SourceX.
Read → - Valuing intangible assets in bankruptcy, from trademarks to operational records
Intangible assets in bankruptcy are valued with the cost, market and income approaches, adjusted for distress, a short sale window and legal limits on transfer. Operational records such as email, CRM and support archives rarely reach the schedules and resist all three methods, so a licensing process with real buyer responses often signals value better than a desk estimate.
Read → - Verifiable rewards enterprise workflow example: one freight invoice dispute, step by step
Verifiable rewards means a task's result can be scored by a written rule instead of a person's opinion. In an ordinary business workflow, that happens when the work ends in a state a program can compare against an accepted document. The example below follows one fictional freight invoice dispute from the rate check to the ledger adjustment that reverses an overcharge, and shows which of its records carry that checkable signal and which are only context.
Read → - Verifiable rewards: why checkable business outcomes matter to AI training
Reinforcement learning with verifiable rewards (RLVR) trains a model by giving it credit only when an automatic check confirms its result is correct, such as code passing its tests or an account that reconciles. Business records showing a task, the steps taken and a checkable end state are valuable raw material for building those tasks.
Read → - Vertical AI companies and the industry workflow records they need to train on
Vertical AI training data is the industry-specific record of real work, such as insurance service requests, freight exception logs or month-end close workpapers, that companies building AI for one sector need to train and test their products. The public web rarely shows these workflows, so licensed records from established operating 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) fill the gap.
Read → - Vertical MSP specialization: which client industries hold licensable records?
A vertical MSP serves clients in one industry, and some verticals hold far more licensable records than others. Professional services, engineering, logistics and distribution fit best; PHI-heavy healthcare and consumer-data businesses are red flags. The test is size, history, rights and an authorized sponsor, not the industry label alone.
Read → - Vessel maintenance deferrals retention timeline: what to inventory before a ship management handover
Before a ship management transition, inventory the closed deferrals, not just the open jobs. A handover usually moves what the incoming manager needs to run the vessel: equipment lists, running hours, planned jobs and the deferrals still open. The closed history, showing what was found, why the work waited and whether waiting was safe, tends to stay in the outgoing manager's maintenance system and mailboxes, and disappears when that access ends. Note each record class, years covered, owner, end date and who approves keeping it.
Read → - Vessel maintenance deferrals system map: the keys that join maintenance, document control and email
Reconstructing a vessel maintenance deferral takes five keys that travel between systems: the vessel's IMO number, the equipment code, the job number, the deferral reference and, when parts are bought, the purchase order number. If every record carries the job or deferral reference, the chain rebuilds itself. If the shore approval sits in an email that mentions the equipment only in words, someone has to match it by date and wording, and that is where chains break.
Read → - Vessel maintenance deferrals: the inspection, deferral and sign-off records behind each exception
The vessel maintenance records that explain how a deferral was handled are the ones that show the initial problem, the authorized action and the checked result, linked by one job reference: the inspection finding, the deferral request with its reason and temporary measures, the shore approval, the eventual repair, and the sign-off that closed it. A partner asks the technical director which of these exist and who holds them, then introduces the person who can authorize a licensing discussion.
Read → - Vulnerability exception renewal history: what to inventory before risk platforms consolidate
Before two risk platforms are merged, inventory every vulnerability exception's chain: the original risk acceptance, the compensating control it relied on, each renewal review, and the evidence that the control was tested. Record which tool holds each piece, the years covered, the owner, and when old-tool access ends. Then introduce the risk owner, usually the CISO or head of IT risk, who can bring in the executive with authority to license.
Read → - Vulnerability exception renewal system map: the IDs that join scanner, GRC and change records
Rebuilding one vulnerability exception across systems takes four joins: finding to exception, exception to each renewal, exception to the evidence for its compensating control, and exception to closure. They are carried by five keys: the vulnerability ID, the asset ID or device group, the exception ID, the change ticket number and, where a fix is planned, a project ID. When each record cites the key of the one before it, the history rebuilds itself. When the control is described only in free text, someone has to match it by date and wording, and that is where chains break.
Read → - Vulnerability exception renewal, worked example: an approved exception with nothing behind it
The records that best explain how a vulnerability exception was handled are the ones that capture each decision in order: the finding, the risk acceptance with its compensating control, the change ticket that put the control in place, every renewal with its test evidence, and the review that found a problem and what was done about it. The case below shows why. It is a temporary exception that kept being approved after its control was gone, and only the sequence of records makes that visible.
Read → - Warm introduction etiquette: five rules careful advisors follow
Warm introduction etiquette comes down to five rules: get permission before connecting anyone, give an honest reason, share nothing confidential, disclose any compensation you could receive, and close the loop once. Applied to SourceX, that means asking the owner first, sending only public or approved context, and saying plainly that you may earn a referral reward.
Read → - WARN Act notice requirements: what happens to company records during the notice period?
The federal WARN Act requires certain employers to give advance written notice of covered plant closings and mass layoffs; the Department of Labor publishes the rules. Coverage and timing are legal questions for counsel, and the notice period is when systems and records decisions get made. This is general information, not legal advice.
Read → - Warranty eligibility disputes system map: the keys that join asset, service and warranty records
Reconstructing a warranty eligibility dispute needs four links: the parent asset to its components, the old serial to the new one after a swap, the component to the warranty terms in force, and the claim to its appeal, approval and any supplier recovery. Each link is a key that has to appear in two systems. Where a key was overwritten or never entered, the dispute can only be rebuilt from notes, and that gap is worth recording.
Read → - Warranty eligibility disputes: the asset histories, terms and approvals that explain each exception
The warranty eligibility records that explain how a dispute was handled link the asset's install record, its component tree and serial changes, the warranty terms in force, the rejected or contested claim, the person who decided, and the final approval. Together they show the initial problem, the authorized action and the checked result. A partner asks the aftermarket operations head which of these exist and who owns them, then introduces the executive who can authorize a licensing discussion.
Read → - Warranty root-cause feedback exception examples: one hard case worked step by step
The warranty records that explain a hard exception are the ones that show the decision at the branch point: the return findings that said "no fault found", the field service reports that described the site, and the engineering change that acted on the field evidence instead of the bench. This page walks through one fictional case in seven steps, names who decided each step and which record captured it, and ends with how to recognize a similar case at a client.
Read → - Warranty root-cause feedback history: what to inventory before a warranty platform renewal
Before a warranty platform renewal, inventory the chain that turns a field failure into an engineering fix: the warranty claim, the field service report, the returns lab finding, and the engineering response with any change order. Note which system holds each, how many years exist, whether the install date was captured, who owns dealer or installer records, and when legacy access ends. Then introduce the executive who can authorize a data discussion.
Read → - Warranty root-cause feedback system map: the keys that join claims, service, returns and PLM
Reconstructing warranty root-cause feedback needs a serial number that survives every hop, plus the claim, RMA and change order numbers written back into the records that came before them. With those keys, a field failure can be followed from the claim to the technician's report, the returns lab finding and the engineering change. The installation date is the weakest link: without it, time to failure cannot be measured.
Read → - Washington CPA referral fee rule: what to read and what to disclose
Washington CPAs should read the Board of Accountancy's current rules in chapter 4-30 WAC and the Public Accountancy Act, chapter 18.04 RCW, before accepting a referral fee or commission. Older notices can still rank in search, so rely on today's text, and put any disclosure in writing before the client decides.
Read → - What a board observer can learn without sharing board material: a signal worksheet that keeps every referral decision on public facts and the CEO's own words
Quite a lot, provided every fact comes from somewhere other than the board pack. Headcount, company age, the systems a company runs and planned migrations often appear in public sources or in what the CEO says outside the boardroom. Board decks, minutes and management reports stay where they are: an observer seat comes with confidentiality terms, not permission to reuse what it shows you. Build the case from public facts and the CEO's own words, ask the CEO in a separate conversation, and leave the decision with the CEO.
Read → - What a compliance training session should teach referral partners: a 60-minute scenario plan for a law or advisory firm in which every case ends in a paid referral, an unpaid introduction or a decision to stay out, and every rule question leaves the room for ethics counsel
A compliance session for referral partners should teach people to recognize three questions they cannot answer alone, and where each one goes: did the idea come from client information, does the firm have a conflict, and may this person or the firm be paid. It should never teach that rewards are allowed or forbidden. Build it from scenarios that end three ways (a paid referral, an unpaid introduction or no part at all), and close by naming the firm's ethics contact and the record each ending leaves.
Read → - What a declined referral can teach the next partner: a consent-first case protocol that builds each lesson from the introducer's own steps, uses only what the company chose to share and holds every case back until an identification check passes
No lessons from declined SourceX introductions have been collected or published, and this page offers none. It sets out a protocol that could produce them. Each case is built from the introducing partner's own dated steps, adds only what the company chose to share and agreed others may read, never records a private reason, and stays unreleased until a second reader confirms the company cannot be recognized. Fit remains SourceX's decision in its own review; the lessons concern what partners themselves controlled.
Read → - What a fund can contribute before it chooses to invest: a six-item learning-and-introduction menu that spends relationships, not capital, and never reads as an endorsement
A fund that has not decided to invest can still contribute two things to an AI data thesis: learning and permissioned introductions. Learning means putting one falsifiable question to founders and operators and keeping the answers that cut against the thesis. An introduction means a relationship owner asks a CEO whose company may fit (50+ full-time employees at peak, years of its own records, rights to license) whether it wants a licensing conversation with SourceX. Neither is an endorsement or diligence, and either can stop after a narrow pilot.
Read → - What a fund should ask before a portfolio company deletes its archives: a five-rung escalation checklist that reaches the retention owner and leaves the decision with the CEO
Ask the CEO, before the deletion date, five questions in order: what is being deleted and when, who owns the retention schedule, whether a hold or legal minimum keeps some records alive, whether a law or contract requires some to go, and whether the CEO wants SourceX to review the company's own remaining records first. The fund never takes custody, never asks for files and never argues to keep records that must be deleted. A no from the CEO at any rung ends the checklist.
Read → - What a geographic expansion reveals about referral complexity: read the announcement for the entity, the decision-maker and the language of the records
A geographic expansion usually means a company now keeps records in more than one legal entity, under more than one privacy regime and in more than one language. That does not make it a weaker referral, but it changes four questions: which entity created the records, whose CEO authorizes the conversation, whether those records meet the language rule for their location, and whether personal data would cross a border. Read the expansion announcement's own wording for those clues before anyone is introduced.
Read → - What a head of value creation in private equity does, and a lever to add
A head of value creation in private equity owns the value creation plan across the portfolio: sizing operational upside in diligence, setting 100-day priorities, deploying operating resources, tracking KPIs against the investment case and shaping the exit story. A newer lever for the role is licensing years of a company's operational records to SourceX for a one-time payment.
Read → - What a long software history can tell a referral partner: four things years in one system suggest, four it cannot prove, and six discovery questions that tell them apart
Years in one business system suggest four things: accumulated transactions, configuration that records how the company works, integrations that tie records together and people who understand them. They prove none of the four that matter next: that history survived upgrades, that the records are the company's own, that the CEO wants a licensing conversation, or that SourceX has demand for them. Use a long history to decide whom to ask and what to ask, then let the company confirm.
Read → - What a new data category means for your founder network: a signal map that turns AI research requirements into one question per founder, and the findings that should end the thesis
A new data category does not make your portfolio eligible. It tells you which records to ask about, and so which founders to ask: those who worked at, sell to or buy from established companies that create those records every day. Translate the category's research requirements into signals a founder can see without touching records, ask each founder one question, and stop when the companies named turn out to hold their clients' records rather than their own.
Read → - What a platform team can ask about business systems: a fourteen-question systems metadata questionnaire, and why a go-live year is not history depth
A platform team can ask about the shape and survival of a portfolio company's systems, never about their contents or their security. With the CEO's agreement, ask which kinds of system hold operating records, when each went live, what it replaced and what became of the old data, how long current settings keep history, whose account holds it and what is about to change. Credentials, configurations, user lists, exports and screenshots stay out entirely. The answers show SourceX where history may live; its review decides what that history is worth.
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