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 avoid creating a new copy of a sensitive archive: a no-copy referral process map that names the copy each stage of an introduction invites, the move that replaces it and the only party who could ever approve a copy
Make no copy at any stage of a referral. A screenshot, a forwarded index, a sample export, a test restore or a data-room upload is a new copy of the archive, made outside the controls on the original and owned by nobody in particular. The referral needs none of them: SourceX's first step asks for no files, and its partner agreement bars partners from collecting dataset copies without separate written authorization. Whether any copy is ever made, for a legal duty or later under a signed deal, is decided by whoever controls the company or its estate.
Read → - How to avoid declaring a winner from five replies: the coin-toss arithmetic a 4-1 split cannot beat, a threshold table fixed before the test, and a no-winner verdict that keeps your current message
Five replies cannot pick a winner. If two outreach messages were exactly as good as each other and went to equal numbers of CEOs, five replies would still split 4-1 or 5-0 in one direction or the other 12 times out of 32, more than a third of the time. Replies are also the wrong count: a reply can be a no. Decide before the test how many verified applications you will wait for, how lopsided the split must be at that total, and what happens when it falls short: you keep your current message and record no winner.
Read → - How to avoid depending on one large referral: a concentration scenario worksheet that keeps your firm's plan working if the biggest introduction pays nothing
You depend on one large referral when a single introduced company carries most of the reward your firm is counting on, most of its referral hours, or a client relationship you cannot risk. Under SourceX's terms that company's reward is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, but it pays nothing until the Acquisition Partner's final written acceptance, handoff and supplier payment, and can stall, shrink or turn out to be a duplicate. Measure the dependence in hours, expectations and relationships, test the plan with that company at zero, and spread capped effort across other companies.
Read → - How to avoid duplicate founder outreach across co-investors: a shared contact plan that gives the founder one sender, one message and one date, and gives every other investor a line to use if asked
Agree a written contact plan before any co-investor writes to the founder. It names one sender, one channel and one send window, keeps every other investor silent until the founder replies, and hands them a single sentence to use if the founder brings SourceX up. The founder's answer is logged once and honored by all. Only one partner can be credited per company, so extra emails produce confusion and duplicate-review work, never extra credit.
Read → - How to avoid founder fatigue from repeated platform offers: a 90-day audit that weighs every ask a founder receives, checks consent, and shows which founders to leave alone
Count before you add. Founder fatigue builds from the total of what a platform asks, not from any single offer, so audit every ask each founder received in the last 90 days: who sent it, how much effort it demanded and whether the founder had signaled wanting that kind of message. Set a per-founder ask budget, honor every "not now" across all programs, and give a data licensing mention one slot, only for founders with room in their budget whose companies pass the published fit screen.
Read → - How to avoid implying fund endorsement in partner content: a name-and-logo permission checklist that matches every use of the fund's name to the person writing and the path on the signed partner agreement
Treat every appearance of the fund's name in referral content as a claim that needs an owner. A title in a bio, a logo on a slide, a fund email address or the word "we" can make one person's post read as the fund's view of SourceX. Match each use to whoever actually signed the partner agreement, add a one-line capacity statement saying who is speaking and who could be paid, and keep a dated record of who approved it. Never call the fund a SourceX partner in public without written authorization.
Read → - How to avoid inferring data ownership from a job title: eight titles decoded into what the person knows, what the company must prove and who says yes
A job title is evidence about what someone works on, not about who owns the records or who can license them. Read every title as answering one question: what this person probably knows. Whether the company holds the rights is settled in SourceX's rights review. Who says yes is already settled by the program: the CEO, or the acquirer's CEO once a company has been bought. Ask your contact about systems and years, then ask whether they will take the idea to the CEO.
Read → - How to avoid promising a data windfall in a listing: an eight-question substantiation check for every data line, and the earliest moment each claim could ever be proven
Put only what the owner can prove on listing day into the listing: which systems the company runs, how many years they cover and roughly what they hold. Leave out any value, any buyer interest, any claim that the data is licensable and SourceX's name. A licensing payout exists only once a Dataset Deal Confirmation is signed, and money moves only after Closing, so a listing published months earlier cannot honestly promise either. Run each data sentence through the eight questions below before the CEO approves it.
Read → - How to avoid reward-driven pressure on customer success teams: a six-question customer trust incentive review that rules out quotas, contests and per-introduction bonuses
Do not pay customer success managers per introduction, set quotas or run time-limited contests for SourceX referrals. When the SaaS company is the registered partner, any reward reaches it well after the introduction, only once the customer's own licensing deal has closed and been paid, so a bonus at introduction time pays for something the program never rewards. Recognize good judgment instead, disclose the reward to every customer, and run any proposed incentive through a six-question customer trust review before launch.
Read → - How to avoid sharing client financial records during referral screening: a metadata-only finance intake that takes every answer from the client's CEO, given for this purpose, and copies nothing from the books you already keep
Do the screening without the records, including the ones you already hold. A fractional CFO or accountant often knows a client's headcount, history and systems from the books, but that knowledge came from the engagement. For a SourceX introduction, every fit answer should come from the client's CEO, given for this purpose, as descriptions and rough figures. Nothing is exported, screened, reviewed or forwarded, and your own professional and pay rules are settled before the first question.
Read → - How to avoid suggesting a corporate partner endorses SourceX: a co-branding permission audit that checks every logo, label and sentence before it reaches a company, and names who must approve each one
Audit every asset before it leaves the team. A corporate logo next to SourceX's, words such as partner, preferred or approved, or a session held under the corporate's banner can each read as the corporate vouching for SourceX, and as a hint that companies will qualify or get special treatment. Take the corporate's marks off unless its brand owner has approved them in writing, describe the relationship in plain facts, disclose any reward, and leave every decision with each company's CEO.
Read → - How to avoid treating headquarters as a data residency answer: ten location questions that keep the head office, the entity that holds the records, each system's storage region and the records' language apart
Headquarters answers one question: where a company says it is run from. It does not say which legal entity holds the records, where each system stores them, what language they are in, or what contracts say about moving them. SourceX's published location test looks at where the company is and, outside the U.S., Canada and the EU, at the language of its data; SourceX publishes no rule about where data is stored. When residency comes up, write "unknown", leave the answer to the company and its own advisers, and let SourceX speak for SourceX.
Read → - How to avoid turning an LP update into an advertisement: an optional resource disclosure guide that keeps any SourceX line below the fund's reporting, says who could be paid and leaves out every company the fund introduced
Keep the update a report. If the fund mentions SourceX at all, put it in one short, labeled box after the fund's own reporting; say plainly that the fund's team could receive a referral reward from SourceX; say nothing that suggests SourceX endorses the fund or its companies; ask nobody to invest in anything; and never name or describe a company the fund has introduced. If the box could be deleted without the update losing a single reporting fact, it is in the right place.
Read → - How to be a useful advisory board member between meetings
To be a good advisory board member, own one topic, prepare twenty minutes before each meeting, make a few well-framed introductions and follow up in writing within a week. Disclose any fee you might earn. The guide also shows how to raise a data licensing question with the CEO without overstepping.
Read → - How to benchmark KPIs across portfolio companies, and where benchmarking ends
To benchmark KPIs across portfolio companies, agree a short metric dictionary, collect monthly figures in one format, compare companies only within comparable cohorts and act on gaps in operating reviews. Benchmarking uses aggregated KPIs the sponsor already gathers; licensing raw operational records is a separate decision each portfolio company makes for itself with SourceX.
Read → - How to brief a newly appointed CEO about an existing referral: a one-page transition packet with your stake on it, three equal choices and nothing from the board pack
Brief the new CEO once, in writing, on a single page: where the introduction stands, what the predecessor approved and when, what you stand to gain as the introducer, and three equally weighted choices: continue, pause or end it. Treat the earlier yes as history rather than permission, keep anything learned from board materials off the page, and let the company, not the fund, tell SourceX what it decided.
Read → - How to brief an assistant who coordinates sensitive introductions: a coordinator access and handoff guide that gives the scheduler names, times and a neutral meeting title, keeps company facts out of delegated inboxes and calendars, and leaves every yes with the CEO
An assistant who coordinates a sensitive introduction needs four things: who is being introduced to whom, how to reach each office, which times work, and a neutral title for the meeting. Everything else stays with the partner: the company's records and figures, anything learned in confidence, the partner's possible reward and every judgment about fit. Brief the assistant in writing before the first email, check what delegated inboxes and calendar titles already expose, and name the moments when the assistant stops and hands back. The company's CEO decides whether any conversation happens.
Read → - How to bring a data licensing question to a CEO peer group (issue processing)
To bring a data licensing question to a CEO peer group, present it as one owner-level decision in a five-part issue statement: situation, decision, what you tried, what worries you and what you want from members. Chairs or members who are also SourceX partners should disclose any potential reward before advising.
Read → - How to bring up a new opportunity with a long-time client without damaging trust
To bring up a new opportunity with a client, tie it to a meeting already on the calendar, ask a curiosity-first question, disclose any reward you might receive, and ask permission before saying more. The owner decides, and accepting a no keeps the relationship intact. This guide gives a 60-second script and a step list.
Read → - How to budget for one-time data licensing income in a forecast
Budget a data license as a separate non-recurring line: keep it at zero in the base case until a signed agreement exists, weight it by deal stage in scenarios, and date the cash from the invoice, typically within about 60 days. Never annualize it or build hiring on it.
Read → - How to build a conservative referral budget with zero as a scenario: a 12-month zero-base cash model that sizes the effort your firm can carry if nothing pays this year
Budget the referral effort as a cost your firm can carry in a year when referral revenue is zero, and set the revenue line itself at zero. Move a dollar into the forecast only when a dated event in the program terms puts it there: SourceX has paid the referred company, finance has approved the reward, or the reward has been paid. Then test two other years against the same cost: one where a real reward slips past year-end, and one where a single reward is the whole result.
Read → - How to build a finance transformation roadmap that starts with a records census
A finance transformation roadmap moves a finance function from its current state to a target operating model in sequenced waves: assess people, process, technology, data and controls; define the target; score and order projects; then deliver and govern. Begin the assessment with a records census so no system retirement deletes years of history by accident.
Read → - How to build a referral queue without uploading client data: a ten-slot metadata template that tags where every fact came from, four controls that keep files out and a routine for the day one gets in
Build the queue from facts, not files. Each company gets one card with ten slots: a code, the entity and its public web domain, its group, the CEO who decides, the colleague who owns the relationship, four fit answers in the CEO's own words, any earlier contact with SourceX, who holds the next move, one dated action and a pointer to the message behind it. Tag every fact with where it came from, give the queue nowhere to attach a file, and empty each card when its referral ends.
Read → - How to build a sales forecast from CRM deal history, and what the data depth tells you
Build a sales forecast from CRM data by measuring stage-to-stage conversion and win rates on closed deals, applying them to open pipeline and adjusting for deal age. The same work shows a fractional CFO how many years of deal history a client keeps, a quiet fit signal for a permissioned licensing introduction.
Read → - How to build a small high-confidence referral queue: a fit-permission-confidence triage board with five ready slots and a column for every card that cannot move
Keep the queue short and let three things move a company forward: fit facts the company itself confirmed, permission from the person who can say yes, and confidence that what you know is firsthand rather than inferred. Score each card on all three, allow at most five in the ready column, and park everything else in verify, ask, no path or out. A public clue can open a card; it never moves one.
Read → - How to build an ARR bridge for due diligence from billing exports
Build an ARR bridge by starting with beginning ARR, adding new, expansion and reactivated ARR, subtracting contraction and churn, and ending at ending ARR, all tied to customer-level billing records. Keep one-time items, including any data license payment, outside ARR so the schedule stays credible to buyers.
Read → - How to build an M&A buyer list, and why AI labs and data users sit on a separate track
To build an M&A buyer list, start from the seller's goals, map four acquirer groups (strategics, financial sponsors, PE-backed platforms, and independent sponsors or search funds), score every name on fit, funding and friction, then tier and sequence outreach. AI labs and data buyers do not belong on it: a data license runs as a separate track.
Read → - How to buy a company out of bankruptcy and keep the records worth having
Buying a company out of bankruptcy usually means buying its assets in a court-approved section 363 sale, where the purchase agreement and sale order define what transfers. Records and systems pass only if they are listed, and privacy promises can limit customer data. Once you own a qualifying business, you can introduce it to SourceX as its authorized sponsor.
Read → - How to carve EU and UK records out of a US data license
To exclude EU and UK records from a dataset, stack several filters: email domains, office and remote-staff rosters, CRM country fields, chat workspace membership and ticket locale. Apply them in order, sample what remains, and log every rule so the exclusion can be shown to a buyer.
Read → - How to check what ServiceNow history your archiving and retention rules have kept
ServiceNow archive rules move closed records such as incidents and changes into read-only archive tables, while archive destroy rules and table cleanup policies delete records for good. To learn how much history remains, list every active rule, count records by year in live and archive tables, and hold any pending purge until the owner decides on a licensing review.
Read → - How to check whether an existing SourceX relationship affects credit: six questions before you introduce, three dated timelines and a duplicate-review inquiry to send when the answer is unclear
Ask the company before you introduce it, because you cannot search SourceX's records yourself. Under the program terms (Version 2026-11-04), a company that already has an application, relationship or earlier valid introduction with SourceX is reviewed as a duplicate and is not credited to a later partner, and a relationship includes any earlier lead, account or email correspondence, however it began. Six dated questions to the CEO settle most cases; the rest go to SourceX with the inquiry below.
Read → - How to choose a partner program's first internal champion: a six-criterion scorecard with two gates, two staffing models and a rule for when nobody should take the job
Choose the person who will protect client trust, not the one most excited by the reward. Score candidates on six criteria. Two are gates: the candidate knows the firm's professional rules and will turn down a weak fit, and the candidate has protected time. Four are scored from 0 to 2: access to client CEOs, record literacy at metadata level, recordkeeping discipline and standing to train colleagues. If no one passes both gates, keep the program small or decline it until someone does.
Read → - How to choose an ABC assignee: the data and records questions to ask before you sign
To choose an assignee for an ABC, interview several experienced professional assignees and compare independence, state and industry experience, fees and their plan for software and data: who keeps systems running, how personal data will be handled, and whether records will be assessed for licensing directly to SourceX to add recovery for creditors.
Read → - How to choose an M&A advisor to sell your software company
Choose a software M&A advisor by testing relevant deal history, the named team, buyer access, fee terms and process design, then add two often-missed questions: does the advisor review your data and records footprint, and how would they handle a parallel licensing offer? Interview at least three firms with the same list.
Read → - How to choose an MSP after an acquisition without losing years of records
When choosing an MSP after an acquisition, pick the provider that will take over admin access, confirm backups and archived mailboxes, and run a documented handover from the old MSP before changing anything else. Ask every candidate in writing how they handle retention, former employees' data, offboarding and data return, then compare the answers side by side.
Read → - How to choose between research, events and direct introductions: a one-quarter channel allocation experiment that counts CEO opt-ins per platform hour
Choose by measured result per platform hour, not by habit. For one quarter, assign the companies you could introduce at random to three channels: a short research memo, an invitation to a closed founder session, or a direct ask from whoever owns the CEO relationship. Count the CEOs who ask for a conversation, how useful founders rate it and the hours each channel costs, with referral income at zero. Keep the channel that produces informed opt-ins most cheaply, and stop if none clears the bar you set beforehand.
Read → - How to clean up a fixed asset register without wiping archives the company needs
A fixed asset register cleanup reconciles the ledger to what physically exists: count and tag assets, write off ghost assets, record what was never capitalized, and fix lives and locations. For retired servers, NAS units and backup tapes, add one step before disposal: confirm with the owner whether they hold archives worth preserving, because deleted history is gone.
Read → - How to clear a referral relationship through your accounting firm's alliance review
An accounting firm alliance program is the internal review that approves third-party relationships, such as a SourceX referral arrangement, before partners use them with clients. To clear one, give risk management the reward terms, a restricted entity list search, a written attest-client rule, a disclosure method and confirmation that no client records leave the firm.
Read → - How to close a referral record after SourceX review: a closure reason and retention checklist that copies SourceX's recorded outcome word for word, files your own theories nowhere and keeps only what reward accounting or a dispute could need
Close a referral record only when SourceX has recorded an outcome you can point to: a reward that reads Paid, a duplicate-review decision, a reward canceled as ineligible, a deal that did not close or a reduction with SourceX's calculation. Copy that outcome as SourceX worded it, with the date and the place you read it. Then keep the introduction evidence, the CEO's permission and any reward statements, and remove everything else. Your own theory about why it ended, or about who was first, never enters the record.
Read → - How to compare data referrals with other platform benefits: price each one per founder outcome, over the same 90 days, with income at zero
Compare every platform benefit in the same unit: team hours and founder hours per founder who reached a usable outcome, counted over the same 90 days, with every income line set to zero. Define the outcome before you count. For a data licensing referral it is a CEO who made an informed decision, an application or a reasoned no, not a link sent. Then put reach and outside dependencies beside the cost. A referral track that costs more per outcome than any benefit founders rate useful should stop.
Read → - How to compare networks without ranking their members: a privacy-preserving cohort design in which a steward strips every name before analysis, caps how many asks any one person contributes, and withholds any count that subtraction could trace to a person
Build the comparison so that a member ranking cannot be produced from it. A steward holds the only list linking asks to people and hands analysts a file with a network label and an outcome, nothing more. No member contributes more than three asks a quarter, a network is reported only with at least eight active members and twenty asks, and any count that subtraction could trace back to a person is withheld. Every failed ask stays in. No network has been compared under this design.
Read → - How to compare personal links and partner resource pages: a path comparison design that counts the dated record each path leaves rather than the click, and keeps readers who find the page alone out of the comparison
Compare the two paths by the dated records they produce, never by clicks. Split the CEOs you were going to contact by coin flip: half get a one-to-one note carrying your personal link, half get the same note pointing to your resource page. Count, per CEO, introductions that reach a verified application credited to you and still open at the cutoff. Report readers who find the page on their own in a separate column, because you cannot count them fairly. No results exist yet.
Read → - How to compare referral candidates across different growth stages: a stage-normalized scorecard that measures every company against its own peak, not its peers
Compare candidates on one set of questions and change only the evidence you accept at each stage. A stage label says how a company is financed or how fast it is moving. The program asks other things: 50+ full-time employees at peak, years of records the company created, rights to license them, a CEO who wants the conversation and fit with a current program. Score every company against its own peak and its own record span, give growth rate no weight, and a contracting 30-year-old firm can be ranked fairly beside a fast-scaling six-year-old.
Read → - How to compare referral programs without comparing only headline caps: a ten-line terms-and-fit rubric that keeps the biggest number out of the score
Compare B2B referral programs on what your clients could actually trigger, not on the largest number on the page. A headline figure can be a ceiling, a flat amount or a floor; it rests on a calculation base, sits behind a payment trigger and an eligibility bar, and comes with a role that costs the firm time. Score each program's written terms and its fit with your client book separately, keep the headline out of the score, then decide whether to pilot, keep it small or decline.
Read → - How to compare specialist depth with broad partner recruitment: a 90-day two-arm test with matched hours, one niche split by coin flip, and verdict rules signed before it starts
Compare the two models by running both at once rather than debating them. For one 90-day attribution window, give a specialist arm (one person, one niche the firm already knows) and a breadth arm (a dozen briefed client leads across the book) the same hour budget, split the one niche both can work by coin flip, and count CEO permissions, verified applications, collisions and hours. Write down beforehand which result means broaden, stay narrow, stay small or decline, because no reward will exist by day 90 to settle the argument.
Read → - How to compare two outreach angles without changing everything: a hold-constant worksheet in which only the opening paragraph differs, CEOs are assigned by a list drawn before you write, and verified applications decide
Change one thing and freeze everything else. Write two truthful versions of the opening paragraph, each giving the CEO a different reason to talk, and keep the sender, the list rule, the subject line, the disclosure, the ask, the links, the timing and the follow-up word-for-word identical. Assign CEOs to the two versions from a list drawn before you write a line, then count verified applications per arm at a fixed cutoff. Opens, clicks and reply totals decide nothing. No partner or SourceX results for this comparison exist yet; this page is the design.
Read → - How to connect a regional business leader with SourceX: settle which of three roles the leader plays, then fill an authorized-contact introduction brief that names one company, its CEO and where its records sit, and keeps the leader's civic standing out of the ask
Start by agreeing which role the leader will play, because "connect them with SourceX" can mean three different things: they run a company and decide for it themselves, they know one CEO who might want the conversation, or they want to make introductions as a registered partner. Then write a short brief that names one company, its CEO and where its records sit, and keeps the leader's civic standing, any membership list and any fund business out of it. Each company's CEO decides.
Read → - How to consolidate an add-on's accounting system without losing its history
To consolidate accounting systems after an acquisition, map the add-on's chart of accounts to the platform's, load opening balances and open items at a month-end cutover, reconcile one parallel close, then archive the legacy file read-only. Before the archive step, export the full transaction, attachment and audit history so it can be screened for data licensing.
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