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
- How to pause an introduction without losing trust: a reason-and-restart log in which every pause names who at the company can lift it, and a no is closed instead of parked
Pause an introduction by writing down three things the day you stop: the reason, as one code; who can lift the pause, which is always someone at the company, never you; and the observable event that would let them. Then tell the founder, once, that nothing moves until they say so. If no company-owned restart condition exists, you are holding a decline, not a pause, so close it. The 90-day attribution window keeps running either way, and that cost stays with you.
Read → - How to pay down acquisition debt faster: options and the checks to run first
To pay down acquisition debt faster, use a cash sweep, working capital release, non-core asset sales, seller note prepayment or one-time proceeds, but check prepayment terms, lender consent and investor approval first. A SourceX data license can be one uncertain, one-time source of cash, never a base-case repayment plan.
Read → - How to prepare a business for sale to private equity, including its records
To prepare a business for sale to private equity, clean up financials, reduce owner dependence and organize diligence materials, then add a records-and-rights review: list systems, confirm who owns the records, and decide whether a data license sits before, alongside or after the sale. SourceX handles licensing once an advisor makes the introduction.
Read → - How to prepare a referral when the archive is inaccessible: name the lock, find the person who can open it and send a summary that says what nobody has seen yet
An archive nobody can open can still be described, and a referral can proceed when the CEO approves a summary that says so plainly. First name the lock: a departed administrator, a lapsed vendor account, a third party holding the data, an unreadable format or a legal hold. Then find the access owner, the one person or organization able to open it, and write the summary from what people remember, with every unseen line marked. The partner never attempts the recovery or asks for credentials.
Read → - How to present a data licensing opportunity to a board or owner
Present a new revenue opportunity to the board as a short decision memo: the approval you want, what the company would and would not license, rights and privacy checks, exclusivity, timeline, internal effort and risks. For data licensing, the right first ask is often permission to complete a data inventory and receive terms, not approval of a deal.
Read → - How to preserve a conversation when a company winds down: an authorized contact plan that records the CEO's answer, names who decides at each phase and keeps a route open after the email domain goes dark
Ask the CEO while the CEO is still in the seat. A licensing conversation survives a wind-down only if four things are written down before the team disperses: whether the company wants the conversation at all, who will hold that decision at each phase of the shutdown, where the records will sit and on whose instructions, and how to reach the decision-maker once company email stops working. Keep custody, control and the introduction as separate entries, and let retention and legal duties come first.
Read → - How to preserve company records before shutting down systems
To preserve company records before shutting down, inventory every system, confirm each vendor's export and retention window, keep admin access and billing alive until exports are verified, document who has authority to decide, and write a short preservation memo. Do this before cancelling anything: once an account lapses, the history may be gone, along with any licensing value.
Read → - How to prevent a referral webinar from becoming a payout pitch: an evidence-first storyboard of nine frames, each with the published source on screen, the money slide it replaces and the person who signs it off
Storyboard the session so that every frame puts a published source on screen before anyone speaks to it. Money gets two fixed frames: the host's opening disclosure that the fund could receive a referral reward from SourceX, and one late frame showing who pays whom, with no amounts. Nobody estimates what a company or an attendee might earn, money questions get answers written in advance, questions about a single company go private, and follow-up goes only to people who ask for it in writing.
Read → - How to prevent channel conflict across advisory networks: a five-overlap map that names one asker per company before any adviser calls a CEO
Decide who asks each company before anyone asks. SourceX credits one partner per company, chosen from dated records, so an advisory network cannot prevent conflict by sharing credit or carving up territories. It can prevent conflict upstream: keep one register of companies across member firms, give each company one named asker (the adviser who holds the CEO relationship), ask the CEO about earlier contact with SourceX before anything is submitted, settle fee disclosure where a profession requires it, and queue checks rather than introductions when the network outruns its coordinators.
Read → - How to prevent duplicate claims before they reach SourceX: an eight-step coordination checklist for the 48 hours before you introduce
Run a short coordination check before anyone sends a link. Pin the company to one legal entity, search your own claim register, ask the CEO whether anyone at the company has already been in touch with SourceX or been offered an introduction, agree in writing with any co-advisor which of you submits, then send the written introduction and the portal submission on the day the CEO agrees. A duplicate found before submission costs a phone call; one found afterwards is settled from dated records in SourceX's review.
Read → - How to prioritize companies you can reach credibly: score your standing with the CEO and the company's confirmed fit separately, then rank by the weaker of the two
Score each company twice, on separate scales: how credibly you can reach its CEO, and how much of its fit the company itself has confirmed. Rank by the lower of the two scores, never by their sum. A close friend whose company fails the size check and a strong-fit company whose CEO has never heard of you both belong at the bottom. Public clues tell you what to ask a contact; they never prove ownership, record quality or demand.
Read → - How to prioritize introductions when review capacity is limited: a queue rubric with a four-company work cap, a 90-day clock check and a rule for when to stop adding candidates
Cap how many companies are in active preparation, fill each open slot from a ranked queue, and finish one before starting another. Rank on what you can check today: a relationship owner who has agreed to ask, the fit facts you know, whether the CEO is ready to apply within the 90-day window, and the hours the case will take. Leave expected reward out of the ranking, because nobody can estimate it before SourceX's review. When the queue grows faster than you clear it, stop adding candidates instead of spreading hours thinner.
Read → - How to prioritize value creation initiatives by cash, effort and management time
Prioritize value creation initiatives by scoring each on run-rate EBITDA contribution, cash timing, capital required, senior management hours and confidence, then rank by weighted score with hours alongside. Fund the top few within each executive's capacity, and add low-load, no-capital initiatives, such as a data licensing review for a qualifying company, as parallel fill-ins.
Read → - How to professionalize a founder-led business without losing its records
Professionalizing a founder-led business means moving decisions, knowledge and controls out of the founder's head and inbox into documented systems, roles and reporting. Do it records first: map every system and archive, preserve complete exports and settle ownership questions before migrations or cleanups, because those years of history are often an asset the company can license.
Read → - How to protect member trust when applications are declined: a member support response playbook that prepares members before anyone applies, asks each CEO at the yes how to follow up and answers a no without relaying it
Protect member trust before anyone applies. Every notice should say that the association cannot tell a member it qualifies, that SourceX reviews and the member's CEO decides, and that a no can come at several stages for reasons the association cannot see. When a member reports a decline, reply once, keep the outcome private, point to SourceX's published reasons, offer a way to give feedback, and never argue the member's case with SourceX.
Read → - How to prove you made a referral, and what to do if credit is disputed
To prove a referral, keep dated written records showing you introduced the company first: the owner's written permission, the introduction email or referral-link application, and a same-week recap of any in-person introduction. At SourceX, credit goes to the first valid referrer whose introduction leads to a verified application within the attribution window, and the signed terms decide disputes.
Read → - How to publish a pilot retrospective investors can trust: a ten-part methods, results and limitations outline that proves the plan came first, accounts for every company the pilot touched and says what was withheld and why
Publish it in an order readers can check. Methods come first: the plan as it stood before the first ask, and every change made since. Results come second: every company the pilot touched, shown once at its last recorded stage, as counts with their denominators, failures included. Limitations come third: the open cases and what the design cannot show. Then say plainly what was withheld, such as company identities, reward figures and SourceX deal details, and why.
Read → - How to publish network research without exposing companies: a twelve-gate anonymization and consent review that tests every table, quote, chart and footnote for a route back to a company, and holds the release until two intruders fail to name one
Treat every number, quote and chart as a possible route back to a company, and close each route before release. Use only the network's own records and what each company agreed to share; strip names and anything searchable; coarsen combinations of sector, size, region and dates; hide small cells and a second cell beside each, so totals cannot be subtracted; keep declined companies in coarser rows instead of dropping them; then have two people try to name the companies. Publish only when both fail. This page reports no research results of its own.
Read → - How to raise data licensing with US portfolio companies from Europe
A sponsor running US portfolio companies from abroad should raise data licensing through existing governance, such as the board agenda, quarterly review or value creation plan refresh, and keep it owner-led. The US CEO or CFO sponsors the screen, names a system owner, and decides whether to be introduced to SourceX.
Read → - How to rank referral candidates without a fastest-growing claim: gates first, weights fixed in advance and a rank range for every company
Rank referral candidates with a method you could hand to a skeptic: pass/fail gates first (50 or more full-time employees at peak, documented operating history, rights to license, location and a CEO path), then five metadata-level criteria with weights written down before anyone scores, unknowns scored as zero, and a sensitivity run that turns each rank into a range. Leave growth rate out. A fastest-growing list measures revenue momentum from a small base, which says nothing about records.
Read → - How to re-engage a dormant partner with useful context: a dated brief of what changed since their last introduction, where their agreement stands and which old companies may now be duplicates
Re-engage a dormant partner with a short, dated brief written for that partner: what changed in the program since their last introduction, what did not, where their signed agreement stands, which companies they once mentioned may now be duplicates, and one ask that fits today's criteria. Send briefs in small waves you can follow with a call, accept "not now" as a complete reply, and stamp every brief with the terms version it describes so you can correct it later.
Read → - How to read a CIM as a buyer, including systems, records and NDA limits
Read a CIM twice: once for the business, then for how work is recorded, meaning which systems run it, how far back they go and who administers them. Information received under an NDA is for evaluating that deal only, so it cannot be used to refer the company to SourceX without the owner's agreement.
Read → - How to read a WARN notice as a signal for a data licensing introduction
A WARN notice is a useful data licensing signal because it shows a larger employer planning a plant closing or mass layoff, usually before its systems are switched off. Treat it as a prompt to screen fit and help preserve records, and reach the company through its advisors, lender or board, never through the employees being laid off.
Read → - How to read IT services company valuation multiples in 2026
IT services companies are valued as a multiple of adjusted EBITDA, and the multiple depends on revenue quality, contract mix and owner dependence rather than the label. A SourceX data license is one-time cash outside the multiple, which advisors can raise with owners who have 50+ full-time employees at peak.
Read → - How to rebrand an acquired company without losing its domain, email and archives
To rebrand after an acquisition without losing history, settle the brand architecture first, then keep the acquired company's domain registered and receiving mail, archive departing mailboxes instead of deleting them, export every system before cancelling it, and save dated copies of the old website and privacy policy. The new brand can launch while the record survives.
Read → - How to recheck eligibility when a company raises capital: a six-step workflow that separates a new cap table from a new controller, a new CEO or a new headcount
A raise neither makes a company eligible nor ends an introduction. SourceX screens on full-time headcount at peak, operating history, rights to license, an authorized CEO and fit with a current program, and funding status is not one of them. What a financing can change is the operating entity, who controls it, who its CEO is, which investor consents its new documents require and, through hiring, its headcount. Recheck those five facts, and the attribution clock, before anyone reopens an introduction.
Read → - How to recognize a company that is ready to explore but not commit: an exploration decision map that reads what the CEO actually asked for, matches it to the steps SourceX publishes before any signature and asks permission for that step alone
A company is ready to explore when its CEO wants to learn what licensing would involve and has room to answer questions, but does not yet want to decide anything. SourceX's published process fits that: its first step asks for answers rather than files and creates no obligation, and nothing is licensed until the company signs a Master Supplier Licensing Agreement and a Dataset Deal Confirmation for a specific deal. Ask the CEO's permission for that first step only, and leave every later decision with the CEO.
Read → - How to recognize a partner network that is starting to compound: six cohort signals, and the growth that only looks like it
A partner network is compounding when each round of introductions makes the next one better: the same introducers come back with another company that fits, the share of introductions reaching a verified application rises from one cohort to the next, and screening questions get sharper because past declines taught something. More names, more links and more applications are growth, not compounding. Track repeat introducers and fit rates by cohort. SourceX has not published network-level figures, so this page gives the dashboard and its method rather than results.
Read → - How to reconcile a reward with the supplier payment basis: a three-way match from SourceX's stated basis to your recomputed entitlement to the cash in your bank
Recompute the reward from the supplier payment basis SourceX states, not from the deposit you received. Entitlement to date is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, on the company's first qualifying transaction, plus 15% of each further qualifying transaction first agreed within 12 months of the first Closing, unless a signed Schedule A says otherwise. Subtract what you have already received, and the result is what should be due once every payment condition clears. Any difference from the cash that arrived gets a reason code: timing, floor or minimum, exclusion, reduction or offset, signed exception, partial handoff, bank or unexplained.
Read → - How to reconcile different definitions of a qualified introduction: a definition alignment worksheet that translates each fund's 'qualified' into a dated event in SourceX's documents, so co-investors agree on what happened before anyone reports it
Retire the word and record the event instead. In one fund a "qualified introduction" means the founder agreed to a meeting; in another it means an associate clicked Qualify in the CRM; in a third it is a line on a platform scorecard. SourceX's terms recognize none of these. Credit goes to the first valid introduction of a new company once that company files a verified application within 90 days, and payment waits for later conditions. Translate each fund's definition into those dated events, pick one introducer, and report status only in event names.
Read → - How to reconcile manual introductions with portal activity: a monthly worksheet that gives every company one of seven match states, keeps each original record exactly as it was and leaves overlapping claims to SourceX
Once a month, line up two lists: the introductions your people made by hand (emails, calls later confirmed in writing, meeting notes) and what the partner portal shows (submissions, link visits, stages). Match them on the company, never on a person or a click, and give each company one of seven match states with one action. A link visit without a written introduction is not an introduction, and a spoken one needs written confirmation. Never back-date, delete or resubmit to make the lists agree: SourceX decides credit from dated records and settles overlaps in its duplicate review.
Read → - How to reconcile SourceX statuses with a fund's CRM: a field map that keeps stage, credit and reward status apart, and a monthly three-way match
Don't force SourceX into one deal-stage picklist. Keep three things apart in the fund's CRM: the referral's stage as the partner dashboard shows it, the credit decision (credited, in duplicate review, not credited or lapsed) and the reward status, which SourceX publishes as Estimated, Eligible, Approved, Processing and Paid. Give each its own field with the date it was last checked, keep win probabilities off these records, and once a month match the CRM against the dashboard and the bank, one row per unique company.
Read → - How to reconnect after a company declined last year: a changed-facts template that renews the relationship without reopening the question, rechecks what lapses in twelve months and leaves the next move to the CEO
Reconnect for the relationship and leave last year's no exactly where the CEO put it. Twelve months is not a reason to ask again: only the CEO can reopen a decline, and nothing you notice makes the company newly fit. Before you get in touch, check what may have lapsed on your side, meaning your Channel Partner Agreement and your knowledge of SourceX's current terms, and who leads the company now. If the CEO raises SourceX, answer from today's pages and from the facts the CEO gives you.
Read → - How to reconnect with a former client about a new opportunity: a five-part permission email built from public clues, never from what the engagement taught you
Write to the person you worked with, not to the company's general inbox, and build the message from only two things you may still use: a dated public clue and the shared history itself. Leave out anything you learned inside the engagement. Say plainly what you are raising and that you may be paid, ask one question that can be declined in a word, and introduce the company's CEO only after a written yes.
Read → - How to record a company's decline without keeping its private reasons: a seven-code taxonomy that stores what the no allows next, never why it was said
Record what the no allows next, never why it was said. A decline record needs one of seven codes, the date, who gave the answer and in what role, how far it reaches and any date the CEO named for hearing back. Reasons a CEO volunteers, such as a pending sale, a cash squeeze, a customer dispute or a founder's illness, stay out of every field. The code alone stops colleagues from asking again, and the CEO's confidences stay where they were told.
Read → - How to record an executive's approval without keeping extra data: six fields, a keep-point-drop test for everything else and a delete-by date
Record the approval, not the conversation around it. Six fields carry everything a later decision needs: an internal company code, the approver's role, the date and channel, the scope approved, anything ruled out, and a pointer to the message in which the approval was given. Point to evidence where it already lives instead of copying it, keep board material, recordings and company records out entirely, and set a delete-by date tied to reward accounting and any dispute.
Read → - How to record what you do not know about a dataset: a known-unknown evidence grid that gives every gap a status, an owner and a date
Record unknowns as entries, not omissions. For each fact in a referral summary, write its status (confirmed by the company, estimated with a range and its basis, or unknown), who can close the gap (the company itself, or only SourceX's review) and the date you asked. Keep the summary to metadata the CEO has approved, attach no records, and send the open items with the introduction so the first call starts from them instead of discovering them.
Read → - How to recover admin access to company systems after an acquisition
To recover admin access after an acquisition, list every system, ask the seller to add two company-controlled admins under the purchase agreement's cooperation clause, and use each vendor's recovery process, which usually means proving control of the domain or billing account, where the seller cannot help. Then remove personal logins and test that exports work.
Read → - How to redact PII from call transcripts and audio before licensing them
To redact PII from call transcripts, agree a written redaction specification first, then remove identifiers from the text and the matching audio segments together, normalize spoken numbers so card, account and phone digits are caught, replace speaker names with role tokens, and hand-check a stratified sample of calls before anything leaves the company.
Read → - How to redact PII from email archives at scale before licensing them
To redact PII from emails at scale, agree a written specification with the company first, then process each message in parts: headers, body, signature, quoted replies and attachments. Replace every person and identifier with the same token across the whole archive, deduplicate threads before review, and sign off only after a sampled manual check passes.
Read → - How to reduce owner dependence in a business before you sell
To reduce owner dependence, log the decisions only you make, sort them into rules, manager judgment and true owner calls, document and delegate the first two with clear authority, hand over key relationships, and test your absence. Start well before a sale so buyers can see a track record.
Read → - How to refer a business in restructuring without promising recovery value: a conditional discussion guide that answers what it is worth, when and for whom with only the facts that exist at each stage
Say only what is true at the stage you are in, and offer no figure before one exists. Before SourceX's review there is no number at all. Qualifying is not an offer. Any range before a signed Dataset Deal Confirmation is indicative, only the signed Confirmation fixes a payout, and data that never reaches Closing earns nothing. Tell the decider, whether the company's CEO or the controller of an estate, that your own reward would grow with the payout. That interest is the best reason you have never to estimate it.
Read → - How to refer a business that recently centralized IT: a centralization sponsor map that shows who gained the view of every system, who still owns the records and why the question waits until the last site has moved
Wait until the move is finished, then ask the CEO, not the new IT function. Centralizing IT puts every site's systems under one team, which makes the head of IT a well-informed guide, but it moves custody, not ownership: the records still belong to the business that created them, and the decision still sits with the CEO. Treat the centralization as context for a single question once the last site has cut over, and never ask IT for access, exports or summaries.
Read → - How to refer a business with a custom-built internal system: a nine-question context brief that stands in for the missing vendor manual, answered by the people who built and run it and kept by the company
Introduce the CEO, not the system. A custom-built system is referred like any other, but it lacks the shorthand a product name gives a reviewer: a known export path, published field lists, a vendor's documentation. Fill that gap with a nine-question context brief answered by the people who built and run the system, covering purpose, lineage, record families, history, volume, documentation, ownership and export. The CEO reads it and decides; the company keeps it and uses it to apply.
Read → - How to refer a business with a recently acquired operating license: ten company-versus-regulator questions that sort what the license settles, what the CEO decides and what only SourceX's review can answer, with a timing table for the months after approval
A new operating license changes what a company may do, not who decides. Its CEO still decides whether the company talks to SourceX about licensing its own records, and a partner never reads the license on the company's behalf or guesses what it permits. The sensible moment is after the licensed work is running and the CEO has shared the license as news, not while approval or its start-up conditions are open. Ask once. Records made under a license granted this year cover months, not years.
Read → - How to refer a business with dormant but documented operations: a nine-box screening canvas that tests the peak, the paper trail and who still answers for a company that has gone quiet
A business that has gone quiet can still be introduced when four things hold: its full-time headcount reached 50 or more at its peak, its own operating records survive, it still has the rights to them, and someone with current authority wants the conversation. Today's skeleton staff does not settle the size question, because peak counts. What usually ends the screen is something else: a lapsed software account, an entity that has been dissolved or struck off, or nobody left who can say yes. Check those first, in conversation.
Read → - How to refer a business with several sellers: a seller authority alignment map that keeps the CEO's yes, each seller's stake and the sale timeline apart
Introduce the company, not the sellers. However many owners are selling, the program looks to one authorizer: the company's CEO until closing, and the acquirer's CEO once the deal closes. Sellers' agreements can still limit what the CEO may agree to, and where two owners hold equal stakes the CEO alone may not be enough. Ask the CEO to align the sellers through the company's own channels, keep each seller's personal stake out of your pitch, and agree which single adviser submits.
Read → - How to refer a client whose data rights need legal review: a counsel handoff note that carries the CEO's own doubts to the company's lawyer, keeps your pay question with your own adviser and never routes a contract through you
Refer a client whose rights to its records are unclear the way you would refer any client, with two additions. The rights question goes to the company's own counsel and to the rights check SourceX runs while it qualifies a company, before any records are shared; you offer no view on it. Your own question, whether you may take part and be paid, goes to your board, society, employer or counsel. A one-page counsel handoff note, written from the CEO's own words, keeps the two questions apart and every contract out of your hands.
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