You'll find answers to common questions about 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) to SourceX on this page. Our goal is to help advisors like you confidently refer businesses in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia, ensuring a smooth and rewarding process. This resource is designed for referral partners who introduce enterprise companies with 50+ full-time employees at their peak to SourceX, their direct licensing partner for approved business data for AI training and evaluation. SourceX licenses data directly from companies and manages the agreement, rights review, data preparation, delivery and payout, subject to acceptance at Closing and agreed terms. Learn how SourceX licenses high-quality business data directly from companies, and understand the steps to refer companies successfully. Referral rewards are the greater of $50,000 plus 5% and 15% of the Actual Supplier Payout—the eligible licensing compensation SourceX actually pays the referred company, excluding separately itemized taxes and expense reimbursements—with no cap, subject to any signed Schedule A or addendum. 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. SourceX funds rewards separately; they do not reduce the company's payout.
Answers to common questions about referring companies
Specific answers to common questions about 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) to SourceX for data licensing. For the short version, see the FAQ.
- 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 type of companies should I refer for data licensing?
You should refer enterprise companies with 50+ full-time employees at their peak. SourceX is their direct licensing partner, licensing approved business data directly from them for AI training and evaluation, subject to acceptance at Closing and agreed terms.
What are the rewards for referring companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia?
Rewards for referring 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) are the greater of $50,000 plus 5% and 15% of the Actual Supplier Payout—the eligible licensing compensation SourceX actually pays the referred company, excluding separately itemized taxes and expense reimbursements—with no cap, subject to any signed Schedule A or addendum. 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. SourceX funds rewards separately; they do not reduce the company's payout.
Who benefits from SourceX's data licensing?
AI labs and data buyers benefit from the approved business data SourceX licenses directly from companies for AI training and evaluation. SourceX manages the agreement, rights review, data preparation, delivery and payout, subject to acceptance at Closing and agreed terms. Advisors contribute by introducing suitable enterprise companies.
What is the process for referring companies to SourceX?
The process involves simple steps for partners to refer companies successfully. Partners submit company introductions, ensuring a smooth and rewarding process for connecting businesses with SourceX.
Related pages
- An AI company offered to buy a client's data mid-sale: what should the advisor do?
- Does helping a client license data affect CPA independence?
- Does a one-time data license raise a portfolio company's ASC 820 mark?
- Can a PE portfolio company license its data to SourceX?
- Can an M&A advisor share client information when introducing a client?
- Can a company use customer data to train AI under its customer contracts?
- Outcome-linked demonstrations evidence gaps: counting how many repair jobs survive each link from work order to field result
The usual gap in outcome-linked records is not missing work. It is broken links: each step was kept in a different place, and some links were never made. Count how many jobs survive each link, from work order to failure codes to a linked final inspection to a known field outcome, and the fully linked set is often a small part of the archive. Four further gaps decide whether a surviving job is usable: procedure version, inspector authority, contradicted outcomes and customer-owned records.
Read → - Outside business activity policy: what to check before you join a referral program
Employees of consultancies, banks and accounting firms should treat a referral partnership as an outside business activity: read the policy, disclose the program and the possible reward in writing, and wait for approval before registering. Conflict, independence and inducement rules may require you to exclude certain clients, decline the reward or not take part at all.
Read → - Partial-credit evaluation evidence gaps: why stalled onboardings, shared logins and moving checklists stop step scoring
Four gaps make partial-credit evaluation hard to assess: missing context (stalled attempts were never kept, so only finished cases survive), missing permissions (approvals made under shared logins or by the wrong role cannot count), versions that moved (the checklist changed and nobody dated it), and unrecorded final outcomes (the vendor was approved, but nobody can tell if the first payment worked). Each gap removes scoreable steps. None rules a company out; together they set how many cases can be graded.
Read → - Permission-aware agents evidence gaps: what a review expects, what companies keep, and how to describe the shortfall
The commonest gap is time: identity tools keep audit logs for days or weeks, so approval history disappears unless someone archived it. The others are loose links between approval and ticket, approver lists and role settings that changed without history, outcomes never recorded, and changes made under shared admin accounts. Each gap shrinks the number of assessable changes; none disqualifies a company alone. Describe gaps in an introduction as what is known, what is likely missing and who can confirm it.
Read → - Rebrand attribution evidence: a fill-in legal-entity timeline and evidence packet for referral partners
The evidence that carries credit through a rebrand is a short dated timeline with one fixed point: an identifier that did not change, such as the registration number, plus three dates (your introduction, the registered or announced change, the application). Assemble it from public records and the company's own statement, in a one-page packet, and send it only if SourceX asks or duplicate review opens. Credit still follows the [program terms](/terms): the first valid introduction within the 90-day window, recorded when the company submits a verified application.
Read → - Recovery loops evidence gaps: what a review expects from failed runs and fixes, and what usually survives
A recovery loop can only be judged if every turn of it survives: the control, each failed run, the diagnosis, the fix and the final signed check. Companies usually keep the start and the end, the legacy control and the clean final balance, and lose the middle. Failed runs vanish when import tools purge history, fixes go unrecorded, permissions are unclear and sign-offs are vague. Describe gaps in an introduction as what is confirmed, what is likely missing and who can check.
Read → - Referral bonus payment conditions: a decision tree from introduction to earned and payable reward
A referral reward can be stopped in three different ways, and they mean different things. Some answers end the referral for good: no signed partner agreement before submitting, a later or invalid introduction, an ineligible company, no licensing agreement. Some only pause it: the buyer has not accepted the data, its payment has not cleared, the company has not been paid. And some hold an earned reward back from being payable: finance approval or your tax and payment details. The [program terms](/terms) govern every branch.
Read → - Referral fee calculation: the same rate on three bases, side by side
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. The reward on a company's first qualifying transaction is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap. SourceX applies it to one base only: the Actual Supplier Payout, meaning the compensation SourceX actually pays the company you introduced, excluding separately itemized taxes and expense reimbursements. The grid below runs a flat 15% across all three bases for three deals and sets SourceX's own formula beside it.
Read → - Referral rewards when you also own equity in the referred company
Owning equity in a company does not by itself stop you from earning a SourceX referral reward for introducing it, but disclose the interest first. The reward is calculated on the actual supplier payout, never deducted from the company's proceeds; still, tell the CEO and board in writing, check fund and professional rules, and stay out of the approval.
Read → - Referral rewards when your employer is an advisory firm: how to get approval
Employees of CPA, consulting, banking and advisory firms usually need written employer approval before accepting a referral reward, and many firms require the firm itself to be the partner. Read your outside-activity policy, send a written request to compliance and do not register until you have the answer.
Read → - Regulation S-P: can an advisor share client names for an introduction?
Only with care. Regulation S-P, the SEC's privacy rule for broker-dealers, registered investment advisers and funds, limits sharing nonpublic personal information about individual clients with nonaffiliated third parties. For a referral, get the business owner's consent first, let them direct the introduction, share business fit facts only, and ideally have them apply through your referral link.
Read → - Restricted payments: can one-time license proceeds be paid to the sponsor?
A portfolio company can usually pay a dividend to its sponsor only through an exception, or basket, in its credit agreement's restricted payments covenant, such as a general basket, a builder basket or a leverage-based basket with no default. License proceeds may first be caught by asset-sale and mandatory prepayment terms, and the executed agreement controls.
Read → - Reward hacking evidence gaps: what a close review expects, what finance teams keep, and how to word the shortfall
Four gaps make reward hacking hard to assess in month-end close records: missing context, when only signed totals survive and line-level matches are gone; missing permissions, when nobody can show who was allowed to post adjustments; lost versions, when a forced entry was deleted instead of reversed; and missing outcomes, when the items carried forward were never traced to a resolution. Each removes the layer beneath the score, so a gamed pass and an honest one look the same. All four can be checked from metadata.
Read → - Rollover equity explained: what sellers reinvest and who controls a data license
Rollover equity is the part of a seller's proceeds reinvested in the buyer's new holding company instead of taken as cash at closing, most often in private equity deals. It keeps the owner invested until the sponsor's exit. A data license signed before closing is the owner's decision; after closing, the sponsor decides.
Read → - Rubric failure evidence gaps: the four missing records that make a wrong pass look clean
Rubric failure is shown by contrast: the checklist said pass, and something later said fail. Four gaps remove one side of that contrast: the checklist version in force was not dated, the attachments the checker should have opened were not kept, the procedure that defined the checker's duty is unknown, and the later evidence, such as a credit memo, never links back to the case. Each makes a wrong pass look clean. All four can be checked by asking about storage and versioning, never by collecting documents.
Read → - Rule 1.6 confidentiality: what a lawyer can share when introducing a client
Only what the client has agreed to. ABA Model Rule 1.6 bars a lawyer from revealing information relating to a representation without the client's informed consent, implied authorization or a listed exception, and some bar opinions treat even the client's identity as confidential. Get informed consent first, share basic fit facts only, and never pass on documents or records.
Read → - Should a company announce its data license publicly, or keep it quiet?
Not by default. Whether a company can announce a data licensing deal depends first on the agreement's confidentiality terms, then on what its customers were promised. For most private companies the better course is to brief employees, owners and key customers privately, answer questions consistently, and keep a short holding statement ready in case the license becomes public.
Read → - Should a company license its data before selling the business?
Often yes, if it happens well before the sale process. A license signed before marketing gives the seller one-time cash, leaves ownership of the records with the company and produces an inventory acquirers can diligence. After an LOI it needs the buyer's consent, after signing interim covenants usually restrict it, and after closing the acquirer decides.
Read → - Should a company wait to license its data for higher prices?
Waiting can be reasonable, but nobody can forecast AI data prices, so base the decision on what the owner controls: whether the archive is preserved, whether systems are being retired, how exclusivity fits future plans and whether the company is ready. Preserve the records either way.
Read → - Should a referral fee be paid to you personally or to your firm?
A referral fee should be paid to whichever party your firm's policy and professional rules entitle to it: possibly the firm if you work inside a PE firm, CPA firm or bank, or you or your own LLC if you advise independently. Decide before registering with SourceX, register that payee once, and settle any internal split inside the firm.
Read → - Should a referral reward go to the estate? Bankruptcy and wind-downs
SourceX funds referral rewards separately, without reducing the company's licensing payout, but whether an introducer may keep a reward depends on their role. Trustees, assignees and estate-retained professionals should assume disclosure and either decline the reward or direct it to the estate, after advice from counsel.
Read → - Should AI labs and data users be on the buyer list in an asset sale?
Usually no, not as bidders for the whole business. AI labs and data users want defined records, not operations, so records are better handled in a separate, scoped licensing process with rights and privacy conditions settled first. SourceX runs that process for qualifying companies, keeping the main sale clean.
Read → - Should an industry association endorse data licensing to members?
Most industry associations should educate members about data licensing rather than endorse it. Endorsement implies the association vouches for the provider and the outcome; education explains how licensing works, its risks and who it suits. If the association earns a referral reward, its policy should require clear disclosure, member-initiated follow-up and no sharing of member data.
Read → - Should companies delete old emails, or assess the archive first?
Not by default. Companies should delete old emails only under a written retention policy, after checking legal holds, record-keeping rules and privacy promises. Before auto-delete runs, owners of companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English) with 50+ full-time employees at peak (contractors excluded) should also have the archive assessed, because years of business email can be licensable AI training data.
Read → - Should employees be paid when company records are used to train AI?
Not necessarily. Licensing proceeds are company revenue, so sharing them with employees is the owner's decision, and there is no single right answer. Owners usually choose a bonus pool, recognition only, or nothing. Check ownership of the records, tax treatment and employment agreements first, and tie any promise to money actually received.
Read → - Should owners take cash off the table before going to market?
Sometimes, but it depends on entity type, loan covenants and how a buyer will treat cash and working capital. A pre-sale distribution only moves existing cash; a records license can add separate one-time proceeds without selling the company, if documented rights allow and the license is disclosed to buyers.
Read → - Should we build our own AI model instead of licensing our data?
Building your own AI model with company data and licensing that data to SourceX serve different goals, so they are not alternatives by default. Internal AI is money you spend to improve your own operations; a license is a one-time payment for letting a developer train on a defined dataset. Check how exclusivity treats internal use.
Read → - Should we wait before licensing our data to AI?
Wait on signing if a sale, lawsuit or rights question is open, but do not wait on preserving the records. Systems are retired and archives deleted, while an export commits the company to nothing. The decision turns on records, rights and live corporate events, not on guessing future prices.
Read → - Should you migrate closed tickets to a new help desk?
Migrate open tickets and the recent closed ones agents search, and export the rest. Do not silently drop the full archive: years of resolved tickets are worked examples that may have licensing value. Split into load, archive and assess, and let the owner decide before the old platform's subscription ends.
Read → - Should you pass a referral fee through to your client?
Usually a partner is not required to pass a referral reward through to the client, and the published program facts describe no pass-through. Whether you should depends on your profession's rules and engagement terms. Disclose in writing, and do not promise a credit until you have checked your own rules and the signed agreement.
Read → - Should you underwrite data licensing upside in an acquisition model?
Generally no: keep data licensing out of the base case and out of the price you pay. Treat it as unpriced upside until three gates clear after close: rights to license, archives that still exist and can be exported, and confirmed buyer interest. Even then, no payment is assured until SourceX accepts the data at Closing.
Read → - Someone referred my company to SourceX. What does that mean?
A referral means someone you know suggested your company might fit SourceX's AI data licensing program and passed along basic contact and fit details. It does not share your records, bind you to anything or require a reply. Nothing is binding until your company agrees price and terms and signs.
Read → - Special indemnities in M&A: when data issues get their own line
A special indemnity is a stand-alone promise in an M&A agreement to cover a named, known issue, whether or not a representation is breached. Buyers may seek one for records with unclear rights, which is why a rights review before a sale or data license shortens the negotiation.
Read → - Staffing agency client referral fees: how they differ from candidate referral bonuses
A staffing agency client referral fee pays someone for introducing a new client account, typically once that client's first placement starts or its first invoice is paid, while a candidate referral bonus pays for introducing a worker who gets placed. Published benchmarks for client fees are scarce, so terms are negotiated case by case.
Read → - Starting-state fidelity evidence gaps: five records that blur the moment a task began
Five gaps blur the moment an order task began: fields overwritten without a change log, shipment events with a date but no time, change requests that lived in an inbox instead of on the order, approvals with no record of who could grant them, and returns split from the original order line. Each one hides part of the starting state, so a correct response and a wrong one become hard to tell apart. Timestamps are the gap to ask about first. None rules a company out; each narrows the share of cases that can be rebuilt.
Read → - State repair evidence gaps: what billing archives keep, what they lose, and how to say so
Billing repairs are hard to assess when one of six kinds of evidence is missing: a written target, stored before-and-after values, event history older than the billing tool keeps, proof the person making the change was allowed to, the product version that defined the plan at the time, and a check that the next invoice came out right. Time is usually the biggest gap. None ends the conversation; each changes how many repairs can be used.
Read → - Steuerberater and Wirtschaftsprüfer: can you accept a reward for an introduction?
A Steuerberater or Wirtschaftsprüfer may not be allowed to accept a referral reward at all, so ask your Kammer before registering. German professional law has its own provisions on fees and on advantages connected with referring engagements, separate from any ethics code. The answer depends on your profession, your role and the client.
Read → - Strict foreclosure under UCC 9-620 for software and IP collateral
Strict foreclosure under UCC 9-620 lets a secured party accept collateral in full or partial satisfaction of a debt, but only with the debtor's consent, which can be deemed in some full-satisfaction cases, and the notice steps in the UCC text. It skips a sale. A lender that ends up with records should then decide whether a SourceX introduction fits.
Read → - Synthetic-to-real validation evidence gaps: when the real side of the comparison is missing
Synthetic-to-real validation is hard to assess when the real side of the comparison is incomplete. Four gaps do most of the damage: only the current policy is kept, nobody recorded who could approve exceptions, case statuses were overwritten as they moved, and final outcomes sit in a retired tool. Each one turns an expert's judgment about a generated case from a checked finding into an opinion. None ends the conversation, but each narrows what can be validated.
Read → - Temporal context evidence gaps: the missing dates and versions that hide which rules applied
Temporal context is hard to assess when a record that rebuilds a past date is missing. Six gaps do the damage: old rule versions thrown away, the decisive date not kept separately, no record of when a change was issued, no link from the case to the version used, no history of later corrections, and no record of who held authority at the time. Each gap invites a specific wrong conclusion. Gaps narrow what can be licensed; they rarely end the conversation.
Read → - Tired of running your business? Five options before you sell
If you are tired of running your business, you can delegate more, hire a CEO or president and become a passive owner, sell part of the company, sell all of it, or, for qualifying companies, license operational records for a one-time payment. Match the option to what is draining you.
Read → - Tool-call provenance evidence gaps: a gap analysis of what reviewers expect and what audit logs keep
Four gaps cause most of the trouble: the actor is not recorded, the rule version is lost, the input is overwritten, or the outcome is never linked. Two hidden gaps follow close behind: shared credentials that make the actor field meaningless, and retention limits that cut history short. Each one removes a different piece of evidence a reviewer expects. The honest introduction names which pieces the company says it has and which it does not know.
Read → - Trajectory-level evaluation evidence gaps: what step-by-step grading needs and what store records lack
The gaps that break trajectory grading are the ones that hide who did what and when: missing permissions (approvals under shared codes or logins), missing context (an optional check field left blank), unclear versions (a rule changed with no date) and unproven outcomes (a reversal recorded elsewhere). Outcome evidence is usually strongest and approver evidence weakest. Each gap changes how much of a company's history can be graded, not whether the company is worth introducing.
Read → - Trustee abandonment of property under section 554: what happens to company records?
Under section 554 of the Bankruptcy Code, a trustee may abandon estate property that is burdensome or of inconsequential value and benefit to the estate, after notice and a hearing, and abandoned property generally reverts to the debtor. Company records are often abandoned by default, so a quick fit check before abandonment can show whether they deserve administering.
Read → - UCC-3 terminations: clearing old liens before licensing records
Clear old liens by searching the state UCC index under the company's exact name, matching each financing statement to a loan, and asking paid-off lenders to file a UCC-3 termination. For live debt, obtain a payoff letter or consent. Doing this early removes friction from rights review before a SourceX license.
Read → - UK Bribery Act and referral fees: what disclosure and adequate procedures mean
Referral fees are not illegal under the UK Bribery Act as such, but an undisclosed payment to someone who owes duties to a client can amount to a secret commission or bribery. Disclose in writing, keep written terms and take UK legal advice before accepting a SourceX reward.
Read → - Using AI tools vs licensing data to AI: two separate decisions
Using AI tools and licensing data to AI are separate decisions. Buying a subscription makes you a customer; a data license makes your company the seller of defined records under a signed agreement and a one-time payment. Using an assistant does not license your records, and nothing is binding until the company signs.
Read → - Verifiable rewards evidence gaps: what an AI-data review expects, what companies keep, and how to say what is missing
Six kinds of evidence make a workflow checkable: the task, the inputs available at the time, the rule version in force, the approver's identity, the action log and the final outcome. Companies usually keep the task and the action well. The gaps cluster in rule versions, approver identity and final outcomes, and each one turns an exact yes-or-no check into a judgment call. The honest way to introduce such a company is to name the gap in one plain sentence rather than hide it or oversell it.
Read →
Free resources
- Earnout scenario calculator — Probability-weighted earnout value and its present value.
- Profit margin calculator — Profit and margin across three scenarios.
- Client opportunity brief generator — An editable intro email, summary and checklist.
- 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