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
- Appeal-to-course-correction missing context: one rubric fix read from an LMS export alone, then with its ticket and appeal
A single-system export loses the reason and the reach. An LMS export can show the current rubric and sometimes when it was edited. It cannot show that a learner's appeal caused the edit, which intake raised the problem, which delivery groups actually received the new wording, or whether learners graded under the old wording were reviewed. Those facts live in the support desk, the assessment platform and the LMS sync history, and they only make sense read together.
Read → - Appeal-to-course-correction record chain: the keys that join a support ticket, an appeal decision and a versioned rubric change
A company connects appeal-to-course-correction records by passing a reference number forward at every hand-off: the help desk ticket number onto the appeal, the appeal number onto the marking-scheme change, and a named version onto all three. Ticket and appeal numbers are often present. The version is the identifier most companies skip, storing a course title and leaving the edition implied by a date. Once that happens, nobody can later prove which wording a learner challenged, or whether the repair reached them.
Read → - Appointment referral reconciliation: what to inventory before an administrative platform migration
Before an administrative platform migration, inventory the full life of a referral, not just its open or closed status: the original referral request with its intended service and location, every scheduling event, the work-queue or service desk notes made when a request could not be matched, the location and provider mapping tables, and the closure confirmation. Record which system holds each, how many years exist, who controls the records under the company's contracts and when legacy access ends.
Read → - Approval-to-delivery missing context: what a Teams export alone loses, shown before and after the Planner and SharePoint records
A single-system export keeps one fact and loses the decision around it. A Teams export shows that someone posted "approved" and when. It does not show which document version was approved, whether the related task closed, or which file the client finally accepted. In the Illustrative case on this page, the context missing from the Teams export is precisely what reveals that the client received a version saved after the approval. Each piece of that context is held in Planner or SharePoint, by a different owner.
Read → - Approval-to-delivery record chain: joining a Teams approval, a Planner task and a SharePoint file version end to end
A company connects approval-to-delivery records by finding the shared key at each hand-off: a link or file reference from the Teams approval to the Planner task, the task's attachment pointing at the SharePoint file, a version number tying the approval to the exact file version, and a transmittal or acceptance record tying that version to the client. Only the task-to-file key is a built-in feature. The rest depend on habit or on matching timestamps, and the record should say which.
Read → - Approval-to-delivery records in Teams, Planner and SharePoint: a metadata packet for an introduction
A partner can collect a metadata packet: which Microsoft 365 tools hold each step from approval message to task to accepted document, the date range and rough volume of each, the object types (chat message, channel post, task, file version), who administers each system, and which links between steps are known or unknown. Nothing in the packet requires opening a message, task or file. The open question to flag is a document that changed after someone approved it informally.
Read → - Are workers' compensation records PHI? HIPAA limits for claims notes and licensing
Workers' compensation records are PHI only when a HIPAA covered entity or its business associate holds them in that role, so the answer depends on the holder and the line of business. Any PHI offered for licensing generally needs HIPAA de-identification or authorization, and state rules and contracts may still apply. Confirm with counsel.
Read → - Article 9 sales of IP and data collateral: running a defensible disposition
An Article 9 sale of intellectual property lets a secured lender dispose of IP and data collateral after default without going to court, provided every aspect is commercially reasonable and the required notices are sent. Article 9 also treats a license as a disposition, so operational records can be licensed alongside the IP sale to add to the recovery.
Read → - Assessment appeal resolution across systems: a system map of the records, linking keys and owners
To reconstruct an assessment appeal across systems you need four joins: candidate to attempt, attempt to the version of the marking scheme (the rubric) in force, attempt to the appeal case, and the appeal decision back to the revised score. Each join depends on an identifier that both systems recorded, such as an attempt ID or case ID. The scheme-version join is the one most often missing, because many setups keep only the latest scheme. An advisor maps these at metadata level and never handles the records.
Read → - Assessment appeal resolution records: how a company shows the way an exception was handled
The records that explain an appeal are the ones that show the problem, the authorized action and the checked result: the candidate's response, the rubric version in force, the first and second markers' scores and comments, the appeal grounds, the panel decision with its reasoning, and any rubric change that followed. Together they show how a valid answer outside the original rubric was handled. An assessment systems advisor asks the head of academic operations about them at metadata level, then introduces the executive who can authorize a licensing discussion.
Read → - Association member value proposition ideas, including AI and data education
An association member value proposition is the clear promise of what members get for their dues that they cannot easily get elsewhere: advocacy, standards, research, education, connections and visibility. A timely addition is AI education, including how member companies can evaluate licensing their own records directly to SourceX, a benefit that never requires the association to collect member data.
Read → - ASU 2025-06 explained: new internal-use software rules and the evidence they require
ASU 2025-06 removes the project stages from internal-use software accounting under ASC 350-40. Companies capitalize costs once management has authorized and committed to funding a project and completion is probable, which requires any significant development uncertainty to be resolved. It applies to all entities for annual periods beginning after December 15, 2027, with early adoption permitted.
Read → - Attribution eligibility and payment eligibility are two gates: an event map and a status card that show which one a referral is waiting behind
Attribution eligibility answers whose introduction counts for a company. Payment eligibility answers whether a reward is owed yet, and how much. They are separate gates, decided at different times from different records. The first closes early: the first valid introduction of a new company within 90 days is credited when the company submits a verified application. The second opens late and keeps moving: it waits on acceptance, cleared funds, the supplier being paid, finance approval and your details, and it shrinks if the payout is reduced.
Read → - B2B referral fee structures: percentage, flat fee and capped share
B2B referral fees usually take one of four forms: a flat fee, a percentage of revenue, a tiered scale or a capped share. Each rewards different behavior. SourceX pays the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, where the Actual Supplier Payout is the eligible licensing compensation SourceX actually pays the referred company, excluding separately itemized taxes and expense reimbursements; the USD 50,000 element applies once per referred company, on its first qualifying transaction, and further qualifying transactions within the 12-month Repeat Window pay 15%, 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.
Read → - Back-office AI agents in portfolio companies: the records that train them
Back-office AI agents handle multi-step finance, support and operations work such as invoice exceptions, collections follow-up and ticket triage. Builders train and test them on records of real work, which are scarce on the public web. Portfolio companies with years of such records can sit on the supply side too, licensing them directly to SourceX.
Read → - Backlog and book-to-bill in engineering firm due diligence: what buyers test and what it proves
Buyers test an engineering firm's backlog by checking whether it is signed, funded, convertible to revenue and independent of a few principals, then reading book-to-bill for direction. The proposal, project and QA/QC records that prove this are also the firm's work records, which may be licensable directly to SourceX for AI training.
Read → - Backorder substitution decisions across ERP, CRM and email: a system map of records and linking keys
To reconstruct a backorder substitution across systems you need five joins: the order line, the original and substitute item, the time of the decision, the customer approver, and the outcome. The ERP holds the order and item keys; the CRM and email hold the approval and the feedback. The joins survive only where both sides recorded the same identifier, usually the sales order number. The approver join is the most fragile and the one that matters most for licensing, because it is where customer personal data sits.
Read → - Backorder substitution decisions: the records that explain how a distributor handled the exception
The records that explain a backorder substitution are the availability snapshot that showed the shortage, the substitute offered and why, the customer's approval, the shipped order, and any note on how the substitute worked in use. Together they show the problem, the authorized choice and the checked result. A distribution ERP consultant asks the sales operations director about them at metadata level, then introduces the executive who can authorize a licensing discussion: the CEO, or the owner in an owner-run distributor.
Read → - Backup restore validation hard case, step by step: the restore that passed and the application that failed
A restore validation exception is explained by the decisions around it, not by the status codes. In the Illustrative case below, a test reported success, the application still failed, a technician found why, the client refused to accept a softer outcome, an approved fix followed and a retest proved it. Each of those moments left its own record, owned by a different person, and the sequence is what turns a log into evidence of judgment.
Read → - Backup restore validation records: what a partner should bring to a company introduction
A useful introduction about backup restore validation describes the records, not the data itself: which restore logs, integrity checks and client sign-offs exist, which systems hold them, how many years they cover, and who can authorize a licensing discussion. Restore tests that failed and were fixed are the most informative part, because they link an exception to an action and a checked outcome. Whether any of it can be licensed depends on rights, qualification and the proposed use.
Read → - Backup restore validation system map: which system holds each record and the keys that join one case
Following one restore validation case end to end takes four systems and four identifiers. Think of them as nodes in a small network: the backup console, the service desk, the document store for signed reports, and the client register. The identifiers that travel between them are the run ID, the incident number, the server name with its quarter, and the client code. Drop any one and a red result and a later green one sit side by side with nothing explaining the change.
Read → - Backup vendor switch: the restore test that reveals a data introduction
A backup vendor switch is the moment a company proves whether its history can come back in one piece. Ask the owner one metadata question: has the company verified that archived records can be restored with their links, so a ticket still points to its customer thread, approval and invoice? If those chains exist and the company is eligible, introduce the decision-maker to SourceX. You never touch the records, and any reward depends on a qualifying paid handoff under the [terms](/terms).
Read → - Bain's Global Private Equity Report 2026: what operating partners should change
Bain's 2026 report shows buyout holds around seven years, almost 40% of portfolio companies held beyond five years, and about 32,000 unsold companies worth $3.8 trillion. For operating teams, that means re-underwriting late holds and adding non-dilutive levers, including licensing operating records directly to SourceX where companies qualify.
Read → - Bankruptcy Code section 504: does it reach an outside referral reward?
Section 504 generally restricts estate professionals from sharing estate compensation with people outside their firm, but a SourceX reward is paid separately by SourceX, not from estate funds. Whether it still needs disclosure or court approval depends on your role, the case and your counsel's advice.
Read → - Bankruptcy data sales in the AI era: what restructuring practitioners now watch
In bankruptcy, data can be sold or licensed as estate property, but the debtor's privacy promises still bind it: section 363(b)(1) limits transfers of personally identifiable information that a privacy policy prohibited, often requiring a consumer privacy ombudsman and court approval. Operational business records licensed for AI training raise narrower questions, but still need redaction and proper authority.
Read → - Bankruptcy Rule 2014: should referral relationships be disclosed?
Yes, assume a referral relationship tied to estate records should be put to counsel for disclosure. Rule 2014 asks professionals seeking retention to disclose connections, and disinterestedness turns on them. Disclose the reward, decline it, or do not introduce; the estate can still benefit from a licensing introduction.
Read → - Bartz v. Anthropic explained: the authors settlement and what it means for licensed data
Bartz v. Anthropic is a copyright case brought by book authors in 2024. In June 2025 the court found training on lawfully bought books was fair use but sent claims over pirated library copies toward trial, and the parties then agreed a class settlement. The lesson for licensed data: how material was acquired matters, so documented provenance carries weight.
Read → - Become a SourceX referral partner
SourceX's referral program allows professionals to introduce qualifying companies to license their operational data to SourceX. Partners earn by facilitating these introductions through a simple online process.
Read → - Before a dispatch vendor change: a retention timeline for emergency work order prioritization records
Before a dispatch vendor change, inventory each record class against its own deletion point: call recordings usually go first, then priority change history held in audit logs, then SLA timers once the old platform is decommissioned, and closed work orders when read-only access ends. Open jobs, sites and assets normally move to the new vendor. For each class, record the years covered, the owner, the real date in writing and who must approve keeping it. Keep the inventory at metadata level.
Read → - Before a flag platform replacement: a retention timeline for feature flag rollback history
Before a flag platform is replaced, inventory four facts for each record type: what it is, the years it covers, who owns the system, and the real date access ends. Then look at the order in which records disappear. Dashboard recovery checks usually go first, chat messages go at whatever retention the workspace sets, and the old platform's change history ends with its contract. Incident timelines and postmortems tend to survive. Nothing should be kept without the authority to keep it.
Read → - Before a pricing transformation: a retention timeline for special pricing agreement exception history
Before a pricing transformation, inventory the special pricing approvals as they were, with their original validity dates, before new price structures are loaded over them. Then list the pricing requests in the quote tool, claims and rejections in supplier portals, and the configuration history of the rules that let exceptions through. For each, record the years covered, the owner and the real date it stops being reachable. The risk is less deliberate deletion than history being quietly reshaped.
Read → - Before a pricing-model migration: a retention timeline for usage billing correction records
Before a pricing-model migration, inventory the records that the new model does not need on day one but that explain every past correction: raw meter events, retired plans and price books, CRM amendment history, closed dispute cases, credit approvals in email or chat, and the credit notes that settled them. For each, record where it lives, how many years it covers, who owns the system, and the documented date access ends. Short-lived logs disappear first; invoices and credit notes usually outlast everything else, without the reasons behind them.
Read → - Before a processor migration: a retention timeline for merchant settlement records
Before a processor migration, list each settlement record class with four facts: where it lives, how far back it goes, who administers it and the documented date access ends. A migration moves future payments, not the past. In the Illustrative plan below, transaction API access and portal settlement reports go first, then the reconciliation tool and approver mailboxes, while ledger journals survive. Keeping any of it is a decision for the records owner and counsel, not the advisor.
Read → - Before a SaaS migration strips the context: what to inventory, and when to make the introduction
Before a SaaS migration, a company should inventory the context that explains its records, not only the records: activity history, app-specific fields, custom events and notifications, user properties and the settings that shaped each workflow. Migration tools often move the core objects and leave those behind. The inventory is metadata only (what exists, how many years, which system, who owns it), and it gives the owner time to decide what to keep before an export deadline closes the option.
Read → - Before a service platform migration: a retention timeline for first-visit failure history
Before a service platform migration, inventory each record class behind first-visit failures (work orders, technician notes and attachments, part issues, inventory ledgers, callback jobs, sign-offs), the years each covers, who owns each system and the written cutover date. Then follow the order of loss: images on personal devices go first, field change history ages out on a rolling limit, and closed jobs, part-issue history and attachments are often left behind at cutover. Nothing should be kept without the authority to keep it.
Read → - Before an accountant accepts a referral reward, check the applicable rules: a ten-line service-and-jurisdiction review that names what to ask your board, society or counsel, run when you introduce, when your work for the client changes and before payment
Before accepting a referral reward, an accountant should learn from their state board, professional society or counsel which rules on commissions, referral fees, disclosure and independence apply to them for this particular client. Two sets of facts drive the answer: the services they and their firm perform for the company, and where they are licensed and practice. Both can change between an introduction and a payment months later, so the check is repeated. This page gives no legal or professional-conduct advice; it shows what to ask and whom.
Read → - Before an assessment platform renewal: a retention timeline for appeal resolution records
Before a platform renewal changes what is kept, list five facts for each appeal record class: what the class is, the years it covers, which system and team hold it, what the vendor documents as exportable, and the real date access ends. Then add the company's existing retention rule for that class. A renewal carries active candidates, current rubrics and open appeals. Closed appeals, superseded rubrics and marker comments on old sittings are the history most often left behind, and grade history can be trimmed earlier still.
Read → - Before an asset register cleanup: a retention timeline for warranty dispute history
Before an asset register cleanup, inventory each record class behind warranty disputes: install records, component trees, old-to-new serial links, past warranty term versions, claims and rejection reasons, appeals and approvals, and supplier recoveries. For each, note the years held, the system, the owner and the stage of the cleanup that touches it. Old serials and orphaned components usually disappear first. The records owner, with the CFO or COO, decides what is kept.
Read → - Before an expense policy redesign: a retention timeline for exception review history
Before an expense policy redesign, inventory the context that disappears first: retired audit rules and exception codes, the superseded policy text with its effective dates, and HRIS grade and manager history if those fields are overwritten. Receipts and reimbursements usually sit under longer tax and payroll retention and are rarely the first loss. Note each record type's owner and the date it becomes unrecoverable, and leave any decision to keep it to finance, HR and counsel.
Read → - Before an inventory platform rollout: a retention timeline for backorder substitution history
Before an inventory platform rollout, list each substitution record class, the years it covers, the system and team that hold it, what the migration plan says moves, and the real date read access to the old system ends. Then record the company's own retention rule for each class. A rollout usually migrates item masters, open orders and current balances. Closed orders, order change history, substitution cross-references and the CRM notes and emails tied to them are the parts most often left behind, and some go before the rollout starts.
Read → - Before and after: a landlord waiver condition read from a standalone Salesforce FSC export, then with Box and servicing context
A single-system credit-condition-to-cure export loses the story around the decision. A Salesforce Financial Services Cloud export can show a checklist item and its approval steps, but not the evidence file itself, the servicing outcome, or a cure recorded under a related borrower's account. Read alone, a condition the lender cured on time can look rejected and still open. The missing context lives in the document store, in servicing and in the links between related accounts.
Read → - Before and after: one chargeback read from a standalone export, then with CRM and warehouse context
A single-system export of a dispute keeps the charge, the reason code, the deadline and the outcome. It loses the customer's side of the story (the call, the complaint, the promise), the delivery record that answers the reason code, and any link to a second order such as a replacement. Read alone, a dispute the seller handled well can look like one it should lose. The context lives in the CRM and the warehouse or carrier records, owned by different teams.
Read → - Before and after: one partial bundle refund read from a Shopify export alone, then with its ticket, return and inspection note
A single-system export of an ecommerce order keeps the amounts: what was charged, what went back and when. It loses why. The customer's request, what the warehouse actually received, the conversation that settled a disputed item and the reason a refund was partial all live elsewhere, usually in the helpdesk, the returns app and a warehouse note. Read alone, a careful partial refund can look like a mistake or a short-changed customer.
Read → - Before and after: one price-lock deal read from an Outlook export alone, then with its approval and signature records
A single-system negotiation-to-contract export loses everything that happened outside that system. An Outlook export keeps the conversation and the draft attachments, but it loses the pricing policy the request broke, the approval and its conditions, and proof of which draft was finally signed. Salesforce alone loses the customer's reasons. DocuSign alone loses the approval. Only the three together show whether the signed terms match what was approved, which matters most when a late redline changes the promised scope.
Read → - Before and after: one unbilled drawing revision read from three separate exports, then joined
A single-system export of RFI-to-paid-change records loses the joins between question, drawing and money. The RFI log shows questions and answers but not which answers cost anything. The markup file shows the design conversation but carries no commercial status. The accounting export shows approved changes and billing but is silent about any revision that never got approval. That silence is the biggest loss: a missing record cannot be seen from inside the system that should have held it.
Read → - Before and after: one usage correction read from a standalone Stripe export, then with billing, contract and ledger context
A single-system usage-to-revenue-correction export loses the reasons. A standalone Stripe export shows a payment and two refunds; it cannot show that one refund undid a retry storm that double-counted API calls and the other applied a price cut the contract had already granted, which month was really overcharged, or why the money came back in two pieces weeks apart. The billing system, the contract file and the ledger each hold part of that answer.
Read → - Before and after: what a Slack-only incident export loses, and where the missing context lives
A single-system incident export usually keeps the conversation and loses the decision. A Slack export alone shows when the incident started, who responded and when someone said it was resolved. It does not show the severity the team assigned, which code changed, whether anyone reviewed the change, or whether the first fix actually worked. That context lives in the issue tracker and the code host, and it only reconnects if the same identifier was typed in all three places.
Read → - Before and after: what a standalone SAP invoice export loses about a delayed payment
A single-system invoice-to-payment export loses the reason for the delay. An SAP export alone shows the invoice, its match to the order and goods receipt, any payment block and the release date. It does not show that the order changed after approval, which version of the order the reviewer was looking at, or what finally cleared the hold. That context sits in Ariba, where order versions live, and in the SharePoint library where review packets are kept.
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