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
- Detention charge disputes across TMS, Outlook and AP: a system map of records and linking keys
To reconstruct a detention dispute across systems you need four keys to line up: the load number, the carrier identifier, the appointment time and the invoice number. The TMS holds the load, the stop times and the carrier pay lines; Outlook holds the appointment confirmation and the argument; AP holds the invoice image and the payment. The case can be rebuilt only where each system recorded the same identifier at the time. The mailbox join is the most fragile, and it carries the reasoning.
Read → - Detention charge disputes, a worked hard case: when a carrier arrives before the booked slot
Three records explain most detention exceptions: the arrival timestamp, the appointment email that set the booked slot, and the invoice as finally accepted. In the hard case below, which is Illustrative, a carrier arrives 80 minutes early and bills detention from arrival; the broker disputes from the appointment time and settles at $75 instead of $155. Each decision left a record in a named system. That sequence is what makes a dispute history useful evidence, and it is what a partner should listen for at a client.
Read → - Detention charge disputes: the evidence trail to inventory before a TMS replacement
Before a TMS replacement, inventory the three records that explain each detention dispute: the arrival timestamp (gate check-in or ELD event), the appointment email that set the booked slot, and the invoice as finally accepted. Note which system holds each, how many years exist, who owns them and the date old-system access ends. Then introduce the executive who can authorize a data discussion; whether the records can be licensed depends on rights and qualification.
Read → - DGCL section 279: appointing a trustee or receiver for a dissolved Delaware corporation
Section 279 of the Delaware General Corporation Law lets the Court of Chancery appoint trustees or receivers to wind up a dissolved corporation, including when assets remain. If a long-closed Delaware company still holds archives, that appointment can supply the authority needed before anyone introduces it to SourceX.
Read → - Digital transformation in PE portfolio companies: assess the archive before you modernize
Digital transformation in private equity portfolio companies means replacing legacy ERP, CRM, helpdesk and file systems during the hold so the business scales, reports faster and sells well. Add one checkpoint before any old system is switched off: keep a complete export and assess whether those years of records could be licensed to SourceX for a one-time payment.
Read → - DIP budgets and wind-down carve-outs: how to fund records preservation
To keep a records license possible, put three line items into the DIP budget and the post-sale wind-down budget: key systems kept live or on an archive tier, a retained administrator who can run exports, and storage for those exports. Tie each line to an end date, such as a SourceX decision, so lenders see a bounded cost.
Read → - DIP financing sale milestones: how to fit a records license in without missing a date
DIP financing sale milestones are dates in a DIP agreement, DIP order or forbearance agreement by which the debtor must file bid procedures, hold an auction, obtain a sale order and close, with a default if one is missed. A records license can run in parallel when records are carved out early and approval rides on hearings already scheduled.
Read → - Dispatch platform change: do work orders keep diagnosis revisions and repair verification?
Often they do in the legacy system, and the migration plan decides whether they survive. A repeat visit usually leaves a first diagnosis, a callback, a revised diagnosis, parts used and a closing record showing the fix held. Field service integrators can ask the owner whether that sequence stays attached to the work order and the asset, or whether only final statuses move to the new dispatch platform. If the history survives and the company qualifies, the owner may choose an introduction to SourceX.
Read → - Dispute-to-evidence-packet record chain: the keys that join a chargeback, CRM case and delivery proof
A company connects dispute-to-evidence-packet records by following one spine: the disputed charge's order number, carried from the dispute notice through the order, the CRM case, any replacement order, the carrier tracking and the packet that was submitted. Each record must carry a key the next one recognizes. The link that snaps most often is between an original order and its replacement, because few companies store it as a field rather than a sentence in a case note, so delivery proof ends up proving a different order.
Read → - Dispute-to-evidence-packet records: what a partner can note from metadata before an introduction
A referral partner can describe a company's dispute-to-evidence-packet history from metadata alone: where card disputes are received, which CRM holds the customer's contact history, which warehouse or carrier system holds shipping and delivery proof, how many disputes exist over how many years, which order or case number links them, and who assembles each response. The case to test is a replacement shipment, because its delivery proof carries a different order number from the disputed charge.
Read → - Do mature businesses respond differently to AI data opportunities? A maturity-based response study that fixes each company's age, leadership generation and record span before the CEO is asked, follows every answer and every silence, and reports nothing until the cohort closes
Nobody knows yet, and this page publishes no results. Two plausible stories point in opposite directions: older companies hold longer runs of their own records, while a Census Bureau working paper found AI use more common among younger firms once size and industry were controlled. The study below would settle the question for introductions made through partner networks. It fixes each company's age, leadership generation and record span before the CEO is asked, follows every answer, silence included, and compares bands only after the cohort closes.
Read → - Do not confuse a fund write-off with abandoned rights: what a zero mark changes, what stays with the company, and nine authority questions for counsel before anyone mentions licensing
No. A write-off is the fund's judgment about the value of its own shares, recorded in its books and its tax filings. It moves nothing the company owns: the records still belong to the entity that created or acquired them, and a licensing discussion still needs that entity's CEO, or the controller of a formal process if one has begun. "Abandoned" has narrow legal meanings, and none of them makes a company's archive free for a shareholder, a former manager or anyone else to offer.
Read → - Do specialized networks produce better-qualified referrals? A matched network cohort study design that pairs asks about like companies across specialist and general networks, keeps every declined ask in the count and has no results yet
Nobody knows yet, and a raw comparison cannot tell you. Specialist networks may simply ask about larger, older companies in sectors where demand happens to run high. This study design compares like with like: each ask from a specialist network is paired with an ask from a general network about a company in the same size band, record span, record type, geography and quarter, matched before anyone sees an outcome. Every declined and unsuccessful ask stays in the count. No results have been collected or published.
Read → - Does a company fit checklist improve application quality? A checklist-versus-control experiment in which the company answers seven published fit questions for itself and the partner never sees the answers
Nobody knows yet: no partner or SourceX results for this test are published. A company fit checklist could raise application quality by letting a CEO rule the company out before applying, or lower it by reading like an exam or an approval. Test it on your own outreach: split the CEOs who agree to hear about SourceX between your normal message and the same message plus seven self-check lines restating SourceX's published criteria, which the company answers and keeps. Judge it on verified applications that stay in review, never on clicks.
Read → - Does a personal introduction improve handoff completion? A choice-first handoff test that gives every CEO the route they prefer, randomizes only the CEOs with no preference and counts verified applications from the date of the CEO's yes
Nobody has published whether a personal introduction completes more often than a link for SourceX introductions, and research from health care, where warm handoffs have been studied for years, points both ways. Test it on CEOs who have already said yes. Ask each one whether they would rather apply with your link or have you make the introduction, honor any preference, and randomize only the CEOs with none. Count a handoff as complete when the company's verified application appears within 90 days of the CEO's written yes. No results exist yet.
Read → - Does a shorter referral brief improve founder response? A brief-length experiment specification that keeps every line a founder needs to say no in both versions, moves only explanation behind SourceX's own pages, and counts a quick, informed no as a response
Nobody knows yet, and the answer turns on what "response" means. If it means more yeses, a shorter brief can win by leaving out the conditions that make founders say no. Count decided answers instead: yes, no or not now, given within 14 days, with every founder who was sent a brief in the denominator. Keep every condition in both versions, shorten only the explanation, and let a count of late surprises veto the short one. No results exist.
Read → - Does a small specialist network make better data referrals than a big one? A 90-day specialization-versus-scale test for VC platform leads
Referral quality in a specialist network comes from members who know which companies in their sector keep long operating records and who can ask those companies' CEOs directly, not from the network's size. That advantage is plausible but unproven: nobody has published comparison data for company data introductions. Before you reorganize a platform around it, brief a small specialist group and a broad community with the same page, count both from the same denominator, and judge them by authorized introductions rather than replies.
Read → - Does git history matter? Why commit history is worth more than a code snapshot
Git history matters because commits, pull requests and review comments record how code changed and why, which a snapshot cannot show. For a data license, full history is the more useful asset. A fractional CTO should preserve it before any migration, then introduce qualifying companies to SourceX.
Read → - Does referring my company commit it to licensing anything? An eight-rung ladder that shows the only two signatures that bind it, and the way off every rung
No. Referring your company commits it to nothing. The partner's agreement with SourceX states that it does not bind a contact who is not a party to it, and SourceX's application page says applying signs nothing and licenses or transfers nothing. Your company takes on licensing obligations at two points only, both signed by its CEO: a Master Supplier Licensing Agreement after qualification, and a Dataset Deal Confirmation that fixes the exact dataset and payout. Before the first of those, a no simply ends it.
Read → - Does showing the payment sequence reduce partner confusion? A two-layout comprehension test that sets SourceX's payment conditions in their real order beside the same sentences in the terms' own order, asks partners to place five status updates, and counts every reader who turns the order into a timetable
Nobody knows yet, so test it. An ordered display of SourceX's published payment conditions should help partners place a status update, such as a signed agreement or an accepted dataset, at the right point and see which two events start the 60-day deadline. It can also backfire if the order reads as a timetable or as one strict chain. Compare two layouts of identical sentences, score five placement tasks, and count every partner who infers a date the terms never give.
Read → - Does software development qualify for the R&D tax credit, and what records prove it?
Software development can qualify for the federal research credit under Internal Revenue Code section 41 when the work aims to improve a product's function or performance, relies on computer science, starts with technical uncertainty and resolves it through experimentation. Internal-use software faces a stricter test. Tickets, pull requests, design documents and commit histories are the usual evidence.
Read → - Does the federal M&A broker exemption preempt state broker registration?
The federal M&A broker exemption does not preempt state law. It addresses SEC registration under the Exchange Act, while state securities regulators apply their own rules, so an M&A advisor must check the home state and each client state. A data licensing introduction is not an ownership transfer and is assessed separately.
Read → - Domain consolidation: how Google Workspace resellers check which years of mail and linked files survive
Ask the owner which years of company-owned mail threads, attachments and linked Drive files will still open after the consolidation, and who decides. In a Google Workspace domain consolidation the messages are usually copied safely; what breaks is the context around them: oversized messages that do not migrate, Drive links whose owners were deleted, and accounts removed before anyone checked. A reseller can map those years from metadata, then introduce the owner to SourceX if the company wants to explore licensing.
Read → - DOT compliance consultants: which fleet records stay out of a data license
A DOT compliance consultant can introduce a fleet with 50+ full-time employees at peak to SourceX, but driver qualification files, MVRs and drug and alcohol testing records are regulated personal data and stay out. Safety-program, maintenance and dispatch records the carrier wrote itself may fit. The consultant shares fit information only.
Read → - DPI pressure: how funds create distributions without a full exit
Funds create distributions without a full exit through dividend recapitalizations, partial or minority stake sales, continuation vehicles, NAV-based financing and sales of non-core assets. Data licensing is a smaller, slower lever: the one-time payment goes to the portfolio company, arrives only after dataset selection and a signed agreement, and reaches LPs only if the company then distributes it.
Read → - Driver report to asset return record chain: the keys that link a DVIR defect, a work order and the next dispatch
A company connects driver-report-to-asset-return records by following two identifiers. The unit number travels through every system, so it ties records to the same truck. The defect identifier ties records to the same repair, and it usually survives only where one system holds both the driver's report and the work order. The chain then needs an approval reference, a close event, a release check and the next load. The links most easily lost are the defect ID crossing into a separate shop system and the release check before redispatch.
Read → - Driver-based forecasting: map each driver to its source system
Driver-based forecasting links a few operating drivers, such as tickets per customer or hours per project, to financial outputs. Tracing each driver to its source system and years of history gives a metadata-only map that also answers SourceX's fit questions about system breadth and record depth, without exporting records.
Read → - Driver-report-to-asset-return records: a sample metadata packet for a fleet introduction
A referral partner can describe a fleet's driver-report-to-asset-return history without opening a single inspection report. The useful facts are metadata: which system records the driver's defect, which records the repair approval and the closed work order, which marks the unit available again, how many of each exist per year, which identifier links them, and who owns each step. The one case to test first is a repair that closes with no inspection record before the truck goes back out.
Read → - Duplicate payment recovery across AP platform, ERP and mailbox: a system map of records and linking keys
To reconstruct a duplicate payment recovery across systems you need four joins: the supplier to its vendor records, each invoice to its payment, the payment to the vendor correspondence, and the credit or refund to the payment it offsets. The AP platform holds captured invoices, the ERP holds vendor master, payments and credits, and the shared mailbox holds the reasoning. The joins survive only where both sides recorded the same identifier. The weakest is often the vendor itself, when one supplier exists under two vendor IDs.
Read → - Duplicate payment recovery records: what a useful exception history contains
The records that explain a duplicate payment recovery are the invoice pair, the match that found the duplicate and the rule behind it, the payment lines for both payments, the vendor correspondence, the credit memo or refund that brought the money back, and the close note or rule change that followed. Together they show the problem, the authorized action and the checked result. A partner describes those record classes, systems and years, never the records themselves, and introduces the person who can authorize a licensing discussion.
Read → - Earnouts and data licensing: the transaction questions a broker raises first
Before a client that is selling its business discusses licensing its data, a broker should raise five questions with the deal team: does the LOI's exclusivity or no-shop wording reach a data license; do interim operating covenants require buyer consent for new contracts or asset licenses; how does the earnout define the metric; who decides post-closing whether to pursue licensing; and which entity holds the rights at each stage. Each question has a document and an owner. None needs a legal conclusion from the broker.
Read → - ECPA for employers: the Wiretap Act, the Stored Communications Act and consent to disclose
ECPA combines the Wiretap Act, which restricts intercepting communications, and the Stored Communications Act, which covers stored messages. Employers can often access systems they own, but disclosing archives to a licensee is a separate question governed by notices, state law and contracts, so counsel should review before any email or chat records are licensed.
Read → - EHS consultants in manufacturing: which safety records can be licensed and which stay out
An EHS consultant can introduce a manufacturer to SourceX when it has 50+ full-time employees at peak and years of exportable audits, root-cause analyses and corrective actions. Injured-worker medical details and OSHA privacy-case entries are excluded, and the consultant never handles the records.
Read → - Email archive migration: what to decide before the legacy archive contract lapses
Email archive migration forces a decision about years of journaled mail before the old archiver's contract ends. An MSP or migration consultant can use that moment to ask the owner whether the history should be assessed for a SourceX data licensing introduction, before anything is deleted or moved.
Read → - Emergency work order prioritization across systems: a map of records, linking keys and owners
Rebuilding one P3-to-P1 jump takes four links: the service desk call that raised the alarm must carry the work order number, the dispatch platform must keep the history of priority changes on that work order, the scheduling board must show which booking was moved to make room, and the technician app must tie on-site and completion notes back to the same order. The work order number is the spine. Where a system stores no shared key, the case breaks there.
Read → - Emergency work order prioritization records: what explains a job that turned safety critical
A useful emergency work order prioritization history shows the dispatch rule in force, the original priority, the escalation request and who raised it, the reclassification and who approved it, the booking it displaced, and the response and completion times measured against an SLA. Together those records show a person reading new facts and overriding a rule, then a checked result. A partner describes the record classes, systems and years at metadata level and introduces the executive who can authorize a licensing discussion.
Read → - Employee referral incentives inside a venture firm: a six-stage participation approval workflow that sorts staff by what their job lets them see, picks one seat per company and keeps any internal bonus away from counts of introductions
A venture firm's employee referral policy answers three questions before anyone mentions SourceX to a CEO: which staff may raise it, whether the firm or the person signs SourceX's partner agreement, and whether the firm pays its own people anything for it. SourceX's terms settle only the outer edge: one partner is credited per company and paid separately from the company. Everything inside the firm, bonuses included, is the firm's call with fund counsel. Route each request through a written approval workflow and keep any internal bonus away from counts of introductions.
Read → - Employee voices in licensed recordings: what publicity and voice laws mean
A company can sometimes license recordings containing employee voices, but state right-of-publicity and voice laws, employee notices and consent all affect the answer. Many deals deliver transcripts instead of audio, and licenses typically ban voice cloning and speaker identification. Company counsel should check each state where speakers live or work.
Read → - Engineering change exception, worked step by step: an order released between approval and effectivity
The records that explain an engineering change exception link the problem, each decision and the checked result. Here that means the requirement that started the change, the design review choice and the board-approved change request. It also means the change notice with its effectivity date, the production order released before that date, the quality hold that caught it and the disposition that closed the gap. In the Illustrative case below, an order slipped between approval and effectivity, and every decision that followed left a dated record.
Read → - Engineering change impact review system map: the Jira, Windchill and ERP keys that join one change
An engineering change impact review is reconstructed across systems by four identifiers, each held by a different owner. The Jira issue key goes into the PLM change request. The change number goes onto the new part and BOM revision with its effectivity. The PLM-to-ERP interface carries the change into an ERP BOM version, and the BOM version is stamped on each production order. The map below lists every system, the record it holds, the identifier it hands on, and the person who can describe that system.
Read → - Engineering change impact review: a one-page handoff for PLM integrators
A company introduction about engineering change impact review should fit on one page: the business task, the record classes (change requests, BOM versions, effectivity approvals), the systems holding each, years of coverage, who owns the records, and the hard case the history can answer, such as a component that changed while a production order was open. Add the decision-maker and what was deliberately not shared. Licensing depends on rights, qualification and the proposed use.
Read → - Engineering change to effectivity record chain: one valve coating change followed link by link
A change can be traced from the customer's request to the valves actually built only if every handoff passes along a reference to the step before it. The request number rides into the change form, the change number rides onto the new drawing revision and its serial cut-in, the same number rides into the manufacturing bill, and each shop order records which bill it was built from. Drop one reference and the chain falls apart into pieces nobody can reassemble with confidence.
Read → - Engineering change to effectivity, before and after: what a standalone Windchill export loses
A single-system export of an engineering change usually keeps the what and the when: the affected part, the new revision, the approval and the effectivity date or serial. It loses the why and the so-what: the customer requirement that started the change, the design reasoning, the production orders that missed the cut-in, the units held or reworked, and whether the fix worked. That context lives in the requirement tracker, the ERP, the quality system and email, not in the PLM.
Read → - Engineering firm succession planning: options
Engineering firm succession planning usually runs through a key-employee buy-in, an ESOP, a sale to a larger firm or a merger, with state licensing and client concentration shaping each. A firm's project histories may be valued records, but client IP and contract terms must be checked before any licensing review.
Read → - Engineering system modernization: can a change be traced to affected production orders?
Often only partly, and modernization is when the gap shows. A full trail runs from the engineering change order to its effectivity (a date, serial or lot), to the BOM revision that took effect, to the production orders built before and after, and the disposition of work in progress. The PLM usually holds the first half and the ERP or MES the second. PLM partners can ask the owner whether that bridge survives the new system. If it does and the company qualifies, the owner may want an introduction to SourceX.
Read → - Enterprise AI data licensing deals: what advisors should know beyond the headlines
Enterprise AI data licensing deals are private agreements in which operating companies license internal records, such as support tickets, CRM history and email, to SourceX. Unlike the publisher and platform deals reported in the press, their terms are rarely disclosed, so advisors should treat headline figures as evidence of demand, not as a price guide.
Read → - Enterprise exception handling training data: a six-class taxonomy tied to the records that prove each case
Exception histories matter because an evaluation is only as hard as its hardest cases. Routine invoices, orders and tickets show that an agent can follow a rule; exceptions show whether it knows when the rule does not fit, who may authorize a departure, and how to confirm the fix worked. The useful unit is a chain of three records: the initial problem, the authorized action and the checked result. The taxonomy below sorts exceptions into six classes by what breaks.
Read → - Entitlement exception records across systems: a map of CRM, billing, identity and helpdesk keys
Reconstructing an entitlement exception takes three joins across four systems: the CRM account to the billing plan, the plan change to the identity event that changed permissions, and the identity event to the helpdesk ticket that asked for it and confirmed it. The keys are usually an account or customer ID, a user or group ID with a timestamp, and a ticket number typed into a change note. Each join can break, most often after an acquisition.
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