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
- Shift to paid invoice, before and after: what a one-system export loses about one corrected week
A single-system export loses the disagreement. In a staffing firm, the firm's own system of record, the client's vendor management system and payroll each keep a slightly different true account of the same week, and none of them alone reveals that the accounts differ. One shows corrected hours with no idea what the client was charged; one shows charged hours with no sign of a correction; one shows a paycheck with no reason behind it. Only the connected chain shows the correction, who signed off each version, and who quietly absorbed the difference.
Read → - Shift-to-paid-invoice record chain: the IDs that join a placement, timesheet versions, pay line and client invoice
A staffing firm joins its shift-to-paid-invoice records by anchoring every hop on the placement: assignment to time record, time record to client sign-off, sign-off to invoice line, and time record to pay line. Where a system stores the firm's own placement number, the hop is a clean one-to-many join. Where it stores only its own record number, or only the worker's employee number, matching falls back to name and week, and that fallback fails on precisely the rows that matter: corrected, split and overlapping weeks.
Read → - Shift-to-paid-invoice records: a sample metadata packet for staffing firms
A referral partner can map a staffing firm's shift-to-paid-invoice history from metadata alone: which system holds the approved placement, where hours are entered and signed off, which pay run settled them, which system issued the client bill, how many years each goes back, and which identifier ties one week of hours to both the paycheck and the invoice line. Nobody opens a record. The case worth testing is a correction that reached payroll but never reached the client.
Read → - Shipment-to-credit-resolution record chain: one anchor key from dispatch to carrier remittance to ledger credit
A company connects shipment-to-credit-resolution records by choosing one anchor key that every team already types, usually the bill of lading (BOL) number, and checking that each later record carries it or a reference that points back to it. The usual weak point is the carrier's remittance: carriers pay against their own claim numbers, so the money lands in the ledger unmatched unless accounts payable writes the company's claim number beside it.
Read → - Shipment-to-credit-resolution records: a sample metadata packet from WMS scan to carrier claim to ERP credit
A referral partner can describe a company's shipment-to-credit history from metadata alone: which system records the dispatch scan, where the carrier claim lives, which ledger records the credit, how many claims a year, which reference ties them together, and who owns each step. No claim file or invoice changes hands. The case to test before introducing is a claim that references a shipment the carrier or warehouse later split, because that is where credits stop matching their claims.
Read → - Shopify Plus agencies: the data introduction hidden in a returns platform replacement
Sometimes. In a typical Shopify Plus stack, the customer's return reason and instructions, the approval in Shopify, the warehouse inspection and the final refund decision can sit in three or four different systems, and the returns app often holds the middle of that chain. Replacing the app can keep every order and still separate the instruction from the inspection outcome. Shopify Plus agencies can ask the brand's owner this metadata-level question and, if the company appears eligible and wants to proceed, introduce its decision-maker to SourceX.
Read → - Should a firm lead with education or direct introductions? A four-question decision map that picks from facts about your client book, and keeps education from costing you the credit
Lead with direct introductions when you can already name clients that pass the fit facts and you speak with their CEOs. Lead with education, such as a client briefing or a newsletter piece on licensing operating records, when your book is broad and you cannot tell who fits. In both cases, ask clients to reply to the firm rather than contact SourceX on their own: under the program terms, a company's earlier contact with SourceX makes it an existing relationship, not a new introduction.
Read → - Should a fund run a broad survey or a targeted referral pilot? A decision matrix that picks by what you already know, and the case where neither is right
Run a broad survey only when you cannot yet tell which portfolio companies pass the published screen, and keep it to a few metadata questions. Run a targeted pilot when a handful already pass and each has someone who will ask its CEO. A survey records what founders say; a pilot records what happens. When the screen facts are missing and nobody can ask, run neither: screen from what the fund already holds, then look beyond the portfolio.
Read → - Should a venture fund accept data referral rewards? Decide who would take part and who would benefit before any compensation story, using an eight-item fund-policy review agenda that ends in firm-level participation, unpaid mentions or no part
Not as a reflex, and not before the fund has a policy. A venture fund first decides who would take part (the management company, an individual partner, an outside affiliate or nobody) and who would benefit economically, then asks fund counsel how its own documents and duties treat that benefit. SourceX's sample agreement lets an entity sign as the partner, and a reward never reduces what the company is paid, but neither fact answers the fund's question. The eight-item agenda below ends in one of three policies.
Read → - Should I sell my business in 2026, or wait? A decision guide for owners
Sell your business in 2026 if you are personally ready, earnings are stable or rising and the company runs without you; wait if those are shaky but fixable within two years. Market data points to more sellers competing over the next decade. Owners who wait can still prepare and, if eligible, license records for one-time cash.
Read → - Should your firm add a data referral program? Score client fit and effort on one canvas before you look at the reward
Add one only if enough clients fit and the work stays small. A firm that can name at least five clients with 50+ full-time employees at peak, years of their own records and a CEO it can ask directly, and whose professional rules allow a disclosed referral fee, has a case for a one-quarter pilot. With fewer fits, a conflict you cannot manage or partner hours pulled off paid work, stay small or decline. Weigh compensation last: it is uncertain and arrives only after a client is paid.
Read → - Shutting down a business unit: the records plan for operating partners
When shutting down a business unit, assign an owner to each system, freeze deletions, take verified exports and ask the sponsor whether a licensing review is wanted before anything is cancelled. Closure keeps records with the company, unlike a divestiture, where they usually go to the buyer.
Read → - Side income for accountants and CPAs that fits professional rules
The best side income for accountants is work that survives your ethics rules: teaching, writing, templates, fractional roles and disclosed referral arrangements. For CPAs in public practice, AICPA rules on commissions, referral fees and contingent fees bar some payments where the firm performs attest work for that client, so screen every idea before you start.
Read → - Side income for board members: which outside earnings are allowed and which pay
Board members can usually earn side income from other board and advisory seats, consulting, expert calls, teaching and referral rewards, provided the work does not compete with the company, use its confidential information or create an undisclosed conflict. Check the conflict-of-interest policy, your director agreement and any employer or regulator rules before accepting payment.
Read → - Side income for consultants that needs no extra delivery work
The side-income routes that add the least delivery work for consultants are introductions and referrals, not new products or expert calls. SourceX offers one: introduce a qualified US client and step back. On a company's first qualifying transaction the reward is 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), with no cap, 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 → - Silver tsunami business owners: what happens to company records when boomers retire
The silver tsunami is the wave of baby boomer owners retiring and deciding whether to sell, hand over or close their companies. For referral partners it is a trigger: each decision puts years of email, CRM and finance records at risk, so raising an assessment early can preserve a licensable asset.
Read → - Slack retention policy best practice: decide before the first purge
Best practice for a Slack retention policy is to check legal holds, assess the value of existing history, preserve a copy, then change the policy by channel type. A short auto-delete rule can erase years of operational discussion on its first run, and deleted content may not be recoverable.
Read → - Software M&A trends in 2026: what sellers and their advisors should plan for
Software M&A in 2026 is shaped by a large backlog of sponsor-owned companies awaiting exit, a higher growth bar for new deals, diligence questions about AI exposure and code provenance, and AI developers paying for non-public data. For sellers, engineering and support records can be licensed beside a sale, on a separate track.
Read → - Solar company bankruptcy: which records hold value, and who decides what happens to them
In a solar company bankruptcy, the installer's operational records, such as permit packages, interconnection files, system designs, inspection results and service tickets, can be an estate asset worth assessing separately from homeowner, credit and financing data. The trustee or debtor in possession, with court approval where required, decides whether to introduce those records to SourceX for licensing.
Read → - Someone wants to buy my business: how to evaluate an unsolicited offer
When someone makes an unsolicited offer to buy your business, do not share financials or sign anything yet. Ask for a written summary of the buyer, structure and funding, bring in your M&A advisor, attorney and CPA, and apply the same discipline to any unsolicited offer for your company's data.
Read → - SOP revisions change the introduction: a twelve-question process-history interview that finds who wrote each version, who approved it and what was copied in from outside
A current SOP tells you how a company says its work is done today. The revision history tells you how that answer changed, who approved each change and why, and where text was borrowed. That shifts an introduction in two directions: the history can be the richer material for review, and it exposes origins a single version hides, such as pages copied from an equipment maker's manual or a franchisor's operations manual. Interview the document owner the CEO names, open no files, and leave rights and fit to SourceX's review.
Read → - Source code due diligence: what SourceX review in a software sale
Source code due diligence is a buyer's review of a target's codebase and engineering practices to confirm who owns the code, which open-source licenses apply, how secure and maintainable it is, and whether the team can keep shipping. The same Git history, pull requests and review threads can also be licensable records when the company's rights are clear.
Read → - SourceX referral terms, November 2026: what version 2026-11-04 says and what a signed Schedule A can change
The published SourceX referral terms are version 2026-11-04, published November 4, 2026. They define the reward on a company's first qualifying transaction as the greater of $50,000 plus 5% and 15% of the Actual Supplier Payout, with no cap and a USD 100,000 Minimum Transaction, and 15% on each further qualifying transaction first agreed within the twelve-month Repeat Window, never calculated on SourceX's fees, with a payment deadline 60 calendar days after the later of the Acquisition Partner's final written acceptance and completed handoff. Since 2026-10-12.2, the partner agreement has become the SourceX Channel Partner Agreement and section 3 has defined an existing relationship. A signed Schedule A prevails on the reward formula, base, Minimum Transaction, Repeat Window and any cap.
Read → - SourceX, Mercor, micro1 and Defined.ai: four enterprise data partnership models compared
Three structures sit behind the word "partnership". In a direct license, one counterparty contracts with the company, reviews rights, prepares and delivers the data and pays the company. In a sourcing program, the company connects tools or supplies records to a platform that runs its own pipeline and sets compensation by volume or value. In a marketplace, the company lists datasets and is paid per license as buyers come. Ask who signs, who prices and who the buyer is.
Read → - Special pricing agreement exceptions across CPQ, ERP and supplier claims: a system map of records and linking keys
Reconstructing a special pricing agreement exception takes four joins: the approval number, the validity dates as they stood on the order date, the end customer or project, and the claim reference. The quote tool, the ERP and the supplier's claim portal each hold part of the case, and they line up only where both sides recorded the same identifier. The approval number usually survives; the dates and the end customer link are the fragile joins, and they are the ones that explain why a claim was paid or refused.
Read → - Special pricing agreement exceptions: when an expired approval reaches a new order
The records that explain a special pricing agreement exception are the pricing request, the supplier approval with its validity dates, the order lines priced under it, the claim the distributor filed, the supplier's rejection or credit, and the note or re-approval that repaired it. Together they show a price that was authorized, misused, caught and corrected. A CPQ consultant should confirm these exist at metadata level and introduce the pricing director.
Read → - Spotting Data Licensing Referral Opportunities in Google Drive Projects
Google Workspace partners can identify potential SourceX referrals by focusing on 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) managing extensive historical data within Google Drive, particularly those with 50 or more full-time employees at peak (contractors excluded) and the rights to license their records. These insights often emerge during data migration, audit, or governance consultations.
Read → - Spotting Data Referral Opportunities in Jira Projects
Engineering process consultants working with Jira clients can identify SourceX referral opportunities 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, extensive operational records, and data licensing rights. Rewards are the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, on a company's first qualifying transaction, and 15% on repeat transactions within the 12-month Repeat Window.
Read → - Spotting Data Referral Opportunities in Microsoft Teams Projects
Microsoft ecosystem consultants can identify referral opportunities 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, a history of operations, and data licensing rights, especially during Microsoft Teams engagements. SourceX rewards partners based on the compensation it actually pays these companies for licensing their data directly to SourceX.
Read → - Spotting SourceX Referral Opportunities in Slack Projects
MSPs and operations advisors can identify SourceX referral opportunities 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, years of operational data, and licensing rights, often discoverable during Slack project audits or integrations. Rewards are the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap (the Actual Supplier Payout is the 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, to its first qualifying transaction, and transactions below USD 100,000 do not qualify unless SourceX agrees in writing. 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 → - Starting-state fidelity: rebuilding an order the moment a change request arrived
Starting-state fidelity is how accurately a record captures the situation at the moment a task began, not just how it ended. In an ordinary order desk, it means knowing which lines had shipped, which were picked and which were still open when a customer's change request arrived. For a referral, what matters is whether the company's shipment and order-change events are timestamped and kept, so that moment can be rebuilt, and who can authorize a licensing discussion.
Read → - Startup shutdowns in 2026: what the numbers show and where the records go
Startup shutdowns in 2026 have no single official count. Federal data covers all employer firms, while venture-backed shutdown figures come from private datasets with different coverage. The sourced data does show most small-business exits are closures, not sales. When a closing company had 50+ full-time employees at peak, its code, CRM and support history may be licensable, not deleted.
Read → - Startups selling Slack data to AI companies: what happened and what advisors should know
Startups selling Slack data to AI companies became news in 2026 because agent developers want real records of how work gets done, and shuttered companies had archives to sell. The privacy backlash shows the real questions: who owns the messages, who appears in them, what was promised, and who controls the decision if the company is insolvent.
Read → - State AI laws in 2026 that touch AI training data: what to check before licensing
State laws that reach AI training data in 2026 fall into three groups: developer documentation duties, consumer privacy statutes and automated-decision rules. Their status and dates keep shifting, so verify each against official sources. For licensed business records, the practical lesson is that buyers value clear provenance, documented rights and agreed redaction.
Read → - State repair data: the overlooked record of fixing a broken business workflow
State repair is the act of putting a business record back into the correct state after something broke it: a sync overwrote a field, an order stuck on hold, an invoice posted to the wrong account. The records that show it are a before value, the repair action with who and why, and an after value someone checked. A company that keeps all three, linked, holds a rare record of how its workflows get fixed.
Read → - State repair in subscription billing: restoring a customer's entitlements after a bad plan change
State repair means returning a business system to the state it should be in after an error moved it somewhere else. In an ordinary workflow it looks like this: a customer's subscription is changed to the wrong plan, paid features switch off, and a billing specialist restores the correct plan, seats and features, then checks the account against the signed order. The useful record is the intended state, the broken state, each corrective action and the check that confirmed the result.
Read → - Store transfer discrepancies across warehouse, POS and ERP: a system map of records and linking keys
Reconstructing a store transfer discrepancy takes four joins: the transfer order number, the license plate number (LPN) on each shipping unit, the item and quantity on each line, and timestamps on both sides. The warehouse system holds the first half of the story, the store POS the second half, and the inventory adjustment and case note sit wherever inventory control works. The transfer order number pairs a shipment with its intended receipt; only an LPN can follow stock that went somewhere else.
Read → - Store transfer discrepancies: tracing a partial shipment that was marked complete
The records that explain a store transfer discrepancy are the transfer order, the dispatch scans at the shipping site, the shipment posting, the store receipt, the variance case or ticket where someone investigated, and the inventory adjustment with its reason code and approver. Together they show the gap, the decision and the closed variance. A retail ERP partner should confirm these exist at metadata level, then introduce the inventory operations head.
Read → - Strategic options review for independent board advisors: which executive owns the record inventory and commercial permission?
In most companies two people hold the answer. The executive who owns the record inventory is the operating leader responsible for the systems that hold the history, often the COO or CIO. The executive who holds commercial permission is the CEO acting under authority the board has delegated, with the board itself deciding anything material during a strategic options review. Independent board advisors can ask which executive owns each key, and introduce the one authorized sponsor to SourceX if the company wants to explore licensing.
Read → - Structured dismissal after a 363 sale: who holds the leftover records?
A structured dismissal ends a chapter 11 case by court order with added terms, often after a 363 sale leaves too little to fund a plan. On dismissal, records excluded from the sale generally revert to the debtor entity, which may have no staff, so name a custodian and assess the records before the order is entered.
Read → - Studying unanswered referral offers: an owner interview and survey instrument with its sampling frame, consent wording and analysis plan published before a single answer is collected
Nobody has measured why owners leave SourceX referral offers unanswered, and this page reports no results. To a sender, "ignored" covers several different events: the message never arrived or went unread, was misread, looked irrelevant, came at a bad moment, never reached the CEO, was not trusted, or was declined without a reply. The instrument below asks owners which of these happened, through a consented 20-minute interview and a matched survey, with the sampling frame, consent wording, variables and analysis published before anyone is asked.
Read → - Subchapter V and data assets: can a small business debtor license its records?
A subchapter V debtor can, in principle, license operational records to fund plan payments, but court approval may be required and privacy promises can limit what is transferable. SourceX only works with 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, so many subchapter V debtors will not meet the baseline.
Read → - Subcontractor evidence reconciliation exception, worked step by step: evidence filed against a superseded scope
The records that explain a subcontractor evidence exception are, in order: the clause list in force after a contract change, the evidence package that did not match it, the reviewer's note naming the gap, the letter asking for more, the decision that let work continue or stopped it, and the follow-up attestation that closed the condition. Read together, they show the problem, who decided, and the checked result. The worked case below walks through one such chain.
Read → - Subcontractor evidence reconciliation system map: the keys that join contract files, portal and project records
Four keys join subcontractor evidence reconciliation across systems: the subcontract number with its modification number, the scope revision, the evidence submission ID, and the deficiency number. Contract files, a supplier portal, a project platform, a compliance mailbox and a quality log each hold one part of a case. When every record carries the key it needs, one case can be rebuilt end to end without anyone guessing; when one key is missing, the sequence breaks at that point.
Read → - Subcontractor evidence reconciliation: what to inventory before a subcontractor transition
Before a subcontractor transition, inventory the record classes that explain each evidence reconciliation: the flowdown list for every subcontract modification, the evidence the subcontractor submitted, the reviewer's notes, the approval or rejection that closed it, and the scope changes behind it. For each, record the system, the years covered, the named owner and the date access actually ends. Then introduce the supplier compliance director. Partners describe records; they never collect them.
Read → - Submittal revision review exception, worked step by step: a substitute unit that no longer fit the approved curb
The submittal records that explain an exception are the revision sequence of one item read together with the drawing revisions its comments cite: each submission version with its attachments, the reviewer's comment, the status code, the drawing change that resolved the conflict, and the field check that confirmed it. In the case below, a discontinued rooftop unit forced a substitute that clashed with an approved curb detail, and six records show what went wrong, who decided, and how the fix was verified.
Read → - Submittal revision review records: what to inventory before a document system transition
Before a document system transition, inventory every revision of each submittal, not just the final approved one: submission versions with their attachments, reviewer comments, approval status codes, and the drawing revision each comment refers to. Note which system holds each, the projects and years covered, who administers it and the date old access ends. Then introduce the design coordination head; whether the records can be licensed depends on rights, qualification and the proposed use.
Read → - Submittal revision review system map: joining submittal revisions, drawing revisions and field checks
Four keys join submittal revision review across systems: the specification section, the submittal number with its revision, the drawing sheet number with its revision, and the reviewer's identity with the review date. The submittal platform holds items and revisions, the drawing repository holds sheet revisions, consultant comments often arrive by email, and field verification sits in an inspection tool. When each record carries the right key, one case can be followed from first submission to installed work.
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