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
- What a portfolio team should record about an eligibility exception: a twelve-field log, a written-review checklist and five situations that are not exceptions at all
Record six things: the published criterion the company misses, the fact that misses it, who asked SourceX to look anyway, the exact questions asked, SourceX's written answer with its date and scope, and the trigger that reopens the row. An exception exists only when SourceX says so in writing; a fund's ownership, a warm relationship or a partner's conviction is not one. Keep the log at metadata level, and never tell a founder an exception is coming.
Read → - What a private equity fund CFO does, and how to review a portfolio-linked referral reward
A private equity fund CFO runs fund finance: capital calls and distributions, the waterfall and carried interest, management fees and offsets, quarterly valuations, the annual audit, tax reporting and LP reporting. When anyone at the firm could earn a fee connected to a portfolio company, such as a SourceX referral reward, the CFO reviews it against the LPA first.
Read → - What a project-tool export of a client sign-off cannot show: one acceptance read before and after
Almost everything about what was signed off can be lost. A project tool's export of an accepted job shows that the sign-off task was ticked, when, and usually the account lead's note. It does not hold the customer's own words, which arrived by email, the request revision the work answered, or which edition of a linked annex the customer had open at the moment of sign-off. Those sit in the mailbox and the shared file store. Joined, the same task becomes a full case: request, delivered edition, customer wording, a later edit and the question that followed.
Read → - What a single introduction can unlock in the AI data economy: six gates from a trusted conversation to a paid license, who holds the key to each, and where the introducer's part ends
One introduction can unlock a chain of separate decisions: a CEO who understands what their records are and wants to talk, a verified application, a qualified company, a signed Master and deal Confirmation, data accepted at Closing, and then payment to the company, which is what can make the introducer's reward payable. Each gate has its own key-holder. The introducer holds only the first key, but how well that gate opens shapes the rest, and any later gate can end the chain.
Read → - What a software ecosystem can learn from a failed referral pilot: a blameless review of a ten-week stall and the product-trust scorecard to pass before trying again
Look for the cause of a stalled referral pilot in decisions made before the first email: who was chosen, by what data, who sent the message and what it implied. Review those decisions without blame, keeping every contacted customer in the record, including the ones who said nothing or complained. Then score product trust before trying again, because a customer who now wonders whether you sell their data is a cost the next pilot cannot repay. Relaunch only with opt-in customers and CEOs who asked for the conversation.
Read → - What a standalone automation run log loses: one failure read before and after its tickets and article history
A single-system export of a failed automation keeps what failed, when and with which error. It loses what people did about it: the invoices a clerk matched by hand, the judgment behind the fix, the macro and article that turned the fix into a rule, and the later tickets showing the rule worked. Read alone, a failure the business absorbed by hand for weeks looks like a short glitch that fixed itself. The missing context lives in the helpdesk and the knowledge base.
Read → - What a standalone Freshdesk export loses: one escalated complaint read before and after its retention context
A standalone Freshdesk export loses the decision and its cost. The ticket list export shows that a customer complained, when and how the ticket was categorized, but it does not include the full conversation or archived tickets, and nothing in it says whether the account team offered a credit, held the price or let the customer go. That reasoning sits in HubSpot property history, and the money sits in Xero, sometimes in two organizations at once.
Read → - What a standalone Greenhouse or Workday export loses: one hire read before and after its offer context
A single-system export keeps the facts its own system recorded and drops the reasons around them. A Greenhouse export shows how an offer was negotiated but not what pay the employee started on. A Workday export shows the hire and every later pay change but not what the candidate signed. Read alone, the correction of a keying error looks like an early raise. The missing context sits in the other systems: the offer versions, the signed letter and its completion time, and the payroll query that exposed the gap.
Read → - What a standalone Intercom export loses: one complaint read before and after its product-change context
A single-system export keeps what happened inside that system and drops why. An Intercom export alone shows a customer complaining and an agent replying with a help article. It cannot show that the complaint was already a known product issue, that a fix had been decided and shipped, what the policy said on the day of the reply, or that the article the agent cited was out of date. Those facts live in Linear, Notion and the article's own version history.
Read → - What a standalone LIMS export loses: one corrected lab result read before and after its QMS and report context
A standalone LIMS export loses the reason and the approval. It shows that a value changed, both numbers and when, but not why, who signed off, which neighboring samples were rechecked or which report version the customer is relying on. Those facts sit in the quality system and in controlled documents. Without them, a fixed result looks like an unexplained edit, and the wrong unit still sitting in the customer's own systems never appears.
Read → - What a standalone model, claim sheet or ERP export loses: one progress claim read before and after its context
Read alone, each system tells the truth and hides the reason. The design model shows two issues of a parking deck, but not which issue fed which payment application. The spreadsheet shows 3,250 feet of cable tray billed, but not that 450 feet sit in both issues. The ERP shows a certified amount cut the following month, but not why. Only the joined history shows one length counted twice, caught by a field count and written back.
Read → - What a standalone monday.com export loses: one agency job read before and after its billing context
A monday.com export alone shows that scope changed and who approved it, but not what the change was worth, what was delivered or what was billed. A Dropbox export shows that a file changed, not that the client accepted it. A QuickBooks export shows $18,400, then a credit and $22,900, but not why. Each single export answers a question about its own tool. The context that explains the job, an invoice built from an outdated scope and corrected weeks later, only appears when the three are read together.
Read → - What a standalone Oracle payables export loses: one new vendor read before and after its portal and inbox context
A single-system payables export keeps the outcome and loses the approval story. An Oracle export shows a vendor, a bank account and a first payment. It does not show who asked for the bank change, how the change was verified, whether proof was collected, or whether the way the change was entered could have raised an approval at all. Read alone, a routine change and an unverified one look identical. The supplier portal and the shared inbox hold the difference, and the gap table below shows where.
Read → - What a standalone sales export loses: one branch's promotion-to-service-recovery Sunday, read before and after its context
A single-system export keeps one true fact and drops the reason behind it. The point-of-sale file shows a busy Sunday and a markdown that sold well, but not that the store had planned for an ordinary day, that three team members were pulled off replenishment to cope, that shoppers complained about the wait, or that the chain handed out store credit to keep them. Those facts sit in the scheduling tool and the service desk log, and they turn a sales peak into a service-recovery story.
Read → - What a standalone Salesforce export loses: one renewal read before and after its call and contract context
A standalone Salesforce export keeps a deal's skeleton: account, opportunity, stage, amount, dates and whatever the seller typed into notes. It loses what was said on calls, how terms moved in negotiation and what was finally signed, and it cannot show a promise that never became a term. That context lives in the call recorder and the contract system. Read together with the CRM, they show where talk and paper diverged, which is the part a single export hides.
Read → - What a standalone Samsara export loses: one truck repair read before and after its TMS and shop records
A single-system driver-report-to-asset-return export loses the reasons and the money. A telematics export keeps the reported fault, the vehicle and its cleared status, sometimes with the technician who signed it off. It drops how long the truck was out of service, which load moved and whether it delivered on time, what the repair cost, who approved it and whether anyone checked the truck before it went back out. That context lives in the TMS, the shop system and often an inbox.
Read → - What a standalone SAP EWM export loses: one spring failure read before and after its supplier-lot context
Each system exported alone keeps its own part of the story and loses the connection between the decision and the material. The quality file keeps the nonconformance, the disposition and the approver but not which supplier lot was involved. The production file keeps orders and test results but not the lot behind them or what quality decided. The warehouse file keeps receipts and relabels but not that the material failed. Joined, they fill each other's gaps, except at any step where no key was ever written.
Read → - What a standalone warehouse or ledger export loses: one freight claim read before and after its carrier and finance context
A single-system export keeps one team's view and loses the reason the money moved. A warehouse export shows what shipped, when and in how many units, but not the claim, the carrier's offer or the write-off. A finance export shows a credit and a write-off with no link to a shipment or a cause. Read alone, each one leads a reviewer to a confident and wrong conclusion. The connected history explains the outcome, and the gap table below shows where each missing piece lives.
Read → - What a standalone Zendesk export loses: one service credit read before and after its billing and ledger context
A single-system support-to-credit export keeps one side of the decision. A help desk export keeps the conversation and loses the money: it shows the complaint, the agent's reply and an approval field, but not whether a credit was issued, against which invoice, or what the customer still owed. A billing export keeps the money and loses the reason. Read alone, each one supports a confident conclusion that the other would contradict. The joined history explains both, and the gap table below shows where each missing piece lives.
Read → - What a web-shop export of a refunded order cannot explain: catalog context read before and after
A web-shop export loses the reasons behind a correction. Adobe's product import and export format needs only one value, the product code, with one row per item, so the file describes each item as it reads today. A refund issued after a supplier revision then looks unprovoked: the description matches what shipped, and nothing records that a buyer saw an older description first. The explanation lives elsewhere: in the product information system's change history, the publishing job's logs and the ERP's refund trail.
Read → - What AI roll-ups look for in acquisitions, and what that means for your clients
AI roll-ups look for services firms whose delivery is labor-heavy, repeatable and well documented, with loyal clients and workflows software can take over. Those same records can interest AI labs and data users: a client with 50+ full-time employees at peak and rights to its own workflow records may license them directly to SourceX without selling.
Read → - What AI-training terms of service backlashes teach a company licensing its data
Public backlashes over AI-training clauses in terms of service show three failures: vague scope, late explanations and no real choice. A company licensing its own operational records avoids them by naming systems and years precisely, telling customers and staff before signing, and writing the license in plain language.
Read → - What an integration team can tell a referral partner: a permissible summary interview guide with ten questions, the level of detail each answer may reach, and the point where only the acquirer's CEO can answer
An integration team can tell a referral partner that records exist, roughly what shape they are in and when integration will move them, at a level of detail its employer is comfortable with. It cannot hand over records, customer details or deal terms, and it does not decide anything: once a deal closes, the acquirer's CEO decides for the acquired company. Before closing, the same people may sit behind clean-team limits. Ask summary questions, take "ask the CEO" as a complete answer, and route the introduction there.
Read → - What an investment committee should see about channel evidence: a ten-line appendix where every count names the record behind it, and no forecast gets a line
An investment committee should see channel evidence as records, not forecasts: how many unique companies the fund introduced with each CEO's knowledge, how many were credited after a verified application, how many reached a supplier agreement, how many produced a reward that has actually been paid, and how many are still open. Every count needs its source record, its export date and its denominator. Projected rewards, pipeline value and run rates stay out.
Read → - What an M&A advisor should ask about legacy systems: a 14-question metadata interview that dates each old system, shows who will control it after the deal and stops before anyone opens a file
Ask about the systems, never their contents. For each old system: which record families it holds and for which years, whether it still runs or sits read-only, who administers it, whose name is on the contract, whether it moves in the deal, when it will be switched off, and whether any of it was ever licensed for AI training. Ask the company's CEO, or the person the CEO names, once the CEO wants the conversation, and leave what the data room taught you out of it.
Read → - What an M&A process letter contains in each round, and how to disclose a data license
An M&A process letter is the sell-side advisor's instructions to bidders: what to submit, by when and under which conduct rules. The first-round letter asks for a non-binding indication of interest; the second-round letter asks for a final bid and a purchase agreement markup. Disclose any data license in both rounds so bidders price it up front.
Read → - What an RL environment needs from a real business archive: task, state, tool and outcome records
An RL environment for business work needs five things from records: a task request, the starting state of the relevant systems, the tools and actions allowed, the policy that limits them, and an end state a program can check. Tickets and emails supply tasks, change histories supply starting states, system permissions supply tools, policy documents supply limits, and the final record values supply the outcome. Archives that keep field-level history are the ones that can supply all five.
Read → - What an unsuccessful pilot can teach a venture platform: five failure types, two false alarms and a one-page learning report that can say stop
An unsuccessful referral pilot teaches a venture platform one lesson per failure type, so name the type before drawing the lesson. Place every company at the stage where it stopped and give it one label: empty cohort, no willing relationship owner, misread offer, SourceX decline or platform slippage, or one of two false alarms, still moving and informed no. Read that pattern beside the hours logged and what founders said. A zero caused by an empty cohort and indifferent founders means stop.
Read → - What buyers look for when buying a business, and how brokers can prepare clients
Buyers look for trustworthy earnings, repeat revenue, low customer concentration, management depth, documented processes and clean records they can verify. Brokers can prepare a client for diligence and for data licensing at once, because the same organized, retained records serve both.
Read → - What can a private equity team do with a deal it passed on?
A private equity firm usually treats passed deals as firm opportunities: the team can decline cleanly, keep the company warm, route it to a portfolio company or another buyer through the firm, or point the owner to a non-sale option. A personal finder's fee raises conflict and registration questions, so clear any SourceX introduction under the firm's outside-compensation policy first.
Read → - What capital providers look for in an independent sponsor, and how to present upside
Capital providers look for an independent sponsor with a relevant track record, a well-sourced deal, real alignment through the sponsor's own money and deferred fees, sensible governance and a written value creation plan that works without optimistic assumptions. Upside that depends on outside conditions, such as a data license, belongs outside the base case and needs capital-partner consent.
Read → - What CAS growth at Top 100 accounting firms means for client referrals
Client accounting services are a growth focus at many Top 100 accounting firms, and the dated figures sit in the annual Top 100 rankings and CAS benchmark surveys. For referrals, the useful effect is reach: CAS teams see client systems every month, so they can spot data-rich companies, provided every introduction clears risk management, independence and referral-fee checks first.
Read → - What changed after we explained eligibility up front? A switch-date comprehension analysis that codes each CEO's own words before and after the change, re-checks every company that ruled itself out and reports nothing until both periods close
Nobody can say yet. No network has published a before-and-after reading of this change, SourceX has released no figures on it, and this page reports none. What it publishes is the analysis a platform research team would run after moving SourceX's published fit facts into the first message a CEO receives: one dated switch, at least three monthly readings on each side, every CEO asked kept in the denominator, comprehension coded from the CEO's own written words, and a one-time re-check of every company that ruled itself out.
Read → - What CMMC enclave scoping tells MSPs and RPOs about data licensing
A CMMC MSP or RPO can use enclave scoping to separate controlled unclassified information, which stays out entirely, from commercial operating records outside the boundary. Clients with 50+ full-time employees at peak, years of history and clear licensing rights can then be introduced to SourceX, which handles inventory, SourceX review and contracting.
Read → - What corporate compliance teams need to review in a referral program: a 24-question pack that sorts each question by who can answer it, SourceX's published documents, your own policies, counsel or SourceX in writing, and ties the approval to one terms version
Compliance needs to clear four things before anyone at the corporate records a SourceX introduction: who the partner is and who signs for it, whether anyone may accept the reward, what information may travel to SourceX, and what anyone may say about SourceX, the corporate and the company. SourceX's published terms and its sample Channel Partner Agreement answer most program questions. Your own policies answer the employee questions, counsel answers the rest, and none of them decides for the operating company: its CEO does.
Read → - What counts as an active venture channel partner? A three-test definition that counts verified applications from new companies, not logins or signatures
Count a venture partner account as active in a period only when a company it introduced, with the CEO's knowledge, submitted a verified application in that period and was not already known to SourceX. Registrations, signed agreements, link clicks and introductions sent are earlier stages worth reporting, but they measure intent, not channel activity. Report each stage separately, count unique companies rather than people or emails, and keep unresolved cases in the denominator until they close.
Read → - What counts as useful evidence of an authorized sponsor? A six-check test that grades each proof, from the CEO's own email down to a forwarded screenshot
Useful evidence shows, in the company's own words, who is speaking, that they write from the company's real domain, that the CEO is the speaker or has named them, what they may share and when it was said, ideally confirmed outside one email thread. The strongest single item is a short, dated message from the CEO's company account naming the sponsor and the scope. A sponsor's report of the CEO's view, a job title or a forwarded screenshot is a lead to verify, not evidence.
Read → - What cross-border referrers should know before requesting documents: a no-document first-step checklist that limits a partner's asks to public information and the CEO's agreement to talk, and leaves every file with the company
Nothing in a SourceX introduction needs a company document to pass through you, so do not ask for one. A partner may ask for two things: information the company has already made public, and the CEO's agreement to a conversation. Contracts, org charts, record samples, exports, system lists and registration papers stay with the company, and whatever SourceX's own process needs, it arranges with the company directly. Across a border the case gets stronger, because every file you hold raises questions you are not placed to answer.
Read → - What data does AI dispatching need, and where do dispatcher decision records live?
AI dispatching needs records of real dispatcher decisions linked to outcomes: assignments, overrides, exception messages and job close-outs. They live in transportation management and field service systems plus the email and chat around them. SourceX licenses such records directly from eligible 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); partners introduce companies with years of dispatch history.
Read → - What do business clients expect from accounting firms in 2026?
Business clients in 2026 expect accounting firms to be proactive, advisory and able to answer AI questions with specific steps. One concrete step is asking an owner whether the company's records have licensing value, once the firm has cleared its independence and fee rules and the owner has agreed to an introduction.
Read → - What do CFP Board standards say about conflicts and referral compensation?
CFP Board standards expect planners to disclose compensation and manage material conflicts of interest before they affect a client. For a referral reward, that means telling the client in writing before the introduction, documenting that the client asked, and checking your firm's own rules. Read the current text on the CFP Board website.
Read → - What does a private equity firm data team do, and where do data assets fit?
A private equity firm's data team usually builds sourcing models, diligence analytics and portfolio monitoring from data the firm collects or buys. An asset view adds a further question: which portfolio companies hold years of licensable records of real work. Licensing itself stays company-led, with each company deciding and contracting with SourceX directly.
Read → - What founders think data licensing means before the first call: a ten-pair belief survey that counts the skeptics and the silent
Nobody has measured this yet. SourceX has not run or published a founder belief survey, so any claim about what most founders assume before a first call is a guess, and the stories partners trade are not evidence either. This page publishes the instrument instead: ten paired belief statements, each scored against a published program fact, asked before anyone explains anything, with every invited founder counted, including those who decline or never reply. Results will be reported only after real, consented responses exist.
Read → - What happens after ERP hypercare, and why it is the last good moment to find old records
After ERP go-live hypercare, the project team disbands and the legacy system heads toward shutdown, so this is the last time someone knows where every record lives. Raise the old-records question before final sign-off and send the owner a one-page handoff note naming a retention decision-maker.
Read → - What happens to a fund's referral when the company is sold? The milestone it reached before closing decides, and this notification checklist says who must hear what, and when
Nothing in the program terms cancels a referral because the company changes hands, and nothing carries it forward on its own either. What survives depends on the milestone it reached before closing. Credit is still decided from dated records, the 90-day attribution window keeps running, the decision to continue passes to the acquirer's CEO, the company joins the buyer group for the once-per-company USD 50,000 floor, and payment conditions stay as written. The fund's job is to make sure the right people hear the right facts, at signing and at closing.
Read → - What happens to an EV startup's test logs and supplier-quality records in bankruptcy?
In an EV or hardware startup bankruptcy, bidders often focus on IP and equipment, so PLM, test-bench and supplier-quality records can lapse unless someone preserves them. Restructuring advisors can inventory them by metadata, check ownership, supplier and export limits, and, with estate authority, introduce them to SourceX for a possible AI-data license.
Read → - What happens to company records when private credit lenders take the keys
Private credit lenders take the keys when a sponsor hands a struggling portfolio company to them through a debt-for-equity swap or consensual foreclosure. The company's records normally stay with the business, but admin access, retention settings and data rights should be settled before handover. Afterwards, the new board can weigh a SourceX records license, which needs no new capital.
Read → - What happens to data when a transition services agreement ends
When a transition services agreement ends, the seller stops running the carved-out company's systems, and historical data either migrates to the new owner, stays with the seller or is deleted. The purchase agreement, not the TSA, decides who owns which records. Settle ownership and extract the full history before cutoff; only the rights holder can later license it.
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