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
- Missing email attachments: what they reveal about an archive before you make an introduction
Missing attachments show how much of an email archive is whole. A message that says "see attached" but carries a dead link, a vault shortcut or no file at all still has its text, but the document the work turned on may be gone. Counting embedded, linked, stubbed and missing attachments against the total that reference one gives a completeness ratio, with the unknowns labeled, before anyone discusses licensing. The company's administrator runs the counts; the partner only hears the totals.
Read → - Mission Product v. Tempnology: what license rejection means for a data license
In Mission Product Holdings v. Tempnology (2019) the Supreme Court held that a debtor's rejection of a contract is a breach, not a rescission, so a licensee does not lose rights it already holds merely because the debtor rejected. For a data license, that makes drafting, scope and rights review matter before any filing.
Read → - Monetizing your professional network through data referrals
Monetize your professional network by referring 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) with qualifying data. SourceX licenses approved business data directly from companies for AI training and evaluation as their direct licensing partner. Referral partners do not handle data and may earn the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, on a company's first qualifying transaction (Actual Supplier Payout is the eligible licensing compensation SourceX actually pays the referred company, excluding separately itemized taxes and expense reimbursements), and 15% of each further qualifying transaction first agreed within 12 months of the first qualifying Closing, 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 → - Monitoring tool retirement: can alerts still be traced to the fix?
When a company retires a monitoring or alerting tool, the question that matters for a data introduction is whether alert groups can still be connected to the human actions taken and the final incident closure. If the client can trace an alert through acknowledgment, responder notes, resolution and a postmortem, it holds a multi-step operational record. Ask that at metadata level, and if the company is eligible and the owner opts in, introduce its decision-maker to SourceX.
Read → - Motion to abandon and destroy books and records: what to check before you file
Before filing a motion to abandon and destroy books and records, a trustee should screen four things: how many years the records cover, which systems hold them, whether the debtor had rights to license them, and whether a licensing route exists. A SourceX fit check can run before the objection deadline, so destruction proceeds only if the screen fails.
Read → - Motion to shorten notice on a sale hearing: getting a records license heard in time
A motion to shorten notice asks the bankruptcy court to hear a sale or license motion sooner than the default notice period allows, and courts expect specific cause. For business records, that cause is usually dated and provable: subscriptions lapsing, admins leaving or retention rules deleting history. Start the SourceX conversation in week one so a real deal exists.
Read → - Moving support to an AI agent: what happens to your ticket archive
Your ticket archive stays yours when you adopt an AI support agent, but cutover is where it is most often lost. Using tickets to tune your own agent is internal use; licensing an exclusive copy to SourceX is a separate grant, so agree the scope explicitly if you want both.
Read → - Moving upmarket: how brokers win clients with 50+ employees
Brokers move upmarket by changing who they meet, what they prepare and how they describe value: owners of companies with 50+ full-time employees at peak expect process documentation, buyer-universe thinking and options beyond one sale. A data-licensing introduction can be a differentiating, optional topic in those meetings.
Read → - Moving you to BCC: who replies first to an introduction email and how to step back
When someone introduces you by email, the person who asked for the introduction, or whoever the introducer named, replies first, thanks the introducer in one line and writes moving you to BCC to spare their inbox. The introducer then stays out of the thread. Referral partners should file the original email as their dated record.
Read → - MSP AI services offering: why the data inventory leads to licensing conversations
An MSP AI services offering usually packages a readiness assessment, data governance and permissions cleanup, Copilot or other AI tool deployment, an AI use policy and managed adoption. The readiness work maps where a client's records live and how far back they go, and that map can also support an owner-approved introduction to SourceX, which licenses business data directly from companies for AI training and evaluation.
Read → - MSP client acquired: why to introduce the owner before integration
When an MSP client is acquired, introduce the owner or executive who can authorize a license to a SourceX assessment before integration retires its systems. After cutover, years of email, tickets and finance records may be gone, and the managed contract may end too.
Read → - MSP compliance services: how to raise data licensing without new risk
Compliance-focused MSPs can use the data maps and retention schedules they already maintain to spot clients with years of connected records, then introduce the owner to SourceX. The MSP only flags and introduces. Rights, consent and de-identification decisions stay with the client and SourceX, and the MSP never handles data.
Read → - MSP M&A in 2026: what buyers pay for, and which records to settle before an LOI
MSP M&A in 2026 rewards recurring revenue, client retention, service margins and documented operations, so owners should settle record ownership before signing an LOI. An MSP's own PSA tickets, runbooks and internal documents may be licensable with SourceX if it has 50+ full-time employees at peak; client data it holds as a provider generally is not.
Read → - MSP valuation multiples in 2026: the drivers buyers pay more for
MSP valuation multiples in 2026 rise or fall with drivers a buyer can verify: the share of revenue under recurring managed-services agreements, client concentration, how much depends on the owner, margin per agreement and how clean the PSA data is. A one-time license of the MSP's own operating records adds cash once without changing the MRR math.
Read → - MSPs: answering client security questions about a data license
When a client asks an MSP whether licensing its data is secure, the honest answer is that security depends on scope, handling and agreement terms the client controls. Before any export, get written authorization from the sponsor, agree scope and exclusions, settle who holds credentials, and keep files in the client's storage or on encrypted drives.
Read → - Multi-entity rollout data referral opportunity: a playbook for NetSuite implementers
Often only partly. Once a group runs its entities as NetSuite subsidiaries, each intercompany line names the subsidiary it posts to and, where journal approvals are on, an approver. Adjustments booked in the separate legacy books before go-live often show the entity in a memo at best and the approver nowhere. That split is the opening for an implementer: the rollout is already deciding what happens to that older history, so one metadata question to the controller can tell you whether the group holds an approval-traced correction record worth introducing.
Read → - Multimodal workflow context, one job end to end: a walk-in freezer service call
Multimodal workflow context means the photos, notes, forms and readings a job produces stay attached to that job, in order, with its outcome. In an ordinary field-service call, a technician photographs a fault, writes what it means, gets a repair approved, photographs the fix and closes the job; a month later the system shows whether it held. Each step leaves a record. Together they show how what someone saw led to what they did.
Read → - Negative demonstrations: a retry that duplicated a purchase order, annotated record by record
Negative demonstrations are recorded examples of actions that fail, kept together with the reason they fail. In an ordinary purchasing workflow, one looks like an integration that retried a timed-out order as a fresh create and sent the supplier a duplicate purchase order, followed by the ticket, the cancellation and the fix. For a referral, what matters is whether the company kept the state before the action, the action, its consequence and the written reason, and who can authorize a licensing discussion.
Read → - Negotiation-to-contract record chain: three keys that join a customer request, its sign-off and the signed order
A company connects negotiation-to-contract records with three keys: the opportunity ID, the draft number and the e-signature package ID. The opportunity ID ties the customer's request and the sign-off to one deal. The draft number ties the approved terms to a specific order form. The package ID, plus a deal ID stored on that package, ties the signed document back to the deal. When all three are present, a commercial exception can be followed from first request to signature without guesswork.
Read → - Negotiation-to-contract records in Outlook, Salesforce and DocuSign: a sample metadata packet for an introduction
A referral partner can describe a company's negotiation-to-contract history without reading a single email or draft. The useful facts are metadata: how many deals a year carry a commercial exception, which years each system covers, which identifier links an email thread to an approval and a signed envelope, who administers each system, and which links are known to be missing. A RevOps consultant can usually fill the packet below from one conversation and their own memory of the Salesforce project.
Read → - NetSuite consultants: Spotting data referral opportunities
ERP consultants, particularly those working with NetSuite, can identify potential SourceX referrals by looking for clients with extensive operational data, 50+ peak employees, and clear data licensing rights. Rewards are the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap (eligible licensing compensation SourceX actually pays the referred company, excluding separately itemized taxes and expense reimbursements), subject to any signed Schedule A or addendum; the USD 50,000 floor applies once per referred company, and further qualifying transactions first agreed within 12 months of the first Closing pay 15%. 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 → - Network change acceptance across change, inventory, test and backup systems: a map of linking keys
Reconstructing one accepted network change takes a change number that appears in every system, device identifiers that match between the inventory and the test tool, circuit or service IDs that say which customers were in scope, and timestamps on a common clock. The change system holds the request and approval, the inventory says what the device served, the test system holds results, the backup store holds before-and-after configs, and the service desk holds any customer follow-up.
Read → - Network change acceptance records: what to inventory before a network refresh
Before a network refresh retires old devices and tools, inventory the records that explain each accepted change: the change request and impact analysis, the test plan and test results, the engineer's maintenance notes, the acceptance approval, the configuration backups taken before and after, and any customer ticket that followed. Record which system holds each, the years covered, the team that administers it and the real decommission date. Then introduce the network operations head, who can bring in the executive with authority to license.
Read → - Network reach is not a reachable decision-maker: a five-rung consent audit that shows a platform lead which CEOs can actually be asked
Network reach counts the companies someone at your fund could contact. A reachable decision-maker is narrower: the CEO of a company that passes the published fit tests, whom a named relationship owner has agreed to ask, and who has said yes to the conversation. Only that row can become a data licensing introduction. Audit every contact on five consent rungs, record who agreed to what and when, and report the rows at the top rung separately from the size of the network.
Read → - New Jersey CPA commission and contingent fee rules: what to check before a referral
New Jersey regulates CPA commissions, referral fees and contingent fees, and its rule can be stricter than the AICPA Code. A CPA considering a data licensing referral should read the current regulation, review each client by service type, disclose in writing and confirm with the board or counsel before registering.
Read → - New revenue streams for accounting firms: what to add beyond compliance work
The new revenue streams that suit accounting firms best build on information the firm already sees: outsourced controller and CFO work, forecasting, systems implementation, transaction and succession support, industry niche packages and disclosed referral income. Referral income, such as introducing data-rich clients to SourceX, needs a written firm policy and an ethics review before the first fee.
Read → - New revenue streams for B2B companies that build on what you already have
The most practical new revenue streams for B2B service companies reuse assets already paid for: productized services, retainers and managed services, training, internal tools sold as products, partner income and, newer still, licensing years of operational records to SourceX for a one-time payment. Each fits a different company profile, timeline and effort level.
Read → - New York CPA commission and referral fee rules: what applies and how to disclose
New York CPAs are regulated by the State Education Department under the Education Law and the Rules of the Board of Regents, whose Part 29 defines unprofessional conduct with provisions for public accountancy. Read that current text, apply the AICPA commission rule if you are a member, and disclose any SourceX reward to the client in writing.
Read → - New York Times v. OpenAI: where the case stands and why licensing matters
The New York Times sued OpenAI and Microsoft in December 2023, alleging that using Times journalism to train and run AI models infringed its copyrights. Rulings keep arriving, so confirm the current status on the federal court docket. For data owners, the key question is whether markets for licensing content to SourceX weigh against fair use.
Read → - No-re-identification clauses in data licenses and who is liable
A no-re-identification clause is a recipient's contractual promise not to identify individuals in de-identified data, link it to other datasets or extract identities from models. Statutory de-identification tests expect that commitment. Under a SourceX license, SourceX de-identifies the data, through approved processing routes, and the supplier agreement records that re-identification may still be possible and that SourceX is not liable for it.
Read → - Non-dilutive capital for mature businesses: options beyond loans
Non-dilutive capital is money raised without selling equity. For established companies, loans and revenue-based financing must be repaid, while licensing existing operational records to SourceX is a one-time payment with no repayment, no new owner and no commitment until the company signs.
Read → - Non-dilutive funding options for established companies, not startups
Non-dilutive funding for established businesses means raising cash without issuing equity: operating cash flow, bank and asset-based debt, sale-leasebacks, selling or licensing non-core assets, tax incentives and, for some 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) with years of records and 50+ full-time employees at peak (contractors excluded), an exclusive data license, usually paid as a one-time fee, that leaves ownership with the company.
Read → - Non-dues revenue ideas for associations, and where an AI data session fits
The most dependable non-dues revenue ideas for associations are events, sponsorships and exhibits, education and certification, affinity programs, career centers, publications and paid research. Associations and chambers whose members include 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) with 50+ full-time employees at peak can add an AI-data education session with opt-in introductions to SourceX, after settling tax and endorsement questions.
Read → - Nonconformance disposition history: what to inventory before a quality platform migration
Before a quality platform migration, inventory the full chain behind each nonconformance disposition: the nonconformance report with its inspection evidence, the material review board or engineering review, any customer concession, the rework instruction and the re-inspection result. Note which system holds each link, how many years exist, who administers it, whether it migrates, stays read-only or is retired, and the date legacy access ends. Then introduce the quality director and the executive who can authorize a data discussion.
Read → - Nonconformance disposition system map: QMS, MES, inspection and mailbox records joined by five keys
Reconstructing one nonconformance disposition takes five keys across four or five systems: the NCR number, the work order or lot number, the part number with its drawing revision, the inspection report ID, and the customer concession reference. The QMS records the decision, the MES records what happened to the parts, inspection software holds the measurements, and the concession often sits in a mailbox. If one key is missing, a verdict and its evidence sit in separate systems with nothing proving they describe the same parts.
Read → - Nonstandard contract approval records: what a CPQ migration can break and what to keep
Before a CPQ migration, inventory the trail that shows how nonstandard deals were approved: the quote and its approval steps, the redline history in the contract tool, the discount and term decisions, and the executed order. Note which system holds each piece, which records are tied to objects the migration will retire, and how long field history is kept. A RevOps consultant records only metadata and introduces the revenue operations head together with the executive who can authorize a licensing discussion.
Read → - Nonstandard contract approval system map: CRM, CPQ, CLM and order records joined by the quote version
Reconstructing a nonstandard contract approval takes five links across four to six systems: opportunity to quote version, quote version to its approval steps, quote version to the contract redline, redline to the executed order, and order to the outcome record. The quote version is the hinge, because every other record should point to it. If any link depends on matching customer names and dates, the trail can still be read, but the approval in one system no longer provably belongs to the redline in another.
Read → - Notion Consultants: Unlocking Data Referral Opportunities
Operations consultants can identify valuable data licensing opportunities for SourceX by looking for 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) with 50+ peak employees and years of operational data during their Notion projects. SourceX licenses approved business data directly from companies for AI training and evaluation. Partners earn the greater of $50,000 plus 5% and 15% of the Actual Supplier Payout (eligible licensing compensation SourceX actually pays the referred company, excluding separately itemized taxes and expense reimbursements) on a company's first qualifying transaction, with no cap; repeat transactions within 12 months pay 15%, subject to any signed Schedule A or addendum.
Read → - Number porting failure resolution: the records to inventory before a provisioning migration, and who to introduce
Before a carrier provisioning migration, inventory the record classes behind each failed port: the original port order, the rejection notice and its reason code, the customer service record the old provider relied on, the service desk ticket, and the corrected submission that was accepted. Note which system holds each, how many years it covers, who owns it, and the real date old-platform access ends. Then introduce the provisioning director to a decision-maker who can authorize a licensing discussion.
Read → - Number porting failure system map: order platform, service desk and mailbox fields joined by order ID
Three keys do most of the work in reconstructing a failed port: the port order ID with its supplement or version number, the list of telephone numbers, and the customer account identifier. Add the reject reason code, the approver on the corrected order and reliable timestamps, and the order platform and service desk can be read as one story. Lose the version number, and the address or account value that caused the rejection disappears from the record, leaving a port that looks routine.
Read → - Objecting to a 363 sale that undervalues intangible assets: grounds, evidence, remedies
An objection to a 363 sale over undervalued assets usually argues that marketing was too narrow, the price misses fair value, or the deal lacks a sound business reason. When the package sweeps in books, records and data for no allocated value, evidence that they could be licensed separately can support a targeted carve-out instead of blocking the sale.
Read → - Offer-to-onboarding record chain: the identifiers that carry one hire from offer version to signed letter to HR record
A company connects offer-to-onboarding records by following one hire through the identifier each system hands to the next: the application ID and offer version in the applicant tracking system (here Greenhouse), the signing package ID in the e-signature tool (Docusign), and the employee ID in the HR system (Workday). The chain holds where one system writes the previous system's key, usually the application ID, onto its own record. It breaks where a person retypes the accepted terms instead, which is also where the accepted offer and the HR record start to disagree.
Read → - Offer-to-onboarding records across Greenhouse, DocuSign and Workday: a metadata packet for introducers
A referral partner can describe a company's offer-to-onboarding history without opening a single offer letter. The useful facts are metadata: which system holds each offer version, where the signed letter lives, how the hire record is created, the date range and volume of each, which identifier carries an offer into the HR record, and who owns each step. The case to test before introducing is the one where the accepted offer and the HR record disagree.
Read → - Oilfield services bankruptcy: which job records can be licensed, and who must approve
In an oilfield services bankruptcy, the company's own field tickets, job logs, equipment maintenance histories and HSE incident records may be licensable estate assets, but only with approval from whoever controls the estate. Operator-owned well data and customer MSA confidentiality terms limit what can be included, so sort those out before any introduction to SourceX.
Read → - One claim, read twice: what a claims-system-only export loses from question to closure
A claims-system export keeps what happened and loses why. On its own it shows a claim that was declined, then accepted, with no visible reason. The broker's question lives in email, the late endorsement in the policy system, and the first, wrong letter in the document library. Read the same Illustrative claim twice, once from the export and once with those three pieces restored, and the gap is plain: the decision only makes sense with its context.
Read → - One company, three funds: who makes the introduction? A six-step protocol that compares each fund's own standing, lets the CEO pick the messenger and settles status and money before anyone asks
One fund makes the introduction, and the company's CEO chooses which one. Before anyone mentions SourceX to the company, the three funds compare facts about themselves only: whether anyone has already raised it, who has signed the partner agreement, whose policy permits a referral reward and who talks with the CEO directly. The best-placed fund then asks the CEO, once, whether the conversation is wanted and from whom. SourceX credits a single partner per company, so a second and third ask add noise and no credit.
Read → - One indexing backlog, read twice: what a standalone Datadog export loses from alert-to-runbook revision
A standalone Datadog export keeps the metric, the limit and the times a limit was crossed. It drops the people, the reasoning and the fix: who got the page, what they tried, what the cause turned out to be and which written procedure changed. It also cannot say whether a recovery meant the problem was solved, so one stubborn fault that clears and returns looks like two short, unrelated blips. That missing context sits in the paging tool and the team wiki.
Read → - One pump repair, read twice: what a standalone Salesforce Field Service export leaves out of alert-to-repair verification
What gets lost is whether the fix held. A Field Service export shows a job, a part and a status that says verified. It leaves out the number that triggered the job, the transducer swapped during it, the stock the ERP issued and what the replacement transducer reads on a healthy machine. Put back together, those pieces can show the numbers fell partly because the measuring device changed, something no lone export reveals.
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