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 test a workshop's effect on actual introductions: a now-or-later draw that gives every invitee the session, half of them only after the counting window closes, and scores the gap on CEO-agreed introductions that reach a verified application
Draw everyone you would invite into two groups before sending a single invitation: a now group that attends the workshop at once and a later group that attends after a 90-day counting window. Then compare the groups on introductions whose CEO agreed in writing and that reached a verified application SourceX credited, read on day 180. Compare by invitation, never by attendance, because the people who show up are the ones most likely to introduce anyway. No results from this design are published.
Read → - How to test eligibility messaging without hiding restrictions: an accurate-message variant pair in which both versions carry every published condition and only the framing changes, judged on qualified next steps and on how many founders felt misled
Test framing, never content. Write two versions of one introduction that state every published SourceX condition in the same order, using SourceX's exact wording wherever it publishes one, and change a single thing: whether the conditions read as what a company needs or as what rules a company out. Assign CEOs at random, judge the versions on qualified next steps and on founders who later felt misled, and stop the moment either version drops or softens a condition. This page is the design; no results are published here.
Read → - How to test long and short company introductions: a context-controlled email experiment that keeps one required core in both versions, balances relationship types between them and is judged on qualified applications, never on replies or opens
No results exist yet: nobody has published a test of introduction length for this program. Run it on your own outreach. Write a short and a long version of the note you send a CEO who has agreed to hear about SourceX, give both the same required core (the CEO decides, who could be paid, no records wanted, SourceX decides fit), assign CEOs to one version or the other inside each kind of relationship, and judge on a fixed reading date by qualified applications per assigned company. Reply speed is secondary; opens and clicks are never counted.
Read → - How to test which company fit questions partners can answer: a screening question usability study that walks each published question with a partner, logs the step where it stalls and records whether the partner could answer, never the answer itself
Take the five pre-introduction questions SourceX publishes on its who-qualifies page and walk partners through them one at a time, each thinking of a company they already know: did they understand the question, do they know the answer, do they know whom to ask, or does it stall? Record the step reached and the seconds taken, never the answer and never the company. Add think-aloud interviews with a few partners to learn why a question stalls. Nothing has been collected yet, so this page publishes the method and no results.
Read → - How to tie referral timing to company milestones without pressure: a milestone permission calendar in which the CEO names the milestone, the company signals when it is done, every entry expires and no milestone the fund controls ever carries the ask
Tie the timing to a milestone the CEO names, not one you notice and never one you control. Ask the CEO once whether any point in the company's year would suit a licensing conversation, write the answer down in their words, wait for the company to say the milestone is done, then ask one question and let the entry expire if the moment passes. A milestone your fund controls, such as a tranche or a follow-on decision, never carries the ask.
Read → - How to track declined and ineligible referrals respectfully: a minimal-identifier decline log with a reason code, a revisit trigger and a delete-by date, and no founder quotes
Give each declined, ineligible or withdrawn introduction one row keyed by an internal code, and store only what the next decision needs: the stage where it ended, a reason code, where that reason came from, a revisit trigger and a delete-by date. Keep credit outcomes such as duplicates apart from fit outcomes, never copy the CEO's words or guess at SourceX's reasoning, and count every ending against a stated cohort that includes the companies still open.
Read → - How to track questions waiting on the company: a question owner and deadline board that records who must answer, where the answer travels and the day you stop asking, while every answer stays out of your files
Track the question, never the answer. Each open item is one line: which permitted question was asked, who at the company can answer it, where the answer should travel, when it was asked, one reminder date and a drop date. When the answer comes, the line records that it came, by which route and on which day, and nothing it said. Questions SourceX raises in its review never appear on your board, and a decision, such as whether to apply, gets no reminder at all.
Read → - How to train customer-facing teams on data referral boundaries: eight role-play scenarios, each with the trap, the line and a passing answer
Train the boundary, not the pitch. Customer-facing staff need to hold five lines: the customer's records stay the customer's and never pass through the vendor, the CEO decides, any reward is disclosed, nothing is promised about fit, price or timing, and the introduction stays separate from pricing and renewals. Run eight short role-plays in which a realistic customer pushes on one line, score each answer against a written rubric, and let nobody mention SourceX to a customer until they pass.
Read → - How to train partners without promising they will earn: a six-module curriculum in which every lesson ends in a skill check and the reward math starts at $0
Train partners on behaviors you can observe, and leave income out of every learning objective. Each module should end in a skill check a trainer can score: screening a company at metadata level, spotting a duplicate, asking a CEO with an easy no, stating the reward rule correctly. Teach the reward as a formula whose first worked case is $0, because SourceX publishes no income projections and every reward depends on conditions no trainee controls. Then judge the course by what graduates do afterward.
Read → - How to transition clients from compliance to advisory, starting with their records
To transition clients from compliance to advisory, start with facts already in your file: the systems they run, how far back their records go and where the close gets stuck. A short records-and-systems review is a low-risk opener because it asks the client for nothing new and ends in a few priced options instead of a pitch.
Read → - How to treat intangible assets and records in a chapter 11 liquidation analysis
A chapter 11 liquidation analysis usually gives intangible assets, especially operational records, little or no value because it assumes no ready buyer in a hypothetical chapter 7. A records recovery line is defensible only with evidence of a real licensing route, such as a completed SourceX qualification, and it should stay conservative until a license is signed and paid.
Read → - How to turn a contrarian data thesis into testable questions: keep only the questions where the consensus and your bet predict different answers
Put the consensus view and your contrarian view side by side, write down what each predicts a CEO in your network will say about records the company already keeps, and keep only the questions where the two predictions differ. Ask those about the past, at metadata level, with the answer that counts against you written before the first call. A question that both views answer the same way cannot test anything, however good the conversation feels.
Read → - How to update a referral brief after material facts change: a four-tier materiality test, a versioned change log and a notice routine that never edits silently
Never edit an approved brief silently. When a fact it relies on changes, log the old value, the new one, the date you learned it and who told you, then grade the change. Cosmetic fixes wait for the next version. Changes to fit, scope, authority or the company's history with SourceX need a new numbered version approved by the CEO, a short note to SourceX saying what changed, and every earlier version kept on file.
Read → - How to use an entrepreneur-in-residence network responsibly: participation boundaries that let an EIR say which company and why, keep the fund's deal flow and any employer's secrets out of it, and leave the decision to the CEO
Ask an EIR network for judgment, not access. An entrepreneur in residence can tell you which established company they know from their own career, why its records might fit, and who could put the question to its CEO. What they saw in the fund's pitches and diligence, any former or current employer's confidential information and their own startup's interests stay out of it. An EIR may suggest who to ask and why; they never decide for a company, and nobody in the network collects company data for SourceX. The company's CEO decides.
Read → - How to use customer growth as a referral conversation starter: a six-rung question ladder that turns a growth headline into facts about records, rights and the CEO
Use customer growth as a reason to ask questions, never as evidence that a company fits. A rising customer count says a company is doing more work for more people. It does not say whether that work left records the company owns, how many years they span, whether the company reached 50 or more full-time employees at peak, or whether its CEO wants a licensing conversation. Climb a short ladder from the growth number to those facts, and make the first rung you cannot answer your next conversation.
Read → - How to use public AI research to ask better referral questions: a research-to-question translation guide that sorts papers by what they measured, drops what never survives translation and leaves three questions a CEO can answer from memory
Read a paper for what it measured, not for what it seems to say about demand. A finding about training data can point to a property of company records worth asking about: whether people wrote them, when, and whether they record what actually happened. Turn that property into one question the CEO can answer from memory, write down the answer that would end the conversation, and drop everything the paper never said: buyers, prices, and whether SourceX wants a given company's records. Three such questions per conversation is plenty.
Read → - How to value data assets in M&A: the cost, market and income approaches
Data assets in M&A are valued with the same three approaches used for other intangibles: cost (the price of recreating the records), market (what buyers paid for comparable data) and income (cash flows the data can earn). For a private company's operating records, an executed license with an independent party is the clearest market evidence a seller can show.
Read → - How to verify a founder-supplied growth claim before repeating it: a claim-source-date ledger that records who said it, when, what backs it and whether you may pass it on
Verify a founder's growth claim by logging it before it travels: the exact words, who said them and on what date, a record that corroborates or contradicts them, and whether you are allowed to pass them on. Then pick one treatment: state it with its source, attribute it to the CEO, ask the CEO to give it to SourceX directly, or hold it. For a SourceX introduction no growth claim decides fit; the program's review tests the facts underneath.
Read → - How to win sell-side mandates by showing owners every source of proceeds
Win more sell-side mandates by showing the owner something competing pitches often skip: a short data asset review that maps the company's systems, years of records and data rights, and flags whether a separate data license could add proceeds. It needs one metadata-only conversation, adds a single slide, and gives the owner a concrete reason to choose you.
Read → - How to wind down a company: an orderly plan that keeps the records
To wind down a company, the board picks the route (solvent dissolution, an assignment for the benefit of creditors or bankruptcy), then the team settles employees, customers, creditors and taxes, sells or licenses assets and files to dissolve. Before any system is cancelled, inventory it, keep admin access and decide what its history is worth.
Read → - How to work with your private equity sponsor as a portfolio company CEO
Working well with a private equity sponsor as CEO comes down to predictable reporting, board materials that lead with decisions, and bringing the sponsor in early on anything that touches cash, debt or risk. New options, such as licensing operational records directly to SourceX, belong on the agenda as a question for the board and lenders, not as a finished plan.
Read → - How to write a community resource page about data referrals: an eight-section evidence brief that gives every line a published source and a refresh trigger, sets the disclosure beside the link and takes the link down when the partnership ends
Write it as a short public reference that members can check line by line: what SourceX is, which companies may suit it, who decides, how the association is involved and could be paid, and what a member can do alone. Give every factual line a published source and a reason to refresh it, put the disclosure next to the partner link, mark that link as paid, and never name SourceX as a partner without its written authorization. Date the page, name the terms version it was checked against, and take the link down when the partnership ends.
Read → - How to write a founder note about an emerging data opportunity: a nine-part memo with a verb for every grade of evidence, a paragraph against your own thesis and one reply as the only ask
Write it as a dated, one-page memo that a skeptical founder could check line by line. State the thesis in one sentence and label it as your view, back it with no more than two primary sources, give the strongest evidence against it a paragraph of its own, turn it into one question a CEO can answer about their own records, and send it only to the few founders whose companies pass the published fit facts. Match every verb to its evidence: published analysis "estimates", a company announcement "says", your view is "we think", and gaps are named as gaps.
Read → - How to write about AI data without sounding like a gold rush pitch: eight windfall lines rewritten on one company's facts, with the evidence each rewrite rests on
Write about the company in front of you, not the market behind it. A gold rush pitch borrows its excitement from AI headlines: scarcity, huge sums, a closing window. An evidence-led message uses at most one sourced market fact, states the program terms as written, and builds everything else from what the owner told you about their own records. Test each sentence with one question, "how do you know?", and cut any line whose honest answer is "everyone says so".
Read → - How transportation insurance agents can turn the fleet renewal file into a referral screen
A transportation insurance agent's fleet renewal file already shows which trucking clients keep years of dispatch, safety and maintenance records in real systems. Fleets with 50+ full-time employees at peak (contractors excluded) and long operating histories can be introduced to SourceX for data licensing, while the agent never handles driver files, MVRs or camera video.
Read → - How UAE family offices and advisers can refer US companies to SourceX
UAE family offices, sponsors, advisers and US expats can join as partners and 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) they hold stakes in or know personally. The company must be a business in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE or Saudi Arabia with 50+ full-time employees at peak, rights to its records and an authorized sponsor. 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.
Read → - How UK advisers can refer US companies and what to check first
UK advisers can refer 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 if the business has 50+ full-time employees at peak, years of records and an authorized sponsor. Typical sources are US parents of UK subsidiaries, transatlantic deals and US clients. Check professional-body rules, UK tax treatment and US tax forms before accepting any reward.
Read → - How wholesale distributors are valued, and what raises or lowers the multiple
Distribution company valuation multiples start with the earnings basis: smaller owner-run distributors are usually priced on seller's discretionary earnings, larger ones on adjusted EBITDA. Within either range, buyers pay for stable gross margin, diversified customers and suppliers, clean inventory and value-added services. Quote, order and customer-service histories in the ERP can also support a separate data license.
Read → - Human adjudication records: how a support team settles two QA reviewers who disagree about an escalation
Human adjudication records are the written trail left when a third person settles a disagreement between two reviewers who judged the same work. In an ordinary support team, that is two QA reviewers scoring one escalated ticket differently, a lead checking the ticket history and ruling, and the reason and rule version written down. For a referral, what matters is whether the company kept both scores, the ticket, the ruling and its reason, and who can authorize a licensing discussion.
Read → - Human capital operating partners: spotting migrations and handling employee notice
Human capital operating partners in private equity are well placed to spot data licensing candidates because they see leadership changes, HR system migrations and reorganizations first, and they field employee questions about how work records are used. Their job is to flag records before systems are retired, route notice questions to counsel, and introduce qualifying companies.
Read → - IATF 16949 consultants: PPAP and APQP archives at auto suppliers
IATF 16949 consultants can identify tier suppliers whose own PFMEAs, control plans, 8D histories and APQP records may be licensable for AI training. OEM drawings and customer-specific requirements stay out. Consultants screen size, history and rights, then introduce qualifying suppliers to SourceX without handling any records.
Read → - ICF Code of Ethics and referral fees: what coaches should disclose, and when
The ICF Code of Ethics treats referral fees as a disclosure and conflict-of-interest matter: coaches are expected to tell clients and sponsors about compensation they may receive from third parties for referrals and to manage any conflict openly. Before introducing a client to SourceX, disclose the possible reward in writing and leave the decision with the client.
Read → - Identifying data licensing opportunities during a business sale
M&A advisors can find data licensing referrals during business sales by recognizing companies with 50+ peak employees, extensive records, and clear licensing rights. SourceX assesses and licenses approved business data directly from companies for AI training and evaluation, subject to acceptance at Closing and agreed terms. Partners only introduce the company, never handling data.
Read → - Illinois BIPA and call recordings: when voice data becomes biometric
Illinois BIPA regulates voiceprints, not ordinary call recordings, but audio becomes a problem when any system extracts a voice template from it. Before licensing contact center audio, owners should confirm that no vendor created voiceprints, check consent and retention records, and have counsel review the facts.
Read → - Illinois CPA commission rules: what to check before accepting a referral fee
Illinois CPAs should check two layers before accepting a commission or referral fee: the Illinois Public Accounting Act with IDFPR's rules, and, for AICPA members, ET 1.520, which bars commissions from clients receiving audits, reviews and certain other attest work and requires disclosure of permitted ones. Read the current Illinois text and document what you checked.
Read → - Incident containment handoff exception examples: a worked case of an account compromise that changed hands overnight
The incident records that explain a containment exception are the ones that pair each action with its approval, the person who owned the incident at that moment, and a later check that the action worked. The hardest exception sits at a shift change, when an incident is handed over as contained before every step is done. Below is one Illustrative case, worked step by step, and then how to recognize similar histories at a client without opening a single case.
Read → - Incident containment handoff records across systems: a map of the keys that join case tool, chat, consoles and provider portal
Reconstructing an incident containment handoff takes one identifier, the internal case number, reaching every other system: the chat channel where approvals were given, the identity and endpoint consoles where actions ran, the case history that records each owner change, and the outside provider's portal. Where a system cannot carry the case number, the join falls back on account IDs, hostnames and timestamps. Map which system holds each record, the key it carries, how long it keeps it and who owns it.
Read → - Incident containment handoffs: what to inventory before a response service transition
Before an incident response provider or retainer changes, inventory the records behind each containment handoff: the event timeline, the approvals for each containment action, the record of who owned the incident at each shift change, and the evidence that containment was verified. Note which system holds each (case tool, provider portal, chat, endpoint console), the years covered, the owner, and when access ends. Then introduce the incident response director, who can bring in the executive with authority to license.
Read → - Incident response histories: sensitive context requires a careful handoff, so this boundary guide sorts eight layers of an archive into what a partner may mention, may ask about and must leave alone
An incident response archive can point to a company worth introducing, but a partner should touch almost none of it. Mention only what the company has made public or approved, ask only metadata questions, such as how many closed cases, which years, which system and who wrote the reports, and never request, read or describe case files, indicators, privileged reports or breach notices. Find out whose each layer is: the company's own team, an outside response firm, counsel or a client. Then hand the conversation to the CEO, who decides whether to talk.
Read → - Incident-to-fix record chain: the identifiers that join each step, and where the joins fail
A company connects incident-to-fix records by carrying one identifier, usually the tracker's issue key, through every step: posted into the incident thread, used as the ticket itself, then repeated in the names engineers give their work so the code host can link back. The PR number then carries review and merge. The chain holds wherever someone typed the key and breaks wherever nobody did, most often on an emergency change opened after the status update.
Read → - Incident-to-fix records: a sample metadata packet for an introduction
A referral partner can describe incident-to-fix records without reading any of them: which systems hold the incident thread, the issue and the patch; how many incidents and over what years; which identifier links each step to the next; who owns each system; and where links are known to break. That metadata packet is enough for SourceX to decide whether a first conversation with the company makes sense.
Read → - Independent sponsor deal sourcing: what to offer owners who will not sell
Independent sponsor deal sourcing creates far more owner conversations than closed deals, and an owner who declines to sell can still be a fit for a scoped data license. If the company had 50+ full-time employees at peak (contractors excluded), years of records and rights to license them, a sponsor can introduce it to SourceX with the owner's permission.
Read → - Independent sponsor fees disclosure: when referral income needs investor consent
Independent sponsors and searchers should disclose referral income to capital partners whenever the introduction involves a company they control, pursue or advise, and whenever their documents cover third-party fees. Disclose in writing before introducing, seek consent where the agreement requires it, and confirm the details with securities counsel.
Read → - Independent sponsor fees explained: closing fee, monitoring fee and promote
Independent sponsor fees usually come in three layers: a closing fee when the acquisition funds, a management or monitoring fee from the portfolio company during the hold, and a promote on the capital partners' profits above agreed hurdles at exit. Each layer is negotiated deal by deal with capital partners, since a fundless sponsor has no standing fund terms.
Read → - Independent sponsor trends in 2026: what the signals mean for your post-close plan
Independent sponsor trends in 2026 center on three questions: what share of lower-middle-market deals sponsors lead, what terms capital partners require, and which sectors they favor. Owner succession keeps deal flow strong. One addition belongs in every post-close plan: a five-minute records-and-rights screen to see whether the company's operating records could be licensed.
Read → - Independent sponsors: explaining a data license to capital partners
An independent sponsor should explain a portfolio company's data license to co-investors before signing: check consent rights in the operating agreement, present a one-time payment as non-recurring, offer reputational controls, and disclose any referral reward. This guide gives the document checklist, a timing table and a short update email.
Read → - Installment referral reward ledger: a template that ties each line to an actual supplier payment
Each installment adds its own line only after SourceX has actually paid it to the referred company. The first line that meets every condition carries the USD 50,000 element plus 5% of its qualifying amount; each later line adds 5% of its own, and the running total is checked against 15% of the running base, with no cap. With three installments the first line is the largest and the two later lines add their 5%. A ledger with one line per paid installment makes this easy to check.
Read → - Insurance brokerage statement to reconciliation: tracing commissions across Applied Epic, Excel and the ERP
A referral partner can describe an insurance brokerage's statement-to-reconciliation history from metadata alone: which system records the placement and expected commission, how insurer statements arrive and where they are reconciled, whether a spreadsheet sits between the agency system and the ledger, how far back each goes, which identifier links a statement line to a policy, and who owns each step. Nobody opens a statement. The case to test is a cancellation that shows up on a later statement than the original commission.
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