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
- Post-merger integration data migration: what to migrate, archive or retire
Post-merger integration data migration works best as a system-by-system decision: migrate what the combined business uses daily, archive what law, contracts, diligence or licensing value say to keep, and retire only what fails every test. Adding licensing value as a test protects years of acquired-company history that AI developers may pay to license.
Read → - Post-merger tenant control vs data ownership: a chain-of-title worksheet for each inherited system
No. Controlling a tenant means holding its admin roles: the power to export, migrate, retain or delete what is stored there. Ownership is a separate chain: who created the records, what the deal documents transferred, and whose content sits inside, such as client deliverables, customer attachments or vendor-licensed data. After a merger the two often diverge. Before anyone discusses licensing, the company should trace both for each inherited system and record where they part.
Read → - Pre-liquidity event planning: when wealth advisors can raise data licensing
In pre liquidity event planning, data licensing is a company-level question: license proceeds are paid to the company, not the owner, and the decision sits with the company and its advisors. Wealth advisors can raise it when systems are about to change, after checking their own firm's rules on referral fees and disclosure.
Read → - Preparing the Introduction Email with Your Client
In your client conversation, prepare the introduction email by asking key questions about their data, confirming their authorization, and collaboratively drafting the message. This clarifies their understanding and ensures their comfort and control over the referral process.
Read → - Preserve rebate claim reconciliation records: a retention timeline before a rebate tool replacement
Before a rebate tool replacement, inventory what the new tool will not recreate: superseded tier versions, past buying-group membership dates, closed and adjusted claims with their notes, and matched or written-off deductions. A replacement loads live agreements and open accruals because the business needs them on day one; the history of how old claims were settled is the part most likely to stay behind. For each class, record the system owner, years covered and the date access to the old tool ends.
Read → - Preserving chargeback evidence assembly records: a retention timeline before a dispute platform renewal
Before a dispute platform renewal, inventory the submitted response files, the records each response file was built from, the analyst notes, and the card-issuing bank's decision, and note when each one would disappear. Links from cases to orders and tickets usually fade first, then notes and outcomes; response files and order history tend to last longest. For each record, write the system, the years covered, the documented deletion or access-end date, and who must approve keeping it. Record only dates a contract or setting confirms.
Read → - Preserving engineering change history through a PLM migration: a retention timeline from mapping to retirement
Before a PLM modernization, inventory the engineering change history the migration might leave behind. That means closed change requests and notices, past effectivities, the cross-system keys that tie Jira issues and ERP BOM versions to each change, the old PLM-to-ERP integration log, and scanned pre-PLM change forms. Past effectivities and integration logs usually go first, at data mapping and cutover. Note the owner of each class and the documented date the legacy system goes read-only, and leave the decision to keep anything to the company.
Read → - Preserving proof-of-delivery dispute records: a retention timeline for a carrier integration change
Before a carrier or delivery-platform integration changes, list every copy of the dispute evidence and the clock that ends each one: detailed status codes that cutover may flatten, delivery photos hosted by the old platform, signature letters on the carrier's portal, support tickets, adjudication notes and credit memos. Note which copy is still readable and linked to its case after cutover, who owns it, and who must approve keeping it. Then introduce the executive who can authorize a licensing discussion.
Read → - Preserving restore validation history before a backup vendor migration: a retention timeline
Before a backup vendor migration, inventory the history of restore testing, not the backups: console session history, verification job reports, the tickets raised when a test failed, the change records that fixed it and the client's signed acceptance. Then put a date on each. Console history usually goes first, ending at decommission or earlier under its retention setting; tickets and signed sign-offs tend to outlast the switch. Whoever owns each record type decides whether anything is kept longer.
Read → - Preserving RFI-to-change-order history at closeout: a retention timeline of what disappears first
Before closeout, inventory five record classes and the date each one loses access: RFIs with responses and activity logs, drawing version history, notice letters, change-coded cost, and executed or rejected change orders. Personal mailboxes and owner-portal access usually go first. Platform seats follow, then the contractor's own retention period. Note who owns each class and the real access date, and leave the decision to keep anything to the company's authorized people and counsel.
Read → - Preserving roadside repair authorization records: a retention timeline before a fleet system retires
Before a fleet system retires, list each roadside repair record class with the clock that ends it: driver reports kept for three months, roadside inspection copies for 12 months, repair records for one year, invoices for the tax period, and approvals, quotes and variance notes for however long the old system survives. Note who owns each, which ones the new system will not import, and who must approve keeping them. Then introduce the executive who can authorize a licensing discussion.
Read → - Preserving royalty dispute history: a retention timeline before a royalty platform replacement
Before a royalty platform is replaced, list what the new system will not load: sales reports as originally submitted, closed disputes, superseded agreement versions and the exclusion rules they carried, waived late charges, and the notes behind credits. Record the clock that ends each one, such as the old platform's deletion date, the refund window, disclosure document retention and tax retention, plus who owns it and who must approve keeping it. Then introduce the franchise finance head and the executive who can authorize a licensing discussion.
Read → - Preserving subscription pause recovery history: a retention timeline before a platform renewal
Before a subscription platform renewal, inventory four things at metadata level: the record classes behind pause recoveries, how far back each goes, who owns each system, and the real date each one stops being readable. Detail fades in a predictable order. Rich event data goes first, then closed tickets drop out of everyday views, then the old platform's history ends at shutdown, and a cancelled support desk is deleted after its documented window. Anything kept must be approved by the person who owns the record.
Read → - Pricing as a value creation lever in private equity, and what a pricing review surfaces
Pricing is a private equity value creation lever because a better price or tighter discount, with volume and costs unchanged, flows straight to EBITDA. A pricing review pulls years of quotes, discount approvals and win-loss notes; those decision-with-outcome records are what AI labs and data buyers license, so the review is a natural moment to screen for a SourceX introduction.
Read → - Prior authorization follow-up across work queue, payer portal and clearinghouse: a system map of linking keys
Reconstructing one prior authorization follow-up takes five links: the internal request or encounter ID, the payer's reference or authorization number, the version or resubmission sequence, the attachment list for each version, and the date of each status change. The internal work queue usually anchors the request; the payer portal or a clearinghouse's 278 log holds what was sent and returned; a document system holds attachments; scheduling receives the final authorization number. The version sequence is often the weakest link.
Read → - Prior authorization follow-up: the submission versions, document requests and final statuses to inventory before a revenue cycle platform change
Before a revenue cycle platform change, inventory the three records that show how each pended authorization was resolved: every submission version with its date and attachments, every missing-document request with the requirement it cited, and the final status with its reason. Note which system holds each, the years covered, who owns it and when read access to the old platform ends. Then introduce the executive who can authorize a data discussion. Licensing depends on rights, de-identification, qualification and the proposed use.
Read → - Private archive benchmark contamination: a provenance and exposure worksheet that never assumes private means unseen
No. A private archive puts a record in scope for clean testing, but only a documented exposure check keeps it there. Records leave companies in ordinary ways: a help article that describes the same case, a vendor that received copies, a customer who posted the dispute, an acquired business that shared data before the deal. The worksheet below records, task by task, where each record has been and what a search found, and it starts every task as unchecked rather than assuming that private means unseen.
Read → - Private code without issue history: the referral questions to ask
A private code archive shows what changed. Four other records explain it: the issue or requirement says why the change was needed, the pull request and its review show what was accepted and what was pushed back, the tests show the change worked, and the links between them tie each answer to the right change. Before introducing a company with code history, find out which of these it kept and whether they point at each other.
Read → - Private credit default rates in 2026: why the numbers differ and what workout teams watch
There is no single private credit default rate for 2026. Published figures differ because sources count different events (payment defaults, distressed exchanges, PIK switches, stressed amendments), weight by borrower count or loan value, and sample different borrowers. Workout teams should read each rate by its method and treat rising PIK and amendment activity as earlier signs of stress.
Read → - Private equity exit options, and how a data license works with each
Private equity exit options are trade sale, secondary buyout, IPO, recapitalization and continuation vehicle. A data license is not an exit route but a separate transaction a portfolio company can complete before, during or after any of them. Trade sales carry the biggest risk of archives disappearing during integration.
Read → - Private equity finder's fees: what sponsors pay deal finders and what to check first
Private equity firms usually pay a deal finder only when an introduced acquisition closes, under a written agreement that sets the fee base, any minimum fee, a sliding scale for larger deals and a tail period. Terms are negotiated deal by deal, and anyone employed by a sponsor who sources personally must clear the firm's conflict rules first.
Read → - Private equity operating partner trends shaping 2026
The main private equity operating partner trends in 2026 are longer holds, a backlog of unsold companies, a higher EBITDA growth bar, larger operating teams and pressure to turn AI into measurable results. Together they push operating partners toward levers that add value without new capital, including licensing operational records that portfolio companies already hold.
Read → - Private equity owned CPA firms: why advisory growth matters and where referrals fit
Private equity investment in CPA firms usually runs through an alternative practice structure: licensed CPAs keep the attest firm while an investor-backed company owns tax, advisory and shared services. Growth plans then lean on advisory, which is less tied to filing seasons and credentialed hours. Referral relationships can add to that line, but only after independence and disclosure checks.
Read → - Private equity value creation levers, and where data licensing fits
Private equity value creation levers fall into four classic groups: revenue growth, margin improvement, capital efficiency and multiple expansion. A fifth group, monetizing idle assets, includes licensing a company's operational records to SourceX. That license brings one-time cash that is usually treated as non-recurring, so it strengthens the balance sheet rather than run-rate EBITDA.
Read → - Private equity vendor rebates and portfolio disclosure: how data licensing differs
A portfolio data license differs from a vendor rebate because the company receives the payment, not the sponsor. SourceX funds partner rewards separately, without reducing the company's payout, but a reward that reaches a sponsor-affiliated person should still be disclosed under your fund documents and conflicts policy before making the introduction.
Read → - Private fund fees and conflicts: SEC scrutiny and referral rewards
Treat portfolio-linked referral compensation as a conflict to identify, disclose and approve under your fund documents. The Fifth Circuit vacated the Private Fund Adviser Rules in June 2024, but fiduciary duties, antifraud provisions and examiner attention to fees and conflicts remain. Decline, offset or disclose it; do not keep it quietly.
Read → - Process design documents as a fit signal: how automation consultants can introduce clients
An automation consultant can treat well-kept process design documents, exception catalogs and as-is maps as a fit signal, then introduce a client with 50+ full-time employees at peak to SourceX. Documents written under a client statement of work are generally the client's to license, subject to the contract; the consultant shares fit information only.
Read → - Procurement decision records: avoid confusing client and company content with a two-gate origin screen that sorts every sourcing document into the company's, a supplier's or a client's
A company's procurement decision records can support an introduction when its own buyers wrote the reasoning behind its own purchases: the need, the evaluation, the negotiation and the award. Two kinds of material get mistaken for that. Bids, quotes and price files were written by suppliers, and sourcing a company ran on behalf of clients records the clients' decisions even when it sits in the company's platform. Screen every document at two gates, whose purchase and whose pen, before anyone puts the idea to the CEO.
Read → - Product change logs are useful context, not a dataset promise: a product-history checklist that sorts release notes by who wrote them before an owner hears the word licensing
A product change log shows that a company has shipped software in versions and explained each change in its own words. It does not show that a licensable dataset exists, who owns every entry, or whether any AI developer wants it. Use it to open a metadata conversation the CEO knows about: who wrote the entries, what each one links to, and which parts came from vendors, open-source projects or contractors. Rights, fit and demand are settled only in SourceX's review.
Read → - Product sunset plan: what to do with the support and engineering history
A product sunset plan should include data retention: list the support, engineering and decision systems tied to the product, confirm admins can export them, and preserve exports before accounts lapse. For qualifying companies, that history can be reviewed for a SourceX data licensing introduction, another possible source of proceeds.
Read → - Production schedule recovery hard case: a heat-treat furnace fails mid-batch, decision by decision
The records that explain how a plant handled a production exception are the ones that capture each decision as it happened: the equipment alarm and the downtime event, the shortage status on the orders that could no longer be met, the rescheduling choice and who approved it, the quality decision on parts caught mid-process, any outside processing order, and the partial and final confirmations that show what was actually built. Lined up in time, they let a reviewer test every judgment the plant made.
Read → - Production schedule recovery records retention timeline: what disappears first when a scheduling tool is replaced
Before a scheduling tool or MES is replaced, inventory each record class behind a recovery: what it is, the years it covers, who owns the system, and the real date access changes. The order matters, because records disappear at different times. On-screen alerts and availability logs often vanish immediately, chat and leavers' mailboxes go under retention rules, scenario runs go when the old license ends, and downtime history goes when the old database is switched off. Closed ERP orders usually survive longest, often in an archive.
Read → - Production schedule recovery system map: which system holds each record and the keys that join them
Reconstructing a production schedule recovery takes five kinds of link: the production order and operation number shared by the MES and the ERP, the machine or asset ID shared with the maintenance system, the maintenance work order or quality notification number where those records cite the order, timestamps in every system, and a time window plus machine name to attach the email or chat where the reason was written. With those joins, one case reads end to end; without them, it is five unrelated lists.
Read → - Program eligibility and finance approval are different decisions: a nine-gate payment checklist for the months between a qualifying company and a paid reward
Program eligibility says whether a company, a partner and an introduction can earn a reward at all: the company meets SourceX's sourcing criteria, the partner has an approved account and a signed Channel Partner Agreement, and the introduction is credited. Finance approval is a later decision about one specific amount: after the company has been paid, SourceX finance approves eligibility, attribution, calculation and Minimum Transaction status, payment by payment. An eligible company can still produce a delayed, smaller or zero approval, and only an approved amount with your details on file is close to cash.
Read → - Programmatic M&A strategy: how serial acquirers can treat acquired records as an asset
A programmatic M&A strategy is a series of smaller acquisitions in a defined theme, run by a standing team with a repeatable sourcing, diligence and integration playbook. For serial acquirers, that playbook should also decide what happens to each acquired company's historical records, because years of pre-acquisition email, tickets and finance history can be licensed when rights are clear.
Read → - Progress claim reconciliation exception example: a milestone claimed before it was complete, step by step
The records that explain a progress claim exception are the measured work, every claim version, and the certificate or payment schedule with its stated reason, each dated and tied to the same contract line. In the Illustrative case below, a slab milestone was claimed at 100% when site measurement showed 70%. The file is useful because it records the problem, who reduced the amount and why, and the later measurement that released the balance. Remove any of those and the case stops explaining itself.
Read → - Progress claim reconciliation system map: the keys that join project controls, ERP and certificates
Reconstructing progress claim reconciliation across systems takes three keys stored in every system that matters: the schedule of values line ID or cost code, the claim number with its version, and the certificate or payment schedule number that references the claim. With those, measured work in project controls, claims in workbooks, reasons in document control and amounts in the ERP join into one case. Where a key is missing, someone matches by amount and date, and that is where histories often break.
Read → - Progress claim reconciliation: what to inventory before a commercial system migration
Before a commercial system migration, inventory the three records that explain each progress claim: the measured work from project controls, every version of the claim as submitted and revised, and the certified amount booked in the ERP. Note which system holds each, the projects and years covered, who owns them and the date old access ends. Then introduce the executive who can authorize a data discussion; whether the records can be licensed depends on rights, qualification and the proposed use.
Read → - Project postmortems: ask about rights before celebrating the archive, with a nine-question ownership sheet that sorts every write-up by who wrote it, whose project it was and what was pasted in
A shelf of project postmortems can be some of the richest history a company owns: what was planned, what went wrong, why, and what changed afterwards. Whether it can be licensed depends on three things the shelf does not show: who wrote each write-up, whose project it described and what was pasted into it. Before anyone calls the archive an asset, sort it with ownership questions an operator can answer from memory, then take the result to the CEO, who decides whether the company wants a conversation. Nobody needs to open a file.
Read → - Project-change-to-invoice record linkage: the keys that tie a scope change to its corrected invoice
A company connects project-change-to-invoice records by naming the identifier that carries across each hand-off, usually a job number typed on the board item, the project folder and the invoice memo, and by pointing to each tool's own history: the Activity Log, file versions, the transaction audit history and credit memos. Where no identifier carries, the join is inferred from dates and should be labeled that way. The weakest link sits between the accepted file and the scope version it delivered.
Read → - Project-change-to-invoice records in monday.com, Dropbox and QuickBooks: a sample metadata packet for an introduction
A partner can note, without opening anything, which tools hold each step from scope change to accepted file to revised invoice (here monday.com, Dropbox and QuickBooks Online), the years and rough volumes each covers, who administers each one, how long each keeps its change history, and which links between the steps are recorded or only remembered. The case to flag is an invoice built from an outdated scope version. Whether the records can be licensed is decided later, after SourceX's review.
Read → - Promise-to-obligation records: following a sales commitment from a Gong call to an Ironclad redline and the signed contract
A company connects promise-to-obligation records by tying the Gong call where a commitment was spoken to the Salesforce opportunity it belongs to, then to the Ironclad workflow launched from that opportunity, its redline versions and the executed contract. The joins are the opportunity ID, call associations and the workflow's version history. A referral partner can describe which joins exist and for which years. The case that matters most is the spoken promise that never enters the contract, because no contract system records its absence.
Read → - Promotion exception records across systems: a map of promotion engine, POS, back-office and supplier claim keys
Reconstructing a promotion exception takes four keys around one receipt line: the promotion or discount ID printed on the line, a rule version with its start and end dates, the original receipt number on any refund or override, and the supplier deal number when a vendor funded the offer. With all four, a reviewer can show what the rule said, what the till charged, how the shopper was made whole and what was claimed back. The key most often missing is the dated rule version, because promotion engines are reconfigured in place.
Read → - Promotion exception records before an engine replacement: a retention timeline
Before a retailer replaces its promotion engine, inventory five record types and the date each stops being readable: rule change logs, dated rule versions, store override notes, POS receipts that carry a promotion ID per line, and finance corrections. They do not disappear together. Change logs and rule versions usually go first, at the engine cutover; receipts and finance entries tend to survive because tax law keeps them. Note who owns each system and who can approve keeping it.
Read → - Promotion exception, worked step by step: a multibuy offer and a loyalty coupon stack for one weekend
The records that explain a promotion exception are the rule version in force on the day, the POS receipts showing which discounts actually applied, the store corrections with manager and reason code, and the corrected rule with the receipts that followed. In the Illustrative case below, a multibuy offer and a loyalty coupon stacked for one weekend against the intended rule. Store managers, a pricing analyst and a commercial director each made a decision, and each decision left a dated record.
Read → - Promotion-to-service-recovery record chain: the keys that join POS discounts, shift edits and incident remedies
A retailer connects promotion-to-service-recovery records mostly by store and hour, because its POS, workforce system and incident log rarely share an ID. The discount name ties a promotion to its sales, store and timestamp tie sales to the shifts added that day, store and visit time tie complaints to the spike, and a coded comp or reason field ties the remedy back to the complaint. Where the remedy is typed as free text, that last hop is only a guess.
Read → - Promotion-to-service-recovery records in POS, workforce and incident systems: a sample metadata packet for an introduction
Without reading a sale, a timesheet or a complaint, a partner can record which systems hold each step from promotion event to staffing exception to accepted remedy (typically the POS, a workforce scheduling system and an incident or customer service log), the stores and years each covers, who administers them, and whether store number, date and promotion name are captured consistently enough to join them. The case to flag is a local promotion that created a workload spike nobody planned for.
Read → - Proof-of-delivery disputes system map: the keys that join scans, photos, tickets and credits
Reconstructing a proof-of-delivery dispute takes five keys: the tracking number, the stop and driver IDs, the client account ID, the ticket or claim ID, and the address ID. The tracking number joins scan, ticket and credit; the stop ID joins the photo; the account ID finds the client's delivery rule; the claim ID ties the reviewer's note to the money; the address ID shows whether the fix held. Where a system stores a key only as free text, the case breaks.
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